Train Diagnostic System

1
Train Diagnostic System

• MITRAC-TDS

2
Agenda

• Functionality of the TDS - Products
• Supported Vehicle Structures
• MITRAC-TDS Architecture
• data model
• component model
• communication model

3
Functionality of the TDS - Products

• Software products which support transmitting,
  storing and off-line evaluation of train and
  vehicle related diagnostic data.
• diagnostic related data are
• disturbance data with environment data
• event data
• condition data

4
Supported Hardware Topologies 1

• the following topologies are supported
• stand-alone vehicles
• trainsets (preferable connected by a TCN bus)
• open trains (preferable connected by a TCN bus)
• standalone subsystems

5
Supported Hardware Topologies 2
6
Supported Hardware Topologies 2a
7
Supported Hardware Topologies 2b
8
Supported Hardware Topologies 3
9
TDS Overview

• Corrective Maintenance
• Event Data
• Environment Data
• Fault Texts
• Preventive Maintenance
• Condition Data

10
MITRAC-TDS Architecture

• TDS Data Model (What kind of data types are
  handled by TDS?)
• TDS Component Model (What components does TDS
  consist of?)
• TDS Distribution Model (How can the TDS
  components be distributed on a train ?)
• TDS Communication Model (How do the TDS
  components communicate?)

11
TDS Data Model Event Data

• Disturbances/Protocol Events
• Timestamped at event source
• prioritized
• active/passive edge
• identification via
• Process ID / Event ID unique identification
  inside of MITRAC-TDS
• up to 4 Error Codes is handled like texts
• location geographical information, handled like
  texts
• subsystem logical "module" information, handled
  like texts

12
TDS Data Model Event Data
13
TDS Data Model Condition Data

• Used to store persistent application data over a
  long time
• Parameters
• Read-only (wheel-diameter)
• Read-write (adaptive control loop tuning)
• Counters
• predictive maintenance (door cycles)
• Condition Data is modified by Tools and
  Process-gt consistency is ensured by MITRAC-TDS

14
TDS Component Model
COM
15
TDS Communication Model
16
TDS Communication Model

• Communicating Entities rather than TCN Functions
• Multiple Channels on WTB / Economical use of
  Function Numbers
• UIC address mapping / Train Inauguration
• Version Handling

17
Process ClientEvent Data - state update
problem after powering of a vehicle the state
of the process and the ODBS could be
inconsistentexample replacement of devices
18
redundancy concept - Event Data
19
Process Client for IEC1131Condition Data - state
update
20
ODBS

• Stores Events and Condition Data
• supports 4 languages
• features a cache mechanism
• features the state update mechanism

21
ODBS - Overflow behaviour
different behaviour for two cases
1. all memory is used
2. one event is toggling all the time
22
Communication between VisuAppl and ODBS
23
Tool Client - used by MAVIS, MITRAC Remote

• DLL on WinNT
• Read Events with filter and sorting criteria
• Navigation in event database
• Operations on events (acknowledge)
• Read environment data description
• Upload events
• Read/write condition data
• Upload condition data

24
MAVIS
25
MAVIS
26
MAVIS
27
MAVIS
28
MITRAC TDS open interfaces
COM
29
End