Train communication network

From Wikipedia, the free encyclopedia
  (Redirected from Train Communication Network)
Jump to: navigation, search
Train communication network (TCN)
Protocol Information
Type of Network Device bus, process control
Physical Media Twisted pair, glass fiber
Network Topology Bus
Device Addressing hardware/software
Governing Body TrainCom

The train communication network (TCN) is a hierarchical combination of two fieldbus for data transmission within trains. It consists of the Multifunction Vehicle Bus (MVB) inside each vehicle and of the Wire Train Bus (WTB) to connect the different vehicles. The TCN components have been standardized in IEC 61375.


The TCN is used in most of the modern train control systems usually connecting the vehicles with an 18-pin UIC 558.

Wire train bus[edit]

The wire train bus has been designed for international passenger trains with variable composition, consisting of up to 22 vehicles.

The medium consists of a duplicated shielded twisted pair cable, which runs in the UIC cables between the vehicles.

The connector between the vehicles is the 18-pole UIC connector. Since connectors are exposed and can oxidize, a current pulse is applied at connection establishment to evaporate the oxide layer, called fritting. The standard connector for the WTB nodes is a DIN 9 pin connector.

The physical level usesRS-485 levels at 1 Mbit/s data rate. The encoding uses a Manchester II code and a HDLC frame protocol with proper voltage balancing to avoid DC components in the galvanic isolation transformers. The Manchester decoder uses a phase/quadrature demodulation (not RS485, that operates with zero-crossings) which allows to span 750 m under worst-case conditions, especially when only the two extremity vehicles are equipped, as is the case with multiple traction for freight trains. No repeaters are foreseen since vehicles in between can have discharged batteries.

A unique property of the WTB is the train inauguration (Zugtaufe) in which the newly connected vehicles receive an address in sequence and can identify the vehicle side (called port and starboard like in the marine) so that doors open on the correct side. Up to 32 addresses can be dynamically allocated. When two train compositions join, the addresses are reallocated to form a new composition of vehicles with a sequential address. Vehicles without WTB node ("conduction vehicles") are not counted. The frames have a maximum payload of 1024 bits.

The WTB operates cyclically to provide deterministic operation, with a period of 25 ms, used mainly for the traction control. The WTB also supports sporadic data transmission for diagnostics. The content of the periodic and sporadic frames is governed by the UIC 556 standard. [1] Since frame size is limited, a version of TCP with reduced overhead was used for message segmenting and reassembly, that at the same time allows to cope with changes in composition, called RTP (Real-Time Protocol).

History: the WTB was derived from the German DIN bus developed by ABB Henschel (now Bombardier). It benefited from the phase/quadrature decoding provided by Italy and from an improved train inauguration provided by Switzerland, based on the experience with the FSK multiple traction bus of ABB Secheron, Geneva used in the SBB freight trains. The physical layer of MVB shows similarities with the WorldFIP field bus (EN 50170 part 4) - its "voltage mode" did use 1 Mbit/s and a maximum of 32 stations on the bus with a maximum length of 750 meters, the use of FIP transceivers was studied early in the TCN evaluation, but the Phase/Quadrature decoding was used instead.

Multifunction vehicle bus[edit]

The multifunction vehicle bus connects individual nodes within a vehicle or in a closed train set. Unlike the WTB there is no requirement on a single international connector standard for the vehicle bus inside a coach, locomotive or train set – instead there are three predefined media and connector classes.

  1. OGF (Optical glass fibres) uses 240 μm fibers for a line distance of 2000 m,
  2. EMD (Electrical Medium Distance) uses shielded twisted pair with RS 485 transmitters and transformers for galvanical isolation), for a length reaching 200 m and
  3. ESD (Electrical Short Distance) uses a simple backplane wiring without galvanic isolation, for which case the cable may be up to 20 m in length.

The plugs and sockets are the same as used by Profibus (with two 9-pin Sub-D sockets per electrical device).[2]

For OGF, the media sources are connected by repeaters (signal generators) being joined on a central star coupler  A repeater is also used for the transition from one medium to another.

There is no inauguration, the addresses are statically allocated. The number of addressable devices depends on the configuration of the vehicle bus – there may be up to 4095 simple sensors/actuators (Class I) and up to 255 programmable stations (Class 2, with configuration slots). The physical level is using transmissions at a 1.5 Mbit/s data rate using Manchester II encoding. The maximum distance is determined on the restriction of a maximum allowed reply delay of 42.7 µs (where for longer distances a second mode is used that allows up to 83.4 μs with reduced throughput, in case MVB is used for switchgear on the track side) while most system parts communicate with a response time of a typical 10µs.[2]


MVB was derived from the P215 bus developped by Brown Boveri Cie, Switzerland (now ABB), incorporating the publisher/subscriber principle from early field busses (DATRAS). Back in 1984, IEC TC57 defined the requirement specifications for busses to be used in electrical substation in collaboration with IEC SC65C. MVB presents many similarities with the FIP field bus (originally "Flux d'Information vers le Processus", relabeled as Factory Instrumentation Protocol and later Flux Information Protocol) that was developed in the French NFC 46602 standard series.,[3] since both stemmed from the same IEC TC57 specifications. This explains why MVB and FIP have similar operation (cyclic and event-driven), only the arbitration method in case of multiple access differs, as MVB used a binary bisection mode relying of collision detection while FIP piggy-backed a "look-at-me" bit over periodic data. Efforts to merge FIP and MVB failed at the stubbornness of the two parties. MVB, Profibus and WorldFIP were proposed as a substation bus in IEC TC57, but to avoid parallel solutions, IEC TC57 decided that none will be used and favored Ethernet as a common denominator.

The MVB frames are not compatible with IEC 61158-2 fieldbus frames as it omits most of the preamble synchronization (which is not required if zero-crossing detection is possible).[2] The paradox situation is that the IEC 61158 field bus and MVB physical layer were developed by the same persons in IEC TC57. The difference came from the fieldbus physical layer which assumes a phase-locked loop to decode the Manchester data, requiring a preamble to synthonize the decoder, while MVB operated principally with optical fibres where this method is useless, MVB's decoding relies on zero-crossing detectors and Manchester pattern recognition.

However most the modern development and test equipment can equally communicate WTB/MVB frames as well as Profibus frames on the line as the telegram structure similar to Profibus.

The WorldFIP connectors found usage in train equipment in France and North America (by Bombardier) until a joined effort on a common UIC train bus was started (with Siemens and other industry partners) that led to the WTB/MVB standard in late 1999.

Alternate vehicle buses[edit]

The MVB standard was introduced to replace the multitude of field buses in the train equipment. Despite the advantages of the MVB field bus, many vehicle buses are still built from CANopen, WorldFIP (in France), LonWorks (in the USA) and Profibus components. While the WorldFIP, CANopen, Lonworks and Profinet are controlled by international manufacturer associations targeting a wide range of application, MVB was tailored to the rolling stock application, with the goal of plug-compatibility, and therefore allows no options. This was intentional as the fight between the field busses raged in the 1990's and the decision of the IEC that any of the eight field busses was a standard did not help plug-compatibility.

MVB modules are more expensive than for instance CANopen or LonWorks components. This is not due to the communication technology: most devices implement the MVB protocol machine in a small area of an FPGA which is today anyhow present, and the costliest component remains the connector. But railways certification is costly and not always needed for uncritical applications such as comfort and passenger information. When total cost of ownership is considered, the cost of the hardware elements can easily be outweighed by additional engineering costs in the railways market with its small series.

In the USA, the IEEE RTVISC evaluated both MVB and LON as vehicle and train bus. The IEEE finally decided to standardize both in IEEE 1374, with a clear separation of tasks: MVB for critical operation such as traction control and signalling in the driver's cab, and LON for uncritical and slow data transfer, but low-cost connections such as passenger displays and diagnostics. This separation is not always observed.

Additionally more and more components are added to rail vehicles that need far more bandwidth than any field bus can provide (e.g. for video surveillance), so switched Ethernet IEEE 802.3 with 100 Mbit/s is being introduced into train sets (according to the EN 50155 profile). Still all the alternate vehicle buses are connected to the Wire Train Bus.[4]

MVB is similar to FlexRay, both have the "process data", which is called "static segment" in FlexRay, and "message data", which is the "dynamic segment" and are driven by a fixed TDMA scheme. Running FlexRay with 2.5 Mbit, an RS485 physical layer and only one "coldstarter" would lead to a very similar behavior in respect to the application. Despite the similarities, no rail-manufacturer has considered FlexRay, since they valuated a common solution higher than a multitude of better busses. Conversely, in 1999, the automotive industry evaluated MVB (in an extended 24 Mbit/s version), but dropped it because of the costs, which should be unreasonably low for the mass-market of millions of vehicles.

Further reading[edit]

External links[edit]

  1. ^ Prof. Dr. Hubert Kirrmann (1999-01-20). "Train Communication Network IEC 61375 - 4 Wire Train Bus" (powerpoint). Ecole Polytechnique Fédérale de Lausanne (EPFL). 
  2. ^ a b c Prof. Dr. Hubert Kirrmann (1999-01-20). "Train Communication Network IEC 61375 - 3 Multifunction Vehicle Bus" (powerpoint). Ecole Polytechnique Fédérale de Lausanne (EPFL). 
  3. ^ WorldFIP
  4. ^ "Informations – und Steuerungstechnik auf Schienenfahrzeugen – Bussysteme im Zug". elektronik industrie 8/9 2008 (in German). InnoTrans Special: Bahnelektronik. 2008-09-14.