40(42)
Datum/Date Rev
Dokumentnr/DocumentnrUppgjord/Prepared
Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference
1999-07-15 F
1545-ASB 150 02 Uen
FAULT TRACING DESCRIPTION
Faktaansvarig - Subject responsible
Fault
Code
Service
class
Fault
Threshold
Description
1 2 2 Unexpected message/primitive Message received but not within specified time
2 1 99 Board/CPU communication error or time out. Message corrupted or not received
3 2 99 Threshold Fault counter exceeded
4 3 1 Board controller ROM error
5 3 1 Board controller RAM error
6 3 2 Internal loop back error
7 2 5 Peripheral state error- state of periph. differs from state listed in CPU data base
8 1 6 Base Station not present - wiring fault or power lost
9 3 2 Peripheral ROM error
10 3 2 Peripheral RAM error
11 2 99 Peripheral status unknown. Two simultaneous faults: status can not be obtained
12/13 2 99 Board status unknown. No communication with board: status can not be obtained
14 2 5 Peripheral communication error or time out. Message corrupted or not received
15 2 2 Board signalling link was cut. When a board is not polled, it resets itself and after
communication has recovered it sends this message to CPU
16 1 10 Board controller poll response error
17 3 99 CPU main processor RAM error
18 3 99 CPU main processor ROM error
19 3 99 CPU EEPROM error
20 2 1 CPU real time clock failure
21 3 2 CPU-poll processor (8031) RAM error
22 3 2 CPU-poll processor (8031) ROM error
23 1 2 CPU-poll processor communication error
26 2 5 Internal buffer overflow
27 2 99 Board controller watchdog reset
28 1 2 HSCX error. Serial communication controller on CPU of signalling high way
29 3 99 Signalling high way down. No communication between CPU and all other boards
33 1 1 Initialization procedure not successful. Due to e.g.: no communication with board
34 1 99 Portable related circuit not present. DTU-channel.
39 PC communication error. When statistics run, logging is stopped. Statistics must be
set ON again
50 1 Minimum configuration error
51 2 Subject unreliable. Fault not continuously present
52 Subject could not be tested after maintenance action due to a coincidence-Subject
must be verified if operational. It may be ’AVE’ but not working. Reset subject