6 — DIAGNOSTICS AND TROUBLESHOOTING
pg. 37
Return to TOC Curtis 1353 CANopen Expansion Module Manual – June 2017
6 — DIAGNOSTICS AND TROUBLESHOOTING
When an error occurs in the 1353, a fault message can be monitored through the Curtis programmer.
Meanwhile, an emergency message will be produced on the CANbus according to the CANopen
standard. is message will be sent once. When the fault clears, a No Fault emergency message will
be transmitted.
For each new fault, the fault code and timestamp will be logged in a 16-error-deep FIFO buer in
this format:
Byte5 Byte6 Byte7 Byte8
Fault Code FFh Hour LSB Hour MSB
Fault Time Stamp
e fault log is accessed by SDO reads of the Standard Object at Index 0x1003. Reading the Fault
Log Length sub-index 00h 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 yellow 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 1353’s two LEDs will display this repeating pattern:
Red Yellow Red Yellow
(rst 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 soware is
found to be corrupted, the red Status LED will ash rapidly.
To Next Page
Loading...
Need help?
General
