Curtis 1356/1356P CAN Expansion Module Manual, Rev. A
39
6
6 — DIAGNOSTICS & TROUBLESHOOTING
DIAGNOSTICS AND TROUBLESHOOTING
When an error occurs in the 1356 /1356P, a fault message can be monitored
through the Curtis programmer. Meanwhile, an emergency message will be
produced on the CAN bus according to the CANopen standard. is message
will be sent once. When the fault clears, a No Fault emergency message will
be transmitted.
e fault log is accessed by SDO reads of the Standard Object at Index
0x1003. Reading the Fault Log Length sub-index 0x00 will return a value of 16
(the depth of the fault log). Reading from the sub-index 1 though 16 (0x01 – 0x10)
will return the faults plus time stamps in order from newest to oldest. e fault
log can be cleared by writing 0 to the Fault Log Length object (sub-index 0x00).
Additionally, the highest priority fault code will be ashed on the red
and yellow status LEDs. e red LED enumerates the digit place and the yel-
low LED enumerates the value. For example, a code 23 would be displayed as
one red ash, followed by two yellow ashes, followed by two red ashes and
nished with three yellow ashes. e 1356 /1356P’s two LEDs will display
this repeating pattern:
red yellow red yellow
✱
✲
✲
✱
✱
✲
✲✲
(first digit)
(2) (second digit) (3)
e fault codes are listed in the troubleshooting chart (Table 5).
During normal operation, the yellow LED ashes continuously.
On power-up, the integrity of the code stored in memory is automatically
tested. If the software is found to be corrupted, the red Status LED will ash
rapidly.
e ash code can also be ashed on a single remote LED connected to the
serial port. For example, a code 23 would be displayed as two ashes, followed
by a 500 ms delay, and nished with three ashes. e 1356 /1356P will repeat
this pattern at 1 second intervals.
To Next Page
Loading...