Train GraphicClick on the map to explore geographics
 
I need help
FAQ
Emergency
About .
Travel & transport from BBC stories as at 19:55 20 Apr 2025
 
- RAF jets intercept Russian aircraft near Nato airspace
Read about the forum [here].
Register [here] - it's free.
What do I gain from registering? [here]
 10/05/25 - BRTA Westbury
10/05/25 - Model Railsay Show, Calne
13/05/25 - Melksham TUG / AGM
14/05/25 - West Wiltshire RUG

On this day
20th Apr (1789)
Opening of Sapperton Canal Tunnel

Train RunningCancelled
17:37 London Paddington to Swansea
17:48 Bristol Temple Meads to Weymouth
18:00 Cardiff Central to Taunton
18:15 Penzance to Plymouth
18:23 Swansea to London Paddington
19:43 Swindon to Westbury
20:00 Bristol Temple Meads to London Paddington
20:11 Weymouth to Bristol Temple Meads
20:17 Taunton to Bristol Temple Meads
21:09 Portsmouth Harbour to Bristol Temple Meads
22:45 London Paddington to Bristol Parkway
23:11 Cardiff Central to Bristol Temple Meads
21/04/25 08:03 Bristol Temple Meads to Weymouth
21/04/25 12:12 Salisbury to Bristol Temple Meads
Short Run
15:00 Cardiff Central to Penzance
16:18 Penzance to London Paddington
16:25 Cardiff Central to Portsmouth Harbour
17:09 Portsmouth Harbour to Cardiff Central
17:25 Cardiff Central to Portsmouth Harbour
18:09 Portsmouth Harbour to Cardiff Central
18:25 Cardiff Central to Portsmouth Harbour
19:00 Cardiff Central to Taunton
19:09 Portsmouth Harbour to Cardiff Central
19:25 Cardiff Central to Portsmouth Harbour
19:39 Bristol Temple Meads to Worcester Shrub Hill
20:00 Cardiff Central to Taunton
20:09 Portsmouth Harbour to Cardiff Central
20:30 Cardiff Central to Portsmouth Harbour
21:57 Worcester Shrub Hill to Bristol Temple Meads
22:30 Cardiff Central to Westbury
21/04/25 10:45 Bristol Temple Meads to Salisbury
21/04/25 11:29 Weymouth to Gloucester
21/04/25 16:31 Barnstaple to Axminster
Delayed
18:00 London Paddington to Penzance
20:30 London Paddington to Weston-Super-Mare
23:12 Bristol Temple Meads to Weston-Super-Mare
PollsThere are no open or recent polls
Abbreviation pageAcronymns and abbreviations
Stn ComparatorStation Comparator
Rail newsNews Now - live rail news feed
Site Style 1 2 3 4
Next departures • Bristol Temple MeadsBath SpaChippenhamSwindonDidcot ParkwayReadingLondon PaddingtonMelksham
Exeter St DavidsTauntonWestburyTrowbridgeBristol ParkwayCardiff CentralOxfordCheltenham SpaBirmingham New Street
April 20, 2025, 20:02:51 *
Welcome, Guest. Please login or register.

Login with username, password and session length
Forgotten your username or password? - get a reminder
Most recently liked subjects
[178] Fortuitous connections ... and an App which fails to offer the...
[105] RNLI station celebrates 10 years of saving lives - Portishead,...
[54] FOSS and FOSW validity - some quirks
[53] St Erth station - facilities, footbridge, improvements, incide...
[44] More than half of train travellers now use the railway for lei...
[41] Eyesight rules for motorists unsafe, says coroner
 
News: the Great Western Coffee Shop ... keeping you up to date with travel around the South West
 
   Home   Help Search Calendar Login Register  
Pages: 1 2 3 [4]
  Print  
Author Topic: Power outage strands trains  (Read 15572 times)
stuving
Transport Scholar
Hero Member
******
Posts: 7425


View Profile
« Reply #45 on: September 11, 2019, 22:39:23 »

The frequency disruption was for a relatively long duration, some put this down to the lack of inertia on the National Grid due to the loss of so much heavy rotating generating plant

There is a figure for "inertia" in those reports - 200GVAs, which I suspect is about the usual level at the moment. A useful number to tuck away in your toolbox (ideally with a proper definition). NG (Natural Gas) do have research going on on the use of batteries to provide "synthetic inertia", but I could see no mention of that in the reports. They do talk about campaign to reprogram small (embedded) generators to trip on a RoCoF (rate of change of frequency) of 1 Hz/s rather than the current value of 0.125 Hz/z. That would have kept a lot more of that generation on line. They say that will take three years, but some of the other evolutionary changes do seem to be going rather slowly.

On more point that I don't think was addressed directly was the cliff-edge effect of generators tripping due to RoCoF. The 1st July event (described in the main report) saw 1,000 Belgian MW lost, and the system coped - just.  The 9th August event was initially not much larger, but was just big enough that the reserve could not cope and, for want of enough power, the frequency fell. That led to enough extra generation disconnecting itself that the power shortfall suddenly became very large. Changing the RoCoF limit does address this, of course - eventually. 

Logged
stuving
Transport Scholar
Hero Member
******
Posts: 7425


View Profile
« Reply #46 on: September 11, 2019, 22:52:46 »

The Times has pointed out that the makers of the turbines farmed at Hornsea - who presumably supplied the control software - were Siemens Gamesa (59% owned by Siemens). They didn't labour the point, but ... Before anyone starts on about "German software", Gamesa's engineering centres are in Denmark, Spain, and India.

Incidentally, the Hornsea system is new to the grid - the three modules went live on 1/2/19, 30/4/19, and 15/7/19 - so a certain amount of optimisation based on observation is to be expected. In which case, why had they not picked up the tendency for oscillatory power flows (as in the example ten minutes before the outage) already?

« Last Edit: September 13, 2019, 10:42:05 by stuving » Logged
stuving
Transport Scholar
Hero Member
******
Posts: 7425


View Profile
« Reply #47 on: January 03, 2020, 18:22:32 »

You may have seen that Ofgem have issued their final report on this event, and announced some voluntary fines to be paid by the operators of the two generators that disconnected and one DNO (Distribution Network Operator) (UKPN, for reconnecting before being asked to). They seem uncertain whether they have a clear right to impose such fines, but a bit of arm-twisting of the emabarrassed has had the same effect.

Their analysis of what happened changes NGET's original story very little. However, some more poor performance has shown up in the operation of the low-frequency response process (LFDD). Not only did less than 5% of the load get shed, but two DNOs reconnected some load before NG (Natural Gas) told them to. LFDD disconnected some of the generators contracted to supply reserve power too, which was unintended. And the total of distributed generation lost in the event is now estimated at 1300-1500 MW (and the exact figure isn't knowable).

ORR» (Office of Rail and Road, formerly Office of Rail Regulation - about) have also published their report on ... well Siemens, mainly. They do document all the minor loss of power incidents too, none of which was serious.

The background at Siemens was much as reported earlier; a concern that some genuine failures produce a trip that could be reset and cause more damage led to some trip conditions being moved across to the list causing permanent lock-out. Low frequency was one of those, and should not have been. ORR's explantion is that, such events being rare, the risks of doing this were not considered - potentially the whole fleet could shut down out on the network and need a technician to attend.

Siemens admit this. A couple of quotes:
Quote
Most permanent lock-outs are triggered by events relating to the train itself, which are unlikely to arise simultaneously on multiple trains. Variations in the power supply frequency, however, affect many trains at the same time and result in the same response from all trains that have the same software. It appears therefore that the collective response of the Class 700 and 717 trains to the out-of-specification supply frequency was in accordance with the software design, but was not an explicit intention. Siemens accepts that the temporary reduction in frequency should not have been considered a situation that requires a permanent lock-out.

Quote
In an interim email to ORR, Siemens stated, “The original design of the class 700 is for the 4QCs to stop pulsing when the line frequency is out of range and automatically restart when the frequency come back in range. This does not require driver action. With the hysteresis implemented, the 4QCs lock when line frequency drops below 49Hz and they restart when the frequency rises above 49.5Hz.”
Logged
Do you have something you would like to add to this thread, or would you like to raise a new question at the Coffee Shop? Please [register] (it is free) if you have not done so before, or login (at the top of this page) if you already have an account - we would love to read what you have to say!

You can find out more about how this forum works [here] - that will link you to a copy of the forum agreement that you can read before you join, and tell you very much more about how we operate. We are an independent forum, provided and run by customers of Great Western Railway, for customers of Great Western Railway and we welcome railway professionals as members too, in either a personal or official capacity. Views expressed in posts are not necessarily the views of the operators of the forum.

As well as posting messages onto existing threads, and starting new subjects, members can communicate with each other through personal messages if they wish. And once members have made a certain number of posts, they will automatically be admitted to the "frequent posters club", where subjects not-for-public-domain are discussed; anything from the occasional rant to meetups we may be having ...

 
Pages: 1 2 3 [4]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
This forum is provided by customers of Great Western Railway (formerly First Great Western), and the views expressed are those of the individual posters concerned. Visit www.gwr.com for the official Great Western Railway website. Please contact the administrators of this site if you feel that the content provided by one of our posters contravenes our posting rules via admin@railcustomer.info. Full legal statement (here).

Jump to top of pageJump to Forum Home Page