Jump to content

Moving block

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Diannaa (talk | contribs) at 20:47, 27 November 2016 (remove copyright content copied from http://www.railway-technical.com/sigtxt3.shtml). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

In railway signalling, a moving block is a signalling block system where the blocks are in real time defined by computers as safe zones around each train. This requires both the need to know the exact location and speed of all trains at any given time, and continual communication between the central signalling system and the train's cab signalling system. Moving block allows trains to run closer together, while maintaining required safety margins, and thus increasing the line's overall capacity. Information about the location can be gathered through active and passive markers along the tracks, and train-borne tachometers and speedometers.

Theory

In railway signalling, a moving block is a signalling block system where the blocks are in real time defined by computers as safe zones around each train. This requires both the need to know the exact location and speed of all trains at any given time, and continual communication between the central signalling system and the train's cab signalling system. Communications Based Train Control (CBTC) or Transmission Based Signalling (TBS) is required to detect the exact basic information of trains and to transmit back the permitted operating speed to enable this flexibility.[1] Information about the location can be gathered through active and passive markers along the tracks, and train-borne tachometers and speedometers. Satellite-based systems cannot be used because they will not work in tunnels.

Location Updates

Another version of the moving block system would be the location computers on the trains itself. Each train determines its location in relation to all the other trains and sets its safe speeds using this data. Less wayside equipment is required compared to the off-train system but the amount of transmissions is much greater.

Implementation

Urban

Moving block is in use on several London Underground lines including the Victoria line, Jubilee line, parts of the Northern line as well as the Docklands Light Railway.[2][3] New York City Subway's L train, Singapore's North East Line, Circle Line, Downtown Line and Vancouver's Skytrain, also employ Moving Block signalling. It is also in operation in Hong Kong on the Westrail line and MOSrail Line.[2]

Inter-city

It was supposed to be the enabling technology on the modernisation of Britain's West Coast Main Line which would allow trains to run at a higher maximum speed (140 mph or 230 km/h), but the technology was deemed not mature enough, considering the large number of junctions on the line, and the plan was dropped.[4] It forms part of the European Rail Traffic Management System's level-3 specification for future installation in the European Train Control System, which will at level 3 feature moving blocks that allow trains to follow each other at exact braking distances.

Communications-based train control

Nowadays, with the current radio-based Communications-based train control (CBTC) systems using the moving block principle, to reduce headways and increase transport capacity, it is very much a reality.

References

  1. ^ "Moving Block — The Theory". ATP Beacons and Moving Block. Railway Technical Web Pages. 17 November 2016. Retrieved 17 November 2016.
  2. ^ a b "The Jubilee Line Upgrade" (PDF). London Underground Railway Society. 13 October 2009. Retrieved 22 November 2009.
  3. ^ "IRSE Newsletter (Hong Kong section)" (PDF). March–April 2008. Retrieved 26 November 2016.
  4. ^ "Background to the West Coast Modernisation Programme — The West Coast Route Modernisation began as a private sector programme" (PDF). The Modernisation of the West Coast Main Line. Comptroller and Auditor General, National Audit Office. 22 November 2006. p. 26. Archived from the original (PDF) on 22 November 2016. Retrieved 26 November 2016. {{cite web}}: |archive-date= / |archive-url= timestamp mismatch; 26 November 2016 suggested (help); Unknown parameter |deadurl= ignored (|url-status= suggested) (help)