EBICAB

EBICAB is a trademark registered by Bombardier for the equipment on board a train used as a part of an Automatic Train Control system. EBICAB was originally derived from Ericsson's SLR system in Sweden. Most trains in Sweden and Norway use a similar on-board system, Ansaldo L10000 (more known as ATC-2) from Bombardier's competitor Ansaldo STS (now Hitachi Rail STS).[1] ATC-2 was also developed in Sweden.[2]

EBICAB balise in the Mediterranean Corridor

These on-board systems use pairs of balises mounted on the sleepers. The pairs of balises distinguish signals in one direction from the other direction with semicontinuous speed supervision, using a wayside to train punctual transmission using wayside transponders.[3]

Versions

EBICAB comes in two versions, EBICAB 700 in Sweden, Norway, Portugal and Bulgaria and EBICAB 900 installed in the spanish Mediterranean Corridor (vmax= 220 km/h), and in Finland (Finnish: Junakulunvalvonta) under the name ATP-VR/RHK. In Portugal it is known as Convel (the contraction of Controlo de Velocidade, meaning Speed Control).

The EBICAB 900 system uses wayside transponders (also called balises) with signal encoders or series communications with electronic lookup table, and on-board equipment on the train. The transmission of data occurs between the passive wayside transponders (between 2 and 4 per signal) and the antenna installed under the train, which powers the transponders when it passes over the transponder. The coupling between the transponder and the on-board antenna is inductive.

In comparison with ASFA, a system which transmits only a maximum amount of data per frequency, EBICAB uses electronic lookup table, the amount of data transmitted is much larger.

Adif/Renfe, in Spain, sometimes use the term ATP to refer to EBICAB 900, which is the first system on its network to provide Automatic Train Protection.

Main Characteristics

  • Transponders operating in the ISM band at 27 MHz amplitude modulated for the clock pulses and impulse frequency of 50 kHz.
  • Transmission of data to trains at 4,5 MHz at 50 kbit/s with 32 bit packets encoding 12 bits of information (EBICAB 700) or 255 bit packets encoding 180 bits of information (EBICAB 900), including the necessary synchronisation bits.
  • The signals are linked (concatenated), but the signs, for example, for warnings and speed, are not necessarily linked (concatenated); it is acceptable to have 50% of the transponders linked to be safe against failures.
  • The driver may input characteristics such as train identification, length, speed type, maximum speed, braking characteristics, and train pressure.
  • The driver receives visual indications such as speed limit, target speed, overspeed, ASFA Alarm, braking reset, Permission to Pass, alarm signals, braking warning, red or alphanumeric indications.

Supervision

  • Line velocity, as a function of line capacity and the vehicle's performance capabilities in situations of overspeed or the imposition of lower velocity for some types of trains.
  • Multiple objectives, including signaling information without wayside signals.
  • The system can enforce permanent, temporary and emergency speed restrictions by using unlinked (concatenated) transponders.
  • Stop Point.
  • Dynamic braking profile.
  • Status of the level crossing and landslide detectors.
  • Maneuvers.
  • Protection against wheel wear.
  • Slip/Slide compensation.
  • Authorization to pass a signal at Stop.

Warnings

  • Acoustic warning at excess of 5 km/h, service braking at excess of 10 km/h and emergency brake application at excess of 15 km/h
  • The operator may release service braking when the speed is below one of the speed limits (Normally below the speed limit + 10 km/h in Portugal).

EBICAB 700

The most important difference with EBICAB 900, is that EBICAB 700 can only transmit packets with 12 useful bits for a total of 32bits and allows up to 5 transponders per signal.

gollark: That should also do it, but it'd also be a 1-line fix on my end.
gollark: I'll use socket.receive instead of pulling websocket message events.
gollark: Wait, I think I can make it work fine otherwise...
gollark: Or just make it be slightly evil and store the socket globally.
gollark: I should add a skynet.disconnect function or something, but whatever.

See also

References

This article incorporates information from a Ferropedia article, published in Castilian under a Creative Commons Compartir-Igual 3.0 license.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.