Troubleshooting Reference
2-85
element
TM
Series
SPB: PLD DSL1 Mismatch (178) Traction only. The DSL1 signals seen by the SPB and PLD do no match.
This fault is generated on a hydraulic controller or if DNTS1 is configured
as a physical switch on a traction controller.
1. Possible problem with the physical input to SPB or PLD.
2. Possible communication problem between SPB and PLD.
SPB: PLD DSL2 Mismatch (177) Traction only. The DSL2 signals seen by the SPB and PLD do no match.
This fault is generated if DNTS2 is configured as a physical switch on a
traction controller. (Traction only)
1. Possible problem with the physical input to SPB or PLD.
2. Possible communication problem between SPB and PLD.
SPB: PLD DTL Mismatch (176) Traction only. The DTL signals seen by the SPB and PLD do no match.
This fault is only generated if the direction limit is configured as a physi-
cal input.
1. Possible problem with the physical input to SPB or PLD.
2. Possible communication problem between SPB and PLD.
SPB: PLD MRDN Mismatch (207) Traction only. The MRDN signals seen by the SPB and PLD do no match.
1. Possible problem with the physical input to SPB or PLD.
2. Possible communication problem between SPB and PLD.
SPB: PLD MRIN Mismatch (204) Traction only. The MRIN signals seen by the SPB and PLD do no match.
1. Possible problem with the physical input to SPB or PLD.
2. Possible communication problem between SPB and PLD.
SPB: PLD MRUP Mismatch (206) Traction only. The MRUP signals seen by the SPB and PLD do no match.
1. Possible problem with the physical input to SPB or PLD.
2. Possible communication problem between SPB and PLD.
SPB: PLD USL1 Mismatch (175) Traction only. The USL1 signals seen by the SPB and PLD do no match.
This fault is generated on a hydraulic controller or if UNTS1 is configured
as a physical switch on a traction controller.
1. Possible problem with the physical input to SPB or PLD.
2. Possible communication problem between SPB and PLD.
SPB: PLD USL2 Mismatch (174) Traction only. The USL2 signals seen by the SPB and PLD do no match.
This fault is generated if a QUTE landing system is used on a hydraulic
controller or if UNTS2 is configured as a physical switch on a traction con-
troller.
1. Possible problem with the physical input to SPB or PLD.
2. Possible communication problem between SPB and PLD.
SPB: PLD UTL Mismatch (173) Traction only. The UTL signals seen by the SPB and PLD do no match.
This fault is only generated if the direction limit is configured as a physi-
cal input.
1. Possible problem with the physical input to SPB or PLD.
2. Possible communication problem between SPB and PLD.
SPB: SPA Comm Sync (259) Informational. SPB has established communication with SPA.
SPB: SPA is Offline (145) Safety processor B reports safety processor A is not communicating. The
car will perform an emergency stop and will not be allowed to move. All
calls will be canceled and the doors will not be allowed to move. May
occur subsequent to an unsuccessful parameter update. Cannot be
bypassed.
System Verifies:
- SPA sequence numbers offline
Correction:
1. Press SCE-CPU board RSTA button.
2. If the processor resets, monitor activity for recurrence.
SPB: SPC Comm Sync (260) Informational. SPB has established contact with SPC.
Table 2.15 Touch Screen Event Listings
Event Description