Error Code List & Recommended Actions For Block Working With UFSBI & DAC in Case of Faults/Errors
Error Code List & Recommended Actions For Block Working With UFSBI & DAC in Case of Faults/Errors
ANNEXURE C
Error code list & Recommended actions for Block Working With UFSBI &
DAC in case of Faults/Errors
NOTE: BEFORE TAKING OUT OR INSERTING A CARD, ALWAYS TURN-OFF THE POWER SUPPLY
Supplied with Users Manual for Block Proving with Axle Counter using UFSBI Ver No.: BPAC/UM/DL 0.0
Pg. 1 of 7
Error Code List for Block Proving with Axle Counter using UFSBI Deltron Equipment & System Pvt. Ltd.
Supplied with Users Manual for Block Proving with Axle Counter using UFSBI Ver No.: BPAC/UM/DL 0.0
Pg. 2 of 7
Error Code List for Block Proving with Axle Counter using UFSBI Deltron Equipment & System Pvt. Ltd.
OUT15 complementary failure
2E
(Ckt ref. W86 & W93)
OUT16 complementary failure
'2 ' (2F)
(Ckt ref. W87 & W94)
30 BIPR1 complementary failure
Take similar steps as in the case for other relays.
31 BIPR2complementary failure
If the error code appears in any one of the CPU card:
i) Swap it with other slot. If the error shifts with the card
Change the CPU card.
If the error code appears in any one of the CPU card:
i) Check the communication link from crone box, terminal, to
33 Link Fail (SSB mode) modem RJ11 jack. If external communication link is
confirmed OK change the CCC Card.
ii) If the problem still persists, Switch off the Modem , and then
restart it after 60s.
iii) If the problem still persists perform Power-On Reset of the
System and observe its operation
34 This mode indicates that the UFSBI on the other side is not
RSSB mode receiving data. Try by checking the channel, modem and
communication in that order as stated for error code ‘33’.
Ensure that the other side System is working and showing error
code ‘33’ only.
37 CPU A bad i) Change corresponding CPU Cards in which the static error
38 CPU B bad code is showing. Manually RESET the system and observe its
39 CPU C bad operation.
ii) If this indication is on all the CPU cards then change the
CCC (Communication) Card. Manually RESET the system and
observe its operation
3A Inter-processor communication channel If occurs in all the CPUs, change the communication card.
failure (common mode) Manually RESET the system and observe its operation
40 OUT1 forced pickup Manually RESET the system following the same process as
[LFR Non-vital relay] stated in item no. II.15. If the problem persists then For codes
41 OUT2 forced pickup “40” to “4F” check the corresponding relays as follows
[TCFXR vital relay] i) Check if the relay is properly plugged and the retaining
42 OUT3 forced pickup clip is place correctly. Also ensure that all its receptacles
[TCFCR vital relay] are rightly placed and locked in the plug board.
Manually RESET the system and observe its operation.
43 OUT4 forced pickup ii) Check the corresponding relays to see if the front
[TGTYR vital relay] contacts somehow got voltage or back contacts got
44 OUT5 forced pickup broken or if the relay has got picked up out of sequence
[ASGNCPR vital relay] by some stray feed given externally. Manually RESET the
45 OUT6 forced pickup system and observe its operation.
[TGTZR vital relay] iii) Check the wago terminals for unwanted shorting
46 OUT7 forced pickup between terminals other than those showed in circuit. In
[BLR vital relay] case any such short circuits found please remove the
same. Manually RESET the system and observe its
47 OUT8 forced pickup operation.
48 OUT9 forced pickup Manually RESET the system following the same process as
stated in item no. II.15. If the problem persists then For codes
49 OUT10 forced pickup “40” to “4F” check the corresponding relays as follows
iv) Check if the relay is properly plugged and the retaining
clip is place correctly. Also ensure that all its receptacles
4A OUT11 forced pickup
are rightly placed and locked in the plug board.
Manually RESET the system and observe its operation.
4B OUT12 forced pickup v) Check the corresponding relays to see if the front
contacts somehow got voltage or back contacts got
4C OUT13 forced pickup broken or if the relay has got picked up out of sequence
by some stray feed given externally. Manually RESET the
4D OUT14 forced pickup system and observe its operation.
vi) Check the wago terminals for unwanted shorting
between terminals other than those showed in circuit. In
4E OUT15 forced pickup
case any such short circuits found please remove the
same. Manually RESET the system and observe its
4F OUT16 forced pickup operation.
Supplied with Users Manual for Block Proving with Axle Counter using UFSBI Ver No.: BPAC/UM/DL 0.0
Pg. 3 of 7
Error Code List for Block Proving with Axle Counter using UFSBI Deltron Equipment & System Pvt. Ltd.
50 IN1 jitter
Jittery contacts of the relay may occur when a particular
51 IN2 jitter relay does not stabilize, i.e. it ‘chatters’. This may happen due
52 IN3 jitter to low coil voltage, faulty receptacles (coil or contacts) or
53 IN4 jitter improper plugging of the relays without retaining clips.
54 IN5 jitter The following actions are suggested:
a) Check the setting in the plug board for proper plugging
55 IN6 jitter
b) Check firmness of the contacts and all connections from
56 IN7 jitter output connector coil (for output relays).
57 IN8 jitter c) Check coil and contact voltage for each input paths
58 OUT1 jitter [LFR Non-vital relay] from the circuit. Try removing and re-plugging each relay
59 OUT2 jitter [TCFXR vital relay] in the circuit path separately ensuring that it is fitted firmly
to the plug board and the retaining clip is in the right
5A OUT3 jitter [TCFCR vital relay]
place
5B OUT4 jitter [TGTYR vital relay] d) For output relays, try to measure the coil voltage at the
5C OUT5 jitter [ASGNCPR vital relay] corresponding wago terminal as well as the relay coil R1-
5D OUT6 jitter [TGTZR vital relay] R2. Note that this voltage is available for less than ½ sec,
5E OUT7 jitter [BLR vital relay] so using an analog voltmeter is preferred. It is advisable to
5F OUT8 jitter try by changing the corresponding output card.
Manually RESET the system and observe its operation.
60 IN9 jitter
61 IN10 jitter Jittery contacts of the relay may occur when a particular
62 IN11 jitter relay does not stabilize, i.e. it ‘chatters’. This may happen due
63 IN12 jitter to low coil voltage, faulty receptacles (coil or contacts) or
improper plugging of the relays without retaining clips.
64 IN13 jitter
The following actions are suggested:
65 IN14 jitter a) Check the setting in the plug board for proper plugging
66 IN15 jitter b) Check firmness of the contacts and all connections from
67 IN16 jitter output connector coil (for output relays).
68 OUT9 jitter c) Check coil and contact voltage for each input paths
from the circuit. Try removing and re-plugging each relay
69 OUT10 jitter
in the circuit path separately ensuring that it is fitted firmly
6A OUT11 jitter to the plug board and the retaining clip is in the right
6B OUT12 jitter place
6C OUT13 jitter d) For output relays, try to measure the coil voltage at the
6D OUT14 jitter corresponding wago terminal as well as the relay coil R1-
R2. Note that this voltage is available for less than ½ sec,
6E OUT15 jitter
so using an analog voltmeter is preferred. It is advisable to
6F OUT16 jitter try by changing the corresponding output card.
70 BIPR1 jitter Manually RESET the system and observe its operation.
71 BIPR2 jitter
73 Shut down relay phase generator failure If this indication is on a single CPU card change the CPU card.
(phase not changing within 30 minutes) If all the 3 CPUs show this code then change the
communication card.
75 Timer2 input bad RESET the system by pressing RESET button and then BI-OK
78 Data bus check failed button in a sequential manner. If problem persists change
79 EPROM Checksum failed corresponding CPU card.
7A BIPR1 input to GAL stuck at low RESET the system by pressing RESET button and then BI-OK
7B button in a sequential manner. If problem persists change
BIPR2 input to GAL stuck at low corresponding CPU card. If the problem still remains change
CCC Card. When all CPUs show the code, change CCC.
7C BIPR1 command output not matching
RESET the system by pressing RESET button and then BI-OK
with shutdown relay phase.
button in a sequential manner. If problem persists change
7D BIPR1 command output not matching
corresponding CPU card.
with shutdown relay phase.
Supplied with Users Manual for Block Proving with Axle Counter using UFSBI Ver No.: BPAC/UM/DL 0.0
Pg. 4 of 7
Error Code List for Block Proving with Axle Counter using UFSBI Deltron Equipment & System Pvt. Ltd.
Supplied with Users Manual for Block Proving with Axle Counter using UFSBI Ver No.: BPAC/UM/DL 0.0
Pg. 5 of 7
Error Code List for Block Proving with Axle Counter using UFSBI Deltron Equipment & System Pvt. Ltd.
Supplied with Users Manual for Block Proving with Axle Counter using UFSBI Ver No.: BPAC/UM/DL 0.0
Pg. 6 of 7
Error Code List for Block Proving with Axle Counter using UFSBI Deltron Equipment & System Pvt. Ltd.
NOTE: AFTER EACH PROCESS, PERFORM THE RESET OPERATION TO RESTART THE MUX.
Supplied with Users Manual for Block Proving with Axle Counter using UFSBI Ver No.: BPAC/UM/DL 0.0
Pg. 7 of 7