Train communication network

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
Website www.traincom.org

The train communication network (TCN) is a hierarchical combination of two fieldbus systems for digital operation of trains. It consists of the multifunction vehicle bus (MVB) inside each coach and the wire train bus (WTB) to connect the MVB parts with the train control system. The TCN components have been standardized in IEC 61375.

Usage

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

Wire train bus

The wire train bus interconnect can be performed by an electric twisted pair cable or by an optical glass fiber. The standard connection is done with the UIC connector using a shielded twisted pair cable. The physical level is using digital RS-485 transmission at 1 Mbit/s data rate. The encoding uses a Manchester II code and a HDLC frame protocol. There is a maximum of 32 nodes on a maximum length of 860 meters (without repeaters). With a maximum of 1024-bit payload per telegram, the system allows response times of typically 100 µs.[1]

The wire train bus shares some similarities with the earlier 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 WorldFIP was based on the earlier work on 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.[2] (The FIP standard effort is the French analogue of the German Profibus standard effort that ran both in the late 1980s / early 1990s where eventually the Profibus components did prevail the market down the road). 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.

Multifunction vehicle bus

The multifunction vehicle bus interconnect can be performed by an electric twisted-pair cable or by an optical glass fiber. 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 connector classes for OGF, EMD and ESD media. Using optical glass fibres (OGF) a line distance of 2000 meter is possible, using shielded twisted pair with RS 485 (EMD, electrical medium distance) the allowable length reaches 200 meter and with a simple backplane wiring (ESD, electrical short distance without galvanic isolation) the cable may be up to 20 meter in length. The plugs and sockets are the same as used by Profibus (with two 9-pin Sub-D sockets per electrical device).[3]

The media sources are usually connected by repeaters (signal generators) being joined on a central star coupler – the repeater is also responsible for the transition from one medium to another. 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 with reduced throughput) while most system parts communicate with a response time of a typical 10µs.[3]

Alternate vehicle buses

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).[3] 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 is derived from Profibus.

The MVB standard was introduced to replace the multitude of field buses in the train equipment. This was noted to be not the case for several reasons. While the CANopen and Profinet are controlled by international manufacturer associations targeting wide application range this is not the case for MVB which allows no options and is used only in railways and in some electrical substations. As a result, MVB modules are more expensive than for instance CANopen components. This is not due to the communication technology itself: most devices implement the MVB protocol machine in a small area of an FPGA which is today anyhow present, and the most costly 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.

This has led to the observation that – despite the advantages of the MVB field bus – many train vehicle buses are still built from CANopen and Profibus components. 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 behaviorin respect to the application. Despite the similarities no rail-manufacturer has considered FlexRay, the reason may be the availability of CAN and Ethernet based Nodes, along with the number of parameters that need to be set for a FlexRay Communication-Controller.

Further reading

  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. ↑ WorldFIP
  3. 1 2 3 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).
  4. ↑ "Informations – und Steuerungstechnik auf Schienenfahrzeugen – Bussysteme im Zug". elektronik industrie 8/9 2008 (in German). InnoTrans Special: Bahnelektronik. 2008-09-14.
This article is issued from Wikipedia - version of the 4/5/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.