Fam CC206 - 2

08-3003
Incident Message
FAM Incident Intent
FAM Incident Detection
FAM Incident Clearing
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Console Selector Switch Bad

The purpose of this incident is to annunciate that the feedback indicating the
position of the Console Selector Switch is Bad.
This incident shall only log on Dual Console Locomotive and when the Console
Selector Switch feedback is invalid.
Clears on Power up or when the Console Selector Switch has a valid reading of
either Primary or Secondary Console
1. Console Selector Switch
2. BCA
3. Wiring
Check Console Transition Screen on the Locomotive Display to Ensure Console
Selector Switch position does not read â€˜Invalidâ€™.
If it is invalid:
1. Check the Console Selector Switch. Look for mechanical or electrical failures
with the switch. troubleshoot wiring to the switch and terminals.
2. Troubleshoot wiring, terminals and connectors back to BCA
3. Replace BCA (17FE102/198) DI Card.
4. Replace the Console Selector Switch
3. No Dynamic Brake Or Motoring
52. No Self Load
54. No Battery Jog
30 Second
08-3004
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Secondary Console Gen Field May Be ON When Primary Is Active

The purpose of this incident is to inform the operator Gen Field Breaker May be ON
on the Inactive (Secondary) Console.
This incident logs on a dual console locomotive when the Primary Console is the
Active Console and the Gen Field Breaker circuit is detected to be ON on the
Secondary console.
This incident shall clear on Power up or when the Gen Field Breaker circuit is
detected to be OFF on the Secondary Console.
1. Secondary Console Gen Field Breaker
2. BCA
3. Wiring
1. Verify that the Gen Field Breaker is not ON at Secondary Console. If it is ON,
turn it off
3. Troubleshoot Secondary Console Gen Field Circuit Breaker
5. Replac BCA(17FE102/198) DI Card.
92. Secondary Console Gen Field Breaker May Be ON
52. No Self Load
54. No Battery Jog
30 Second
08-3005
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Primary Console Gen Field May Be ON When Secondary Is Active

The purpose of this incident is to inform the operator Gen Field Breaker May be ON
on the Inactive (Primary) Console.
This incident logs on a dual console locomotive when the Secondary Console is the
Active Console and the Gen Field Breaker circuit is detected to be ON on the
Primary console.
This incident shall clear on Power up or when the Gen Field Breaker circuit is
detected to be OFF on the Primary Console.
1. Primary Console Gen Field Breaker
2. BCA
3. Wiring
1. Verify that the Gen Field Breaker is not ON at Primary Console. If it is ON,
turn it OFF.
3. Troubleshoot Primary Console Gen Field Circuit Breaker
5. Replace BCA(17FE102/198) DI Card.
93. Primary Console Gen Field Breaker May Be ON
52. No Self Load
54. No Battery Jog
30 Second
08-3006
Incident Message
Direction Detected on Secondary Console When Primary Is Active
Author: Naresh K Approval: Rakesh Jain
GE Proprietary and Confidential
Page 79 of 332
Tuesday, September 24, 2013
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
BCCA Fault Analysis Manual
84A220120FH Rev: D
The purpose of this incident is to annunciate that there is intent to operate the
locomotive from the Inactive (Secondary) Console.
This incident is logged on a Dual Console locomotive if the Primary Console is
Active and the system detects that the Reverser handle on the Secondary console is
in Forward or Reverse.
This incident shall clear on Power up or when - Reverser handle on the Secondary
console is detected to be in its Centered position.
1. Secondary Console Master Controller
2. BCA
3. Wiring
1. Verify that the Secondary Console Reverser handle is centered. If it is not
Centered, Center the Reverser handle.
3. Troubleshoot wiring, terminals and connectors back toBCA
4. Troubleshoot the Secondary Master Controller. Check for mechanical and wiring
and fastener issues.
5. ReplaceBCA (17FE102/198) DI Card.
52. No Self Load
54. No Battery Jog
30 Second
08-3007
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Direction Detected on Primary Console When Secondary Is Active

The purpose of this incident is to annunciate that there is intent to operate the
locomotive from the Inactive (Primary) Console.
This incident is logged on a Dual Console locomotive if the Secondary Console is
Active and the system detects that the Reverser handle on the Primary console is
in Forward or Reverse.
This incident shall clear on Power up or when - Reverser handle on the Primary
console is detected to be in its Centered position.
1. Primary Console Master Controller
2.BCA
3. Wiring
1. Verify that the Primary Console Reverser handle is centered. If it is not
Centered, Center the Reverser handle.
4. Troubleshoot the Primary Master Controller. Check for mechanical and wiring and
fastener issues.
52. No Self Load
54. No Battery Jog
30 Second
08-3008
Incident Message
FAM Incident Intent
FAM Probable Cause
Possible Bad Reverser Handle Not Centered Feedback

The purpose of this incident is to annunciate that the Reverser Handle Not Centered
feedback is bad.
This incident shall log on Dual Console locomotives if the Reverser Handle Not
Centered feeback of the reverser circuit to be Stuck High or stuck Low.
This incident shall clear on Power up or when the Reverser Handle Not Centered
feedback is detected to be reading properly.
1. BCA
2. Master Controller
3. Wiring
FAM Fault Isolation
Operator Message
Alarm Bell

2. Troubleshoot the Master Controller's. Check for mechanical and wiring and
fastener issues.
3Replace BCA (17FE102/198) DI Card.
52. No Self Load
54. No Battery Jog
30 Second
08-3009
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Possible Bad Primary Console GF ON Feedback

The purpose of this incident is to detect Bad Primary Console GF Feedback.
This incident shall log on Dual Console locomotives if there is suspicion that the
Primary Console GF Feedback is Bad.
This incident shall clear if the Primary Console GF Feedback appears good.
1. BCA
2. Primary Console Gen Field Circuit Breaker
3. Wiring
fastener issues.
52. No Self Load
54. No Battery Jog
30 Second
08-3010
Incident Message
FAM Incident Intent
FAM Probable Cause
Possible Bad Secondary Console GF ON Feedback

The purpose of this incident is to detect Bad Secondary Console GF Feedback.
This incident shall log on Dual Console locomotives if there is suspicion that the
Secondary Console GF Feedback is Bad.
This incident shall clear if the Secondary Console GF Feedback appears good.
1. BCA
2. Secondary Console Gen Field Circuit Breaker
3. Wiring
FAM Fault Isolation
Operator Message
Alarm Bell
1. Troubleshoot Secondary Console Gen Field Circuit Breaker

fastener issues.
52. No Self Load
54. No Battery Jog
30 Second
08-3011
Incident Message
FAM Incident Intent
Possible Bad Primary Console Not Centered Feedback

The purpose of this incident is to annunciate that the Primary Console Not Centered
feedback is bad.
Page 80 of 332

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
84A220120FH Rev: D
This incident shall log on Dual Console locomotives if the Primary Console Not
This incident shall clear when there is indication that the Primary Console Not
Centered Feedback is detected to be reading properly.
1. BCA
3. Wiring
fastener issues.
52. No Self Load
54. No Battery Jog
30 Second
08-3012
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Possible Bad Secondary Console Not Centered Feedback

The purpose of this incident is to annunciate that the Secondary Console Not
Centered feedback is bad.
This incident shall log on Dual Console locomotives if the Secondary Console Not
This incident shall clear when there is indication that the Secondary Console Not
Centered Feedback is detected to be reading properly.
1.BCA
3 Wiring
fastener issues.
52. No Self Load
54. No Battery Jog
30 Second
08-3013
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Dual Console Digital Feedbacks Quality Bad

The purpose of this incident is to annunciate that the Quality of the Dual Console
digital inputs is bad.
This incident shall log on Dual Console locomotives if the Quality of any of the
Dual Console digital inputs are detected to be bad.
This incident shall clear when there is indication that the Quality is Good for all
the Dual Console digital inputs.
1.BCA
2. Wiring
1) Check wiring
2) Replace BCA DI Cards
3) Replace BCA Panel
52. No Self Load
54. No Battery Jog
30 Second
08-3014
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Console Transition Restriction - Throttles Must Be In Idle, COB ON And PCS Cleared
The purpose of this incident is to ensure the locomotive is restricted during a
console transition and remains restriction until all Operator Setup conditions are
proper. This incident will remain active through a Power Cycle.
This Incident shall log on Dual Console locomotives when a Dual Console Transition
Occurs.
The incindent shall clear only when the Throttles are in IDLE, Control CB is On and
PCS is cleared.
1. Operator Setup Issue
3. PCR
4. COB
5. Wiring
1. Place all Throttle Handle in IDLE, Turn COB ON and Clear PCS with Air Brake EBV.
2. Troubleshoot Master Controller. Inspect Cam's K, G, H, J, U, E for issues.
Inspect wiring, terminals, connectors for issues.
3 Inspect Control Circuit Breake Switch. Inspect wiring to COB.
4. Inspect PCR Relay. Inspect PCR Coil. Inspect PCR wiring. Inspect PCR wiring
feedback to BCA
52. No Self Load
54. No Battery Jog
08-3015
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Possible Bad Dual Console GF ON Feedback or Cam F Feedback

The purpose of this incident is to restrict locomotive operation if there is a
prolem with the Console GF _ON Feedbacks or Cam F. These inputs are critical in
protecting the locomotive from inappropriate operation from the inactive Console on
Dual Console locomotives
This incident shall log when a Bad Console GF ON Feedback (Stuck Low) or CAM F
(Stuck High)
The incident shall clear when Cam F goes Low.
1 BCA
3. Wiring
2Troubleshoot Secondary Console Gen Field Circuit Breaker
3. Trouble Cam F Circuit
fastener issues.
6. Replace CIO DI Card.
.
52. No Self Load
54. No Battery Jog
30 Second
09-0000
Incident Message
FAM Incident Intent
Software: RM Error Spawning Rm Task

Detecting Software Abnormality
System Detected a Low Level Software Abnormality
There is No clearing Conditon for this Incident.

Page 81 of 332
FAM Probable Cause

FAM Fault Isolation
Operator Message
84A220120FH Rev: D
Software Abnormality
No Isolation Required..
36. Ready
09-0001
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Error Killing Rm Task

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Add Called With Null Pointer

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Add With Bad Incd Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Chg Incd With Bad Incd Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Upd Auto Dec With Bad Incd Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Chg Incd Called With Null Pointer

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Chg Incd Finds Incd Obj Has Wrong Id
36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Chg Incd Finds Bad Restr Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Software: RM Get Restr Called With Bad Restr Id

09-0002
09-0003
09-0004
09-0005
09-0006
09-0007
09-0008
09-0009

Page 82 of 332
Operator Message
84A220120FH Rev: D
36. Ready
09-0010
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Get Incd Called With Bad Incd Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Clear Restr Called With Bad Restr Id

No Isolation Required
36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Clear Finds Incd Obj With Wrong Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Clear Finds Null Ptr Or Wrong Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Clear Finds Bad Restr Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Enable Called With Bad Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Finds Bad Restr Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Disable Called With Bad Id

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: RM Set Restr Called With Bad Restr Id

36. Ready
09-0011
09-0012
09-0013
09-0014
09-0015
09-0016
09-0017
09-0018
09-0020
Page 83 of 332
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: MMI Task Can't Link To Sm

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: MMI Task Can't Map To Sm

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: MMI Task Active Incd List Is Full

36. Ready
84A220120FH Rev: D
09-0021
09-0022
09-0025
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Vehicle Ctrl Active Restr Table Is Full

There is No clearing Conditon for this Incident
36. Ready
09-0026
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Vehicle Ctrl Active Restr Table Can't Cut A Restr

36. Ready
09-0030
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Open Incd Log File

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Open Incd Log Status File

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Make Incd Log File Max Size

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Seek Failed On Save To Incd Log

36. Ready
09-0031
09-0032
09-0034
Page 84 of 332
84A220120FH Rev: D
09-0035
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Write Failed On Incd Log

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Get Incd Rec Req Out Of Range

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Seek Failed On Get From Incd Log

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Get Failed On Incd Log

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Get Path For Incd Dump File

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Open Snap Log File

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Open Snap Log Status File

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Make Snap Log File Max Size

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Seek Failed On Save To Snap Log

36. Ready
09-0036
09-0037
09-0038
09-0039
09-0040
09-0041
09-0042
09-0044
09-0045
Incident Message
Software: Write Failed On Snap Log
Page 85 of 332
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Get Snap Rec Req Out Of Range

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Seek Failed On Get From Snap Log

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Get Failed On Snap Log

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Get Path For Snap Dump File

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Open Diag Log File

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Open Diag Log Status File

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Make Diag Log File Max Size

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Seek Failed On Save To Diag Log

36. Ready
Incident Message
FAM Incident Intent
Software: Write Failed On Diag Log

84A220120FH Rev: D
09-0046
09-0047
09-0048
09-0049
09-0050
09-0051
09-0052
09-0054
09-0055

Page 86 of 332

FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D

36. Ready
09-0056
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Get Diag Rec Req Out Of Range

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Seek Failed On Get From Diag Log

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Get Failed On Diag Log

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Get Path For Diag Dump File

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Create RM Shared Memory

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Link To RM Shared Memory

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Truncate RM Shared Memory

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Map To RM Shared Memory

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
Software: Can't Create Snap Shared Memory

09-0057
09-0058
09-0059
09-0060
09-0061
09-0062
09-0063
09-0064

Page 87 of 332
FAM Fault Isolation

Operator Message
84A220120FH Rev: D
36. Ready
09-0065
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Link To Snap Shared Memory

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Truncate Snap Shared Memory

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Can't Map To Snap Shared Memory

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Diag Logger Can't Open Display Shared Memory

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Diag Logger Can't Map To Display Shared Memory

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Critical Incidents Active

Inform Operator that incidents that may be preventing damage are currently set.
Critical Incidents are Active
Clear the Critical Incident after verifying that no damage will occur.
Check other Active Incidents
Check other Active Incidents
36. Ready
09-0066
09-0067
09-0068
09-0069
09-0082
09-0100
Incident Message
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: GPS Information Out Of Range

This incident is for informational purposes only.
36. Ready
10-0210
Incident Message
FAM Incident Intent
FAM Probable Cause
Panel Software Version Does Not Match The Distribution

This purpose of this incident is to inform the maintainer that there is a software
mismatch.
This incident occurs when the actual version of any panel software on the Loco
Config screen does not match the expected version of panel software.
This incident is cleared when there are no mismatches shown on the Loco Config
screen.
1. The panel software version is incorrect on one or more panels.
2. One or more panels is not communicating.
FAM Fault Isolation
1) Go to the Loco Config screen.

2) If there are "***" for any panel, correct communication issues using Network
Trouble Shooting Guide (drawing No. 84A200750NW).
3) If there are no "***", press the Reload All key once it appears to reload
mismatching panel's software.
Operator Message
36. Ready
10-0220
Incident Message
FAM Incident Intent
Operating System Software Versions Do Not Match Across SDIS/CIO/DTC on Operating

System
The purpose of this incident is to inform the maintainer that the software versions
across the computing nodes do not match.
Page 88 of 332

FAM Probable Cause
84A220120FH Rev: D
This incident occurs when the software between the computing nodes do not match.
This incident is cleared when all computing nodes have the same version of
software.
1. Not all computing nodes have the same version of software.

2. Software loading.
FAM Fault Isolation
1) Copy software from the computing node with the correct version of software to
the other computing nodes or download correct version of software to the
computing node with the incorrect version using a hard card.
2) For more information on software loading, see Software Loading Procedures
(drawing no. 84A212193).
Operator Message
36. Ready
10-0221
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operating System Software Versions Do Not Match Across SDIS/DTC on Application

The purpose of this incident is to inform the maintainer that the software versions
across the computing nodes do not match.
This incident occurs when the software between the computing nodes do not match.
This incident is cleared when all computing nodes have the same version of
software.
1. Not all computing nodes have the same version of software.
2. Software loading.
1) Copy software from the computing node with the correct version of software to
the other computing nodes or download correct version of software to the
computing node with the incorrect version using a hard card.
Operator Message
36. Ready
10-0222
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
The Options Files Do Not Match Across the Computing Nodes

The purpose of this incident is to inform the maintainer that Options Files across
the the computing nodes do not match.
This incident occurs when the Option Files do not match across all computing nodes.
This incident is cleared when the Option Files match on all computing nodes.
1. The Option file is corrupt.
2. The Option file did not properly copy during the software loading process to all
computing nodes.
1) Cycle power twice and ensure that incident 10-0226 is not active.
2) If incident is still active, reload the option files using the Update Restore
key so that the computing nodes all have the same Option/Configuration File.
Operator Message
36. Ready
10-0223
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
The Identification Files Do Not Match Across the Computing Nodes.

The purpose of this incident is to inform the maintainer that Identification Files
across the Computing Nodes do not match.
This incident occurs when the Identification Files (Rail Road and/or Road Number)
do not match across all Computing Nodes.
This incident is cleared when the Identification Files match on all Computing
Nodes.
1. The Identification file is corrupt.
2. The Identification file did not properly copy during the software loading
process to all Computing Nodes.
1) Cycle power twice and ensure that incident 10-0226 is not active.
2) If incident is still active, reload the Identification files using the Update
Restore key so that the Computing Nodes all have the same Rail Road and Road
Number.
Operator Message
36. Ready
10-0226
Incident Message
FAM Incident Intent
FAM Probable Cause
Control System Restart Required To Invoke New Options

The purpose of this incident is to inform the maintainer that the options between
the system at power up and the option file do not match.
This incident occurs when the options specified in the Options File are different
from the ones set when the system powered up.
This incident is cleared when the options match.
1. Software load incomplete.

2. Customer configurable parameters changed and not enough power cycles have
occured.
Page 89 of 332
FAM Fault Isolation
84A220120FH Rev: D
1) Cycle power until this incident is no longer active.

2) If this incident persists, consult the Software Loading Procedures (drawing no.
84A212193 [CCA Locomotive] or 84A226872AF [ECA Locomotive]).
Operator Message
Alarm Bell

52. No Self Load
90. Cycle BCCB To Activate New Configuration
91. Trip Optimizer Unavailable
30 Second
10-0231
Incident Message
FAM Incident Intent
FAM Probable Cause
Invalid Options File On SDIS 1

The purpose of this incident is to inform the maintainer of an invalid Option File
on SDIS 1.
This incident occurs when the Configuration manager detects an invalid Option File
on SDIS 1.
This incident is cleared when the Option File is valid.
Corrupted Option File.
FAM Fault Isolation
1) Reload the Option/Configuration File using the Update Restore key, and cycle
power twice.
Operator Message

36. Ready
10-0232
Incident Message
FAM Incident Intent
FAM Probable Cause

FAM Fault Isolation

on SDIS 2.
on SDIS 2.
Corrupted Option File
power twice.
Operator Message
36. Ready
10-0233
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

on SDIS 3.
on SDIS 3.
power twice.
Operator Message
36. Ready
10-0234
Incident Message
FAM Incident Intent
FAM Probable Cause

FAM Fault Isolation

on SDIS 4.
on SDIS 4.

power twice.
Operator Message
36. Ready
10-0241
Incident Message
FAM Incident Intent
FAM Probable Cause

FAM Fault Isolation
Operator Message
The Identification File Is Invalid On SDIS 1

The purpose of this incident is to inform the maintainer that there is an invalid
Identification File on SDIS 1.
This incident occurs when the Configuration Manager detects an invalid
This incident is cleared when the Identification File on SDIS 1 is valid.

Corrupted Identifications File (Road Number and/or Rail Road)
1) Re-enter Rail Road and Road Number using the Update Restore key, and cycle power
twice.
36. Ready
10-0242
Incident Message
FAM Incident Intent

Page 90 of 332

FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D

twice.
36. Ready
10-0243
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

twice.
36. Ready
10-0244
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message

twice.
36. Ready
10-0251
Incident Message
FAM Incident Intent
FAM Probable Cause

FAM Fault Isolation
The ID File Does Not Match The Options File On SDIS 1

The purpose of this incident is to inform the maintainer that Rail Road and/or Road
Number is not in the range of the option file.
This incident occurs when the Rail Road and/or Road Number in the Locomotive
Identification File is not within the range of the Locomotive Options File for
SDIS 1.
This incident is cleared when the Rail Road and/or Road Number is within the
correct range.
There is a mismatch between the Rail Road and/or Road Number allowed in the Option
file and the actual Rail Road and/or Road Number.
1) Ensure that incident 10-0226 is not in the list of active incidents. If it is on
the list, cycle BCCB.
2) Make sure the Rail Road and Road Number are correct for this locomotive. If the
ID is not correct then load the correct Rail Road and Road Number and cycle
power twice for the new Rail Road and Road Number to take effect. (Note: If this is
ECA, then RR and RN must be changed on locomotive platform according
standard procedure).
3) If this incident is still active, consult e-sevices for the latest software FMI.
Verify that the locomotive/software and Option file are correct for this
locomotive. If
incorrect, load the correct software and Option file(s).
4) If this locomotive has been re-numbered by the railroad and an Option file is
not available, contact engineering to obtain a new Option file.
(drawing no. 84A212193 [CCA] or 84A226872AF [ECA]).
Operator Message
36. Ready
10-0252
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
The ID File Does Not Match The Options File On SDIS 2

The purpose of this incident is to inform the maintainer that Rail Road and/or Road
Number is not in the range of the option file.
This incident occurs when the Rail Road and/or Road Number in the Locomotive
Identification File is not within the range of the Locomotive Options File for
SDIS 2.
This incident is cleared when the Rail Road and/or Road Number is within the
correct range.
There is a mismatch between the Rail Road and/or Road Number allowed in the
configuration file and the actual Road Number.
1) Ensure that incident 10-0226 is not in the list of active incidents. If it is on
the list, cycle BCCB.
2) Make sure the Rail Road and Road Number are correct for this locomotive. If the
ID is not correct then load the correct Rail Road and Road Number and cycle
power twice for the new Rail Road and Road Number to take effect. (Note: If this is
ECA, then RR and RN must be changed on locomotive platform according
standard procedure).
3) If this incident is still active, consult e-sevices for the latest software FMI.
Verify that the locomotive/software and Option file are correct for this
locomotive. If
incorrect, load the correct software and Option file(s).
4) If this locomotive has been re-numbered by the railroad and an Option file is
not available, contact engineering to obtain a new Option file.
Operator Message

(drawing no. 84A212193 [CCA] or 84A226872AF [ECA]).
36. Ready
10-0254
Incident Message
Criticl Files Checksum Error On SDIS 1 - Recopy Software
Page 91 of 332
FAM Incident Intent

FAM Probable Cause
84A220120FH Rev: D
The purpose of this incident is to inform the maintainer of a file error on SDIS 1.
This incident occurs when the configuration manager detected a checksum error or
file size on any of the files on SDIS 1.
This incident is cleared when all file checksums and file sizes match the expected
checksum and file size values for each file on SDIS 1.
1. One or more corrupt software files on SDIS 1.
2. SDIS 1
FAM Fault Isolation
1. If this incident occurs during the process of loading software, ignore it.
2. If software has been loaded with the correct Rail Road, Road Number, and Option
file and this incident occurs copy software to this display from one of the
other displays or download software using a hard card.
3. For more information on software loading, see Software Loading Procedures
Operator Message
4. If problem persists, and reloading software does not correct after several
attempts using different software loading cards, change out SDIS 1.
36. Ready
10-0255
Incident Message
FAM Incident Intent
FAM Probable Cause
Configuration Checksum Error On SDIS 2 - Recopy Software

file size on any of the files on SDIS 2.
1. One or more corrupt software files on SDIS 2.
2. SDIS 2
FAM Fault Isolation
Operator Message
36. Ready
10-0263
Incident Message
FAM Incident Intent
FAM Probable Cause

FAM Fault Isolation
Software Reload In Process For The ECU Panel

The purpose of this incident is to inform the maintainer that software is being
reloaded to the ECU panel.
This incident occurs when when the system starts to load software for the ECU
panel.
This incident is cleared when the system has completed the reload operation. It
will clear if the reload was successful or not.
Software is being loaded to the ECU panel.
1)This is an informative incident.
2) Wait up to 30 minutes for software download to complete. Software copy progress
will be shown on the Loco Config screen.
Operator Message
2. No Dynamic Brake, Motoring, Or Battery Charge

52. No Self Load
10-0266
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software Reload In Process For A PT Panel

To inform the maintainer that software is being reloaded to the PT.
This incident occurs when the Configuration Manager starts to reload the PT panel.
This incident is cleared when the Configuration Manager has completed the reload
operation to the PT panel.
Software is being loaded to the PT.
1)This is an informative incident.
2) Wait up to 30 minutes for software download to complete. Software copy progress
will be shown on the Loco Config screen.
54. No Battery Jog
10-0268
Incident Message
FAM Incident Intent
FAM Probable Cause
Operating System Checksum Error On SDIS 1 - Recopy Software
To inform the maintainer of an operating system file error on SDIS 1.
This incident occurs when the configuration manager detected a checksum or file
size error on any of the operating system files on SDIS 1.
1. One or more corrupt operating system files on SDIS 1.
2. SDIS 1
FAM Fault Isolation
file and this incident occurs, copy software to this display from SDIS 2 or
SDIS 3, or download software using a hard card.
Operator Message
attempts using different software loading cards, replace SDIS 1.
36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
Operating System Checksum Error On SDIS 2 - Recopy Software

To inform the maintainer of an operating system file error on SDIS 2.
This incident occurs when the configuration manager detected a checksum or file
size error on any of the operating system files on SDIS 2.
1. One or more corrupt operating system files on SDIS 2.
10-0269
2. SDIS 2
FAM Fault Isolation
file and this incident occurs, copy software to this display from SDIS 1 or
Page 92 of 332
84A220120FH Rev: D
SDIS 3 or download software using a hard card.

Operator Message
attempts using different software loading cards, replace SDIS 2.
36. Ready
10-0271
Incident Message
FAM Incident Intent

FAM Probable Cause
Application Checksum Error On SDIS 1 - Recopy Software

file size error on any of the files on SDIS 1.
1. One or more corrupt files on SDIS 1.
2. SDIS 1
FAM Fault Isolation
Operator Message
36. Ready
10-0272
Incident Message
FAM Incident Intent
FAM Probable Cause
Application Checksum Error On SDIS 2 - Recopy Software

This incident occurs when the configuration manager detected a file size error on
any of the files on SDIS 2.
1. One or more corrupt files on SDIS 2
2. SDIS 2
FAM Fault Isolation
Operator Message
36. Ready
10-0400
Incident Message
FAM Incident Intent
FAM Probable Cause

FAM Fault Isolation
Operator Message
Statistics File Could Not Be Found Or Read On Any Of The Hard Disks
To inform the maintainer that the Statistics Manager could not find a good
statistics file.
This incident occurs when the Statistics Manager could not find and read a good
statistics save file.
This incident is cleared when a new file is created and written by the Statistics
Manager.
A good statistics file could not be found.
Reload last known good statistics file from eServices to locomotive.
36. Ready
11-0001
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Cannot Communicate With Any Of The Nodes On Network
The purpose of this incident is to alert the maintainer that the system controller
can not communicate with network nodes.
This incident occurs for both of the following conditions:
â€¢ ARCNet communication is not established within 2 minutes after start-up
â€¢ All primary communication is lost for 2 minutes and all ARCNet nodes are not
visiable on the network
This incident is cleared when communication with any node one the network is
established.
1) Defective/loose ARCnet connectors/ cables(s)
2) Any network panel
3) SDIS
1. Cycle BCCB. If fault is still active, see Network Trouble Shooting Guide
(drawing No. 84A200750NW) for fault isolation.
36. Ready
11-0002
Incident Message
FAM Incident Intent
FAM Probable Cause
Battery Voltage < 40 V

The purpose of this incident is to alert the maintainer that the battery voltage is
below the normal level.
This incident occurs when the battery voltage falls below 45V.
This incident is cleared when the battery voltage is above 50V.
1) Battery
Page 93 of 332
84A220120FH Rev: D
FAM Fault Isolation
Operator Message
1. Check that LCCB is on, and EC switch is in start.

2. If Monitor parameter 2202 Battery Volts is less than 35 volts, charge the
battery until 60 V and try again.
36. Ready
11-0099
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Software: Vehicle Ctrl Shared Memory Mirror Set Broken

The purpose of this incident is to detect a broken vehicle control shared memory
mirror set.
This incident occurs when the vehicle control shared memory mirror set is not
functioning properly.
This incident is cleared when the vehicle control memory mirror set is functioning
properly.
N/A
36. Ready
11-0150
Incident Message
FAM Incident Intent
Software: LPC Shared Memory Mirror Set Broken (LPC1 to LPC2)

FAM Probable Cause

FAM Fault Isolation
Operator Message

36. Ready
11-0151
Incident Message
FAM Incident Intent
Software: LPC Shared Memory Mirror Set Broken (LPC1 to VPC2)

FAM Probable Cause

FAM Fault Isolation
Operator Message

36. Ready
11-0152
Incident Message
FAM Incident Intent
Software: LPC Shared Memory Mirror Set Broken (LPC2 to LPC1)

FAM Probable Cause

FAM Fault Isolation
Operator Message

36. Ready
11-0153
Incident Message
FAM Incident Intent
Software: LPC Shared Memory Mirror Set Broken (LPC2 to LPC1B)


FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
11-0154
Incident Message
FAM Incident Intent
Software: LPC Shared Memory Mirror Set Broken (VPC2 to LPC1)

FAM Probable Cause

FAM Fault Isolation
Operator Message

36. Ready
11-0155
Incident Message
FAM Incident Intent
Software: LPC Shared Memory Mirror Set Broken (VPC2 to LPC1B)

FAM Probable Cause

FAM Fault Isolation
Operator Message

36. Ready
11-2600

Page 94 of 332
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
84A220120FH Rev: D
No Communications With ECU At Startup

The purpose of this incident is to inform the maintainer that the system controller
(SDIS) was not able to establish communication with the ECU Panel at start-up.
This incident occurs when the control system (SDIS) has been initialized and a
request to establish communication with the Engine Control Unit (ECU) Panel is
not granted within 25 seconds of the first request.
This incident is cleared when communication is established between the SDIS and the
ECU Panel.
1) FPB - Fuel Pump Breaker
2) No power to ECU Panel - (wiring)
3)Defective/loose ARCnet connectors/ cables(s) - Control Network Issues
4) ECU Panel
1. Confirm that FPB is closed (up).

2. Go to the incident log in the SDIS. Check to see if there are any other network
comm. loss incidents active along with this incident for other panels. If there
are,
execute Network Trouble Shooting Guide, Drawing No. 84A200750NW, for fault
isolation.
3. If there are no other comm. loss incidents active, cycle FPB and BCCB. Go to the
incident log and check if this incident is still active. If the incident is active,
go to step 4. If it is not active, go to the Network Monitor screen and verify that
Network 0 and Network 1 reconfig's are not increasing, and verify that X's are
present for the ECU Panel on both networks. If it is not on the network, this
column will be blank. If the network is healthy, release the loco for service.
4. If the incident is still active in the incident log, ensure ARCNET network
cables are secure at the ECU Panel.
5. If cables are intact, shut off BCCB and FPB. Verify 74 volts FPB at connector S
on ECU between point 1(+) and 2 (+) and point 3(-) and 4(-) is 74 volts. If
voltage is not there, troubleshoot wiring per schematic.
Operator Message
Alarm Bell
6. If voltage is present at the panel connector, and incident is still active,

replace the ECU Panel.
16. Engine Won't Restart If Shutdown
53. Can't Crank
30 Second
11-2601
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Loss Of Communications With ECU While Running

(SDIS) is no longer communicating with the ECU Panel.
This incident occurs when communication between the control system (SDIS) and
Engine Control Unit (ECU) Panel has been lost for 2.5 seconds.
This incident is cleared when the communication with the ECU Panel is re-
established for 2.5 seconds.
1) No power to ECU Panel - (wiring)
2)Defective/loose ARCnet connectors/ cables(s) - Control Network Issues
3) ECU Panel
1. Confirm that FPB is closed (up).
are,
execute Network Trouble Shooting Guide, Drawing No. 84A200750NW, for fault
isolation.
3. If there are no other comm. loss incidents active, cycle FPB and BCCB. Go to the
present for the ECU Panel on both networks. If it is not on the network, this
column will be blank. If the network is healthy, release the loco for service.
4. If the incident is still active in the incident log, ensure ARNet cables are
secure at the ECU Panel.
5. If cables are intact, shut off BCCB and FPB. Verify 74 volts FPB at connector S
on ECU between point 1(+) and 2 (+) and point 3(-) and 4(-) is 74 volts. If
voltage is not there, troubleshoot wiring per schematic.
Operator Message
Alarm Bell

replace the ECU Panel.
53. Can't Crank
30 Second
11-2602
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
FPB Off - No ECU Communications At Start Up

Alert the maintainer that SDIS and ECU are not communicating because FPB is turned
OFF.
The control system (SDIS) failed to establish communication with the Engine Control
Unit (ECU) Panel because the Fuel Pump Breaker (FPB) is OFF.
Communication is re-established between SDIS and ECU.
None
1.) Turn on the FPB.
45. Fuel Pump Circuit Breaker (FPB) Is Off
53. Can't Crank
30 Second
11-2603
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Alarm Bell
FPB Off - No ECU Communications While Running

Alert the maintainer that SDIS and ECU are not communicating because FPB is turned
OFF
The control system (SDIS) has lost communidation with ECU because the Fuel Pump
Breaker is turned OFF.
Communication is re-established between SDIS and ECU.
FPB Tripped or Turned Off
1.) Turn on the FPB.
2.) Check the Fuel Pump Motor it may be tripping the fuel pump breaker causing the
communications loss.
45. Fuel Pump Circuit Breaker (FPB) Is Off
53. Can't Crank
30 Second
Incident Message
FAM Incident Intent
Fuel Pump Breaker Input Mismatch

Alert the maintainer that the FPB input is not functioning.
The input for the fuel pump breaker status does not agree with the communications
status for the ECU panel.
Operator Message
11-2604
Page 95 of 332

FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D
The input for the fuel pump breaker status agrees with the communications status
for the ECU panel.
1. Wiring for the FPB digital input
2. CIO panel
1.) Turn on the FPB. Check Monitor Parameter #1007. It should be a "1". If it is
not a "1".
2.) Check the wiring for the Fuel Pump Breaker Input from the FPB to the CIO. If
wiring checks good, continue. If wiring is defective, repair it.
3.) Swap CIO Slot 11 with another card of the same type. If fault remains, replace
the CIO panel. If fault goes away, replace the original digital input card.
36. Ready
11-2605
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
ECU Loss Of Communication With System Controller

The purpose of this incident is to inform the maintainer that there is a one-way
communication loss ECU Panel.
This incident occurs when the Engine Control Unit (ECU) Panel has not had
communication with the system controller (SDIS) for 2.5 seconds.
This incident is cleared when communication is established between the ECU Panel
and the system controller.
1. ECU Panel
2. Network Problems
1. If there are any other network comm loss incidents active along with this
incident, troubleshoot per FAM corresponding to those incidents.
2. If there no other comm loss incidents are active, cycle FPB and BCCB.
Operator Message
3. If the incident still persists, change the ECU Panel.

11-2606
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
ECU Bad (Abnormal Request For Software Download)
The purpose of this incident is to identify a bad ECU Panel.
The incident occurs when the ECU Panel unexpectedly requests software download.
This incident is cleared when the ECU Panel is no longer asking for a software
download.
1. ECU panel
1. Cycle BCCB. Go to Loco Config screen. Look for a red X on ECU panel to determine
if the panel has matching software. If there is no red X, release
locomotive for service.
2. If there is a red X, download software to ECU Panel. For more information on
software loading, see Software Loading Procedures (drawing no. 84A212193).
Operator Message
3. If software downloads correctly, release locomotive for service. If incident

returns, change out the ECU Panel.
53. Can't Crank
11-3000
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Loss Of Comm With PT1 (PTD-Slot 2 or PTP)

The purpose of this incident is to inform the maintainer that communication is lost
with the PT1 card.
This incident occurs when there is no communications with Protocol Translator #1
(PT1) card for 8 seconds while running.
This incident will clear when communication is established between the system
controller and the PT1 card/Panel.
1) No power to PTD/PTP Panel
3) PT1 Card (Slot2 in PT Panel)
4)PTD/PTP panel
4) SDIS
1. Verify that MTB is closed (up).
are,
execute Network Trouble Shooting Guide (drawing No. 84A200750NW) for fault
isolation.
3. If there are no other comm. loss incidents active, cycle MTB and BCCB. Go to the
present for the PT1 card on both networks. If it is not on the network, this column
will be blank. If the network is healthy, release the loco for service.
4. If the incident is still active in the incident log, ensure ARCNet cables are
secure at the PTD Panel Slot2 card. Re-seat the Slot2 card.
5. If cables are intact, shut off BCCB and MTB. Verify 15 volts at the Left Hand
Power Connector, 1, on PTD at pins 1 and 2. Verify 15 volts at the Right Hand
Power Connector, 10, on PTD at pins 1 and 2. If voltage is not there, troubleshoot
wiring per schematic.
Operator Message

replace the PTD Slot2 Card. If problem persists, replace the PTD panel.
36. Ready
11-3002
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
PT1 Loss Of Comm With System Controller

communication loss from the SDIS to the PT1 card.
This incident occurs when the Smart Display (SDIS) has not communicated with the
Protocol Translator 1 (PT1) card in the last 8 seconds.
controller and the PT1 card.
1. PT1 Card
2. Network problems
2. If there no other comm loss incidents are active, cycle MTB and BCCB.
Operator Message
3. If the incident still persists, change the PT1 card.

36. Ready
11-3003
Incident Message
FAM Incident Intent
No Communication With PT1 (PTD-Slot 2 or PTP) at Startup

was not able to establish communication with the PT1 card at start-up.
request to establish communication with the Protocol Translator 1 (PT1) card
(Slot2) is not granted within 45 seconds of the first request.
PT1 card. .
Page 96 of 332
FAM Probable Cause
FAM Fault Isolation
84A220120FH Rev: D
1) No power to PTD Panel

4)PTD panel
5) SDIS
are,
isolation.
Operator Message

36. Ready
11-3100
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Loss Of Communications With PT2 (PTD-Slot 3 or PTP)

with the PT2 card.
This incident occurs when there is no communications with Protocol Translator 2
(PT2) for 2.5 seconds while running.
4)PTD panel
5) SDIS
are,
isolation.
Operator Message

36. Ready
11-3102
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Protocol Translator 2 (PT2) panel in the last 8 seconds.
This incident will clear when at least 3 messages have been received by the PT2
panel with in 3 seconds from the SDIS.
1. PT2 Card
2. Network problems
Operator Message

36. Ready
11-3103
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

request to establish communication with the Protocol Translator 2(PT2) Panel is not
granted within 45 seconds of the first request.
4) PTD panel
5) SDIS
are,
isolation.
Operator Message

36. Ready
11-3200
Incident Message
Loss Of Comm With PT3 (PTD-Slot 4 or PTP)
Page 97 of 332
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
84A220120FH Rev: D
with the PT3 card.
This incident occurs when there is no communications with Protocol Translator (PT3)
for 2.5 seconds while running.
4)PTD panel
5) SDIS
are,
isolation.
Operator Message

36. Ready
11-3202
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Protocol Translator (PT3) panel in the last 8 seconds.
This incident will clear when at least 3 messages have been received by the PT3
panel with in 3 seconds form the SDIS.
1. PT3 Panel
2. Network problems
Operator Message

36. Ready
11-3203
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

request to establish communication with the Protocol Translator 3 (PT3) card is not
granted within 45 seconds of the first request.
4) PTD panel
5) SDIS
are,
isolation.
Operator Message
36. Ready
11-3300
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Loss Of Comm With PT4 (PTP)

with the PT4 card.
This incident occurs when there is not communication with Protocol Translator 4
(PT4) card for 2.5 seconds while running.
4) PTD panel
5) SDIS
are,
isolation.
Operator Message

36. Ready
Page 98 of 332
84A220120FH Rev: D
11-5004
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
ECU Network Status Changed

The purpose of this incident is to inform the maintainer change in network
communication for the ECU.
This incident occurs when there is a change in the network communication for the
Engine Control Unit (ECU) due to the following reasons:
1) ECU can no longer transmit on Network 0 and/or Network 1.
2) ECU can no longer receive data on Network 0 and/or Network 1.
3) SDIS can no longer transmit on Network 0 and/or Network 1.
4) SDIS can no longer receive on Network 0 and/or Network 1.
This incident will clear when the communication link for the ECU is re-established
on both networks and is transmitting and receiving messages properly for 15
minutes.
1. Loose / disconnected Arcnet wiring or Terminations
2. Defective ECU Panel
3. Defective SDIS
Cycle FPB and BCCB and see if incident clears.
If incident remains active for more than 1 day, troubleshoot per Network Trouble
Shooting Guide (drawing No. 84A200750NW).
Operator Message
36. Ready
11-5008
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
PT1 Network Status Changed

The purpose of this incident is to inform the maintainer of a network status change
for PT1.
Protocol Translator 1 (PT1) due to the following reasons:
1) PT1 can no longer transmit on Network 0 and/or 1.
2) PT1 can no longer receive data on Network 0 and/or 1.
3) SDIS can no longer transmit on Network 0 and/or 1.
4) SDIS can no longer receive on Network 0 and/or 1.
This incident will clear when the communication link for PT1 is re-established on
both networks and is transmitting and recieving messages properly for 15
minutes.
2. Defective PT1 Panel
3. Defective SDIS
Cycle MTB and BCCB and see if incident clears.
Operator Message
36. Ready
11-5009
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation

for the PT2.
This incident will clear when the communication link for the PT2 is re-established
minutes.
3. Defective SDIS
Operator Message
36. Ready
11-5010
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation

for the PT3.
minutes.
3. Defective SDIS
Operator Message
36. Ready
11-5019
Incident Message
FAM Incident Intent

for the PT4.
Page 99 of 332

FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D
minutes.
3. Defective SDIS
Cycle BCCB and see if incident clears.
36. Ready
11-5030
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Network 0 Recon Rate > 1 per 90 seconds

The purpose of this incident is to inform the maintainer of a low level problem on
the Network 0.
This incident occurs only when the locomotive is in non-powered mode and the
reconconfiguration rate on Network 0 is greater than or equal to 1 every 1.5
minutes and less than 1 per second. This incident is a warning meant to indicate a
possible network problem.
This incident will clear when the reconfiguration rate has been less than or equal
to 1 per 15 minutes for 2 consecutive hours.
1. Loose/ Disconnected Arcnet wiring or Terminations
2. Defective Panels/ Network Interface Cards
36. Ready
11-5031
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Network 0 Recon Rate > 1 per second

The purpose of this incident is to inform the maintainer of a mid-range problem on
Network 0 that may eventually cause communication losses.
This incident occurs anytime when the reconfiguration rate on Network 0 is greater
than or equal to 1 per second and less than 15 per second.
If this incident persists, for more than 1 day, troubleshoot the network at the
next scheduled service shop.
Make sure all the ARCNet connectors are secure.
Cycle BCCB/MTB/FPB.
Check all panels for compatible panel version.
TROUBLESHOOTING BAD PANELS
To determine or eliminate if a panel is the source of the reconfigurations, there
are two methods. One or both may be required.
- Turning power off to that panel: Turn off power to panels one-by-one. This
eliminates the node from the network, but the network still uses the network traces
on
the card to complete the bus configuration.
- Bypassing the panel by connecting its ARCNet network cables together:
This involves connecting the cables that normally go into the panel directly
together. This will completely isolate the panel from the ARCNet, allowing one to
fully
eliminate the panel from suspicion if recons continue to climb.
TROUBLESHOOTING BAD CABLES
To determine if the failure is within one of the network cables, you will need to
use shorting plugs or terminating plugs to create a smaller network, and then bring
each cable back into the network.
- NOTE: To do this step, you need a shorting/terminating plug that is not readily
available.
- Connect all the network cables together leaving just 3 panels in the loop,
placing a shorting plug or a terminating plug at CIO-WB on the CIO Panel.
- Gradually, move the terminator from the last panel. Keep adding cables back into
the loop until recons start to climb.
- Note that when disconnecting cables, both networks will be disrupted and comm
loss incidents will log for all panels.
If problem still exists reference complete network troubleshooting guide. (drawing
No. 84A200750NW)
Operator Message
36. Ready
11-5032
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

The purpose of this incident is to inform the maintainer of a serious problem on
Network 0 that may cause communication losses.
than or equal to 15 per second and a High-Risk Incident has not already been
logged.
Troubleshoot the network as soon as possible at a service shop.
Cycle BCCB/MTB/FPB.
on
fully
available.
- Connect all the network cables together leaving just 3 panels in the loop (SDIS1,
CIO, PTP), placing a shorting plug or a terminating plug at CIO-WB on the CIO
Panel.
Operator Message

No. 84A200750NW)
36. Ready
11-5033
Incident Message
FAM Incident Intent
Network 1 Recon Rate > 1 per 90 seconds

The purpose of this incident is to inform the maintainer of a possible problem on
the Network 1.
This incident occurs only when the locomotive is in non-powered mode and the
reconconfiguration rate on Network 1 is greater than or equal to 1 every 1.5
minutes and less than 1 per second. This incident is a warning meant to indicate a
possible network problem.
Page 100 of 332


FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D
36. Ready
11-5034
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

The purpose of this incident is to inform the maintainer of a mid-range problem on
Network 1 that may eventually cause communication losses.
than or equal to 1 per second and less than 15 per second.
If this incident persists, for more than 1 day, troubleshoot the network at the
next scheduled service shop.
Cycle BCCB/MTB/FPB.
on
fully
available.
Panel.
liss incidents will log for all panels.
No. 84A200750NW)
Operator Message
36. Ready
11-5035
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

The purpose of this incident is to inform the maintainer of a high risk problem on
Network 1 that may cause communication losses.
than or equal to 15 per second.
Troubleshoot the network as soon as possible at a service shop.
Cycle BCCB/MTB/FPB.
on
fully
available.
Panel.
Operator Message

No. 84A200750NW)
36. Ready
11-5036
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Arcnet Network 0 Health Degraded

The purpose of this incident is to inform the maintainer that Arcnet Network 0â€™s
health is being degraded because of an increasing rate of reconfigurations on
Arcnet Network 0. This increases the risk that communication losses may occur.
If the Net 0 Recon Count has incremented more than 10 times in 15 minutes
If the Net 0 Recon Count has incremented less than 2 times in in 30 sec.
1. Loose / disconnected Arcnet wiring or terminations.
2. Defective panels / network interface cards.
Cycle BCCB/MTB/FPB.
If incident remains active for more than 1 day , troubleshoot per network
troubleshooting steps below for bad panels or bad cables.
on
fully
Page 101 of 332

84A220120FH Rev: D

available.
- Connect all the network cables together leaving just 3 panels in the loop (SDIS,
Panel.
No. 84A200750NW)
Operator Message
36. Ready
11-5037
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Arcnet Network 1 Health Degraded

The purpose of this incident is to inform the maintainer that Arcnet Network 1â€™s
health is being degraded because of an increasing rate of reconfigurations on
Arcnet Network 1. This increases the risk that communication losses may occur.
If the Net 1 Recon Count has incremented more than 10 times in 15 minutes.
If the Net 1 Recon Count has incremented less than 2 times in in 30 sec.
1. Loose / disconnected Arcnet wiring or terminations.
2. Defective panels / network interface cards.
Cycle BCCB/MTB/FPB.
If incident remains active for more than 1 day , troubleshoot per network
troubleshooting steps below for bad panels or bad cables.
on
fully
available.
- Connect all the network cables together leaving just 3 panels in the loop (SDIS,
Panel.
No. 84A200750NW)
Operator Message
36. Ready
11-5100
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Computers Too Hot, System Automatically Shutdown

The purpose of this incident is it initiate a system shutdown.
This incident occurs when the system is too hot and must shut down.
This indident will clear automatically upon power down.

1. Enviromental conditions
2. Strip heaters
3. HVAC
3. SDIS Vents
4. SDIS
1. If this incident occurs in the middle of power up, ignore it.
2. If the operator cab temperature is much greater than normal environmental
temperature and/or the sun has been beating down directly on the Smart Displays,
this
incident may log. In this case, turn off SDIS and allow it to cool or turn on HVAC
air conditioning to cool ambient air.
3. If this is not the case, check strip heaters on the side walls of both the
conductor and engineer's side of the operator cab. Ensure that the strip heaters
have not
been left on. If they have been left on, turn off and allow time for ambient air
temperature to cool and incident to clear.
4. Ensure that the HVAC heat was not left on. Check for clogged or dirty vents on
the HVAC and ensure that HVAC control is not stuck.
5. Ensure that there is not dust/dirt clogging the heat vents on the SDIS's. If the
vents are clogged, clear the debris to allow air flow.
6. If all filters are clean, the problem may be a defective temperature sensor. On
the custom monitor screen check the temperature validity bit, MP#524, 546, and
568, to ensure that the temperature is valid. If invalid, replace the respective
SDIS.
Operator Message
Alarm Bell

30 Second
11-5102
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message
Computer Manually Shutdown

The purpose of this incident is to inform the maintainer that the system was
manually shut down.
This is not a fault. This incident logs when the computer was manually shut down by
turning the BCCB breaker off.
This incident will clear automatically upon power down.
1) Normal Operation - BCCB Breaker Manually Shut Off.
2) The breaker could be tripped.
This happens under normal operation. It is possible that BCCB breaker could trip.
Under these circumstances, ensure that when BCCB power is applied the circuit
breaker does NOT trip. Check the LPS if the circuit breaker is tripping.
15. Please Waitâ€¦ System Diagnostics In Progress
Page 102 of 332

84A220120FH Rev: D
11-5103
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
SDIS1 Manually Shutdown

The purpose of this incident is to inform the maintainer that SDIS1 was manually
shut down.
This incident occurs when the SDIS1 receives a shutdown request and can not
communicate with the other displays.
1. SDIS1
2. Ethernet
3. TIO
1. This incident will log if the battery knife switch is pulled or if BCCB and MTB
are turned off at the same time.
2. Verify normal shutdown sequence by all the displays (cycle BCCB). If normal,
release locomotive to the field. If trouble persists, got to step 3.
3. Check that power cable for SDIS1 (#DS1P) is properly connected.
4. Check the cables between SDIS 1 and the Ethernet HUB card (cables #CBLK01,
CBLK02, CBLK03, CBLK04, CBLK-S). Verify that all cabling is connected
and seated properly on the panels. If a cable is not properly connected, re-seat
it. If a broken or damaged cable is found, replace the cable.
5. On SDIS 1, inspect connector 4 pins 1, 3, 9, 11, and SHE for damages. On PTD,
inspect connector 9A pins 2, 4, 7, 9, and SHE. If damaged, replace connector
or replace respective panel. Ensure that ID jumper on connector 4 at pins 7 and 15
is properly connected to both pins.
6. If the cables are tight/secure and pins are intact, verify that the green LED on
SDIS1 is on. If this LED is not on, cycle BCCB off. Remove connector 1 from
SDIS1. Measure 74V power supply at pins 1(+) and 3(-). If it is not 74V,
troubleshoot wiring per schematic.
7. If wiring is not the problem, examine the LED's on the Ethernet HUB. If the
connector from SDIS1 on the Ethernet HUB card has a solid green or red light,
swap the connector from SDIS1 with the connector from a working SDIS panel. Cycle
MTB and BCCB. If the fault follows SDIS1, replace SDIS1. If the fault
follows the connector, replace the cables. If fault remains, replace the Ethernet
HUB.
Operator Message
36. Ready
11-5104
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
shut down.
1. SDIS2
2. Ethernet
4. Check the cables between SDIS 2 and the Ethernet HUB card (cables #CBLL01,
CBLL02, CBLL03, CBLL04, CBLL-S). Verify that all cabling is connected
inspect connector 9B pins 2, 4, 7, 9, and SHE. If damaged, replace connector
Operator Message
HUB.
36. Ready
11-5105
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

shut down.
1. SDIS3
2. Ethernet
4. Check the cables between SDIS 1 and the Ethernet HUB card (cables #CBLX01,
CBLX02, CBLX03, CBLX04, CBLX-S). Verify that all cabling is connected
inspect connector 9C pins 2, 4, 7, 9, and SHE. If damaged, replace connector
Operator Message
HUB.
36. Ready
11-5107
Incident Message
FAM Incident Intent
Computer System Reconfiguration In Progress

The purpose of this incident is to allow an autoreset of the Smart Display system.
Page 103 of 332


FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D
This incident occurs as soon as the system controller recieves shutdown requests
from at least two different displays within the autoreset window time period. The
incident should be logged as soon as the second request is received rather than
waiting to the end of the window.
This incident will clear automatically on powerdown.

This feature is not available at this time.
36. Ready
11-5108
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Inadvertent Shutdown Request Received From SDIS1

The purpose of this incident is to show that an inadvertent shutdown request was
recieved from SDIS1.
This incident occurs when only 1 shutdown request (from SDIS1) is recieved by the
system controller within the shutdown request time window.
This incident will be cleared automatically upon powerdown.
1. BCCB Wireing
2. SDIS1
1. Check BCCB power cable (#5EP1) is properly connected on SDIS1.
2. If the wireing is good, test normal shutdown on SDIS1. If it works properly,
release the unit for service. If problem persists, replace SDIS1.
Operator Message
36. Ready
11-5109
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation

The purpose of this incident is to show that an inadvertenct shutdown request was

1. BCCB Wireing
2. SDIS2
Operator Message
36. Ready
11-5110
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message

The purpose of this incident is to show that an inadvertenct shutdown request was

1. BCCB Wireing
2. SDIS3
36. Ready
11-5111
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
SDIS1 Did Not Power Off / Reset When Commanded

N/A
N/A
N/A
N/A
36. Ready
11-5112
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

N/A
N/A
N/A
N/A
36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

N/A
N/A
N/A
N/A
36. Ready
11-5113
11-5115
Page 104 of 332

Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
84A220120FH Rev: D
Computers Hot, Screen Saver Timeout Shortened

The purpose of this incident is to extend display life by keeping the lamps off as
much as possible in an overtemp condition.
This incident occurs when when all of the following conditions are true AND the
situation persists for at least 60 seconds:
â€¢ At least one display with a valid temperature signal has temperature greater
than 60 degrees
â€¢ At least one other display with a valid temperature signal has temperature
greater than 54 degrees
This incident clears at power up or when all displays with valid temperature
signals have had temperatures less than 55 degrees C for at least 60 seconds.
1. Ambient air temperature

2. Strip heaters
3. HVAC
3. SDIS Vents
4. SDIS temperature sensor
1. If the operator cab temperature is much greater than normal ambint temperature
and/or the sun has been beating down directly on the Smart Displays, this
incident may log. In this case, turn off SDIS and allow it to cool or turn on HVAC
air conditioning to cool ambient air.
2. If this is not the case, check strip heaters on the side walls of both the
conductor and engineer's side of the operator cab. Ensure that the strip heaters
have not
been left on. If they have been left on, turn off and allow time for ambient air
temperature to cool and incident to clear.
3. Ensure that the HVAC heat was not left on. Check for clogged or dirty vents on
the HVAC.
4. Ensure that there is not dust/dirt clogging the heat vents on the SDIS's. If the
vents are clogged, clear the debris to allow air flow.
5. If all filters are clean, the problem may be a defective temperature sensor. On
the custom monitor screen check the temperature validity bit, MP#524, 546, and
568, to ensure that the temperature is valid. If invalid, replace the respective
SDIS.
Operator Message
6. If the fault still remains, the problem may be falsely logged. Change out SDIS.
36. Ready
11-5116
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
SDIS1 Microcontroller Problem (May Not Respond To Keypresses)

The purpose of this incident is to detect a SDIS1 microcontroller that is not
This incident occurs when the SDIS1 microcontroller is not responding properly.
This incident is cleared when the SDIS1 microcontroller is responding properly.
1. SDIS1
1. Turn BCCB off. Wait for green LED to turn off on SDIS1. Turn off the DS1 circuit
breaker behind the EC panel. Remove SDIS1 from the console and replace
display.
36. Ready
11-5117
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
SDIS2 Microcontroller Problem (may Not Respond To Keypresses)

1. SDIS2
breaker behind the EC panel. Remove SDI2 from the console and replace
display.
36. Ready
11-5118
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
SDIS3 Microcontroller Problem (may Not Respond To Keypresses)

1. SDIS3
display.
36. Ready
11-5119
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
SDIS1 Lamp Filament Bad

The purpose of this incident is to detect a bad lamp filiment in SDIS1.
This incident occurs when the SDIS1 backlight is commanded 'on' and the lamp status
for SDIS1 indicates a problem for more than 30 seconds.
This incident is cleared when the SDIS1 backlight is on and the lamp status for
SDIS1 indicates no problems for more than 30 seconds.
1. SDIS1 lamp filiment
bulb per SMI-65032.
2. Reinstall SDIS1 in the console, turn DS1circuit breakers back on and turn BCCB
on. Ensure that incident is no longer active.
Operator Message
36. Ready
11-5120
Incident Message
FAM Incident Intent
FAM Probable Cause

Page 105 of 332

FAM Fault Isolation
84A220120FH Rev: D
bulb per SMI-65032.
Operator Message
36. Ready
11-5121
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

bulb per SMI-65032.
36. Ready
11-5130
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Loss of Communications With SDIS1 On Data Network

The purpose of this incident is to detect the complete loss of SDIS1 from the data
network.
This incident occurs when SDIS1 is an active participant in power up but can no
longer communicate with the other smart displays.
This incident is cleared if communications is returned for 10 seconds.
1. Wiring
2. SDIS1
3. Ethernet HUB card
2. Check the cables between SDIS1 and the Ethernet HUB card replacing where needed.
DS1
Wire
PTD9A
-------------------------4-3
CBLK01 2
4-11 CBLK02 7
4-1
CBLK03 4
4-9
CBLK04 C9BLL01
4-SHE CBLK-S SHE
3. Ensure that ID jumper DSJK on connector 4 at pins 7 and 15 is properly connected
to both pins.
SDIS1 is on. If this LED is not on, turn off BCCB, DS1P, DS2P, DS3P. Remove
connector 1 from SDIS1. Turn on BCCB and DS1P. Measure 74V power supply from pin 1
to 3, and from pin 2 to 3. If it is not 74V, replace wiring to the
switch.
Ethernet HUB card light A is not flashing, turn off BCCB and MTD, swap the
connector from SDIS1 with a connector from another working SDIS panel. Turn on MTB
and BCCB. If a similar incident occurs on the other SDIS unit, replace
the Ethernet HUB. If the fault recurs on SDIS1, replace SDIS1
58. When Locomotive Is Safely Stopped, Cycle BCCB To Reset Computers
30 Second
11-5131
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

network.
This incident occurs when SDIS2 is an active participant in power up but can no
1. Wiring
2. SDIS2
DS2
Wire PTD9B
4-3
CBLL01 2
4-11
CBLL02 7
4-1
CBLL03 4
4-9
CBLL04 9
4-SHE CBLL-S SHE
3. Ensure that ID jumper DSJL on connector 4 at pins 8 and 15 is properly connected
to both pins.
switch.
Ethernet HUB card light B is not flashing, turn off BCCB and MTD, swap the
30 Second
11-5132
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

network.
This incident occurs when SDIS3 is an active perticipant in power up but can no
1. Wiring
2. SDIS3
DS3
Wire PTD9C
------------------------4-3
CBLX01 2
4-11
CBLX02 7
4-1
CBLX03 4
4-9
CBLX04 9
4-SHE CBLX-S SHE
3. Ensure that ID jumper DSJW on connector 4 at pins 13 and 15 is properly
connected to both pins.

Page 106 of 332
84A220120FH Rev: D
switch.
Ethernet HUB card light C is not flashing, turn off BCCB and MTD, swap the
Operator Message
Alarm Bell

30 Second
11-5140
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message
SDIS1 Not Communicating On Data Network At Powerup - Left Offline

The purpose of this incident is to detect the loss of SDIS1 from the data network
at power up.
This incident occurs when SDIS1 is not communicating upon power up.
This incident is cleared automatically on power down.
1. Wiring
2. SDIS1
Perform fault isolation for incident 11-5130.
36. Ready
11-5141
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message

at power up.
1. Wiring
2. SDIS2
36. Ready
11-5142
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message

at power up.
1. Wiring
2. SDIS3
36. Ready
11-5150
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation

Operator Message
Alarm Bell
SDIS1 Cannot Communicate On Data Network

The purpose of this incident is to detect the case were SDIS1 can not communicate
with any other nodes.
This incident occurs when SDIS1 is not receiving messages from nodes active during
power up.
This incident is cleared when SDIS1 recieves 10 consecutive messages from any other
active node within any 15 second period.
1. Wiring
2. SDIS1
30 Second
11-5151
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

This incident occurs when SDIS2 is not receiving messages from nodes active during
power up.
1. Wiring
2. SDIS2
11-5152
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message
Alarm Bell

This incident occurs when SDIS 3 is not receiving messages from other nodes active
during power up.
1. Wiring
2. SDIS3
30 Second
11-5160
Incident Message
FAM Incident Intent
FAM Probable Cause
SDIS1 Has Bad Arcnet Node ID

The purpose of this incident is to identify a bad ARCnet node ID for SDIS1.
This incident occurs when an incorrect Arcnet node ID is detected for SDIS1.
This incident is cleared when the correct Arcnet node ID is detected for SDIS1.
1. Node ID is programmed incorrectly

Page 107 of 332
FAM Fault Isolation
Operator Message
84A220120FH Rev: D
1. On SDIS1, check that ID jumper on connector 4 at pins 7 and 15 is properly

2. If pins are properly connected, change out SDIS1.
36. Ready
11-5161
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
11-5162
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
11-5170
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Non-Critical System Error On SDIS1

The purpose of this incident is to document that one or more non-critical tasks
have been reported lost.
This incident occurs when a non-critical system error occurs in the system for
SDIS1.

No troubleshooting required.
36. Ready
11-5171
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

SDIS2.
36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

SDIS3.
36. Ready
Incident Message
FAM Incident Intent
Critical System Error On SDIS1

The purpose of this incident is to document that one or more critical tasks have
been reported lost.
This incident occurs when a critical system error occurs in the system for SDIS1.
11-5172
11-5180

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

1. Software error
1. Cycle BCCB and check to see if system recovers from incident.
36. Ready
30 Second
11-5181
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

been reported lost.
1. Software error
36. Ready
30 Second
11-5182
Incident Message
FAM Incident Intent
FAM Probable Cause

been reported lost.
1. Software error
Page 108 of 332

84A220120FH Rev: D
FAM Fault Isolation

Operator Message
Alarm Bell

36. Ready
30 Second
Incident Message
FAM Incident Intent
Loss of Communications With IHUB

The purpose of this incident is to inform the maintainer that the IHUB is not
communicating which causes loss of communication with all attached third party
equipment.
11-5200
FAM Probable Cause

FAM Fault Isolation
Operator Message
This incident occurs when the IHUB Ethernet socket shuts down and the control
system is not in power up or power down.
This incident clears when the IHUB socket communications are

re-established.
N/A
This incident should not be occurring on Evolution Series locomotives. Ignore this
incident.
36. Ready
11-5217
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
SDIS1 Vehicle Control Task Not Communicating With Disp Task

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
Incident Message
FAM Incident Intent
Loss of Communications With RMD

The purpose of this incident is to inform the maintainer that communication with
CMU has been lost or is not present.
This incident occurs when CMU cannot communicate with the locomotive for 60
minutes, provided that the control system is not powering up or powering down
with in that time frame.
This incident is cleared when a valid data synch command message is received by the
SDIS from CMU.
1) CMU
2) PTD
3) Wiring
1. Cycle BCCB to see if CMU communicates.
2. Inspect and re-seat connector between CMU & PTD.
3. Follow correct CMU/ARC Shutdown procedure per EOA Troubleshooting guide
(84A212951BF).
11-5218
11-5219
11-5220
11-5250

FAM Probable Cause
FAM Fault Isolation
Operator Message
36. Ready
11-5251
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message
Loss of Communications With RMD

CMU has been lost or is not present.
This incident occurs when CMU cannot communicate with the locomotive for 60
SDIS from CMU.
1) CMU
2) PTD
3) Wiring
36. Ready
11-5252
Incident Message
FAM Incident Intent
Loss of Communications With RMD Second Fault Socket

Cell has been lost or is not present.
This incident occurs when Cell cannot communicate with the locomotive for 60
Page 109 of 332


FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D
SDIS from Cell.
1) Cell
2) ESW
3) Wiring
1. Cycle BCCB to see if CMU communicates.
2.
Inspect and re-seat connector between CMU & PTD.
3.
Follow correct CMU/ARC Shutdown procedure per EOA Troubleshooting guide
(84A212951BF).
36. Ready
11-5253
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message
Loss of Communications With RMD Second Parameter Socket

Cell has been lost or is not present.
This incident occurs when Cell cannot communicate with the locomotive for 60
SDIS from Cell.
1) Cell
2) ESW
3) Wiring
36. Ready
11-5254
Incident Message
FAM Incident Intent
FAM Probable Cause
Operator Message
Loss Of Communication With RMD Smartloco Socket

Identify communication problems between the SDIS and the CMU/ARC Box
Reference Incident 11-5250
36. Ready
11-5255
Incident Message
FAM Probable Cause
FAM Fault Isolation
Operator Message
Smartloco Task Restarted

36. Ready
11-5256
Incident Message
FAM Probable Cause

FAM Fault Isolation
HMI Display Task Failed Node 3

11-5257
Incident Message
FAM Probable Cause

FAM Fault Isolation

11-5258
Incident Message
FAM Probable Cause

FAM Fault Isolation

11-5259
Incident Message
FAM Probable Cause
FAM Fault Isolation
HMI Tilcon Server Failed Node 3

11-5260
Incident Message
FAM Probable Cause
FAM Fault Isolation

11-5261
Incident Message
FAM Probable Cause
FAM Fault Isolation

11-5262
Incident Message
FAM Probable Cause
FAM Fault Isolation
HMI Tilcon Client Failed Node 3

11-5263
Incident Message
FAM Probable Cause
FAM Fault Isolation

11-5264
Page 110 of 332

Incident Message
FAM Probable Cause
FAM Fault Isolation
84A220120FH Rev: D

11-5505
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
SDIS1 Loss of Communications With SDIS2 On Data Network

See 11-5130
See 11-5130
See 11-5130
See 11-5130
30 Second
11-5506
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5130
See 11-5130
See 11-5130
See 11-5130
30 Second
11-5507
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5130
See 11-5130
See 11-5130
See 11-5130
30 Second
11-5509
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5131
See 11-5131
See 11-5131
See 11-5131
30 Second
11-5510
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5131
See 11-5131
See 11-5131
See 11-5131
30 Second
11-5511
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5131
See 11-5131
See 11-5131
See 11-5131
30 Second
11-5513
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5132
See 11-5132
See 11-5132
See 11-5132
30 Second
11-5514
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5132
See 11-5132
See 11-5132
See 11-5132
30 Second
11-5515
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

See 11-5132
See 11-5132
See 11-5132
See 11-5132
Page 111 of 332

Operator Message
Alarm Bell
84A220120FH Rev: D

30 Second
11-5517
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5132
See 11-5132
See 11-5132
See 11-5132
30 Second
11-5518
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5132
See 11-5132
See 11-5132
See 11-5132
30 Second
11-5519
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

See 11-5132
See 11-5132
See 11-5132
See 11-5132
30 Second
11-5527
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
SDIS1 Data Network Status Changed

for the SDIS1.
If any of the MP's below change in value 5 minutes after power up, trigger this
incident
9972, 9987, 9992, 9952, 9977, 9962, 9937, 9932, 9982, 9957, 9997, 9967
If the MP's below have not change for 10 seconds, clear this incident
9972, 9987, 9992, 9952, 9977, 9962, 9937, 9932, 9982, 9957, 9997, 9967
1. Loose / disconnected Ethernet wiring.
2. Defective SDIS1 Panel
3. ESW
If the Incident only occurs at power, then disregard. If the Incident occurs while
running, use the schematic to isolate the ports, cables. Then visually inspect the
connectors and nodes for damage or loose connections. Also check the parameters on
the Ethernet Monitor Screen. Look for parameters that have continuous
changes. If the cables have no damage and are all tight, then begin swapping out
hardware in the following order: SDIS1, ESW till until the problem is fixed.
Operator Message
36. Ready
11-5528
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

for the SDIS2.
incident
9973, 9988, 9993, 9953, 9978, 9963, 9938, 9933, 9983, 9958, 9998, 9968
9973, 9988, 9993, 9953, 9978, 9963, 9938, 9933, 9983, 9958, 9998, 9968
3. ESW
36. Ready
11-5529
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

for the SDIS3.
incident
9974, 9989, 9994, 9954, 9979, 9964, 9939, 9934, 9984, 9959, 9999, 9969
9974, 9989, 9994, 9954, 9979, 9964, 9939, 9934, 9984, 9959, 9999, 9969
3. ESW
36. Ready
Page 112 of 332

84A220120FH Rev: D
11-5552
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Improper reset detected on SDIS1

NA
NA
NA
A quick BCCB cycle
If you see this fault at power up, and you did not wait for the Green LED on the
SDIS to go out before you closed BCCB, Open BCCB and wait for the Green LED
on all SDIS's to go out, then close BCCB. If the fault continues to trigger,
contact RMD.
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

NA
NA
NA
A quick BCCB cycle
contact RMD.
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

NA
NA
NA
A quick BCCB cycle
contact RMD.
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

NA
NA
NA
A quick BCCB cycle
contact RMD.
11-5553
11-5554
11-5555
11-6041
Incident Message
FAM Probable Cause
FAM Fault Isolation
Operator Message
SDIS1 Watchdog Disable Jumper Is Installed

36. Ready
11-6046
Incident Message
FAM Probable Cause
FAM Fault Isolation
Operator Message
SDIS1 Loss Of Communications Due To Reboot Tmr

36. Ready
11-6052
Incident Message
FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
11-6057
Incident Message
FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
11-6063
Incident Message
FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
11-6068
Incident Message
FAM Probable Cause
FAM Fault Isolation
Operator Message

36. Ready
11-6700
Incident Message
FAM Incident Intent
FAM Probable Cause
No Communications With BCA At Startup

(SDIS) was not able to establish communication with the BCA Panel at start-up
request to establish communication with the BCA Panel is not granted within 25
seconds of the first request.
BCA Panel.
1) No application software/ incorrect software
3) No power to BCA Panel
Page 113 of 332

FAM Fault Isolation
84A220120FH Rev: D
4) BCA panel
5) LPS
6) SDIS
1. Check the Loco Config screen. Attempt to download software at least twice. For
more information on software loading, see Software Loading Procedures. If
attempt fails, go to step two. If successful, allow at least 1 minute to see a
software version appear on the Loco Config screen. Verify that the incident is
removed.
Comm loss was due to lack of software in the Slot24 card.
2. If software will not download or incident is not removed, go to the incident log
in the SDIS. Check to see if there are any other network comm. loss incidents
active along with this incident for other panels. If there are, execute Network
Trouble Shooting Guide for fault isolation.
3. If there are no other comm. loss incidents active, cycle BCCB. Go to the
go to step
4. If it is not active, go to the Network Monitor screen and verify that Network 0
and Network 1 reconfig's are not increasing, and verify that X's are present for
the
BCA Panel on both networks. If it is not on the network, this column will be blank.
If the network is healthy, release the loco for service.
4. If the panel has still not returned to the network, verify that all network and
power cables are connected and seated properly. If a cable isn't properly
connected,
re-seat it and verify that the panel has returned to the network per Network
Monitor screen.
5. If cables are intact, shut off BCCB. Open BCA panel. Examine the LED's on the
CPU card (Slot24) card.
6. If both LED's are red, the CPU card is in a continuous reset state and is not
receiving enough volts. Use fault isolation in step 8 to troubleshoot.
7. If one LED is lit, the CPU card is booted and running the CPU card (Slot 24) or
BCA backplane is suspected as the fault. Replace the CPU card. If fault is not
removed, replace the ARCnet card. If fault remains, replace the BCA Panel.
8. If both LED's are not lit, either the BCA is not receiving power or the CPU card
is defective.
Verify that Remote Sense Power Supply cables are connected and seated properly
between the BCA and LPS. Measure the +5V voltage at the LPS. It should be
greater than 5V. If it is not greater than 5V, the Remote Sense Power wiring is
defective. Troubleshoot per schematic. If no trouble is found, replace the LPS.
Verify that the CIO Power Supply cables are connected and seated properly between
the CIO and LPS. Remove connector G. Measure the +5V input power
between pin 5 and pin 10. If the voltage is not present, replace the LPS.
9. If voltage is present at the panel connectors, and incident is still active,
replace the CPU card. If fault remains, replace the BCA Panel.
Operator Message
Alarm Bell

53. Can't Crank
None
11-6701
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Loss Of Communications With BCCA While Running

(SDIS) lostmmunication with the BCA Panel.
This incident occurs when the control system (SDIS) looses communication with BCA
for 2.5 seconds
BCA Panel.
1) No application software/ incorrect software
3) No power to BCA Panel
4) BCA panel
5) LPS
6) SDIS
1. Check the Loco Config screen. Attempt to download software at least twice. For
more information on software loading, see Software Loading Procedures. If
attempt fails, go to step two. If successful, allow at least 1 minute to see a
software version appear on the Loco Config screen. Verify that the incident is
removed.
Comm loss was due to lack of software in the Slot24 card.
2. If software will not download or incident is not removed, go to the incident log
in the SDIS. Check to see if there are any other network comm. loss incidents
active along with this incident for other panels. If there are, execute Network
Trouble Shooting Guide for fault isolation.
3. If there are no other comm. loss incidents active, cycle BCCB. Go to the
go to step
4. If it is not active, go to the Network Monitor screen and verify that Network 0
and Network 1 reconfig's are not increasing, and verify that X's are present for
the
BCA Panel on both networks. If it is not on the network, this column will be blank.
If the network is healthy, release the loco for service.
4. If the panel has still not returned to the network, verify that all network and
power cables are connected and seated properly. If a cable isn't properly
connected,
re-seat it and verify that the panel has returned to the network per Network
Monitor screen.
5. If cables are intact, shut off BCCB. Open BCA panel. Examine the LED's on the
CPU card (Slot24) card.
6. If both LED's are red, the CPU card is in a continuous reset state and is not
receiving enough volts. Use fault isolation in step 8 to troubleshoot.
7. If one LED is lit, the CPU card is booted and running the CPU card (Slot 24) or
BCA backplane is suspected as the fault. Replace the CPU card. If fault is not
removed, replace the ARCnet card. If fault remains, replace the BCA Panel.
8. If both LED's are not lit, either the BCA is not receiving power or the CPU card
is defective.
Verify that Remote Sense Power Supply cables are connected and seated properly
between the BCA and LPS. Measure the +5V voltage at the LPS. It should be
greater than 5V. If it is not greater than 5V, the Remote Sense Power wiring is
defective. Troubleshoot per schematic. If no trouble is found, replace the LPS.
Verify that the CIO Power Supply cables are connected and seated properly between
the CIO and LPS. Remove connector G. Measure the +5V input power
between pin 5 and pin 10. If the voltage is not present, replace the LPS.
9. If voltage is present at the panel connectors, and incident is still active,
replace the CPU card. If fault remains, replace the BCA Panel.
Operator Message
Alarm Bell

53. Can't Crank
None
11-6702
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Partial Communication Loss With BCA

Informative Incident
36. Ready
None
Page 114 of 332

84A220120FH Rev: D
11-6703
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

36. Ready
None
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

36. Ready
None
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

36. Ready
None
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

36. Ready
None
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

36. Ready
None
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

36. Ready
None
Incident Message
FAM Incident Intent
Application Software Mismatch With BCA Panel Detected

To incidate operator/Maintanier that Locomotive is not ready as there is software
mismatch between BCA and SDIS panel.
This incident is logged when Actual appliaction software version at BCA Panel does
not match the expected version
This incident will be cleared once the apprioate software version have been loaded
to SDIS and BSS. On rebooting after the software has been downloaded this
incident would be cleared only when the maintainer would reset in apprioate level
after visual verfication.
1.Incorrect software downloaded to the panel.
2.Incomplete software downloaded.
3.Panel changed after software has been downloaded.
1.Visually verfy the version expected and actual version on the SDIS and BSS panel.
2.If the version matches then reset the fault in apprioate levels.
52. No Self Load
None
11-6704
11-6705
11-6706
11-6707
11-6708
11-8000
FAM Probable Cause
FAM Fault Isolation

Operator Message
Alarm Bell
11-8001
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operating Software Mismatch With BCA Panel Detected

To incidate operator/Maintanier that Locomotive is not ready as there is operating
software mismatch between BCA and SDIS panel.
This incident is logged when Actual operating software version at BCA Panel does
not match the expected version
This incident will be cleared once the apprioate operation software version have
been loaded to SDIS and BSS. On rebooting after the software has been
downloaded this incident would be cleared only when the maintainer would reset in
apprioate level after visual verfication.
1.Incorrect operation software downloaded to the panel.
2.Incomplete software downloaded.
3.Panel changed after software has been downloaded.
1.Visually verfy the operation software expected and actual version on the SDIS and
BSS panel.
2.If the version matches then reset the fault in apprioate levels.
Page 115 of 332

Operator Message
Alarm Bell
84A220120FH Rev: D

52. No Self Load
None
11-8002
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message
Alarm Bell
BCA Panel Configuration Mismatch

To incidate operator/Maintanier that Locomotive is not ready as there is
configuration mismatch between BCA and SDIS panel.
This incident is logged when Configuration on BCA panel does not match the
configuration on SDIS.
This incident will be cleared once the apprioate configuration have been loaded to
SDIS and BSS and rebooted.
1.Incorrect configuration file downloaded.
2.Incomplete/Corrupt config file downloaded.
3.Panel changed after configuration file has been downloaded.
1.Visually verfy the configuration file on the SDIS and confirm the same witn the
maintainer.
2.On verfication if the config file name is the same and the incident still log,
Load the configuration file again till the incidents does not appear after
rebooting.
52. No Self Load
None
11-8003
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message
Alarm Bell
BCA Panel configuration Not Recieved

To indicate that BCA panel is not configurated as all configuration data is not
aviable with BCA Panel
This incident is looged at start up if all configuration data is not recived by BCA
within 5min.
This incidents will clear automatically once all the data required to either panels
have been recevied.
1.Data loss while transmission.
2.Corruption of data while sending.
3.Required data has not been sent.
4.Transmission Sync has not been achieved.
1. Ensure proper connection of the communication channels connected to the
apporpiate ports.
2. Check the network health monitor.
90. Cycle BCCB To Activate New Configuration
None
20-0530
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
DBGs Manually Cutout

The purpose of this incident is to indicate when dynamic braking has been manually
cutout.
The Dynamic Braking Cutout Switch on the HMI is in the Out position.
The Dynamic Braking Cutout Switch on the HMI is in the In position.
1. No Defect - Cut out for train handling only.
2. Braking problems were experienced by operator so braking was manually cut out.
1. Find out why the Dynamic Braking was cutout by checking railroad reports and
checking the incident log.
2. Correct any other faults/incidents if found in the log.
3. Go to the Operator Switches screen (off the main screen) and cut the switch(es)
back in.
4. No Dynamic Brake
10. Dynamic Braking Grid(s) Manually Cutout
20-0607
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Locked Axle Bell is Disabled

To drive summary message to operator indicating that the locked axle alarm bell has
been disabled.
The locked axle switch on the HMI is in the OUT position.
The locked axle switch on the HMI is in the IN position.
This incident drives a message to the operator screen when the locked axle bell is
manually cutout from the Operators â€œSwitchesâ€ screen.
The locked axle alarm bell is cutout and will not ring in the event of a locked
axle fault.
Find out why the locked axle alarm bell was cutout by checking railroad reports and
Correct any other faults/incidents found in the log and then cut the locked axle
switch back in on the Operator â€œSwitchesâ€ screen.
Operator Message
36. Ready
20-0621
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
SS 1 Cut Out
The purpose of this incident is to indicate when #1 traction motor speed sensor has
been manually cutout.
The #1 Speed Sensor Cutout Switch on the HMI is in the Out position.
The #1 Speed Sensor Cutout Switch on the HMI is in the In position.
2. Traction motor problems were experienced by operator so speed sensor was
manually cut out.
1. Find out why the Speed Sensor was cutout by checking railroad reports and
3. Go to the Operator Switches screen (off the main screen) and cut the switch back
in..
55. Warning: Locked Axle Protection Reduced Due To Speed Sensor Cutout
20-0622
Incident Message
FAM Incident Intent
FAM Probable Cause
Operator Message
SS 2 Cut Out
manually cut out.
in..
Incident Message
FAM Incident Intent
SS 3 Cut Out
FAM Fault Isolation
20-0623
Page 116 of 332


FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D
manually cut out.
in..
20-0624
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
SS 4 Cut Out
manually cut out.
in..
20-0625
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
SS 5 Cut Out
manually cut out.
in..
20-0626
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
SS 6 Cut Out
manually cut out.
in..
20-1081
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Motor 1 Manually Cutout

The purpose of this incident is to indicate when #1 traction motor has been
manually cutout.
The #1 Traction Motor Cutout Switch on the HMI is in the Out position.
The #1 Traction Motor Cutout Switch on the HMI is in the In position.
Speed sensor problems, and the operator manually cut out the traction motor
Find out why the Traction Motor was cutout by checking railroad reports and the
incident log.
Correct any other faults/incidents in the log and then cut the motor back in using
the Operator â€œSwitchesâ€ screen on the engineer's SDIS.
11. Traction Motor(s) Manually Cutout
20-1082
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

manually cutout.
incident log.
20-1083
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

manually cutout.
incident log.
20-1084
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

manually cutout.
incident log.
20-1085
Page 117 of 332

Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D

manually cutout.
1Speed sensor problems, and the operator manually cut out the traction motor
incident log.
20-1086
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

manually cutout.
incident log.
30-0102
Incident Message
FAM Incident Intent
FAM Probable Cause
EAB Comm Loss

Indicate communication problem with EAB.
SDIS has lost communication with Electronic Air Brake for 5 seconds.
SDIS has communication with Electronic Air Brake for 1 second.
1. Electronic Air Brake circuit breaker open.
2. Multi-task circuit breaker open.
3. Cable between Electronic Air Brake and Protocol Translator(if equipped).
4. Electronic Air Brake(EPIC 3102) panel CCU (if equipped).
5. Electronic Air Brake(CCBI)panel BI(CRU) (if equipped).
FAM Fault Isolation
Operator Message
6. IHUB cards slots 12-15.

1. Check that Electronic Air Brake circuit
breaker and Multi-Task circuit breaker
are closed.
2. Verify power to appropriate electronic
air brake device:
a. CCU panel for EPIC 3102 equipped
locomotives.
b. BI(CRU) panel for CCBI equipped
locomotives.
c. IHUB panel for CCBII/LEB equipped
locomotives.
3. Check connections between the appropriate
device:
a. Check connections between CCU panel
connector CC1 and Protocol Translator
connector 2C for EPIC 3102 equipped
locomotives.
b. Check connections between BI(CRU)
panel connector 1 and Protocol
Translator connector 2C for CCBI
equipped locomotives.
4. If steps 1-3 above are ok then:
a. EPIC 3102 systems - replace Protocol
Translator slot 2 card, if problem
still exists, replace CCU.
b. CCBI systems - replace Protocol
Translator slot 2 card, if problem
still exists, replace BI(CRU).
c. CCBII/LEB systems - replace IHUB
54. No Battery Jog
30-0103
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
EAB Fault Detected

Indicate to maintainer that EAB has further troubleshooting information.
EAB has logged an internal fault.
EAB no longer has any active faults logged.
N/A
1. Through SDIS, establish remote session with EAB and troubleshoot per active
fault codes.
29. Electronic Air Brake (EAB) Problem
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Operator Message
EAB Status Message 2 Validity

Indicate problems with EAB data
EAB status message2 record containing invalid data was received
EAB status message2 record containing valid data was received
EPCU
BIPM
EBV
Cycle EPCU breaker
36. Ready
Incident Message
FAM Incident Intent
EAB Comm Loss Penalty

Indicate communication problem with EAB to operator.
30-0104
30-0105
Page 118 of 332


FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
SDIS has lost communication with Electronic Air Brake for 15 seconds.
SDIS has communication with Electronic Air Brake for 1 second.
N/A
1. Troubleshoot per FAM 30-0102.
28. Electronic Air Brake (EAB) Unit May Apply Brakes
30 Second
Incident Message
FAM Incident Intent
FAM Probable Cause
Brake Cylinder Applied While Locomotive Speed > 10 MPH

Alert operator of improper brake handle position.
Speed > 10 mph with brake pressure.
Brake pressure < 1 psi.
1. Loco left in brake
2. EAB
1. Check brake handle position (all locos in the consist).
2. Perform EAB self test.
63. To Silence Alarm, Release Brake Cylinder Pressure
Continuous
84A220120FH Rev: D
30-0107
FAM Fault Isolation

Operator Message
Alarm Bell
30-0109
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Airbrake Penalty Expected But Not Recieved

This incident detects the condition if airbrake doesnt apply penalty when
requested.
Could be due to internal SDIS or PTP or EAB issue.
When airbrake and SDIS agree on no-penalty for 10 seconds.
1. SDIS software lockup
2. PTP software lockup
3. Airbrake Software lockup
1.Run alerter function and force an alerter penalty
2. If airbrake doesnt apply penalty, cycle BCCB and MTB.
3. Re run the alerter function and let penalty apply. If penalty applied then it
was a software lockup. If it didnt apply then follow the below.
4. Change PTP.
5. Retry if still problem, Change SDIS.
6. Retry if still problem. Change EAB computer.
36. Ready
30-0112
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Brake Cylinder Applied While Locomotive Speed Is Greater Than Threshold

Alert operator of improper brake handle position.
Speed > 10 mph with brake pressure.
Brake pressure < 1 psi.
1. Loco left in brake
2. EAB
1. Check brake handle position (all locos in the consist).
2. Perform EAB self test.
63. To Silence Alarm, Release Brake Cylinder Pressure
Continuous
30-0113
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
EAB Feedback Does Not Match Setup Request

Setup the fault that provides information to the operator about the communication
error between EAB and ILC
After proper shutdown / startup, if there is communication between the EAB and the
ILC and the feed valve setting or the EAB mode does not match on the status
and command messages after 3 tries then the incident is TRUE
ILC and the feed valve settings and EAB mode match on the status and
command messages for 5 seconds after the mismatch has been declared then the
incident is cleared
1. Improper shutdown / startup
2. Loose connection in wiring between PTP and Air Brake
3. PTP
4. Air Brake
5. Air Brake firmware loaded incorrectly
6. SDIS software and / or configuration file loaded incorrectly
Since fault is logged within 15 seconds of first incorrect message this is for
information purposes only, refer to FAM 30-0114 isolation procedures to clear this
fault. However, 30-0113 is a L3 fault for engineering use only. Contact Train
Control engineering to isolate issue.
30-0114
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Persistent EAB Feedback Does Not Match Setup Request

Provide information to operator about communication error between EAB and ILC
ILC after 30-0113 has been logged and the feed valve setting or the EAB
mode does not match on the status and command messages then the incident is TRUE
ILC and the feed valve setting and EAB mode match on the status and
command messages for 5 seconds after the persistent mismatch has been declared then
the incident is cleared
1. Improper shutdown / startup
2. Loose connection in wiring between PTP and Air Brake
3. PTP
4. Air Brake
5. Air Brake firmware loaded incorrectly
6. SDIS software and / or configuration file loaded incorrectly
1. Open ABCB (or ABCB1 and ABCB2), BCCB, and MTB. Allow system to power down then
close all circuit breakers.
2. If fault persists, perform EAB self-test, if self-test fails, EAB firmware
should be re-installed until EAB self-test is passed.
3. If fault persists, check all wiring and connectors for broken or stressed wires
and loose pins between the PTP and POU.
4. If fault persists, verify Air Brake software and re-load if necessary.
5. If fault persists, verify SDIS software and configuration file and re-load if
necessary.
6. If fault persists, contact Train Control engineering.
29. Electronic Air Brake (EAB) Problem
30-0115
Incident Message
EAB Setup Memory updated unexpectedly due to EAB Status Message Mismatch
Page 119 of 332

FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D
Detect when air brake changes setup without being commanded.

This will log if the air brake setup in ILC memory does not match the actual setup
as reported by the EAB. It will not log in distributed power or following a
commanded setup change from the HMI screen.
After the memory in ILC has been updated to match the actual setup of the airbrake
with 5 second persistance.
1. Following a distributed power exit.
2. Air brake issue.
This is a L3 informative incident. Verify air brake is in desired setup, if not
change setup on HMI screen.
36. Ready
30-0408
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Blended Brake Comm Loss With EAB

Display Comm Loss between BCCA and EAB
Blended Braking is configured, system is Ready, Blended Braking active and BCCA
does not report comm valid with EAB for two seconds continuously
If Blended Braking is NOT active and BCCA reports valid comm with the EAB for three
consective frames
1. EAB panel
2. PTP
3. BSS panel
1. Verify EAB connections on connector 7
2. Verify PTP connections on connector 1
3. Replace BSS panel
4. Replace PTP panel
5. Replace EAB panel
157. No Blended Brake
None
34-0002
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Loss Of Communication With FTM

Determines whether the SDIS can communicate with the FTM
No messages are received from the FTM for 3 minutes
Several messages are received from the FTM within 30 seconds
1.
Faulty communications cable between the protocol translator and the FTM.
2.
Faulty Protocol Translator.
3.
Faulty FTM.
4. Arcnet wiring between the smart display and the protocol translator is
defective.
1. Ensure that the FTB is turned ON and power to the FTM is approximately 74 volts.
2. Examine the incident log on the diagnostics screen. If other incidents are
logged pertained to other third party boxes residing on the same terminal board,
first swap the terminal board with another one and check if the incident clears. If
the incident clears, proceed to step 18, else proceed to next step.
3. Navigate to the cab comm. screen on the smart display and check the network
status. Check if the link between the protocol translator and the FTM or the
link between the protocol translator and the smart display is down.
4. If the link between the protocol translator and the FTM is down proceed to next
step else proceed to step 9.
5. Check the communications cable between the FTM and the protocol translator.
6. If there is no problem found, proceed to step 9, else replace the cable and
proceed to next step.
7. Wait for approximately 4 minutes and check if the incident clears.
8. If the incident clears, proceed to step 18, else proceed to next step.
9. Replace the terminal board on the protocol translator.
12. Replace the FTM. Check if the incident clears.
14. Check the arcnet wiring between the protocol translator and the smart display.
15. If there is no problem found, proceed to step 13, else replace the cable and
proceed to next step.
17. If the incident clears, proceed to next step.
18. End Procedure.
36. Ready
34-0006
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Fuel Tank Monitor (FTM) Sensing Mechanism Bad

Determines if the FTM sensing mechanism is working properly
A message sent from the FTM indicates that the FTM sensor has failed
A message sent from the FTM indicates that the FTM sensor is working properly
1. Failed pressure sensor
1. Replace the FTM
36. Ready
39-0001
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
GPS Receiver Failed Self Test

Determines whether the GPS receiver hardware is functioning properly
GPS receiver self test result reported as failed

GPS receiver self test result reported as good
1. Faulty GPS receiver.
1. Cycle BCCB and MTB circuit breakers. Shut off BCCB first and then MTB. Turn back
on in opposite order (MTB then BCCB). If incident resets and does
not reoccur within 10 minutes release locomotive for service.
2. Inspect GPS receiver to see if power light is on. If not, inspect power cabling
from MTB breaker to GPS receiver.
3. If power light is present but still have communication loss inspect cabling from
protocol translater 3 card (PT3, slot 4) to GPS receiver.
4. If no cabling issues found, swap PT3 with PT2 (slots 3 and 4). If the PT3 card
was bad you should now have problems with the trainline modem (if so
equipped) and the GPS should be ok. If GPS now works, change faulty PT card.
5. If still having problems, replace GPS receiver.
Note: Failure of the GPS system may reduce the reliability of tunnel performance
and HP_Available while operating in severe tunnels
36. Ready
39-0002
Incident Message
Loss Of Communications With GPS Receiver
Page 120 of 332

FAM Incident Intent

FAM Probable Cause
84A220120FH Rev: D
Determines whether the SDIS can communicate with the GPS receiver
No messages are received from the GPS receiver for 30 seconds
Several messages are received from the GPS receiver (takes approximately 15 seconds
to clear if working properly)
1. Faulty communications cable between the protocol translator and the GPS
receiver.
2. Faulty protocol translator.
3. Faulty GPS receiver.
FAM Fault Isolation
4. Faulty ARCNET wiring between smart display and protocol translator.

NOTE: Improper Power Cycling and Very Low Batteries can cause the GPS to loose
communication. The only way to recover the GPS module is to cycle BCCB
and MTB.
1. Cycle BCCB and MTB. BCCB must be shut off first, then once Smart Displays boot
down shut off MTB. Turn the breakers back on in the reverse order. If the
incident resets and remains reset for 5 minutes release locomotive for service.
2. Inspect GPS module to see if power if the power light is on. If the power light
is not on, check wiring from MTB to Radio Power Supply (RPS) to GPS Module.
If power light is on, proceed.
a. If wiring checks ok, measure the 15V output from RPS to GPS. Replace RPS is
voltage is out of range.
b. If RPS output voltage is ok to GPS, replace GPS module.
3. Examine incident log on the diagnostics screen.
a.
b.
c.
If there are numerous communication incidents for various panels on the locomotive
this is likely an ARCNet issue. Please refer to ARCNet troubleshooting
guide (84A200750NW)
Units with PT Cards: If Loss of Comm with PT3 and / or other incidents are logged
pertaining to other third party boxes residing on the same protocol
translater card (MCP, Distributed Power), first swap the PT3 card with another one
and check if the incident clears and follows the card. If the incident
clears replace the PT card.
Units with PTP: If Loss of Comm with PTP and / or other incidents are logged
pertaining to other third party boxes residing on the same protocol translater
panel, replace entire PTP.
4. Navigate to the "Cab Comms" screen (Loco Monitor > Network > Cab Comms) on the
Smart Display and check the network status to see if the link between the
protocol translator and the GPS is down. If the link between the protocol
translator and the GPS is down proceed to the next step, else proceed to step 6.
5. Check the communications cable between the GPS and the protocol translator.
Replace / repair the cables if any issues are found and check to see if the
incident
clears.
6. . If incident is still logging, only the GPS channel on the PT3 card (or panel)
may be bad, replace the PT3 card (or panel). Check to see if the incident clears.
7. If GPS communications still do not recover, replace the GPS and check to see if
the incident clears.
Operator Message
36. Ready
39-0006
Incident Message
FAM Incident Intent
FAM Probable Cause
GPS Antenna Error

Determines whether the GPS antenna is connected and working properly
Antenna current is measured as either short or open
Antenna current is measured as good
1. Faulty wiring/connection from GPS receiver to GPS antenna
2. GPS antenna not working properly
3. GPS receiver not working properly
FAM Fault Isolation
1. Inspect antenna connection on GPS Receiver. If there is a connection problem

repair/replace needed parts and inspect incident log to see if incident clears.
3. Inspect wiring from receiver to antenna looking for loose connections and
possible electrical shorts. If there is a wiring/connection problem repair/replace
needed parts and inspect incident log to see if incident clears.
4. If incident does not clear, replace GPS antenna and inspect incident log to see
if incident clears.
5. If incident does not clear, replace GPS receiver and inspect incident log to see
if incident clears.
Operator Message
36. Ready
39-0007
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
GPS Model Not Identified

Determines whether the connected GPS receiver is a compatible device
The current GPS receiver is not identified as a compatible device
The GPS receiver model is identified as a compatible device
1. GPS receiver is not a compatible device
1. Replace current GPS receiver with a known good receiver
Operator Message
36. Ready
51-0001
Incident Message
FAM Incident Intent
Check MU Setup: (T/L 8 & 9 High)

Protect the reverser from throwing under load
This fault is logged if - Locomotive Directional Trainlines 8 and 9 (FO and RE) are
both above 40 volts
AND
- The GF Trainline (TL6), -OR- The Dynamic Brake Setup (B) Trainline (TL17), -OR-
The Battery Jog Request input
Are above 40 volts
Fault condition is no longer present
Page 121 of 332

FAM Probable Cause
FAM Fault Isolation
84A220120FH Rev: D
1. The MU trainlines 6, 17, 8 or 9 are being energized from more than one
locomotive. 2. A wiring error has energized FO, RE, GF, B or KG incorrectly. 3. The
interlocking of the Master Controller has failed allowing the Reverse handle to
throw while the Throttle or Brake handle are not in idle. 4. The Controller panel
(BCA) inputs are correct, but the Controller panel (BCA) FE198/FE102 card or
backplane has failed and has falsely logged this fault. NOTE: THIS FAULT IS
MOST LIKELY INTERMITTENT. THE FAULT WILL PROBABLY NOT BE PRESENT WHEN YOU TRY TO
FIX IT.
1. If a 51-0006 fault has occurred, correct it before working on this fault.
Correcting the 51-0006 fault may also correct this fault.
2. Monitor inputs to Controller panel (BCA) TL8,9 (RE) MP 25049, TL9,8 (FO) MP
25050, TL6 (GF) MP 25048,TL17 (B) MP 25037 and TL21 (KG) MP
25038, using SDIS, by operating Reverser Handle.
3. Inspect MU Connector and cable for damage. If unit was running in a trail
position at the time of fault, simply reset the fault and restore locomotive to
service.
4. Check at Terminal Boards to see if the trainline voltages correspond with the
various modes of operation. If the voltages are incorrect, and MU jumpers are
installed, remove the jumpers. Check again to see if they are correct. Identify any
trainlines with incorrect voltages. Refer to the schematic for detailed wiring of
the trainline circuits. Correct wiring or replace the failed part which is causing
a wrong trainline voltage.
5. If the trainlines are properly energized, reset the fault. Set up the locomotive
to operate in motoring and then in braking. Try to reproduce the fault condition
by moving the reverse handle. If you can make the fault occur, trace the FO, RE,
GF, B, & KG circuits to find out which circuit is the cause. Repair it.
WARNING: DO NOT MOVE THE LOCOMOTIVE BY MISTAKE.
6. If the trainlines are correct, and the computer still logs this fault, check the
FO, RE, GF, B & KG wiring to the Controller panel (BCA).
7. Replace the Controller panel (BCA) FE198/FE102 card in Slot 17 or the whole
Controller panel (BCA) if it still logs this fault and the FO, RE, GF, B & KG
inputs are correctly energized. After replacing the Controller panel (BCA), reapply
power. Be sure that this fault is no longer logged.
REVERSER and BRAKE CONTROL HANDLES
MODE
IDLE
IDLE or REVERSE BATTERY JOG
IDLE or FORWARD BATTERY JOG
IDLE
IDLE
REVERSE BRAKE SETUP
FORWARD BRAKE SETUP
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE and SELF LOAD
REVERSE MOTOR
FORWARD MOTOR
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
REVERSE BRAKE
FORWARD BRAKE
IDLE
IDLE
IDLE
IDLE
IDLE
Operator Message
Alarm Bell
6
GF
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
21
KG
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
TRAINLINE
17
B
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
9,8
FO
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
8,9
RE
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
FUNCTION
Control Off (Idle)
Idle or Rev BJ
Idle or For BJ
Control Off (Idle)
Control Off (Idle)
Dynamic Braking Setup, Reverse
Dynamic Braking Setup, Forward
Control Off (Idle) see fault 51-0001
Control Off (Idle)
Control Off (Idle)
Control Off (Idle)
Control Off (Idle)
Control Off (Idle)
Control Off (Idle)
N1-8, no load and Self Load
Motoring, Reverse
Motoring, Forward
Control Off (Idle)
Control Off (Idle)
Control Off (Idle)
Control Off (Idle)
Dynamic Braking, Reverse
Dynamic Braking, Forward
Idle, see faults 51-0001 and 51-0004
36. Ready
30 Second
51-0002
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Bad Input From EC Switch

Indicate EC Switch is faulty
This fault is logged if the Controller panel (BCA) received input voltages from the
EC Switch
which are invalid (see Table). Each of the four signals that the EC Switch may send
to Controller panel (BCA) represents a switch position ISOLATE, RUN, START, and
JOG. Only one is expected to be high at any given time.
PO Volts must be > 45 for this fault to log.
For the more-than-one-high case, the fault logs immediately after de-bounced inputs
are detected; for the no-high-input case, the fault logs after 60 seconds of
continuous no inputs to avoid nuisance trips.For the no-High-input case, Controller
panel (BCA) passes through the actual debounced input immediately; this will
inhibit any Mode Call since no Mode Call template will be matched.
Throttle returned to Idle and Fault Condition is no longer present.
1. A wiring error has energized a second or de-energized all EC Switch signal
lines. 2. The EC Switch has failed and indicates more than one position. The EC
Switch signals are correct, but the Controller panel (BCA) has failed and has
falsely logged a fault that more than one EC Switch position was indicated.
NOTE: A BAD INPUT FROM THE EC SWITCH MIGHT HAVE BEEN
MOMENTARY. THE FAULT MAY BE GONE WHEN YOU TRY TO FIX IT.
1. Monitor inputs to Controller panel (BCA) RUN (MP 25025), ISOLATE (MP 25024),
START (MP 25026) and JOG (if applicable) using SDIS.
2. Move EC switch to different positions to find out if the Controller panel (BCA)
reads the proper EC Switch input voltages.
3. Reset this fault. If it will not reset, check the EC Switch input voltages to
the Controller panel (BCA). If more than one or no input is energized check the
wiring and/or switch to find the cause. Fix it. If you can reset this fault, try
various positions of the EC switch. If one of the positions causes this fault,
check the
EC Switch inputs to the Controller panel (BCA) for that position. correct wiring or
replace switch. Check voltages at EC and at Controller panel (BCA) per table
below:
1 = more than 40 volts, 0 = less than 25 volts (referenced to EN)
Replace the Controller panel (BCA) if the EC Switch inputs to the Controller panel
(BCA) are correct and the computer still logs this fault. After replacing the
Controller panel (BCA) and reapplying power, verify that this fault is no longer
logged.
MODES
ALLOWED
IDLE. Self Test
F or R JOG, ST
RUN
0
0
EC SWITCH
SIGNAL
ISOLATE
START
ECS CONTACTS
0
0
0
0
JOG
0
1
FUNCTION
Idle, see fault 51-0002
Battery Jog
Page 122 of 332
Crank, Crank Setup,

SelfTest
IDLE. Self Test
ISOLATE
IDLE. Self Test
IDLE. Self Test
IDLE. Self Test
Motor, Brake, Self Load,
ST
IDLE. Self Test
IDLE. Self Test
IDLE. Self Test
IDLE. Self Test
IDLE. Self Test
IDLE. Self Test
IDLE. Self Test
Operator Message
Alarm Bell
84A220120FH Rev: D
Idle, Crank, or Crank Setup
0
0
0
0
0
1
0
1
1
1
1
0
1
0
0
1
1
0
1
0
1
0
1
0

Isolated
All powered modes and ST
1
1
1
1
1
1
1
0
0
0
1
1
1
1
0
1
1
0
0
1
1
1
0
1
0
1
0
1


52. No Self Load
53. Can't Crank
30 Second
51-0003
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Bad Thrtl DV No BV
Indicate an invalid throttle
This fault is logged if - An invalid throttle or trainline Notch (A,B,C,D) input
(see Table) is
detected AND
- 4.0 seconds has passed.
This fault can wait 4 seconds since no valid Throttle Command will be present and
the control will default to Idle. For the same reason, no restrictions are set.
1. MU Jumper problem caused an invalid Throttle Input.2. Wiring problem between MU
Lines, Throttle and Controller panel (BCA).3. Controller panel (BCA) or
card problem.
1. Monitor inputs to Controller panel (BCA) DV (MP 25044), CV (MP 25045), BV (MP
25046) and AV (MP 25047) using SDIS.
2. Move Throttle to different positions to check inputs to Controller panel (BCA),
if inputs are correct, then the problem was most likely in the MU jumper or
intermittent.
3. If inputs are bad, troubleshoot wiring between the MU and Throttle inputs
(AV,BV,CV,DV) to the Controller panel (BCA).
a. BCCB breaker OFF. Disconnect Controller panel (BCA) connector C.
b.
With a voltmeter, advance the Throttle one Notch at a time measuring, in each
Notch, the voltage to the Controller panel (BCA) from BV to B43
and DV to B49.
c.
If voltages are all correct, and the fault still logs, replace the FE198/FE102 card
in Slot 17 or the Controller panel (BCA). If the voltages are
incorrect, troubleshoot the wiring or Throttle.
NOTCH
IDLE and N1
STOP
N3
INVALID - IDLE
INVALID - IDLE
INVALID - IDLE
N7
N5
N2
INVALID - IDLE
N4
INVALID - IDLE
INVALID - IDLE
INVALID - IDLE
N8
N6
Operator Message
Alarm Bell
15
AV
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
TRAINLINE
12
7
BV
CV
0
0
0
0
0
1
0
1
1
0
1
0
1
1
1
1
0
0
0
0
0
1
0
1
1
0
1
0
1
1
1
1
3
DV
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
fault 51-0003
fault 51-0278
fault 51-0278
fault 51-0279
fault 51-0003
fault 51-0278
fault 51-0278
36. Ready
30 Second
51-0004
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Check MU Setup:(T/L 6_17_&_21 High)

Protect the Motor/Brake Switch (BKT) from throwing under load
This fault is logged if
- GF, Trainline 6 (Motoring), -AND EITHER- B, Trainline 17 (Dynamic Brake Setup), -
OR- KG, Indirectly driven by BG, Trainline 21 (Brake Start)
Are High.This means that the data displayed in the Parameter will not represent the
actual trainline inputs.
Controller panel (BCA) should pass through the actual de-bounced input immediately;
this will inhibit
any Mode Call since no Mode Call template will be matched.
Throttle returned to Idle and Fault Condition is no
longer present
. MU trainlines 6, 17, and/or 21 are being energized from more than one locomotive.
2. A wiring error has energized GF, B, & KG simultaneously. 3. A
component or device failure has energized GF, B, & KG simultaneously. 4. The
Controller panel (BCA) inputs are correct, but the Controller panel (BCA) has
failed and has falsely logged this fault.
25038, using SDIS.
2. Check Terminal Boards with your voltmeter to see if the three trainlines are 64
volts or more.
a. If only trainline 6 or the trainline 17 + 21 combination is above 64 volts, go
to step 3.
b. If all 3 trainlines are above 64 volts.
1. If MU jumpers are installed, remove them.
2. If the trainlines are energized with the jumpers removed, go to step 2.
3. If you find all three trainlines are energized with the jumpers removed,
determine which trainline is energized when it should not be. Refer to the
schematic for detailed wiring of the trainline circuits. Correct wiring or replace
failed component which is incorrectly energizing the trainline.
3. Move Throttle Handle (TH) to different positions and check that the Controller
panel (BCA) reads trainlines correctely.
4. If the trainlines are energized normally, reset this fault. Set up the
locomotive to operate. Move back and forth from motoring to braking to try to
reproduce the
fault condition.
Page 123 of 332

84A220120FH Rev: D
Note: TH must move from IDLE to N1 to cause BKT to throw. Quickly go back to IDLE
to keep locomotive from moving.
a. If the fault can be made to occur, trace the GF, B, & KG circuits to find out
which circuit is getting energized when it shouldn't be. Then repair it.
b. If the fault can not be reset, go to step 6.
WARNING: DO NOT ALLOW THE LOCOMOTIVE TO MOVE UNLESS TRACK IS CLEAR.
Operator Message
Alarm Bell
5. If the three trainlines are not all energized, and the computer still logs this
fault; check the GF, B, & KG wiring to the Controller panel (BCA).
6. If the three trainlines are energized normally, and the computer still logs this
fault, check the GF, B & KG wiring to the Controller panel (BCA).
a. Open BCCB and LCCB, pull plug C at Controller panel (BCA). Inspect both halves
of connector for pushed back terminals. Close BCCB and LCCB.
b. Check GF (pin 45 in the plug). It should be above 64 volts with TH in Motor.
Otherwise it should be zero.
c. Check B (pin 58 in the plug). It should be above 64 volts with BH in Brake Set
up or Brake. Otherwise it should be zero.
d. Check KG (pin 60 in the plug). It should be above 64 volts with BH in Brake.
Otherwise it should be zero.
e. Open BCCB and LCCB before reconnecting plug C.
7. Replace the Controller panel (BCA) if the GF, B, & KG inputs are not
simultaneously energized and the computer still logs this fault. After you replace
the
Controller panel (BCA), make sure this fault does not repeat.
52. No Self Load
30 Second
51-0006
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
T/L 8 And 9 Changed While Loaded

Prevent changing the reverser under load or damaging traction motors from high-
speed plugging
This fault is logged if the digital inputs see a change in the Locomotive
directional
Trainlines while either the Motoring Trainline or the Dynamic Brake Setup Trainline
is high
Throttle returned to Idle and Fault Condition is no
longer present
1. An intermittent open in TL 8 or 9 pin will cause this fault to log. 2. The MU
trainlines 6, 17, 8 or 9 are being energized from more than one locomotive. 3.
A wiring error has energized FO, RE, GF, B or KG incorrectly. 4. The interlocking
of the Master Controller has failed allowing the Reverse handle to throw
while the Throttle or Brake handle are not in idle. 5. The Controller panel (BCA)
inputs are correct, but the Controller panel (BCA) FE198/FE102 card or
backplane has failed and has falsely logged this fault.
25038, using SDIS.
2. Move Reverser Handle (RH) to different positions to check inputs to Controller
panel (BCA) are correct.
3. Inspect MU Connector and cable for damage. If unit was running in a trail
position at the time of fault, simply reset the fault and restore locomotive to
service.
4. Check at Terminal Boards to see if the trainline voltages correspond with the
various modes of operation. If the voltages are incorrect, and MU jumpers are
installed, remove
the jumpers. Check again to see if they are correct. Identify any trainlines with
incorrect voltages. Refer to the schematic for detailed wiring of the trainline
circuits. Correct wiring or replace the failed part which is causing a wrong
trainline voltage.
5. If the trainlines are properly energized, reset the fault. Set up the locomotive
to operate in motoring and then in braking. Try to reproduce the fault condition
by moving the reverse handle. If you can make the fault occur, trace the FO, RE,
GF, B, & KG circuits to find out which circuit is the cause. Repair it.
Operator Message
6. If the trainlines are correct, and the computer still logs this fault, check the
FO, RE, GF, B & KG wiring to the Controller panel (BCA).
7. Replace the Controller panel (BCA) FE198/FE102 card in Slot 17 or the whole
Controller panel (BCA) if it still logs this fault and the FO, RE, GF, B & KG
inputs are correctly energized. After replacing the Controller panel (BCA), reapply
power. Be sure that this fault is no longer logged.
36. Ready
51-0007
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Bad Dynamic Brake Setup

Prevent changing the motor/brake switch (BKT) under load
This fault is logged if the following conditions exist for 1 second.
1. Locomotive Directional Trainlines 8 and 9 (FO and RE) are both sensed low.
2. The Dynamic Brake Setup Trainline (B, TL17) is sensed high.
1. More than one locomotive is energizing the MU trainlines 6, 17, 8, or 9. 2. A
wiring error has incorrectly energized FO,RE,GF,B,or KG. 3. The interlocking
of the Master Controller has failed allowing the Throttle or Brake handle to be
advanced while the Reverser handle is in the centered position. 4. The Controller
panel (BCA) inputs are correct, but the Controller panel (BCA) has failed and
falsely logged this fault.
1. Monitor inputs to Controller panel (BCA) TL8 (RE) MP 25049, TL9 (FO) MP 25050,
TL6 (GF) MP 25048,TL17 (B) MP 25037 and TL21 (KG) MP 25038,
using SDIS.
2. Check at Terminal Boards to see if the trainline voltages correspond to the
operating mode. If the trainline voltages are incorrect, and MU jumpers are
installed, remove the jumpers. Check voltages again. Identify trainlines with
incorrect voltage after you remove jumpers. Refer to the schematic for detailed
wiring
of the trainline circuits. Correct wiring or replace the failed part which is
causing the error.
3. If the trainlines are properly energized, reset this fault. Set up the
locomotive to operate in motoring and then in braking. Try to reproduce the fault
condition.
Try to advance the Throttle and Brake handles while the Reverser handle is in
neutral. If you can make the fault occur, trace the FO, RE, GF, B, & KG circuits to
find out which circuit is energized wrong. Repair it.
Operator Message
Alarm Bell
4. If the computer still logs this fault and the trainlines are correct, check the
FO, RE, GF, B, & KG wiring to the Controller panel (BCA).
5. Replace Controller panel (BCA) if the FO, RE, GF, B & KG inputs are correctly
energized and the computer still logs this fault. After you replace the
Controller panel (BCA), reapply power. Check that this fault is no longer logged.
4. No Dynamic Brake
30 Second
51-0009
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Load Limited: Dirty Eng Air Fltr

Indicate a clogged filter
This fault is logged if the Engine Air Filter Pressure Switch (EFPS) signal is
absent for a period of 30 Seconds and PO volts > 45.
1. The Engine air filters are plugged with snow, dirt, or debris. 2. The Engine Air
Filter Pressure Switch (EFPS) has failed. 3. The wiring for the EFPS has failed.
4. The Controller panel (BCA) has failed and has falsely logged a fault that the
engine air filters are plugged.
Not applicable if ECU present
For Locomotives with EGU having Engine Air Filter Pressure Siwtch (EFPS)
1. Check the engine air filters. If they are dirty replace them.
2. If the locomotive was running in an area of heavy snow, the filters could have
been clogged with snow. Then when the
loco reached the shop, this snow could have melted and now function normally. If
this was the case and the loco is equipped with summer/winter doors, be sure
they are in the correct position. Then skip to step 7 and self load the locomotive.
3. Verify wiring to Controller panel (BCA) and that the Controller panel (BCA)
properly reads this input.
4. If this fault reoccurs with clean air filters, check the pressure drop across
the filters. If the pressure drop is less than 14" of water, check the EFPS to make
sure it
is closed. If EFPS is not closed replace the EFPS.
5. If the EFPS is closed, check the wiring associated with the EFPS. Repair any
faults in the wiring.
Page 124 of 332

Operator Message
84A220120FH Rev: D
6. Replace Controller panel (BCA) if the input is energized at the Controller panel
(BCA) connector C37 and the computer still logs this fault. After replacing the
Controller panel (BCA), reapply power. Verify that this fault is no longer logged.
7. As a final check for proper operation, run the locomotive at Notch 8 full load
and verify that this fault does not occur.
22. HP Limited
51-0010
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
GF Pickup Bad In SelfTest 405

Indicates Alternator Field Contactor (GF) not picking up
This fault is logged during Self Test after 4.0 seconds if Controller panel (BCA)
does not get expected
feedback from the Alternator Field Contactor
Fault Condition is no longer present
1. Faulty contactor coil or wiring to coil.
2. Faulty contactor position feedback or wiring from feedback.
3. If this contactor requires air pressure, lack of air pressure.
4. Faulty FE101/FE187 driver card in Controller panel (BCA).
5. Faulty FE102/FE198 input card in Controller panel (BCA).
6. Faulty Controller panel (BCA).
1. Run Selftest for this contactor.
2. Watch the contactor as see if it actually picks up (energizes).
3. If it does NOT pick up, check wiring from the corresponding Controller panel
(BCA) connector pin to the contactor coil.
a. Verify that the Common (N wire) from the Controller panel (BCA) is connected.
b. Verify that there is battery volts to the high-side of the contactor coil when
trying to energize it.
c. Determine which driver common this contactor utilizes and verify that the
corresponding FE101/FE187 gate drive feed wire is connected:
A13 74 Vdc Pstv EP/BCCB+ (IPS)
B13 BCCB + (IPS)
B19 74 Vdc Pstv required for LCN drivers
B20 74 Vdc Pstv required for N drivers
B23 74 Vdc Pstv required for GS+,GS- FPN drivers
B25 74 Vdc Pstv required for ECN drivers
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
A54 74V Rtn for DVN drivers
A55 74V Rtn for ECN drivers
A56 74V Rtn for FPN drivers
A58 74V Rtn for LCN1 drivers
A62 74V Rtn for N drivers
d. If wiring checks OK, try to jumper the coil manually to get it to energize.
e. If it still does not pick up, the contactor coil is bad. Replace the contactor
or coil.
f. If the contactor picks up when manually jumpered, replace the appropriate
FE101/FE187 card
(the electrical schematic shows which slot the FE101/FE187 card is in by a S1, S2,
â€¦ S9 designation next to the driver on the schematic).
g. If FE101/FE187 replacement does not work, change the Controller panel (BCA) as
the backplane must be bad.
h. If it still does not pick up, go back to start of step 3.
4. If it DOES pick up, but the fault logs anyway:
a. Check that the contactor is really picked-up (no foreign objects between Tips or
between armature and base). The contactor must energize and wipe the
contactors for the position feedback to close. Simply pushing the contactor closed
with your hand or foot may not satisfy the position feedback.
b. If the contactor is positively picked up, check with a voltmeter whether the
position feedback interlock has closed and whether there is 74 volts to one side of
the
position sensor. If it has not closed, adjust the position feedback per Maintenance
Instructions. If no 74V troubleshoot wiring.
c. If the position feedback is OK, check wiring from the position feedback to the
appropriate Controller panel (BCA) connector pin input.
d. If feedback signal is NOT OK to the connector, troubleshoot wiring. Make sure
there is 74V to the position sensor.
e. If feedback wiring to Controller panel (BCA) is OK, replace the corresponding
FE102/FE198 input card.
f. If FE102/FE198 replacement does not work, change the Controller panel (BCA) as
g. If it still does not register the feedback, go back to start of step 4.
36. Ready
51-0011
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
GF Dropout Bad In SelfTest 405

Indicates Alternator Field Contactor (GF) not dropping out
does not get expected feedback from the Alternator Field Contactor (GF).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
Page 125 of 332

Operator Message
84A220120FH Rev: D
the
36. Ready
51-0012
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
AGFR Pickup Bad In SelfTest 411

Indicates Auxiliary Generator Field Relay (AGFR) not picking up
feedback from the Auxiliary Generator Field Relay (AGFR).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0013
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
AGFR Dropout Bad In SelfTest 411

Indicates Auxiliary Generator Field Relay (AGFR) not Dropping out
feedback from the Auxiliary Generator Field Relay (AGFR).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
Page 126 of 332

Operator Message
84A220120FH Rev: D

FE101/FE187 card
the
36. Ready
51-0014
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
P1 Pickup Bad In SelfTest 300

Power Contactor-1 (P1) not picking up
feedback from Power Contactor-1 (P1).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0015
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
P1 Dropout Bad In SelfTest 300

Power Contactor-1 (P1) not dropping out
feedback from Power Contactor-1 (P1).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
Page 127 of 332

Operator Message
84A220120FH Rev: D

or coil.
FE101/FE187 card
the
36. Ready
51-0016
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

feedback via Power Contactor-2 (P2).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0017
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

feedback from Power Contactor 2 (P2).
B13 BCCB + (IPS)
Page 128 of 332

Operator Message
84A220120FH Rev: D

A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0018
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0019
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Page 129 of 332

Operator Message
84A220120FH Rev: D
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0020
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0021
Incident Message
FAM Incident Intent

Page 130 of 332

FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D

B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0022
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0023
Page 131 of 332

Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D

B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0024
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
Page 132 of 332

Operator Message
84A220120FH Rev: D

36. Ready
51-0025
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0026
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
BKT-(M) Pickup Bad In SelfTest 600

Braking Switch Motor (BKT(M)) not picking up
feedback from the Braking Switch Motor (BKT (M)). This fault is not logged from
Manual Self Test
1. No control air pressure. 2. Welded power contacts. 3. Defective MOTOR magnet
valve (stuck open). 4. Defective BKT position indicating interlock or
associated wiring. 5. No continuity between MOTOR coil(+) and MC master controller
6. No continuity between MOTOR coil(-) and Controller panel (BCA)
controller. 7. Defective MOTOR coil or magnet valve. 8. Defective Controller panel
(BCA).
1. Manually cycle BKT to test for presence of air pressure and condition of magnet
valves by pressing and releasing MOTOR and BRAKE magnet valve
armatures.
NOTE: CONTINUE ONLY IF NO PROBLEMS FOUND IN PREVIOUS STEP.
Operator Message
2. Return BKT to BRAKE position by pressing BRAKE magnet valve armature. Run Manual
SelfTest 600 and visually check BKT state.
a. If BKT is in the MOTOR position then check BKT position indicating interlocks
and associated wires.
b. If BKT is in the BRAKE position then check MOTOR coil and associated wires.
3. If no trouble found, check adjustment of position indicator per Locomotive
Service Manual.
4. If problem repeats when Automatic Selftest is run, but no problems are found
above, the Controller panel (BCA) is failed.
36. Ready
51-0027
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
BKT-(B) Pickup Bad In SelfTest 603

Braking Switch Brake (BKT(B)) not picking up
feedback from theBraking Switch Brake (BKT(B)). This fault is not logged from
Manual Self Test
1. No control air pressure. 2. Welded power contacts. 3. Defective BRAKE magnet
valve (stuck open). 4. Defective BKT position indicating interlock or
associated wiring. 5. No continuity between BRAKE coil(+) and MC master controller.
6. No continuity between BRAKE coil(-) and Controller panel (BCA)
controller. 7. Defective BRAKE coil or magnet valve. 8. Defective Controller panel
(BCA).
1. Manually cycle BKT to test for presence of air pressure and condition of magnet
valves by pressing and releasing MOTOR and BRAKE magnet valve
armatures.
2. Return BKT to MOTOR position by pressing MOTOR magnet valve armature. Run Manual
SelfTest 603 and visually check BKT state.
Page 133 of 332

84A220120FH Rev: D
a. If BKT is in the BRAKE position then check BKT position indicating interlocks
b. If BKT is in the MOTOR position then check BRAKE coil and associated wires B,
BKB, N, etc.
Service Manual.
Operator Message
36. Ready
51-0028
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
REV-(F) Pickup Bad In SelfTest 606

Reverser(REV-(F) )not picking up
feedback from the Reverser (REV (F)).
Fault Condition is no longer
present
1. No control air pressure. 2. Welded power contacts. 3. Defective FORWARD magnet
valve (stuck open). 4. Defective REV position indicating interlock or
associated wiring. 5. No continuity between FORWARD coil(+) and MC master
controller. 6. No continuity between FORWARD coil(-) and Controller panel
(BCA). 7. Defective FORWARD coil or magnet valve. 8. Defective Controller panel
(BCA).
1. Manually cycle REV to test for presence of air pressure and condition of magnet
valves by pressing and releasing FORWARD and REVERSE magnet valve
armatures.
2. Return REV to REVERSE position by pressing REVERSE magnet valve armature. Run
Manual SelfTest 606 and visually check REV state.
a. If REV is in the FORWARD position then check REV position indicating interlocks
b. If REV is in the REVERSE position then check FORWARD coil and associated wires.
Service Manual.
Operator Message
36. Ready
51-0029
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
REV-(R) Pickup Bad In SelfTest 609

Reverser(REV-(R) )not picking up
feedback from the Reverser (REV (R)).
present
1. No control air pressure. 2. Welded power contacts. 3. Defective REVERSE magnet
valve (stuck open). 4. Defective REV position indicating interlock or
associated wiring. 5. No continuity between REVERSE coil(+) and MC master
controller. 6. No continuity between REVERSE coil(-) and Controller panel
(BCA). 7. Defective REVERSE coil or magnet valve. 8. Defective Controller panel
(BCA)
1. Manually cycle REV to test for presence of air pressure and condition of magnet
valves by pressing and releasing FORWARD and REVERSE magnet valve
armatures.
2. Return REV to FORWARD position by pressing FORWARD magnet valve armature. Run
Manual SelfTest 609 and visually check REV state.
a. If REV is in the REVERSE position then check REV position indicating interlocks
and associated wires ARR, BRR, etc.
b. If REV is in the FORWARD position then check REVERSE coil, LBTS and associated
wires.
Service Manual.
Operator Message
36. Ready
51-0030
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
LBS1 Pickup Bad In SelfTest 318

Self-Load Box Switch 1 (LBS1) not picking up
feedback from the Self-Load Box Switch 1 (LBS1).
present
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
Page 134 of 332

Operator Message
84A220120FH Rev: D

the
36. Ready
51-0031
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
LBS1 Dropout Bad In SelfTest 318

Self-Load Box Switch 1 (LBS1) not dropping out
present
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0032
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

present
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
Page 135 of 332

Operator Message
84A220120FH Rev: D

or coil.
FE101/FE187 card
the
36. Ready
51-0033
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

present
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0034
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

present
Page 136 of 332

Operator Message
84A220120FH Rev: D
B13 BCCB + (IPS)

A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0035
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

present
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0036
Incident Message
FAM Incident Intent
FAM Probable Cause

present
Page 137 of 332

84A220120FH Rev: D

FAM Fault Isolation
Operator Message

B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0037
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

present
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0038
Incident Message
DB1_2_3 Pickup Bad In SelfTest 360
Page 138 of 332

FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D
Dynamic Brake Contactors 1,2,3 (DB1,2,3) not picking up

feedback from Dynamic Brake Contactors 1, 2, 3 (DB1, 2, 3).
present
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0039
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
DB1_2_3 Dropout Bad In SelfTest 360

Dynamic Brake Contactors 1,2,3 (DB1,2,3) not dropping out
feedback from Dynamic Brake Contactors 1, 2, 3 (DB1, 2, 3).
present
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
Page 139 of 332

Operator Message
84A220120FH Rev: D
36. Ready
51-0040
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

Dynamic Brake Contactors 4,5,6 (DB 4,5,6) not picking up
feedback from Dynamic Brake Contactors 4,5,6 (DB 4,5,6).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0041
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

Dynamic Brake Contactors4,5,6 (DB 4,5,6) not dropping out
feedback from Dynamic Brake Contactors 4,5,6 (DB 4,5,6).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
Page 140 of 332

Operator Message
84A220120FH Rev: D

FE101/FE187 card
the
36. Ready
51-0042
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message

Dynamic Brake Contactors 7,8,9(DB7,8,9) not picking up
feedback from Dynamic Brake Contactors7,8,9(DB 7,8,9)
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0043
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation

feedback from Dynamic Brake Contactors7,8,9(DB 7,8,9)
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
Page 141 of 332

Operator Message
84A220120FH Rev: D

or coil.
FE101/FE187 card
the
36. Ready
51-0044
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
DB10_11_12 Pickup Bad In ST 369

Dynamic Brake Contactors 1,2,3 (DB1,2,3) not picking up
feedback from Dynamic Brake Contactors 10,11,12 (DB 10,11,12)
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0045
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
DB10_11_12 Dropout Bad In ST 369

feedback from Dynamic Brake Contactors 10,11,12 (DB 10,11,12)
Page 142 of 332

Operator Message
84A220120FH Rev: D
B13 BCCB + (IPS)

A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0046
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
B1 Pickup Bad In SelfTest 330

Brake Contactor (B1) not picking up
feedback from Brake Contactor (B1).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0047
Incident Message
FAM Incident Intent
B1 Dropout Bad In SelfTest 330

Brake Contactor (B1)not dropping out
feedback from Brake Contactor (B1).
Page 143 of 332

FAM Probable Cause
FAM Fault Isolation
Operator Message
84A220120FH Rev: D

B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0048
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
GS+ Pickup Bad In SelfTest 420

Engine Crank Contactor (GS+) not picking up
feedback from Engine Crank Contactor (GS+).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
Page 144 of 332

84A220120FH Rev: D
51-0049
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
GS+ Dropout Bad In SelfTest 420

Engine Crank Contactor (GS+) not dropping out
feedback from Engine Crank Contactor (GS+)
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0050
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
GS- Pickup Bad In SelfTest 417

Engine Crank Contactor (GS-) not picking up
feedback from Engine Crank Contactor (GS-).
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
Page 145 of 332

Operator Message
84A220120FH Rev: D
the
36. Ready
51-0051
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
GS- Dropout Bad In SelfTest 417

Engine Crank Contactor (GS-) not dropping out
feedback from Engine Crank Contactor (GS-)
B13 BCCB + (IPS)
A53 EN/BCCB- (IPS)
B18 BCCB - (IPS)
or coil.
FE101/FE187 card
the
36. Ready
51-0054
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
TM Plug Attempted At Too High Speed

Indicate plug speed is going above locomotive speed
This fault is logged if - Locomotive speed is above the plug speed -AND- Operator
is motoring in a direction opposite to the direction of motion.
(Direction call has changed.)
Fault Condition is no longer present.Automatic once speed is below Plug Speed limit
hysteresis.
1. Operator plugged the locomotive. Operator induce fault. 2. Controller panel
(BCA) has failed in speed calculation. 3. Controller panel (BCA) or Reverser
feedback has failed. 4. Controller panel (BCA) has failed.
1. Check that the Plug Speed limit is correct using the MP 27478 (requires Level 3
access)
2. Open Incident log using SDIS to check that this fault is really logged. If not,
it was reported by mistake. Check the Data Pack for the speed at which the fault
occurred. You can do this by downloading and viewing the fault log. Check for other
faults at the same time that would suggest Reverser or Speed sensor failure.
Continue with step 2 if you are sure the operator did not plug the locomotive.
3. Look at Monitor Parameters 25524 [locomotive speed] and 25525 through 25530
[individual motor speeds]. With the locomotive stopped, all should read zero.
If not, change FE114 card slot 23 or Controller panel (BCA).
4. Run self tests 606 and 609 several times to be sure Reverser feedback to
Controller panel (BCA) is working. This may result in changing appropriate
FE198/FE102 card or Controller panel (BCA) if Reverser position feedback is
actually ok.
5. Reset the fault. If it repeats, and actual plugging did not cause it, change
Controller panel (BCA).
30 Second
51-0055
Incident Message
FAM Incident Intent
Main Generator Volts Too High

Indicate main generator voltage is high
Fault is logged instantaneously when the measured voltage exceeds these limits:
Not in dynamic brake
- 1500 volts for GTA11alternator OR
- 1200 volts for GTA28 or GTA17 OR
- 1400 volts for GTA24 OR
- 900 volts for GTA40 alternator OR
- 1250 volts for BHEL GMG10102 alternator OR
- 850 volts if GTA11 and any 118 motor OR
Page 146 of 332


FAM Probable Cause
FAM Fault Isolation
84A220120FH Rev: D
- 1380 Volts for any GE761 OR GE761A19 OR GE761A11 OR GE764C3 motor

In dynamic brake
- 350 volts if not any ED118 traction motor
- 700 volts if any ED118 traction motor
Throttle returned to Idle and fault condition no longer present
1. GA-GN Circuit Problem:
a. Traction Motor Field connection2. Feedback Problem:a.SCM Panel b. b.
Wiring/connectorsc.
c. FE108 card in
Controller panel (BCA) 3. Exciter Field Problem:d.
a. Exciter Field F1-F2 connectione.
b. FE160 card short circuit 4. Traction Alternator Field
Problem5. Operator error caused rapid contactor opening6. Controller panel (BCA)
backplane has failed
1. Unless you know the fault occurred during Motoring or Self Load, inspect the B1
(or S36), REV, and BKT power tips for conditions that can cause high
resistance during dynamic brake operation. Correct any defects found. If the fault
occurred in Dynamic Braking, run Exciter Field Test as outlined below.
2. Verify wiring from SCM to the Controller panel (BCA). For GA - GN voltage, wire
from SCM 1-7 to Controller panel (BCA)-E12.
3. Run the engine with the Throttle in IDLE. Monitor Parameter 25409 [Main
Generator voltage]
4. Verify that the voltage is reading a low value [0 to 10 volts.]. If a higher
voltage is displayed,
a. Use a meter to verify the (GA to GN) voltage at the input of SCM. Measure from
wire into SCM3-2 (+) to GN (-). (SCM8, GA to GN).
CAUTION! THIS IS A HIGH VOLTAGE CIRCUIT!
b. If the voltage actually measured is 0 --ie. a low value-- then either the
Controller panel (BCA) or SCM (SCM8) is bad.
c. Use a meter to measure the output voltage of SCM at wire from SCM 1-7 & SCM 1-1
panel Common. The SCM output should be 1/204.8 X Rectifier output
voltage. That is, 1 volt out of SCM represents 204.8 volts between GA and GN.
- If this condition is not met, replace the SCM Panel.
- If this condition is met, replace either the FE108 or the Controller panel (BCA).
d. If GA to GN voltage measured with your meter is the same as Monitor Parameter
25409, go to step 8.
8. Reset this fault, and operate the locomotive in Self Load - Open Circuit or on
the Load Box Open Circuit (you can trick the locomotive into Open circuit by
insulating the P and S contactor tips and going into Motoring)
CAUTION! Follow established procedures for operating the locomotive in Self Load -
Without Grids (Open Circuit).
a. Observe voltage as a function of notch. Steady state voltages in Monitor
Parameter 25409 should be equal to Reference voltage in Monitor Parameter 25410.
b. If voltages are correct, go to step 9.
c. If this 51-0055fault is logged, or if the voltages are incorrect, or if the
engine does not load properly, proceed to the following steps.
1) Observe Monitor Parameter 25413 Main Generator Field Current.
2) Repeat Open Circuit and watch the field current (MP 25413).
b) If current is observed, and the voltage was too high, then the Controller panel
(BCA).
c) If no current is observed, and the voltage was too low, then check for insulated
power tips on GF. If no problems are found, the Controller panel (BCA) is
bad.
9. Set up for Self load-Loaded operation or Load Box with Grids. Operate the
locomotive in the various notches and observe the output voltage.
a. If voltages seen in MP25409 Actual are below the values in MP25410 Reference,
(step 8a. above) go to step 10. [dynamic brake operation.]
b. If the voltages are not correct, or if there is engine hunting or load control
pot action, or the engine does not appear to be loading - Take the following steps.
1) Observe Monitor Parameter 25411 - Main Generator Current.
2) If Main Generator Current is zero, there is a problem with the CS1/CT1 to
CS6/CT6 inputs to Controller panel (BCA). Check wiring from CS1..6 to SCM
(SCM1...6) to Controller panel (BCA).
3) If Main Generator Current is not zero, the Controller panel (BCA) Card(s) or
Panel is bad.
10. Set up locomotive for dynamic brake.
CAUTION! Follow established procedures for operating the locomotive in dynamic
brake.
a. Operate the locomotive in dynamic brake. Monitor Parameter 25409 [Main Generator
Voltage]. Move the Brake Handle from MIN to MAX. Voltage should
increase from 0 to less than 80 V.
1) If voltage does not follow the brake handle movement, check TL17 (MP 25037) and
TL21 (MP 25038), troubleshoot any problems found.
2) If the engine bogs, or if a fault is logged, the problem is in CS7, SCM
(SCM7)/CT7, or associated wiring, or Controller panel (BCA).
NOTE: CS7 and SCM7 (channel 7) are usually the shunt and channel used to measure
field current, but are herein used generically, see electrical schematic
Block Diagram section to determine which shunt actually reads the field current.
a) Monitor Parameter 25446 Dyn. Brk. TM Field. Try to operate in dynamic brake
again.
1) If field current [Monitor Parameter 25446] follows the brake handle, SCM (SCM7)
and its input to Controller panel (BCA) is functioning normally. If
Fault 51-0055 (High volts) is logged, then problem exists in the Controller panel
(BCA).
2) If there is no field current [Monitor Parameter 25446], then one of the
following is the problem a) There is an open in the traction motor field circuit
when set up for dynamic brake. Carefully check B1 (or S36), REV, BKT, all traction
motor field, and
associated power wiring for an open circuit. Fault 51-0264 (no Field Amps) may log.
b) The CS7 circuit wiring is faulty to SCM or from SCM to Controller panel (BCA).
Carefully check wires from CS7 to SCM (SCM7)
- and wires from SCM (for CS7) to the Controller panel (BCA). Fix any problems
found.
c) The Controller panel (BCA) circuit for CS7 is bad. Use a single D cell or other
isolated low voltage source to apply [1 to 2 volts ] across the CS7 input to
Controller panel (BCA) [1 V = 204 amps ].
- If Monitor Parameter 25446 shows a proper response, CS7 circuit in Controller
panel (BCA) is OK
- If no input is seen on Parameter 25446, replace FE108 card and try again. If
still no response, replace Controller panel (BCA).
d) SCM (SCM7) is bad. Open wires at CS7 that go to SCM and inject a low signal [<
50 mv] across input terminals of SCM. If Parameter 25446 shows no
input, replace SCM (SCM7).
Exciter Field Connection Checkout Procedure:
Operator Message
Alarm Bell
1. Past history has shown that the Exciter Field F1-F2 connection can sometimes be
connected backwards after an engine overhaul where the exciter is
disconnected and removed. The bootmarkers or wire labels are sometimes worn-away or
difficult top distinguish over many years. This misconnection will have no
detrimental effect in Motor or Self Load, but in Dynamic Braking at high speed
there can be uncontrolled operation. The Controller panel (BCA) will actually turn
off the FE160 card output through the field as it tries to regulate Grid Amps, but
since the F1-F2 connection is backwards, it cannot actually turn-off the Exciter
with the help of the Start Winding (K1-K2) and EFR2 resistor. So there is somewhat
of a run-away, self-excited operation that may result in grid overcurrent or
alternator overvoltage.
2. To verify the Exciter Field F1-F2 connection:
3. Connect a voltmeter (+) to Exciter output A2 (sometimes conveniently attached to
GS- contactor braided shunt) and voltmeter (-) to any N wire (also can be
found at GS +/- contactors).
4. Voltmeter should read battery level or charging volts (74 volts for example)
5. Blocks wheels or apply brakes, ensuring locomotive cannot move and setup for
Motoring N1 OR set up for Self Load.
6. Throttle to N1. The voltmeter voltage should increase. If it decreases, then the
F1-F2 Field is connected backwards. Correct this problems and repeat this step.
52. No Self Load
30 Second
51-0057
Incident Message
FAM Incident Intent
Main Generator Field Over Current

Indicate main generator field current is high
This fault is logged if main alternator field current exceeds the following limits:
In motor or self load:
- GTA28 or GTA40 or GTA17 Alternator: 350A
- GTA11 Alternator: 400A
- GTA24 Alternator: 450A
- BHEL TA101012: 280A
- 5GT581C9: 150A
In dynamic brake: 200A
- AND Fault 51-0289, Bad TAFI Read Module, NOT active
All conditions persisting for 4 seconds.
Page 147 of 332

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
84A220120FH Rev: D
1. Alternator Field Amps Feedback Problem:a.bad EXAM (FM394 Panel)/EXACT b.bad

shunt EXASH 2. GA-GN Feedback Problem:a.SCM Panel not feeding
back proper Amps from CS1-7 shunts/CT1-7 f.
b. Wiring/connectorsg.
c. FE108 card in Controller panel (BCA) not reading proper amps from CS1-7
shunts/CT1-7 3. Exciter Field Problem:
a. FE160 card short circuit 4. Controller panel (BCA) backplane has failed.5.
Traction Motor or Traction Alternator
Flash over occurred.
1. Examine fault log. If 51-0289 TA Field Module EXAM Bad faults are present,
troubleshoot them first.
Open Incident Log in SDIS to examine the faults on traction motor over current.
If faults 51-0071...51-0076 occurred at or near to the same time as this fault,
then consider the appropriate traction motor circuit to have experienced a flash
over.
2. Inspect all traction motors and power wiring out of the traction alternator for
any indication of flash over.
3. Check that wiring and connectors between EXAM/EXACT and the Controller panel
(BCA) are intact and not damaged. Disconnect and examine the connector
(Connector E on the Controller panel (BCA)) for pin damage. Repair if necessary.
Check wires for continuity between EXAM/EXACT and Controller panel
(BCA).
4. Check the Traction Alternator Field Circuit for shorts or grounded fields.
Repair if needed.
5. Check the Incident log on SDIS for SCM8 fault 51-0295 If it occurred at or near
to the same time as the 51-0057 fault, then trouble-shoot fault 51-0295 first.
6. Reset the fault and set up the locomotive for operation in Self Load - Open
Circuit.
CAUTION! Observe proper safety procedures when energizing the traction alternator!
a. Operate the locomotive in Self Load-Open Circuit.
b. Observe voltage as a function of notch.
Observe Monitor Parameters - 25409 [Main Generator Volts]. Use a DC Voltmeter to
measure the system voltage ( GA - GN ). If the measured and observed
voltage reading agree, SCM (SCM8) and the associated input into the Controller
panel (BCA) are not the problem.
c. Observe Monitor Parameter 25413 - Traction Alternator Field Current Use a DC
clamp-on Ammeter to measure the current in the traction alternator field
circuit at the output of the Exciter or near GF contactor. If the measured and
observed currents are not equal, problems exist in either the Controller panel
(BCA)
FE108 card, EXAM module/EXACT, or EXASH shunt, or wiring. Troubleshoot one at a
time until the defect is identified.
7. Setup and operate the locomotive in Self Load - Loaded
a. If the 51-0057 fault repeats,
1) Look for problems in Traction Alternator, braking grids, TM fields, or LBS, REV,
or BKT power tips.
8. Setup and operate the locomotive in Dynamic-Brake. [at standstill]
a. If the E039 fault repeats
1) Check polarity on SCM (SCM7)/CT7 output.
2) Look for errors in B1, BKT, REV power tips.
9. If you still haven't found the problem, monitor the main alternator field
current [Monitor Parameter 25413] while track testing the locomotive. If you see
that
this current is erratic, problems exist in either the Controller panel (BCA), or
Exciter. Troubleshoot one at a time until the defect is identified.
52. No Self Load
30 Second
51-0058
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Aux Generator Field Over Current

Indicate aux generator field current is high
This fault is logged when the Auxiliary Generator Field Current exceeds the
following
limits:
- 10A for GY27L and GY27F1,
- 12A for GY48 and GY27J,
- 9A for GY27K,
- AND Fault 51-0292, Bad AGFM, NOT active
All for 6 seconds.
1. Bad Aux Gen Field Shunt, AGSFH.2. Bad Aux Gen Field Module, AGFM.3. Wiring
problem.4. Bad Auxiliary Generator.
1. Engine running, turn off Aux Gen Field Circuit Breaker AGCB.
2. If fault 51-0248 or 51-0249 Aux Gen Field Circuit Shorted is present in the
incident log, troubleshoot it first.
3. Clear fault 51-0058.
4. Check whether there is indeed an over-current condition or a bad feedback:
Connect an ammeter (should be OK with a regular 10A meter, if it is really high,
you'll just blow the fuse in the meter) in series with the Aux Gen Field so you
can measure the actual field amps and then see if the amps are really high or if
the AGFSH/AGFM that reports the current has a problem.
5. Watch Monitor Parameter 26008 Aux Gen Field Current. Once meter is ready, turn
on ECB breaker and Controller panel (BCA) should try to charge. Compare
what the meter reads versus what MP26008 reads. If they agree, then problem is
indeed in the Aux Gen.
If they disagree, like actual is low, but MP26008 is high, then troubleshoot AGFSH
and AGFM.
36. Ready
51-0059
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
High TM Field Amps While B1 Is Open

Indicate TM field current is high
- Traction motor field current is above 80 amps AND - Engine speed is below 1000
rpm AND
- Power Notch is 0 AND - GF is not closed AND - Fault 51-0243, Bad SCM on CS7, is
not active.
All for 24 seconds.
1. SCM7/CT7 failed. 2. B1 contactor welded 3. Controller panel (BCA) failed 4. SCM
Faulty
Procedure to check if Current Shunt (CS) is used
1. Visually check B1 and make sure power tips are open.
NOTE - CAUTION!
If B1 contactor is welded, AND BKT is in Brake position, AND the diesel engine is
running, residual flux in the main alternator will cause up to 30 A to flow in
the traction motor field circuits. Repair B1 contactor if welded.
2. Run manual Self Test 330 and observe operation of B1 contactor. Repair B1
contactor if needed.
3. Reset fault 51-0059 if still active. Monitor Parameter 25446 - " DB Field ". If
displayed value exceeds 10 amps, or if fault returns after 24 sec, go to step 5.
4. Monitor Parameter 25709 - " TM Fld Offset Current ". If displayed value exceeds
20 amps, go to step 5.
5. Monitor Traction Motor offset parameter [25703-25709]. If displayed value
exceeds 15 amps, suspect SCM problem.
6. Measure DC voltage at SCM1-14 (+) and SCM1-1 (common).
a. If measured value does not correspond to value displayed,
[10 V = 2047 or 1365 amps on SDIS], then perform the following:
1) Trace wiring from SCM (SCM7) to Controller panel (BCA)
2) If wiring is OK Replace failed Controller panel (BCA)
3) If wiring error Correct wiring
b. If measured value does correspond to value displayed, then perform the
following:
Check voltage at shunt and wires to SCM (SCM7) input. With B1 open, voltage out of
shunt should be less than .1 millivolt.
c. If input voltage is correct and wiring is correct, replace failed SCM (SCM7).
Procedure to check if Current Transducer (CT) is used
1. Visually check B1 and make sure power tips are open.
NOTE - CAUTION!
If B1 contactor is welded, AND BKT is in Brake position, AND the diesel engine is
running, residual flux in the main alternator will cause up to 30 A to flow in
Page 148 of 332

Operator Message
84A220120FH Rev: D
the traction motor field circuits. Repair B1 contactor if welded.

2. Run manual Self Test 330 and observe operation of B1 contactor. Repair B1
contactor if needed.
3. Reset fault 51-0059 if still active. Monitor Parameter 25446 - " DB Field ". If
displayed value exceeds 10 amps, or if fault returns after 24 sec, go to step 5.
4. Monitor Parameter 25709 - " TM Fld Offset Current ". If displayed value exceeds
20 amps, go to step 5.
5. Monitor Traction Motor offset parameter [25703-25709]. If displayed value
exceeds 15 amps, suspect CT problem.
6. Measure DC voltage at CT terminals. If the value is > offset volts (5mv) replace
the CT. If the value is <5mv, trace wiring from CT to Controller panel (BCA)
a. If wiring is OK Replace failed Controller panel (BCA)
b. If wiring error Correct wiring
36. Ready
51-0060
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
High Generator Field I & GF Open

Indicate main alternator field current is high
- Main Alternator Field Current is above 55 amperes for more than 10 seconds AND
- Engine speed is below 1000 rpm, Power Notch is 0, and GF is not commanded
closed and Fault 51-0289, Bad TAFI Red Module, NOT active
present
1. EXAM FM394 signal conditioning module bad.2. EXASH shunt/EXACT problem.3. Wiring
problem.4. FE108 card problem inside Controller panel (BCA).5.
Controller panel (BCA) problem.
1. Engine running or shutdown, Throttle in Idle.
2. View EXAM output Voltage which is input to FE108 card. This signal is then
converted into amps and shown in MP 25413 Main Generator Field Amps.
3. In Idle the EXAM voltage and amps (MP 25413) should be 0. If MP 25413 > 40, then
that is a sign that the EXAM has probably failed. Check the voltage
output from the EXAM on EXAM-F to EXAM-D.
a. If the measured voltage is 0 but MP 25413 shows amps, then either the wiring
from EXAM-F and EXAM-D to Controller panel (BCA)-E19 and Controller
panel (BCA)-E14, respectively, is bad, or the FE108 card inside Controller panel
(BCA) is bad, or the Controller panel (BCA) backplane is bad. Troubleshoot in
that order.
4. If signal integrity is confirmed from EXAM output and amps still present, then
with a Voltmeter check the voltage from the EXASH shunt which should be 0
volts.
a. If volts = 0 mV, then replace EXAM as it is incorrectly converting a 0 mV input
into a > 0V output.
b. If volts > 5mV, this would ultimately get converted to > 40 amps and log the
fault. If > 5mV check shunt check that there is indeed no current flowing in the TA
Field Circuit by using a clamp-on Ammeter to measure current at the EXASH shunt. If
current is present, troubleshoot that. If no current present, replace the shunt.
1. Engine running or shutdown, Throttle in Idle.
2. View EXACT output Voltage which is input to FE108 card. This signal is then
converted into amps and shown in MP 25413 Main Generator Field Amps.
3. In Idle the EXACT voltage and amps (MP 25413) should be 0. If MP 25413 > 40,
then that is a sign that the EXACT has probably failed. Check the voltage
output from the EXACT.
a. If the measured voltage is 0 but MP 25413 shows amps, then either the wiring
from EXACT to Controller panel (BCA)-E19 and Controller panel (BCA)-E14,
respectively, is bad, or the FE108 card inside Controller panel (BCA) is bad, or
the Controller panel (BCA) backplane is bad. Troubleshoot in that order.
4. If signal integrity is confirmed from EXACT output and amps still present, then
with a Voltmeter check the voltage from the EXACT shunt which should be 0
volts.
a. If volts = 0 mV, then replace EXACT as it is incorrectly converting a 0 mV input
into a > 0V output.
b. If volts > 5mV, this would ultimately get converted to > 40 amps and log the
fault. If > 5mV check CT that there is indeed no current flowing in the TA Field
Circuit by using a clamp-on Ammeter to measure current at the EXACT. If current is
present, troubleshoot that. If no current present, replace the CT.
52. No Self Load
30 Second
51-0061
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
High TM Field Amps In Braking

Indicate TM field current during braking is high
This fault is logged when measured traction motor field current exceeds:
- 1740 amps for 752 motors
- 900 amps for 761 motors or BHEL TM4907 motor
- 600 amps for any ED118 motor
- 700 amps for 764C3 motor
Instantaneously.
Throttle returned to Idle and fault condition no longer
present
1. Faulty or intermittent Signal Conditioning Module SCM7/CT7.
2. Problems in reading the Brake Handle Position.
3. Problems with the Controller panel (BCA)
a. Intermittent or faulty wiring
b. Failed FE160 card.
c. Problems in reading the Current Measuring Module SCM7/CT7.
1. Determine which Shunt Configuration option is set on this locomotive.
current_dash8 1.000 (Indonesia and most locomotives)
current_rec 1.000 (BC Rail, India)
current_carl 1.000 (HLCX, MRS 3801-3809, Estonia C30)
One of these should equal 1.000. This signifies the shunt configuration on the
locomotive. Most locomotives have a dedicated shunt CS7 and scm module SCM7;
but â€œcurrent_carlâ€ option locomotives use CS4 and SCM4 channel to measure Field
Amps.
2. Also determine which kind of SCM panel the shunt feeds. That is, the shunt
feedback wires either go to a 17FM700-type SCM panel or smaller 17FM394-type
scm panel.
1. Check the Current Measuring Module SCM and its connections to shunt and
a. Open Incident Log on the SDIS to examine the faults 51-0099 (FM700-type SCM4),
51-0243 (FM700-type SCM7), or 51-0332 (FM394-type SCM7).
If this from Field Shunt CS to SCM. Check wires from SCM to Controller panel (BCA).
c. Check the shunt circuit in the SCM module (SCM7) [Note! 1500 amps in shunt CS =
50 millivolts out. (752 motors).
1000 amps in shunt CS = 50 millivolts out. (761, India, Russia motors).]
Gain from input to output of the 17FM-700 SCM Module is approximately 146.
Controller panel (BCA) scaling is: 10 volts in = 2048 amperes (752 motors).
10 volts in = 1365 amperes (761, India, Russia motors).]
2. With locomotive in IDLE, use the SDIS to Monitor Parameter 25446 [Dyn. Brk. TM
Field].
1) If displayed value is more than 90 amps, Measure DC voltage on SCM input from
Shunt with a DC voltmeter.
Page 149 of 332

84A220120FH Rev: D
a) If measured value is greater than 1-2 mv, replace failed Shunt.

b) If measured value = 0 mv, replace the SCM panel.
2) If displayed value is less than 15 amps, current measuring is probably ok, go to
the next step.
3. Set up the locomotive for Dynamic Brake.
Use the SDIS to Monitor Parameters 25445 Brake Control (TL 24). and 25446 Dyn Bk.
TM Field
a. EC Switch to Isolate (to prevent Alternator output).
1) Move Brake Handle to MIN Brake. Brake Control [25445] should read less than 10%.
2) Move Brake Handle to MAX Brake. Brake Control [25445] should read more than 90%.
If Brake Control does not respond as in 1) and 2) above a) Check Brake Control Pot
and its input to the Controller panel (BCA). Fix the problem and repeat tests 1)
and 2).
b) If the Brake Control Pot input to Controller panel (BCA) is ok, and Brake
Control does not respond as in 1) and 2) replace the FE137 card in Controller
panel (BCA).
b. If Brake Control does respond as in a. 1) and a. 2) above, return Brake Handle
to OFF, EC Switch to RUN and again set up for Dynamic Brake.
1) Move Brake Handle to MIN Brake. Compare Dyn Bk.TM Field current [25446] to Dyn
Brake Field Reference and they should match.
2) Verify that the Feedback matches the actual. Using a clamp-on ammeter, verify
that the amps from the meter match the amps displayed in MP 25446 DB
Field Amps. If they match, then feedback is OK. If they do not match, check SCM
Panel, shunt, wiring, and FE108 card.
3) If Dyn. Brk. TM Field current is higher than Reference amps, or if engine bogs
return Brake Handle to OFF. There are problems in the Excitation Control
Regulator. The functions of this regulator are divided between the Controller panel
(BCA) and the Exciter. Check the FE160 card in slot 10 and the Exciter.
1. Determine which CT Configuration option is set on this locomotive.
One of these should equal 1.000. This signifies the CT configuration on the
locomotive. Most locomotives have a dedicated CT7; but â€œcurrent_carlâ€ option
locomotives use CT4 to measure Field Amps.
1. Check the Current Transducer and its connections to Controller panel (BCA).
2. With locomotive in IDLE, use the SDIS to Monitor Parameter 25446 [Dyn. Brk. TM
Field].
1) If displayed value is more than 90 amps, Measure DC voltage on CT terminals with
a DC voltmeter for correctness. If displayed value is less than 15
amps, current measuring is probably ok, go to the next step.
Operator Message
Alarm Bell
3. Set up the locomotive for Dynamic Brake.

Use the SDIS to Monitor Parameters 25445 Brake Control (TL 24). and 25446 Dyn Bk.
TM Field
a. EC Switch to Isolate (to prevent Alternator output).
1) Move Brake Handle to MIN Brake. Brake Control [25445] should read less than 10%.
2) Move Brake Handle to MAX Brake. Brake Control [25445] should read more than 90%.
If Brake Control does not respond as in 1) and 2) above a) Check Brake Control Pot
and its input to the Controller panel (BCA). Fix the problem and repeat tests 1)
and 2).
b) If the Brake Control Pot input to Controller panel (BCA) is ok, and Brake
Control does not respond as in 1) and 2) replace the FE137 card in Controller
panel (BCA).
b. If Brake Control does respond as in a. 1) and a. 2) above, return Brake Handle
to OFF, EC Switch to RUN and again set up for Dynamic Brake.
1) Move Brake Handle to MIN Brake. Compare Dyn Bk.TM Field current [25446] to Dyn
Brake Field Reference and they should match.
2) Verify that the Feedback matches the actual. Using a clamp-on ammeter, verify
that the amps from the meter match the amps displayed in MP 25446 DB
Field Amps. If they match, then feedback is OK. If they do not match, check CT,
wiring, and FE108 card.
3) If Dyn. Brk. TM Field current is higher than Reference amps, or if engine bogs
return Brake Handle to OFF. There are problems in the Excitation Control
Regulator. The functions of this regulator are divided between the Controller panel
(BCA) and the Exciter. Check the FE160 card in slot 10 and the Exciter.
52. No Self Load
30 Second
51-0062
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation

Operator Message
Alarm Bell
Low Oil Pressure Trip In Governor

Indicate Low oil pressure input is tripped
This fault is logged under these conditions:
- Controller panel (BCA) has not called for engine shutdown
- Cranking was finished more than 60 seconds ago
- Engine speed is above 200 rpm.
- Low oil pressure switch in the governor is tripped (high)
All for 29 seconds.
1. Insufficient Diesel Engine Lube Oil. 2. Failure in Diesel Engine Lubrication
system. (Plugged oil filter, piping, Lube Oil Pump,etc.) 3. Wiring Errors. 4.
Controller panel (BCA) is bad. 5. Failure of Governor Low Oil Pressure Switch. 6.
Failure in the LCP (Load Control Pot) circuitry causes LCP not to be reduced
when it should and the engine is overloading.
52. No Self Load
30 Second
51-0063
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Low Water Pressure Trip In Governor

Indicate Low water pressure input is tripped
This fault is logged under these conditions:
- Controller panel (BCA) has not called for engine shutdown
- Cranking was finished more than 60 seconds ago
- Engine speed is above 200 rpm.
- Low water pressure switch in the governor is tripped (high)
All for 29 seconds.
1. Insufficient Diesel Engine Water. 2. Failure in Diesel Engine Water system.
(Water Pump, piping, etc. ) 3. Wiring Errors. 4. Failure of Governor Low
Water Pressure Switch. 5. Diesel Engine Water Foaming. (Not likely on later units
with Butterfly Valve). 6. Check diaphragm for leaks, damage or misadjustment. 7.
Bad Controller panel (BCA).
52. No Self Load
30 Second
51-0064
Incident Message
FAM Incident Intent
Battery Charger Over Current

Indicate Battery Current is high
Page 150 of 332


FAM Probable Cause
FAM Fault Isolation
84A220120FH Rev: D
This fault is logged under the following conditions:

- Battery charging current exceeds 330 amps for 15 seconds AND- Fault, 51-0303,
when batt_charge_shunt_option is set, otherwise 51-302, NOT
ACTIVE -AND- Engine not in crank mode.
1. Aux Gen Amps signal Feedback Problem: a.bad (AGAM or BCAM (FM394 Panel))/(BCCT
or AGACT)b.bad shunt AGASH or BCSH
c.
Wiring/connectors d. FE108 card in Controller panel (BCA) not reading properly2.
Aux Gen Field Circuit Problem:
a. FE160 card short circuit 3.
Controller panel (BCA) backplane has failed.4. Auxiliary Generator problem.
1. If Battery Charge Current shunt and SCM (BCSH and BCAM) are present, then its
signal is used in this fault logic. If no BCSH and BCAM and only Aux Gen
Current shunt (AGASH) and scm (AGAM) are present, then its signal is used.
2. Check that the feedback signal reads properly.
a. Engine Idling. Disable battery charging by opening small Aux Gen Field Breaker
AGFB, or main Charging Breaker CCB.
b. Observe Monitor Parameter 26012 â€“ Battery Charge Amps.
c. Close appropriate breakers so that battery charging commences.
d. Use a DC clamp-on Ammeter to measure the actual current through the appropriate
shunt BCSH or AGASH.
e. If the measured and observed currents are not equal, problems exist in either
the Controller panel (BCA) FE108 card, FM394 BCAM or AGAM module,
shunt BCSH or AGASH, or wiring. Troubleshoot one at a time until the defect is
identified.
3. If feedback signal reads properly and the fault is logging legitimately, meaning
there is really > 330 amps in the circuit, check for other faults such as 51-0065
Battery Voltage Too High or 51-0248, 51-249 Aux Gen Field Circuit Shorted.
Troubleshoot the Aux Gen Field Circuit Shorted faults.
4. If the Aux Gen Field Circuit checks OK, troubleshoot the Auxiliary Generator
itself.
1. If Battery Charge Current Transducer (BCCT) is present, then its signal is used
in this fault logic. If no BCCT and only Aux Gen Current Transducer AGACT
is present, then its signal is used.
b. Observe Monitor Parameter 26012 â€“ Battery Charge Amps.
d. Use a DC clamp-on Ammeter to measure the actual current through the appropriate
CT BCCT or AGACT.
e. If the measured and observed currents are not equal, problems exist in either
the Controller panel (BCA) FE108 card, BCCT or AGACT module, or wiring.
Troubleshoot one at a time until the defect is identified.
there is really > 330 amps in the circuit, check for other faults such as 51-0065
Battery Voltage Too High or 51-0248, 51-249 Aux Gen Field Circuit Shorted.
Troubleshoot the Aux Gen Field Circuit Shorted faults.
itself.
Operator Message
36. Ready
51-0065
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Battery Voltage Too Hi

Indicate Battery Voltage is high
This fault is logged whenever the local battery voltage, as measured by PO input,
exceeds
the following limits:
For 74V battery system
- 100 volts for 600 ms
- 85 volts for 4 sec
For 110V battery system
- 130 volts for 600 ms
- 125 volts for 4 sec
1. Battery Voltage signal Feedback Problem
a. Wiring/connectorsk.
b. FE137 card in Controller panel (BCA) not reading properly2. Aux Gen Field
Circuit Problem:
a. FE160 card short circuit causing Aux Gen to go "full-on" 3. Controller panel
(BCA) backplane has failed.4. Auxiliary Generator
problem.
b. Observe Monitor Parameters 26006 RA Voltage and 26009 Local Battery Voltage
(PO).
d. Use a voltmeter to measure the actual voltage on PO and RA and verify that they
agree with Monitor Parameters.
e. If the measured and observed voltages are not equal, problems exist in either
the Controller panel (BCA) FE137 card, wiring, or Controller panel (BCA)
backplane. Check wiring and then replace FE137 card and then Controller panel (BCA)
until problem is solved.
there is really high voltage in the circuit, check for other faults such as 51-
0248,
51-249 Aux Gen Field Circuit Shorted. Troubleshoot the Aux Gen Field Circuit
Shorted faults.
itself.
17. No Battery Charger
Continuous
51-0066
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
SHUTDOWN: Diesel Engine Overspeed

Indicate instantaneous engine speed is high
This fault is logged if engine speed is above 1500 rpm instantaneously.
1. Improper use of the lay shaft has caused severe engine overspeed. 2. Controller
panel (BCA) is failed
Not applicable if ECU present.
For Locomotives having EGU follow the below process,
1. Check incident log for fault 51-0067 on SDIS. If fault 51-0067 is logged, there
is a possible failure of the speed sensor.
a. Check wiring from the diesel engine speed sensor to Controller panel (BCA).
b. Check the speed sensor for resistance. Should be approx. 153 ohms.
2. Check the engine for damaged bearings. There is small chance that 3 seconds
worth of sensor overspeed pulses could result from a wiring failure.
52. No Self Load
53. Can't Crank
79. Shutdown: Engine Overspeed
Continuous
51-0067
Incident Message
FAM Incident Intent
FAM Probable Cause
SHUTDOWN: Diesel Engine Overspeed

Indicate engine speed is high
This fault is logged if the engine speed exceeds 1199 rpm for 1 second.
1. Controller panel (BCA) failed 2. Engine overspeed governor failed
Page 151 of 332

FAM Fault Isolation
Operator Message
Alarm Bell
84A220120FH Rev: D

For Locomotives having EGU follow the below process,
1. Reset fault and start engine allowing it to run in IDLE.
2. Use SDIS Panel to observe Monitor Parameter 1005 and check that engine speed is
in the expected range.
3. If the engine speed is not in the expected range,
a. Check that wiring to the Engine Speed sensor is intact and correct(Wires from
speed
sensor to Pin F12 and F17 of the Controller panel (BCA).
b. Check the speed sensor for resistance. Should be approx. 153 ohms
c. Find the DSS wiring on the locomotive schematic. Use a non grounded oscilloscope
to examine the signal. You should see a clean approximately sine
wave. Length of 1 pulse (1/2 of a sine wave) should be about 1.31 milliseconds at
440 RPM.
If you find normal conditions in a., b., and c. replace the Controller panel (BCA).
If not, trouble shoot the speed sensor and its circuit.
4. If the engine speed displayed is in the expected range, problems exist in the
Engine Governor. Replace the Engine Governor ( Overspeed Governor Bad ).
52. No Self Load
53. Can't Crank
79. Shutdown: Engine Overspeed
Continuous
51-0068
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
Wonâ€™t Motor: Hot Engine

Indicate engine is hot and wont motor
This fault is logged if:
IF (7FDL or Alco)
IF (EWT > T2w for Yw minutes or more)
OR
(EWT > T3w)
OR
IF (LOT > T2o for Yo minutes or more)
OR
(LOT > T3o) then
Log fault E044
IF (CAT3508)
IF (EWT > T3w for Yw minutes or more)
OR
IF (LOT > T3o for Yo minutes or more) then
Log fault E044 Auto Reset when EWT < (T1w 20) and LOT < (T1o-24)
Parameters:
7FDL/Alco
CAT3508
T1w 230 ÂºF ( 110 ÂºC )
201 ÂºF ( 94 ÂºC )
T2w
235 ÂºF ( 110 ÂºC )
211 ÂºF ( 99 ÂºC )
T3w
240 ÂºF ( 110 ÂºC )
213 ÂºF ( 101 ÂºC )
T4w
n/a
220 ÂºF ( 101 ÂºC )
T1o
230 ÂºF ( 110 ÂºC )
229 ÂºF ( 109 ÂºC )
T2o
235 ÂºF ( 110 ÂºC )
239 ÂºF ( 115 ÂºC )
T3o
240 ÂºF ( 110 ÂºC )
240 ÂºF ( 116 ÂºC )
T4o
n/a
245 ÂºF (118 ÂºC)
Yw
10 ( min )
1 ( min.) Yo
3 ( min )
1 ( min )
1. Radiator Fan Not Operating Properly 2. Faulty lube oil or water temperature
sensors. 3. Water Tank Cap Loose 4. Water Fill Vent Valve Open 5. Water
Level Low 6. Water Level Overfilled 7. Water Flow Valve8. Shutters or Shutter
Magnet Valve.
19. No Motoring
52. No Self Load
30 Second
51-0069
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Wonâ€™t Load: Power Circuit Ground

Indicate power circuit is grounded
This fault is logged in these conditions:
- 10 Seconds have passed since cranking was last begun.
- AND - Leakage current exceeds LISTED LIMITS for <Log ground fault>
(below) for 9.0 seconds AND Dash 8 Ground Strategy Option set
- OR - Ground Detection digital input is TRUE (high) for 600 msec AND Dash 7 Ground
Strategy
Option set
- Three individual ground faults have been logged in the last 60
minutes.
Throttle returned to Idle and Fault condition no longer
present
1. Unit had a power circuit ground fault test while locomotive was stationary. 2.
Moisture in Traction Motors. 3. Excessive leakage to ground within the
propulsion power circuits. 4. Failure of Ground relay. 5. Failure of Controller
panel (BCA) or card. 6. Foreign connection into propulsion power circuits
1. Run Self Test 778 on Ground Relay. If it passes then Controller panel (BCA) is
reading the Ground relay input properly.
2. If fault recurs in Motoring or Self Load, verify that there is indeed a ground
by inserting an ammeter in series with the Ground Relay Trip coil.
Enter Motor or Self Load and watch ground leakage current on the meter. Verify that
if the Ground Relay trips, that there is indeed the proper leakage current
Page 152 of 332

Operator Message
Alarm Bell
84A220120FH Rev: D
through the trip coil for this relay (17LV67F9 relays have a trip setting of 0.81
amps, 17LV67F8 have a nominal trip setting of 0.95 amps per GEK_2823C).
3. If the relay trips illegitimately, replace the Ground Relay.
4. If the relay trips legitimately, then there is a real ground. Inspect traction
alternator power circuits for foreign connections/perform megger test. If you don't
find
any, reset this fault. Test the unit in Self Load. If new faults appear, trouble
shoot them. If no faults appear, release the locomotive for service.
52. No Self Load
30 Second
51-0071
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Traction Motor 1 Hi Current

Indicate traction motor1 current is high
Fault is logged if this traction motor armature current exceeds the following
limits:
In motoring
- 2000 amperes for 752 motors
- 1200 amperes for 761 motors and 764C3 motors
- 1650 amperes for BHEL TM4907 motors
- 1150 amperes for any Russian ED118 motors
In Dynamic Braking if Current in this Grid Path is 20% higher than Max Grid Amp
Limit in
MP27411: Trip Limit = (1.2)*(MP27412),
-AND No Extended Range staging event has occurred for 4 seconds.
In Self Load and Current in this Grid Path is 20% higher than Current Reference
MP25412 divided by number of Self Load Grid Path Legs: Trip Limit = (1.2)*
(MP27412)/(Number of LBS Contactors).
Persistence time:
400ms in Motoring and Self Load mode when measured Current exceeds trip limit;
4s in Braking.
present
1. Traction motors were plugged by an operator 2. Traction Motor Current Measuring
Module (SCM)/CT Failure. 3. Traction motor # 1 flash over.4. Exciter
Field Problem. 5. Controller panel (BCA) Failure
a. FE108 Card b. Backplane
1. Check Incident Log on SDIS for other faults at the same time as this one.
2. Determine from the Fault Log whether the fault was logged in Motoring, Self
Load, or Dynamic Braking.
3. Check for faults 51-0096, 51-0097, 51-0098, 51-0099, [and 51-0100, 51-0101 if C
locomotive â€“ Bad SCM/CT].
a. If all 4 (or 6) faults are present, then fault was caused by plugging the
traction motors.
b. If only the Bad SCM/CT Fault for this motor is present, trouble shoot it.
c. If logged in Braking, check for fault 51-0401 Alt Fld Amps Feedback
misconnected, and run through Exciter Field Connection Checkout Procedure
outlined below, as a misconnected Exciter Field F1-F2 can lead to uncontrolled
braking amps at high speed which may result in this fault being logged.
4. If more than one of faults51-0096, 51-0097, 51-0098, 51-0099, 51-0100 or 51-0101
faults are present, Traction motors may have been plugged by an operator.
Depending upon the locomotive speed, this could have caused this fault to be
logged.
5. Check the Motor Current Measuring System by running through procedure below.
6. If other simultaneous faults were not present, then this fault was either caused
by a fault in the traction motor power circuit, or an extremely unusual wheelslip
condition.
a. Examine this traction motor for improper brush holders, worn brushes, or signs
of flash over. Also check P contactors and motor cables for faults.
7. If you did not find trouble in steps 1 through 6, the problem is either
intermittent or falsely logged.
8. Run the locomotive in Self Load with grids, in Dynamic Brake Maximum at
standstill, and then track test it. If the fault does not repeat release the
locomotive
for service.
Exciter Field Connection Checkout Procedure:
1. Past history has shown that the Exciter Field F1-F2 connection can sometimes be
connected backwards after an engine overhaul where the exciter is
disconnected and removed. The bootmarkers or wire labels are sometimes worn-away or
difficult top distinguish over many years. This misconnection will have no
detrimental effect in Motor or Self Load, but in Dynamic Braking at high speed
there can be uncontrolled operation. The Controller panel (BCA) will actually turn
off the FE160 card output through the field as it tries to regulate Grid Amps, but
since the F1-F2 connection is backwards, it cannot actually turn-off the Exciter
with the help of the Start Winding (K1-K2) and EFR2 resistor. So there is somewhat
of a run-away, self-excited operation that may result in grid overcurrent or
alternator overvoltage.
2. To verify the Exciter Field F1-F2 connection:
3. Connect a voltmeter (+) to Exciter output A2 (sometimes conveniently attached to
GS- contactor braided shunt) and voltmeter (-) to any N wire (also can be
found at GS +/- contactors).
4. Voltmeter should read battery level or charging volts (74 volts for example)
5. Blocks wheels or apply brakes, ensuring locomotive cannot move and setup for
Motoring N1 OR set up for Self Load.
6. Throttle to N1. The voltmeter voltage should increase. If it decreases, then the
F1-F2 Field is connected backwards. Correct this problems and repeat this step.
Motor Current Measuring System Test:
Determine which Shunt Configuration option is set on this locomotive.
but â€œcurrent_carlâ€ option locomotives use CS4 and SCM4 channel to measure Field
Amps.
Also determine which kind of SCM panel the shunt feeds. That is, the shunt feedback
wires either go to a 17FM700-type SCM panel or smaller 17FM394-type
scm panel.
1. Use the SDIS and observe the current in each traction motor.
[Monitor Parameters 25467 through 25472 and 25446 for Field Amps in Braking]
a. In Idle, observe and record Monitor Parameters 25703 through 25708, TM #1-#6
Offset Current, and Monitor Parameter 25709, TM FLD Offset, which are
the static errors in the traction motor armature and field current readings. These
errors should not have an absolute value greater than 10 Amps. Replace the SCM
panel and retest if any of these readings is greater than Â± 10 Amps.
b. Wiggle Test
----------Two people are required. With the locomotive in an UNPOWERED MODE (like
Idle), observe parameters 25703 through 25708 while wiggling the
connectors and wiring leading to the SCM panel. If the values for these parameters
fluctuate by more than 2 or 3 amps while the cables are wiggled, then SCM
cabling or connections are loose.
a. IF the locomotive is equipped with a 17FM700 SCF panel, verify the "O" ring from
FMI 26-14583 is present.
b. Check +/- 15V with a voltmeter to all SCM panels.
IF no problem was found in the SCM Checks, Continue to perform a static load test.
2. Static Load Test
Set up for Motoring. WARNING: DO NOT LET THE LOCOMOTIVE MOVE.
a. Operate in notch 1. Limit operating time to two (2) minutes. Look at all motor
currents [Monitor Parameters 25467 thru 25472]:
b. IF all motor currents are about the same, the current measuring system is ok.
[SCM and Controller panel (BCA) have passed this test].
c. If currents are unstable --, there are problems in the Exciter Field Control
circuitry.
Page 153 of 332

84A220120FH Rev: D
1) Exciter Field circuit. Check EFR resistor for intermittents.

2) Check RT6 for short or open.
3) Monitor Parameter 25609 Exciter Fld Percent On while you change notches.
This is FE160 slot card transistor â€œPercent ONâ€ output from the Controller
panel (BCA) CPU card FE200. If it returns to the same value each time you
return to a given notch, Controller panel (BCA) is probably OK. If not, replace the
FE160 card in slot 10 or the Controller panel (BCA) one at a time until the
problem is identified.
d. IF Traction Motor n current is different, temporarily trade shunt (CSn) leads
with another CS and rerun the static load test. Where n = 1, 2, 3, 4, 5 and 6.
e. IF the different-current shifts, the problem is in the motor circuit.
f. IF the different current stays with the original CSn, the problem is in the
wiring, SCM or Controller panel (BCA).
1. Check the Current Measuring Module SCM and its connections to shunt and
a. Check the shunt circuit in the SCM module
[Note! 1500 amps in shunt CS = 50 millivolts out. (752 motors).
1000 amps in shunt CS = 50 millivolts out. (761, India, Russia motors).]
g. Check the wiring from the Current Shunt(s) (CS1-7) to SCM
h. Check the wiring from SCM connector 1 to the Controller panel (BCA).
j. If you did not find a problem with the wiring in g. or h., change SCM. Then
check motor currents in Idle and Notch 1.
1) If offset currents are now OK ( < 10amps) go to Step 3 .
2) If the problem remains, Change Controller panel (BCA) FE108 card and check motor
offset currents in Idle and balanced in Notch 1.
3) If the problem remains, Change Controller panel (BCA) and check motor offset
currents in Idle and balanced in Notch 1.
3. Run the locomotive in Self Load with grids, at Dynamic Brake Maximum at
Standstill, and then track test it. If no faults appear release the system checks
OK
and is ready for service.
Determine which CT Configuration option is set on this locomotive.
One of these should equal 1.000. This signifies the CT configuration on the
locomotive. Most locomotives have a dedicated shunt CT7; but â€œcurrent_carlâ€
option
locomotives use CT4 to measure Field Amps.
1. Use the SDIS and observe the current in each traction motor.
[Monitor Parameters 25467 through 25472 and 25446 for Field Amps in Braking]
a. In Idle, observe and record Monitor Parameters 25703 through 25708, TM #1-#6
Offset Current, and Monitor Parameter 25709, TM FLD Offset, which are
the static errors in the traction motor armature and field current readings. These
errors should not have an absolute value greater than 10 Amps. Replace the CT
and retest if any of these readings is greater than Â± 10 Amps.
b. Wiggle Test
----------Two people are required. With the locomotive in an UNPOWERED MODE (like
Idle), observe parameters 25703 through 25708 while wiggling the
connectors and wiring leading to the CT. If the values for these parameters
fluctuate by more than 2 or 3 amps while the cables are wiggled, then CT cabling or
connections are loose. Check +/- 15V with a voltmeter to all CTs.
IF no problem was found in the CT Checks, Continue to perform a static load test.
2. Static Load Test
Set up for Motoring. WARNING: DO NOT LET THE LOCOMOTIVE MOVE.
a. Operate in notch 1. Limit operating time to two (2) minutes. Look at all motor
currents [Monitor Parameters 25467 thru 25472]:
b. IF all motor currents are about the same, the current measuring system is ok.
[CT and Controller panel (BCA) have passed this test].
c. If currents are unstable --, there are problems in the Exciter Field Control
circuitry.
1) Exciter Field circuit. Check EFR resistor for intermittents.
2) Check RT6 for short or open.
3) Monitor Parameter 25609 Exciter Fld Percent On while you change notches.
This is FE160 slot card transistor â€œPercent ONâ€ output from the Controller
panel (BCA) CPU card FE200. If it returns to the same value each time you
return to a given notch, Controller panel (BCA) is probably OK. If not, replace the
FE160 card in slot 10 or the Controller panel (BCA) one at a time until the
problem is identified.
d. IF Traction Motor n current is different, temporarily trade Current Transducer
(CTn) leads with another CT and rerun the static load test. Where n = 1, 2, 3,
4, 5 and 6.
e. IF the different-current shifts, the problem is in the motor circuit.
f. IF the different current stays with the original CTn, the problem is in the
wiring or Controller panel (BCA).
g. Check the wiring from the Current Transducer(s) (CT1-7) to Controller panel
(BCA).
h. If you did not find a problem with the wiring in g, change CT. Then check motor
currents in Idle and Notch 1.
1) If offset currents are now OK ( < 10amps) go to Step 3 .
2) If the problem remains, Change Controller panel (BCA) FE108 card and check motor
offset currents in Idle and balanced in Notch 1.
3) If the problem remains, Change Controller panel (BCA) and check motor offset
currents in Idle and balanced in Notch 1.
3. Run the locomotive in Self Load with grids, at Dynamic Brake Maximum at
Standstill, and then track test it. If no faults appear release the system checks
OK
and is ready for service.
Note: On both B & C locomotives stability is more important than absolute current
levels. Large differences between values could mean problems in the
braking grids or their power wiring. The Controller panel (BCA) will limit the grid
current to a maximum in each leg. Based on the number of grids, grid kW
rating, and grid resistance, the Controller panel (BCA) will limit the current in
each grid path in order not to overload any grid path. This may mean that one or
more leg carries more current than the other(s).
Operator Message
Alarm Bell
4. No Dynamic Brake
21. TE Limited
52. No Self Load
30 Second
51-0072
Incident Message
FAM Incident Intent

limits:
In motoring
Page 154 of 332


FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
84A220120FH Rev: D

Limit in
MP27411: Trip Limit = (1.2)*(MP27412),
Persistence time:
4s in Braking.
present
traction motors.
misconnected, and run through Exciter Field Connection Checkout Procedure as
outlined in fault 51-0071, as a misconnected Exciter Field F1-F2 can lead to
uncontrolled braking amps at high speed which may result in this fault being
logged.
logged.
5. Check the Motor Current Measuring System by running through procedure outlined
in fault 51-0071.
condition.
locomotive
for service.
4. No Dynamic Brake
21. TE Limited
52. No Self Load
30 Second
51-0073
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

limits:
In motoring
Limit in
MP27411: Trip Limit = (1.2)*(MP27412),
Persistence time:
4s in Braking.
present
traction motors.
logged.
logged.
in fault 51-0071.
condition.
locomotive
for service.
4. No Dynamic Brake
21. TE Limited
52. No Self Load
30 Second
51-0074
Incident Message
FAM Incident Intent

limits:
In motoring
Limit in
MP27411: Trip Limit = (1.2)*(MP27412),
Persistence time:
4s in Braking.
Page 155 of 332


FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell
84A220120FH Rev: D

present
traction motors.
logged.
logged.
in fault 51-0071.
condition.
locomotive
for service.
4. No Dynamic Brake
21. TE Limited
52. No Self Load
30 Second
51-0075
Incident Message
FAM Incident Intent
FAM Probable Cause
FAM Fault Isolation
Operator Message
Alarm Bell

limits:
In motoring
Limit in
MP27411: Trip Limit = (1.2)*(MP27412),
Persistence time:
4s in Braking.
present
traction motors.
outlined in fault 51-0071, as a misconnected Exciter Field can lead to uncontrolled
logged.
in fault 51-0071.
condition.
locomotive
for service.
4. No Dynamic Brake
21. TE Limited
52. No Self Load
30 Second
51-0076
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation

limits:
In motoring
Limit in
MP27411: Trip Limit = (1.2)*(MP27412),
Persistence time:
4s in Braking.
present
traction motors.
misconnected, and run through Exciter Field Connection Checkout Procedure
Page 156 of 332

Operator Message
Alarm Bell
84A220120FH Rev: D
outlined in fault 51-0071, as a misconnected Exciter Field can lead to uncontrolled

logged.
in fault 51-0071.
condition.
locomotive
for service.
4. No Dynamic Brake
21. TE Limited
52. No Self Load
30 Second
51-0077
Incident Message
FAM Incident Intent

FAM Probable Cause
FAM Fault Isolation
TM #1 Hi Amps While Cut-Out

Indicate high traction motor1 current during cut out
This fault is logged under the following conditions
- In Motoring, AND
- TM#1 is Cutout, AND
- Fault 51-0071 TM1 High Current is NOT active, AND
- Fault 51-0096 Bad SCM Module for CS1 is NOT active, AND
EITHER
1. Average current in active traction motors is 80 amperes or more, AND
2. Current in TM#1 is above 80 amperes.
OR
IF Shunt Sandwich present and in Parallel configuration, since there is no direct
measurement of TM1 or TM4 current, the software compares shunt 4 (CS4) current to
average of CS5 and CS6/CT6. If TM1 is properly cutout, meaning its power contactor
is really
open, the current in CS4 should be roughly half of the CS5/CS6 average current only
in
TM4. If the current > (0.8)*(CS5/CS6 average) this fault will log
All for more than 4 seconds
present
1. Failed SCM panel/CT. 2. Welded P1 contactor.3. Wiring Problem.4. Bad Controller
panel (BCA) FE108 card or Panel. 5. Secondary fault caused by a
contactor dropping out
1. Use the SDIS and run Self Test 300 [P1 test]. Verify that power contactor picks
up and drops out properly and that power contact tips are not welded.
2. Examine the appropriate SCM module/CT and verify proper wiring.
3. Use SDIS and monitor Parameters 25467 [Traction Motor # 1 Amps] and 25703 [TM #
1 OFF_SET].
4. At IDLE, Parameter 25467 should be < 10 amps, and 25703 should be < 30 Amps.
a. If either Parameter exceeds these values, look for wiring errors to Controller
panel (BCA). If you do not find a problem with wiring, replace SCM/CT.
5. Check Incident Log for a fault which happened at the same time and could have
caused this motor to be cutout. a. If you find any, normal dropout times of GF,
and P contactors probably caused this fault to be logged. Reset this fault and
trouble-shoot the simultaneous fault that caused the traction motor to be cutout in
the
first place.
6. If no trouble was found in steps 1 through 5, the problem is either intermittent
or falsely logged. Run the locomotive in Self Load with grids and then track test
it.
a. If the fault repeats replace the FE108 card and whole Controller panel (BCA) in
turn.
b. If the fault does not repeat release the locomotive for service.
7. If fault persists, run through Traction Motor Current Measuring system test
procedure as below.
Motor Current Measuring System Test:
Determine which Shunt Configuration option is set on this locomotive.

Fam CC206 - 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fam CC206 - 2

Uploaded by

Copyright:

Available Formats

08-3003

FAM Fault Isolation

Console Selector Switch Bad

FAM Fault Isolation

Secondary Console Gen Field May Be ON When Primary Is Active

FAM Fault Isolation

Primary Console Gen Field May Be ON When Secondary Is Active

Direction Detected on Secondary Console When Primary Is Active

Author: Naresh K Approval: Rakesh Jain

GE Proprietary and Confidential

FAM Incident Intent

FAM Fault Isolation

BCCA Fault Analysis Manual

FAM Incident Clearing

FAM Fault Isolation

Direction Detected on Primary Console When Secondary Is Active

Possible Bad Reverser Handle Not Centered Feedback

FAM Fault Isolation

1. Troubleshoot wiring, terminals and connectors back toBCA

FAM Fault Isolation

Possible Bad Primary Console GF ON Feedback

Possible Bad Secondary Console GF ON Feedback

FAM Fault Isolation

1. Troubleshoot Secondary Console Gen Field Circuit Breaker

Possible Bad Primary Console Not Centered Feedback

GE Proprietary and Confidential

FAM Incident Detection

FAM Fault Isolation

BCCA Fault Analysis Manual

FAM Fault Isolation

Possible Bad Secondary Console Not Centered Feedback

Dual Console Digital Feedbacks Quality Bad

FAM Fault Isolation

FAM Fault Isolation

Possible Bad Dual Console GF ON Feedback or Cam F Feedback

Software: RM Error Spawning Rm Task

Author: Naresh K Approval: Rakesh Jain

FAM Probable Cause

BCCA Fault Analysis Manual

Software: RM Error Killing Rm Task

Software: RM Add Called With Null Pointer

Software: RM Add With Bad Incd Id

Software: RM Chg Incd With Bad Incd Id

Software: RM Upd Auto Dec With Bad Incd Id

Software: RM Chg Incd Called With Null Pointer

Software: RM Chg Incd Finds Bad Restr Id

Software: RM Get Restr Called With Bad Restr Id

Author: Naresh K Approval: Rakesh Jain

GE Proprietary and Confidential

BCCA Fault Analysis Manual

Software: RM Get Incd Called With Bad Incd Id

Software: RM Clear Restr Called With Bad Restr Id

Software: RM Clear Finds Incd Obj With Wrong Id

Software: RM Clear Finds Null Ptr Or Wrong Id

Software: RM Clear Finds Bad Restr Id

Software: RM Enable Called With Bad Id

Software: RM Finds Bad Restr Id

Software: RM Disable Called With Bad Id

Software: RM Set Restr Called With Bad Restr Id

GE Proprietary and Confidential

BCCA Fault Analysis Manual

Software: MMI Task Can't Link To Sm

Software: MMI Task Can't Map To Sm