CITADIS-EVOLUTION - ASYNCHRONOUS

TRACTION STARTER PACK

TROUBLE SHOOTING GUIDE

X X X

22/06/2010 D. CITELLI
Y.TROFFIGUER (Power Engineer) C. DELATTRE
(Technical Manager) M. MOUSTAKALY (Product Architect)
TRANSPORT - Information Solutions
(C&W)

DATE ESTABLISHED CHECKED APPROVED VILLEURBANNE

Confidentiality Category Control Category 11-13 Avenue de Bel Air

DISTRIBUTION Restricted Normal Controlled Not Controlled 69627 VILLEURBANNE Cedex
France

CONFIDENTIAL. Passing on and copying of this document, use and communication of its Lang. N.Shts
All rights reserved. content are not permitted without prior written authorization. TRV1306LB19948-2 en 21
ALSTOM
 -3-
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

REVISIONS
Release Author Date Page / Comments
Paragraph
1 Y. TROFFIGUER 14/06/2010 Creation
2 Y. TROFFIGUER 22/06/2010 Take into account comments from SESTO

"Daniele
CITELLI.doc"

REFERENCE SOLUTION : CITADIS-EVOLUTION - ASYNCHRONOUS

DOCUMENT REFERENCE : TRV1306LB19948

DISTRIBUTION LIST :
Reference Solution TCE Sub-System Manager : M. RIGOSELLI
Reference Solution TIS Sub-System Manager : Nathalie COMBE
Reference Solution Traction Control Work Package Owner : Y. TROFFIGUER
Reference Solution Quality Manager : V. BAILLE
Reference Solution Safety Assurance Manager : C. QUEHEN
Traction Support and Deployment Manager : JP.GALLAND

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 -4-
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

SUMMARY
1. INTRODUCTION................................................................................................................................................5
1.1. SCOPE ............................................................................................................................................................................ 5
1.2. USER PREREQUISITES..................................................................................................................................................... 5
1.3. REFERENCES................................................................................................................................................................... 5
1.4. TERMINOLNOGY AND ACRONYMS................................................................................................................................ 5

2. TROUBLE SHOOTING .......................................................................................................................................6

2.1. ROOT CAUSE SEARCH PROCESS ..................................................................................................................................... 6
2.1.1. list of material used to realize investigations ........................................................................................................................6
2.1.2. TCU rack F48 and COOLING FAN tray POSITRONIC interface connectors ...........................................................................7
2.1.3. EVR maintenance interfaces on TCU front face ....................................................................................................................7
2.1.4. 850-R-STD traction case interface connectors ......................................................................................................................8
2.1.5. Assemblies with resistances to test position/ speed sensor interfaces ......................................................................................8
2.1.6. List of TSP software variables used to realize investigations ...................................................................................................8
2.2. ESTABLISH REMOTE ETHERNET CONNECTION WITH TCU .............................................................................................. 9
2.3. DOWNLOAD TCU EVENTS.............................................................................................................................................. 9
2.4. PI : PRELIMINARY INVESTIGATION ............................................................................................................................. 11
2.5. DI : DETAILED INVESTIGATION ................................................................................................................................... 12
2.5.1. DI.1 : Detailed investigation on TCU address decoding......................................................................................................13
2.5.2. DI.2 : Detailed investigation on ALAX +/-15V power supply ...............................................................................................14
2.5.3. DI.3 : Detailed investigation on position sensor interfaces ..................................................................................................15
2.5.4. DI.4 : Detailed investigation on speed sensor interfaces .....................................................................................................16
2.5.5. DI.5 : Detailed investigation on internal/ external pulses inhibition......................................................................................17
2.5.6. DI.6 : Detailed investigation on MVB mediums ..................................................................................................................18
2.5.7. DI.7 : Detailed investigation on COOLING FAN command ................................................................................................20
2.5.8. DI.8 : Detailed investigation on COOLING FAN efficiency .................................................................................................21

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 5-
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

1. INTRODUCTION

1.1. SCOPE
This is the trouble shooting guide of the CITADIS-EVOLUTION - ASYNCHRONOUS reference solution.
The purpose is to help TCE team for first level investigations. This guide, based on TSP events recorded on
target, describes operations to execute before sending back LRU - if necessary- to VBN site.

1.2. USER PREREQUISITES

TCE team shall have a good knowledge of the AGATE 3 family hardware architectures and shall be
familiar with the use of Winscope and Train Tracer maintenance tools.

1.3. REFERENCES

[1] Product Technical manual TRV1306LB06319

[2] AGC3M-021 system interfaces description TRV1306LB00005-E4
[3] Traction system interfaces description AY00000036769-A
[4] TSPUM_AGATEDebugGuide TRV1306LB12635
[5] TSPUM_MonitoringGuide TRV1306LB12784
[6] TSPUM_UploadGuide.doc TRV1306LB12679

1.4. TERMINOLNOGY AND ACRONYMS

VBN « Villeurbanne » : ALSTOM Transport site in charge of the Reference Solution

TCE « Traction Control Equipment » : ALSTOM Transport team in charge of Application
Reference Solution Made up of AGC3M-021 hardware, TSP-MAS and PUMA piloting software
AGATE 3 « Advanced Generic Alstom Transport Equipment » generation 3
AC3MINI 3U21 size version of AGATE 3 family products
AGC3M-021 Configuration of AC3MINI to use with 850-R-STD/MAS/DLP(/A) traction case
T(B)CU « Traction (Braking) Control Unit » : current name for AGC3M-042 rack
PCE « Propulsion Control Electronics » : other possible name for AGC3M-042 rack
LRU « Line Removal Unit » : correspond to AGC3M-042 rack or FAN tray
TSP « Traction Starter Pack » is made up of QNX real time kernel, OPERA low layer
software, Traction Library and CB functions to realize the system monitoring
PUMA « Pilotage Unifié pour Moteur Asynchrone »
QNX Real time kernel, cots product
OPERA « Operating Platform for Embedded Real time Applications » : lower layer software
Traction Lib « Traction Library » : Set of CB components, libraries to build TSP
CB « Control Build » : design tool for real time applications
STR « Situation Technique de Référence » : STR 3.0= TSP V3.0.x, STR3.1= TSP V3.1.x

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 6-
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2. TROUBLE SHOOTING

2.1. ROOT CAUSE SEARCH PROCESS

To define if VBN LRU must be sent back for repair, TCE team shall follow the process below. VBN LRUs are the
AGC3M-021 rack and the Cooling Fan Tray, see document [1] for LRU detailed description. To realize
investigation, local access to Rack front face - on the vehicle roof - is mandatory.

Beginning of VBN LRUs

Trouble Shooting
Procedure

Establish remote Ethernet

connection with TCU

No
Connection succeed ?

Yes

Realize preliminary
Download TCU events
investigation (PI)

Action to do ?
INVESTIGATE See event list §2.3 of REMOVE TCU
TroubleShootingGuide

Realize detailed
investigation (DI)

REMOVE TCU
or
REMOVE COOLING FAN tray

Send back VBN LRU for

repair

ROOT CAUSE = OTHER

End of VBN LRUs

Trouble Shooting
Procedure

2.1.1. list of material used to realize investigations

• DC Voltmeter & Ohmmeter

• Tooling to remove CHC M6-16 screws (fastening of TCU rack or COOLING FAN tray)
• Ethernet cable to establish local Ethernet connection with TCU
• “Putty” open source TELNET client for Windows and Unix platforms
• USB key prepared with “copyDump” VBN software tool for TCU flash downloading
• USB key prepared with software release delivered by TCE for TCU flash uploading (see document [6])
• Assemblies with resistances to test speed sensor interfaces (see §2.1.5)
• Winscope .eqp file and Train Tracer .etr file to display TSP variables and events (see §2.1.6)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 7-
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.1.2. TCU rack F48 and COOLING FAN tray POSITRONIC interface connectors

The VBN LRU shall be removed to reach connectors (in independence per axle, FAN tray is placed below).

32

dbz

• 301 : ALNV +3,3V/ +5V power-supply module

• 302 & 320 : ALAX +/-15V power-supply module
• 304 : CPU board for ethernet remote connection interface
• 307 : MVB vehicle network interface
• 310 : CCA4-MZA board for inverters A & B current/voltage and speed sensors interfaces
• 312 & 313 : CCB4 board inverter A & B gate drives interfaces and external pulses inhibition
• 315 & 317 : EBT2 and EBT4 boards for LV inputs (TCU location decoding, internal pulses inhibition, …)
• 316 & 319 : SST3 and SST6 boards for LV static outputs (COOLING FAN tray power supply, …)
• 318 : SBT5 board for LV relay outputs

2.1.3. EVR maintenance interfaces on TCU front face

These interfaces are available on TCU front face (the 6 green led corresponds to power-supply status and must
be switched on, UR1 to UR6 state depend on TCU current mode and state).

SFL SRT
SBP SBS
UR1 UR2
UR3 UR4
UR5 UR6
SR1 SG2
NU 15V
24P 24S
UEN UES
UEP URN
SPD DAS
LI ACT
P6 P4 DSx

• P4 : local Ethernet link connector (factory IP address : 192.168.1.69 netmask 255.255.255.0)

• P6 : USB 1.1 connector to download software and execute flash Dump (copyDump)
• DSx : power-supply/ CPU status Leds

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 8-
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.1.4. 850-R-STD traction case interface connectors

2.1.5. Assemblies with resistances to test speed sensor interfaces

The resistances assembly below, to connect to X20 traction case interface connector, allows to simulate MAS1 or
MAS2 open collector speed sensor with 10V or 0V fixed voltage, see document [3] for use of sensors.

MASx SPx 15V Resistance :

+/-5%
0,5W
2,2k

MASx SPx IN

switch

MASx SPx GND

The resistances assembly below, to connect to X20 traction case interface connector, allows to simulate
AXLEADD/AXLEM current source speed sensor with 10mA fixed current, see document [3] for use of sensors.

Resistance :
AXLE 15V
+/-5%
0,5W
820

AXLE SPD

2.1.6. List of TSP software variables used to realize investigations

ControlBuild TSP variable name Expected values

rs_refsol Entrées : +mgt_wr_rs -> b_raz_fault_and_action 1 to 0 falling edge to go out lockout state
rs_refsol Sorties : +rs_rd_mgt -> b_Valid_State =0 if lockout state, =1 if operational state
rs_refsol Sorties : +rs_rd_mgt+abc_data ->FLT_syst_spd_fcap0 =1 if MAS1 SP1 interface failure
rs_refsol Sorties : +rs_rd_mgt+abc_data ->FLT_syst_spd_fcap1 =1 if MAS1 SP2 interface failure
rs_refsol Sorties : +rs_rd_mgt+abc_data ->FLT_syst_spd_fcap2 =1 if MAS2 SP1 interface failure
rs_refsol Sorties : +rs_rd_mgt+abc_data ->FLT_syst_spd_fcap3 =1 if MAS2 SP2 interface failure
rs_refsol Sorties : +rs_rd_mgt+abc_data ->FLT_syst_spd_fcap4 =1 if AXLEADD interface failure
rs_refsol Sorties : +rs_rd_mgt+abc_data ->FLT_syst_spd_fcap5 =1 if AXLEM interface failure
rs_refsol Sorties : +netxio_wr_rs+SST3_wr_rs -> LO_FAN 1 to force fans to run

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 9-
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.2. ESTABLISH REMOTE ETHERNET CONNECTION WITH TCU

The Ethernet remote connection IP address can be configured dynamically at power-up by DHCP server or fixed
in embedded Start_Ethernet_tcu.sh script, see document [4] for use of TCU communication links.

• STR3.0 : IP address fixed only

• STR3.1 : IP address fixed or IP address set by DHCP if server available

2.3. DOWNLOAD TCU EVENTS

The TSP contains ten event’s stacks, two are used by OPERA/ Libraries software, four are used for system
monitoring and four are reserved for application use. See document [5] for connection with Train Tracer.

Event Stack Mode Size (octet) Comment

System Wrap 10 000 Information

Systeme Wrap 1 024 Information
CB_alarm STR 3.0 : Fixed 50 000 STR 3.0 : information or error
STR 3.1 : Wrap STR 3.1 : information
CB_ventil STR 3.0 : Fixed 50 000 TCU or COOLING FAN Tray Error
STR 3.1 : Wrap
CB_system Wrap 50 000 TCU Error
CB_powerup Wrap 50 000 Information
CB_error Wrap 50 000 Reserved for application (contact TCE for detail)
CB_warning Wrap 50 000 Reserved for application (contact TCE for detail)
CB_message Wrap 50 000 Reserved for application (contact TCE for detail)
CB_lock Wrap 50 000 Reserved for application (contact TCE for detail)

Recorded events don’t necessarily traduce an error, it can also represent an information or a message. For
example, CB_powerup stack is used to record, at each power-up, FLT_syst_power_up TCU profile :

• Tcu_id : TCU code in range [1..8] corresponding to TCU location in the train
• Read_status : 0 if EEPROM read access Ok
• Write_status : 0 if EEPROM write access Ok
• Serial_number : TCU hardware serial number
• Power_up_counter : the counter increments at each power-up
• Min_temp : minimum TCU temperature (°C)
• Max_temp : maximum TCU temperature (°C)
• Avg_temp : average TCU temperature (°C)
• Running_time_h : total running time (hours)
• Service_running_time_h : total running time at non zero speed (hours)
• Travelled_distance_km : total travelled distance (km)

To be useful the recorded events have to be downloaded on PC using ALSTOM maintenance tool. TSP system
monitoring contains 35 major events (see list below), 60% leads to TCU removal without any additional
investigation (time saving for TCE team).

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 10 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

TSP fault name Event stack Action to do

FLT_syst_tcu_id STR3.0 : CB_alarm INVESTIGATE

STR3.1 : CB_system
FLT_syst_ps_15_delay CB_system INVESTIGATE
FLT_syst_ps_24P_delay CB_system INVESTIGATE
FLT_syst_sysfail_delay CB_system REMOVE TCU
FLT_syst_topo_netx_eio_delay CB_system REMOVE TCU
FLT_syst_watchdog_dsp1 CB_system REMOVE TCU
FLT_syst_watchdog_dsp2 CB_system REMOVE TCU
FLT_syst_eby2_val_delay CB_system REMOVE TCU
FLT_syst_eby4_val_delay CB_system REMOVE TCU
FLT_syst_sbt_val_delay CB_system REMOVE TCU
FLT_syst_ErrorChangeState CB_system REMOVE TCU
FLT_syst_mut_ctrl CB_system REMOVE TCU
FLT_syst_fpga_dsp1_ctr CB_system REMOVE TCU
FLT_syst_fpga_dsp2_ctr CB_system REMOVE TCU
FLT_syst_spd_fcap0 or FLT_syst_spd_fcap1 STR3.0 : CB_alarm INVESTIGATE
(Dual Chanel speed sensor) STR3.1 : CB_system
FLT_syst_spd_fcap2 or FLT_syst_spd_fcap3 STR3.0 : CB_alarm INVESTIGATE
(Dual Chanel speed sensor) STR3.1 : CB_system
FLT_syst_spd_fcap4 STR3.0 : CB_alarm INVESTIGATE
STR3.1 : CB_system
FLT_syst_spd_fcap5 STR3.0 : CB_alarm INVESTIGATE
STR3.1 : CB_system
FLT_syst_int_inh_coherency CB_system REMOVE TCU
FLT_syst_ext_inh_coherency CB_system REMOVE TCU
FLT_syst_int_inh_no_tripping CB_system REMOVE TCU
FLT_syst_ext_inh_no_tripping CB_system INVESTIGATE
FLT_syst_L_NOT_INV_OFF_no_tripping CB_system INVESTIGATE
FLT_syst_crt4_tst CB_system REMOVE TCU
FLT_syst_mvb_medA_delay CB_system INVESTIGATE
FLT_syst_mvb_medB_delay CB_system INVESTIGATE
FLT_syst_eep_init CB_system REMOVE TCU
FLT_syst_eeprom_wr CB_system REMOVE TCU
FLT_syst_flash_init STR3.1 only : CB_system REMOVE TCU
FLT_syst_flash_wr STR3.1 only : CB_system REMOVE TCU
FLT_syst_tcu_fan_ctrl CB_ventil INVESTIGATE
FLT_syst_tcu_fan_cool CB_ventil INVESTIGATE
FLT_syst_tcu_over_temp CB_ventil REMOVE TCU
Other FLT_syst_xxx TSP events CB_alarm Send recorded events to VBN including
FLT_syst_powerup (CB_powerup stack)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 11 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.4. PI : PRELIMINARY INVESTIGATION

Preliminary investigation shall be done if remote Ethernet connection with TCU failed. Detailed investigation shall
also be done depending on events downloaded using local Ethernet connection.

Investigation consist in discrimination between TCU ALNV/ CPU boards failure and DHCP server or F48
connector pin or wiring failure.
Beginning of Preliminary
investigation (PI)

Observe EVR leds status

No
All leds switched Off ?

Yes
Switch Off battery
Observe EVR
Remove TCU Rack
SFL & SRT leds status Connector pins to test :
Switch On battery
D8/B8/Z8 : +Bat
Check « 301 » F48
D6/B6/Z6 : -Bat
connector with DC
Voltmeter

No No
2 leds switched On ? Presence +/-Bat ?

Yes Yes
Establish local Ethernet Execute USB copyDump
Switch Off battery
connection with TCU
Replug TCU Rack
Reload TCU software
Switch On battery
Download TCU events
Observe EVR
Observe EVR leds status
Check if FLT_syst_tcu_id SFL & SRT leds status

No No No
FLT_syst_tcu_id 2 leds switched On ? All leds switched off ?
Event ?

Yes Yes Yes

ROOT CAUSE = OTHER

ROOT CAUSE = OTHER ROOT CAUSE = OTHER
(Check F48 connector
(Check DHCP server) (Send back USB dump)
and wiring)

Realize DI.1
REMOVE TCU REMOVE TCU
Detailed Investigation

End of Preliminary
investigation (PI)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 12 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.5. DI : DETAILED INVESTIGATION

Interferences may exist between applicative faults managed by TCE software and TCU system faults managed by
VBN TSP software. Analysis will be in priority based on TSP faults, which can lead to applicative faults. TSP system
monitoring coverage is not 100%, it’s why detailed investigation should be necessary to discriminate between
AGC3M-021 interfaces failure or wiring/ sensor failure.

Beginning of Detailed
investigation (DI)

Execute pmode.elf
cmde with TELNET

No
Current mode = 1 ?

Yes
Realize DI.x detailed
Execute USB copyDump
investigation depending
on events recorded
Reload TCU software

Execute pmode.elf
cmde with TELNET
DI.1 FLT_syst_tcu_id ?

FLT_syst_ps_15_delay ?
DI.2 No
FLT_syst_ps_24P_delay ? Current mode = 1 ?

FLT_syst_spd_fcap0/1 ?
DI.3
FLT_syst_spd_fcap2/3 ? Yes

FLT_syst_spd_fcap4 ?
DI.4
FLT_syst_spd_fcap5 ?

FLT_syst_ext_inh_no_tripping ?
DI.5
FLT_syst_L_NOT_INV_OFF_no_tripping ?

FLT_syst_mvb_medA_delay ?
DI.6
FLT_syst_mvb_medA_delay ?

DI.7 FLT_syst_tcu_fan_ctrl ?

DI.8 FLT_syst_tcu_fan_cool ?

REMOVE TCU
or
ROOT CAUSE = OTHER
REMOVE COOLING FAN Tray REMOVE TCU
(Send back USB dump)
or
ROOT CAUSE = OTHER

End of Detailed
investigation (DI)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 13 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.5.1. DI.1 : Detailed investigation on TCU address decoding

FLT_syst_tcu_id event indicates that TCU address built using L_LOCPCE2, L_LOCPCE1, L_LOC3, L_LOC2,
L_LOC1 LV inputs is invalid and, in consequence, no MVB address and no remote Ethernet IP address are set.

Investigation consist in discrimination between TCU EBT2 board failure and F48 connector pin or wiring failure.

L_LOCPCE2 L_LOCPCE1 L_LOC3 L_LOC2 L_LOC1 Comment

0 0 0/1 0/1 0/1 Invalid code : FLT_syst_tcu_id event
0/1 0/1 0 0 0 Invalid code : FLT_syst_tcu_id event
0/1 0/1 0 1 1 Invalid code : FLT_syst_tcu_id event
0/1 0/1 1 0 1 Invalid code : FLT_syst_tcu_id event
0/1 0/1 1 1 0 Invalid code : FLT_syst_tcu_id event

Beginning of
FLT_syst_tcu_id
investigation (DI.1)

Connector pins to test :

Switch Off battery
Remove TCU Rack Z12 : L_LOCPCE2
Switch On battery D10 : L_LOCPCE1
D16 : L_LOC3
Check « 315 » F48 Z18 : L_LOC2
connector with DC D20 : L_LOC1
Voltmeter
B6 : -Bat

Yes
Invalid code ?

No
Switch Off battery
Replug TCU Rack
Switch On battery

Download TCU events

Check if new FLT_syst_tcu_id

New No
FLT_syst_tcu_id
Event ?

Yes
ROOT CAUSE = OTHER
REMOVE TCU (Check F48 connector
and wiring)

End of FLT_syst_tcu_id
investigation (DI.1)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 14 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.5.2. DI.2 : Detailed investigation on ALAX +/-15V power supply

FLT_syst_ps_15_delay event indicates that first +/-15V ALAX power-supply module (302) is out of range.
FLT_syst_ps_24P_delay event indicates that second +/-15V ALAX power-supply module (320) is out of range.

Investigation consist in discrimination between TCU rack ALAX power-supply failure and F48 connector pin or
wiring failure or +/-15V external equipments powered by TCU.

Beginning of Beginning of
FLT_syst_ps_15_delay FLT_syst_ps_24P_delay
investigation (DI.2.1) investigation (DI.2.2) Connector pins
to test :

Switch Off battery Connector pins Switch Off battery D8/B8/Z8 : +Bat
Remove TCU Rack to test : Remove TCU Rack D6/B6/Z6 : -Bat
Switch On battery Switch On battery
D8/B8/Z8 : +Bat 302 : Z24, Z22
D6/B6/Z6 : -Bat 310 : Z32, Z30
Check « 302 » F48 Check « 320 » F48
Z28, Z24
connector with DC 302 : Z32, Z30, connector with DC Z22, Z20
Voltmeter and « 302, 310, Z24, Z22 Voltmeter and Z18, Z14
312, 313, 316 » F48 310 : Z12, Z10, Z8, Z6, Z4, Z2 « 302, 310 » F48 D32, D30
connectors with 312, 313 : Z8, Z2 connectors with D28, D24
Ohmmeter 316 : B18, B14 Ohmmeter D22, D20
D18, D14
302 : B18 : Méchanical ground/ 0V
302 : B18 : Mechanical ground/ 0V
Presence +/-Bat ? No Presence +/-Bat ? No
No +/-15V short-circuit ? No +/-15V short-circuit ?

Yes Yes
Switch Off battery Switch Off battery
Replug TCU Rack Replug TCU Rack
Switch On battery Switch On battery

Check EVR 15V & UES leds status Check EVR 24P & UEP leds status
Yes
Download TCU events Download TCU events

Check if new FLT_syst_ps_15_delay Check if new FLT_syst_ps_24P_delay

Leds switched off ? No Leds switched off ? No

or new or new
FLT_syst_ps_15_delay FLT_syst_ps_24P_delay
Event ? Event ?

Yes Yes
ROOT CAUSE = OTHER ROOT CAUSE = OTHER
(Check F48 connector (Check F48 connector
REMOVE TCU and wiring and external REMOVE TCU and wiring and external
equipments) equipments)

End of End of
FLT_syst_ps_15_delay FLT_syst_ps_24P_delay
investigation (DI.2.1) investigation (DI.2.2)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 15 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.5.3. DI.3 : Detailed investigation on open collector speed sensor interfaces

FLT_syst_spd_fcap0 or FLT_syst_spd_fcap1 event indicates a lost of the first motorized axle speed sensor signal
(dual channels type : MAS1 SP1, MAS1 SP2).
FLT_syst_spd_fcap2 or FLT_syst_spd_fcap3 event indicates a lost of the second motorized axle speed sensor signal
(dual channels type : MAS2 SP1, MAS2 SP2, only in independence per bogie configuration).

Investigation consist in discrimination between TCU rack CCA4-MZA board failure and F48 connector pin or
wiring or sensor failure.

Beginning of Beginning of
FLT_syst_spd_fcap0/1 FLT_syst_spd_fcap2/3
investigation (DI.3.1) investigation (DI.3.2)

STR3.1 only : STR3.1 only :

Observe event contexte of Observe event contexte of
FLT_syst_spd_fcap0/1 FLT_syst_spd_fcap2/3

STR3.1 only Yes STR3.1 only Yes

Crt4_atst_fcap0/1=1 ? Crt4_atst_fcap2/3=1 ?

No No
Switch Off battery Switch Off battery
To realize with switch opened (10V test)

To realize with switch opened (10V test)

Remove X20 connector Remove X20 connector
Add resistance assembly Add resistance assembly
Switch On battery Switch On battery
and closed (OV test)

and closed (OV test)

Force to 1 and after to 0 Force to 1 and after to 0
B_raz_fault_and_action if B_raz_fault_and_action if
B_Valid_State = 0 B_Valid_State = 0

Observe the variable Observe the variable

FLT_sys_spd_fcap0/1 FLT_sys_spd_fcap2/3

No No
FLT_syst_spd_fcap0/1=1 ? FLT_syst_spd_fcap2/3=1 ?

Yes Yes
Switch Off battery Connector pins Switch Off battery Connector pins
Remove TCU rack to test : MAS1 Remove TCU rack to test : MAS2

Check TCU « 310 » F48 Z12/ 1, Z10/ 25 Check TCU « 310 » F48 Z8/ 13, Z6/ 37
to X20 connector wiring B12/ 2, B10/ 26 to X20 connector wiring B8/ 14, B6/ 38
continuity with Ohmmeter D12/ 3, D10/ 27 continuity with Ohmmeter D8/ 15, D6/ 39

Yes Yes
Wiring continuity ? Wiring continuity ?

No No

ROOT CAUSE = OTHER ROOT CAUSE = OTHER

(Check F48 connector REMOVE TCU (Check F48 connector REMOVE TCU
and wiring and sensor) and wiring and sensor)

End of End of
FLT_syst_spd_fcap0/1 FLT_syst_spd_fcap2/3
investigation (DI.3.1) investigation (DI.3.2)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 16 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.5.4. DI.4 : Detailed investigation on current source speed sensor interfaces

FLT_syst_spd_fcap4 event indicates a lost of trailer axle speed sensor current source (AXLEADD1 plus AXLEADD2
in independence per axle configuration)
FLT_syst_spd_fcap5 event indicates a lost of adjacent motorized axle speed sensor current source (AXLEM1 and
AXLEM2 in independence per axle configuration).

Investigation consist in discrimination between TCU rack CCA4-MZA board failure and F48 connector pin or
wiring or sensor failure.

Beginning of Beginning of
FLT_syst_spd_fcap4 FLT_syst_spd_fcap5
investigation (DI.4.1) investigation (DI.4.2)

STR3.1 only : STR3.1 only :

Observe event contexte of Observe event contexte of
FLT_syst_spd_fcap4 FLT_syst_spd_fcap5

STR3.1 only Yes STR3.1 only Yes

Crt4_atst_fcap4=1 ? Crt4_atst_fcap5=1 ?

No No
Switch Off battery Switch Off battery
Remove X20 connector Remove X20 connector
Add resistance assembly Add resistance assembly
Switch On battery Switch On battery

Force to 1 and after to 0 Force to 1 and after to 0

B_raz_fault_and_action if B_raz_fault_and_action if
B_Valid_State = 0 B_Valid_State = 0

Observe the variable Observe the variable

FLT_sys_spd_fcap4 FLT_sys_spd_fcap5

No No
FLT_syst_spd_fcap4=1 ? FLT_syst_spd_fcap5=1 ?

Yes Yes
Switch Off battery Connector pins Switch Off battery Connector pins
Remove TCU rack to test : Remove TCU rack to test :
AXLEADD1 or AXLEAM1 or
AXLEADD2 AXLEAM2
Check TCU « 310 » F48 Check TCU « 310 » F48
to X20 connector wiring Z4/ 49, B4/ 50 or to X20 connector wiring Z2/ 7, B2/ 8 or
continuity with Ohmmeter Z4/ 30, B4/ 31 continuity with Ohmmeter Z2/ 19, B2/ 20

Yes Yes
Wiring continuity ? Wiring continuity ?

No No

ROOT CAUSE = OTHER ROOT CAUSE = OTHER

(Check F48 connector REMOVE TCU (Check F48 connector REMOVE TCU
and wiring and sensor) and wiring and sensor)

End of End of
FLT_syst_spd_fcap4 FLT_syst_spd_fcap5
investigation (DI.4.1) investigation (DI.4.2)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 17 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.5.5. DI.5 : Detailed investigation on internal/ external pulses inhibition

FLT_syst_ext_inh_no_tripping event indicates that L_NOT_INV_OFF=0V and L_A_INHIB =+15V or L_B_INHIB =

+15V (only in independence per bogie configuration) during a delay greater than 150ms.
FLT_syst_L_NOT_INV_OFF_no_tripping event indicates that _A_INHIB=0V or L_B_INHIB=0V (only in
independence per bogie configuration) and L_NOT_INV_OFF=+Bat during a delay greater than 150ms.

Investigation consist in discrimination between TCU rack EBT2 or CCB4 boards failure and F48 connector pin or
wiring or K8 relay failure.

Beginning of FLT_syst_x_no_tripping L_NOT_INV_OFF : sent to EBT board (315)

investigation (DI.5)
from CCB4 board (312) from CCB4 board (313)

Switch Off battery Connector pins to test : +15V 0V +15V 0V

Remove TCU Rack

315 : D28 : L_NOT_INV_OFF K8 relay
Switch On battery
(non energized position)

Ensure INV_ENABLE= -Bat from 312 : D4-Z2 : open-circuit L_x_INHIB : sent to first
L_x_INHIB : sent to second
D4-B2 : close-circuit CCB4 board (313), in
train line on X21-05 connector CCB4 board (312)
independence per bogie

Check « 315 » F48 connector If independence per bogie

with DC Voltmeter and « 312, -Bat
313 » F48 connectors with 313 : D4-Z2 : open-circuit
Ohmmeter D4-B2 : close-circuit

315 : B6 : -Bat

No
L_NOT_INV_OFF : -Bat ?
Open/close circuit Ok ?
Connector pins to test :
Yes
315 : D28 : L_NOT_INV_OFF
Ensure INV_ENABLE=+Bat from
train line on X21-05 312 : D4-Z2 : close-circuit
D4-B2 : open-circuit
Check « 315 » F48 connector
with DC Voltmeter and « 312, If independence per bogie
313 » F48 connector with
Ohmmeter 313 : D4-Z2 : close-circuit
D4-B2 : open-circuit

315 : B6 : -Bat
No
L_NOT_INV_OFF : +Bat ?
Open/close circuit Ok ?

Yes
Switch Off battery
Replug TCU Rack
Switch On battery

Force to 1 and after to 0

B_raz_fault_and_action if B_Valid_State = 0

Download TCU events, Check if new

FLT_syst_ext_inh_no_tripping or
FLT_syst_L_NOT_INV_OFF_no_tripping

No
New event ?

Yes ROOT CAUSE = OTHER

(Check F48 connector
REMOVE TCU and wiring and K8 relay)

End of FLT_syst_x_no_tripping investigation

(DI.5)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 18 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.5.6. DI.6 : Detailed investigation on MVB mediums

FLT_syst_mvb_medA_delay or FLT_syst_mvb_medB_delay event indicates lost of MVB communication.

FLT_syst_mvb_medA_delay investigation procedure :

===================================================
In this case several causes are possible :
1/ The local Duagon board is faulty for decoding information on Medium A.
2/ The event is only a consequence of a global medium problem among the mvb bus
(it can be either a short-circuit somewhere along the bus between A+ and A- wire or either a cut-off line
of A+ or A- or both).

To confirm the event is local to the equipment, it is necessary to get a global vision of the default :

Preliminary check consist in checking if events FLT_syst_mvb_medA of the Stack alarm are present. If so and in important
quantity with several date & time, it can be an indication the problem is present from a while.
______________________________________________________________________________________________________________

* Step 1 : Check if the same event is seen on other TCU (by downloading the event of all others TCUs)

==> If result is other TCU has this event, then it indicates the problem is at MVB bus level and NOT
local to the equipment.
______________________________________________________________________________________________________________

* Step 2 : Connect to the MPU (central calculator of TCMS Sub-system) of the train (through Ethernet front face) :

Launch command "obsterm.elf"

Then, launche command "mvb d s"

The sequence must appear this way (see example below) :

-------------------------------------------------------
login: root
#
#
# obsterm.elf
Demarrage obsterm

OPERA>mvb d s

MVB DEVICES STATUS :

14 devices on the local node:
*----------------------------------------------------------------------------*
* Address | Status *
* | sp ba gw md cs0 cs1 cs2 cs3 lat rld ssd sdd erd frc dnr ser *
*----------------------------------------------------------------------------*
* device 0x001 | 0 1 0 1 0 0 1 1 1 0 0 0 0 0 0 0 *
* device 0x010 | 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 *
* device 0x011 | 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 *
* device 0x012 | 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 *
* device 0x013 | 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 *
* device 0x014 | 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 *
* device 0x015 | 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 *
* device 0x016 | 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 *
* device 0x017 | 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 *
* device 0x018 | 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 *
* device 0x01a | 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 *
* device 0x092 | 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 *
* device 0x0a1 | 0 0 0 1 0 0 0 0 0 1 1 0 0 0 0 0 *
* device 0x0a2 | 0 0 0 1 0 0 0 0 0 1 1 0 0 0 0 0 *
*----------------------------------------------------------------------------*

Each line represents the status of each mvb node.

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 19 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

device 0x... indicates the mvb address of each device.

Determine the address of the local TCU by checking its mvb address on the TCMS documentation.

Then focus on the two column lat & rld.

The signification is a follow :

RLD (Redundant Line Disturbed) : means one the 2 lines is faulty.
LAT (Line A trusted) : Indicates the Line A is the one trusted (sued to decode the data).
So, interpretation is as follow :

For each node :

If RLD equals 0, then LAT is not significant.

Means no medium faulty whatever the LAT value.
If RLD equals 1, then look at LAT value.
If LAT equals 1 : Then Medium B is faulty.
If LAT equals 0 : Then Medium A is faulty.

Check every equipment following this procedure and check if most equipment provide the same information :
If most of equipment provide the information of Medium A faulty (LAT=0 & RLD=1) :

This indicates the problem is at MVB bus level and NOT local to the equipment.
______________________________________________________________________________________________________________

************* CONCLUSION CRITERIA *************

If Step 1 OR Step 2 results indicate the problem is NOT local to the Equipment :

****************************************
!! ROOT CAUSE = OTHER (Check wiring)!!
****************************************

Investigation at mvb bus level are necessary.

Check TCMS procedure.

On the contrary If Step 1 indicates only the local TCU has the type of event AND
Step 2 shows only one line (corresponding to the MVB address of the local TCU) with the LAT = 0 and RLD = 1

********************
!! REMOVE TCU !!
********************

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 20 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.5.7. DI.7 : Detailed investigation on COOLING FAN command

FLT_syst_tcu_fan_ctrl event indicates that, after switch on the FAN, the static output voltage is lower than 13V or
the static output current is lower than 16,5mA or greater than 670mA.

Investigation consist in discrimination between TCU rack SST3 board failure or COOLING FAN tray failure and
F48 connector pin or wiring failure.

Beginning of
FLT_syst_tcu_fan_ctrl
investigation (DI.7)

Remove Cooling Fan tray

Connector pins to test :
Force LO_FAN variable
Between 14 (+) and 05 (-)
Check POSITRONIC
Between 13 (+) and 04 (-)
connector with DC
only if independence per axle
Voltmeter

Yes
Presence +15V ?

No
Connector pins to test :
Switch Off battery
Remove TCU rack
Between « 316 » F48 D14 to
POSITRONIC 14 or 13 (+)
Check TCU to Cooling
Fan tray wiring continuity
Between « 316 » F48 Z14 to
with Ohmmeter
POSITRONIC 05 or 04 (-)

Yes
Wiring continuity ?

No

REMOVE ROOT CAUSE = OTHER

REMOVE TCU
COOLING FAN tray (Check wiring)

End of
FLT_syst_tcu_fan_ctrl
investigation (DI.7)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010
 21 -
CONFIDENTIAL. All rights reserved. ALSTOM. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.

2.5.8. DI.8 : Detailed investigation on COOLING FAN efficiency

FLT_syst_tcu_fan_cool event indicates that, after switch on the FAN, the CPU temperature don’t decrease at least
2°C in 3mn delay.

Investigation consist in COOLING FAN tray control, indeed, the failure of one of the two Fans is not detected by
FLT_syst_tcu_fan_ctrl under-current monitoring.

Beginning of
FLT_syst_tcu_fan_cool
investigation (DI.8)

1U-A2 COOLING FAN tray in

independence per bogie :
Remove Cooling Fan tray
TCU rack controls two Fans
LO_FAN1 : +15V : pin 14
Use extension lead of
0V : pin 05
cabling to connect
Cooling Fan tray to
1U-S4 COOLING FAN tray in
POSITRONIC connector
independence per axle :
Each TCU rack controls two
Switch On battery
of the four Fans
Force LO_FAN variable
LO_FAN1 : +15V : pin 14
0V : pin 05
Observe the two Fans
LO_FAN2 : +15V : pin 13
0V : pin 04

Yes
Two fan are running ?

No
ROOT CAUSE = OTHER
REMOVE
(Ask VBN for thermal
COOLING FAN tray
expertise)

End of
FLT_syst_tcu_fan_cool
investigation (DI.8)

CITADIS-EVOLUTION - ASYNCHRONOUS TRV1306LB19948-2

TROUBLE SHOOTING GUIDE 22/06/2010