PD CLC TR 50542 — Railway Applications Driver’s Cab Train Display Controller (TDC) Technical Report Series

Railway Applications — Driver’s Cab Train Display Controller (TDC)

🚆 PD CLC TR 50542 is the British Standards Institution (BSI) Published Document implementing the European Committee for Electrotechnical Standardization (CENELEC) technical report CLC/TR 50542, addressing the railway driver’s cab train display controller (TDC). Prepared by the UK technical committee GEL/9 “Railway Electrotechnical Applications” and classified under ICS 35.240.60 (IT applications in transport), 45.020 (railway engineering in general), and 93.100 (railway construction), the series provides a unified specification for the TDC’s overall architecture and its functional interfaces (FIS) with display systems and other train systems — a key basis for interoperability and standardisation of driver display systems.

💡 The train display controller is a critical human-machine interface through which the driver obtains train status, signalling, and operating information. Unifying its architecture and functional interfaces ensures interoperability between display systems and train systems from different manufacturers and vehicle types, reducing integration and maintenance costs.

1. Series Structure and Overall Framework 📌

The PD CLC TR 50542 series consists of 3 parts, corresponding to general architecture, display-system functional interface, and other train-system functional interface. Part 1 was published in 2014, while Parts 2 and 3 were published in 2016.

PartYearTitleCore Content
PD CLC/TR 50542-12014General architectureSpecifies the overall TDC architecture, function definitions, and data flows with connected systems
PD CLC/TR 50542-22016Display systems FISSpecifies the functional interface between the TDC and driver’s cab display systems
PD CLC/TR 50542-32016Other train systems FISSpecifies the functional interface between the TDC and other train systems (e.g., signalling, traction, monitoring)
⚠️ This series is a CENELEC Technical Report (TR) of reference nature, not a mandatory standard. Always reference the current BSI version and consider its linkage with EN and ERTMS/ETCS standards.

2. General Architecture: Part 1 Framework 🏗️

Part 1 specifies the general architecture of the TDC, laying the foundation for the whole series:

  • Function definitions: define the functional scope of the TDC, including organisation of display data, transfer of control commands, and state management.
  • Data flows: define the direction, content, and semantics of bidirectional data flows between the TDC and connected systems.
  • Connection relationships: describe the connection topology and communication means between the TDC and display systems and other train systems.
  • General principles: specify the terms, symbols, abbreviations, and design principles common across parts.

Part 1 provides a unified architecture and terminology basis for the Part 2 and Part 3 functional interface specifications, ensuring consistency among the parts.

3. Display System Interface: Part 2 Functional Specification 🖥️

Part 2 specifies the functional interface (FIS) between the TDC and driver’s cab display systems, covering the interaction of display information and operating commands:

Interface ElementDescription
Display informationSpecifies the data content, format, and refresh requirements provided by the TDC to the display system
Operational functionsSpecifies the driver’s operations on the TDC through the display system, such as display switching and menu operations
Display buttonsDefines the operating buttons on the display and their function mapping
State and alarmsSpecifies the status, alarm, and fault information presented by the display system

Part 2 ensures consistency of information exchange between the driver’s cab display system and the TDC, supporting replacement and interoperability of display systems from different manufacturers.

4. Other Train System Interface: Part 3 Functional Specification 🔌

Part 3 specifies the functional interface (FIS) between the TDC and other train systems (e.g., signalling, traction, monitoring, diagnostic systems), covering state and command interaction:

Interface ElementDescription
State informationSpecifies the state data the TDC obtains from other systems (e.g., speed, signalling, equipment status)
Command transferSpecifies the control commands and operation requests the TDC sends to other systems
Alarms and diagnosticsSpecifies the acquisition and display of fault, alarm, and diagnostic information
Data synchronisationSpecifies data synchronisation and consistency requirements between the TDC and other systems
✅ The three parts form a complete specification for the TDC: Part 1 sets the architecture, Part 2 the display interface, and Part 3 the train-system interface, together ensuring interoperability and standardisation of the driver’s cab display controller.

5. Engineering Practice and Application Notes 🛠️

  • 🔍 Vehicle integration: integrate display systems and train systems from different manufacturers per the Part 1 architecture and Part 2/3 interface specifications, reducing customisation costs.
  • 🔧 Display design: design the display interface and operating logic per Part 2 to ensure clear, ergonomic driver operation.
  • 📊 System integration testing: verify and validate information exchange between the TDC and each system per the functional interfaces.
  • 📋 Alignment with ERTMS/ETCS: coordinate the TDC interface specification with ERTMS/ETCS driver display requirements (e.g., DMI) to ensure European railway interoperability.

6. Frequently Asked Questions ❓

❓ Q: What is a TDC and what does it do?
A: The TDC is the driver’s cab train display controller that organises and displays train status, signalling, and operating information, and passes control commands to other systems — a key interface for driver information.
❓ Q: Why standardise the TDC functional interface?
A: A unified interface enables display systems and train systems from different manufacturers and vehicle types to interoperate, avoiding duplicated development and reducing integration, maintenance, and upgrade costs.
❓ Q: How do Parts 2 and 3 differ?
A: Part 2 specifies the interface between the TDC and display systems (focused on display and operation); Part 3 specifies the interface between the TDC and other train systems (focused on state and command).
🔍 Q: Why is this series published as a Technical Report (TR)?
A: Because it is a CENELEC technical report providing architecture and interface guidance rather than mandatory requirements, for reference in railway vehicle design and integration.
🔒
正在加载下载地址,请稍候 10 秒

Leave a Reply

Your email address will not be published. Required fields are marked *