Fault Log - Curtis 1353 User Manual

Canopen expansion module
Table of Contents

Advertisement

Return to TOC
Table 5 Troubleshooting Chart cont'd
Code
Fault
41
Coil1 Fault
42
Coil2 Fault
43
Coil3 Fault
44
Coil4 Fault
45
Coil5 Fault
46
Coil6 Fault
47
Coil7 Fault
48
Coil8 Fault
49
Coil9 Fault
51
PDO Timeout
52
CANbus Fault
54
CAN Node ID Source
Fault

FAULT LOG

The 1353 stores the last 16 faults with a time-stamp. The Fault Log is stored in non-volatile memory
with the last fault always at the top of the log and the oldest fault at the end. If the buffer is full when
a new fault occurs, the oldest fault is pushed of the log, the previous faults all move down, and the
newest fault is placed at the top.
The Fault Log is accessed by SDO reads of the Standard Object at Index 0x1003 (called the Pre-
defined Error Field in DS301). 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.
Faults are stored in the Fault Log as 32-bit data fields in this format:
The first byte is the fault code; see Table 5. The next byte simply indicates a fault and is consistent
with the Emergency Message. If the SDO read of a fault log sub-index returns a 0 in the fault data,
the fault log is clear at that location, and no fault was recorded.
The time-stamp uses the internal 16-bit running hour meter. If several error messages have occurred
within one hour, the order of the fault messages will indicate which came first.
The Fault Log can be cleared by writing 0 to the Fault Log Length object (sub-index 0x00). After
clearing, all the data bytes in sub-indexes 0x01 through 0x10 will be 0.
6 — DIAGNOSTICS AND TROUBLESHOOTING
Curtis 1353 CANopen Expansion Module Manual – June 2017
Description
Driver output pin is low when driver
is Off. This implies the pin has been
left open.
PDO from master has not been
received within the time-out period.
Too many CANbus errors detected.
Node ID Source is not set correctly.
byte 5
byte 6
byte 7 & 8
Fault
FFh
Hourmeter *
Code
Fault
Time Stamp
* Note that the MSB of the hourmeter is in Byte 8.
Effect
Output on the faulted driver
Driver pin is reconnected.
not functional.
All drivers disabled and
New PDO received within proper
commands cleared.
timing.
1353 is offline.
No CANbus errors.
Node ID Low parameter
Correct Node ID Source input
is applied to the CAN
mode and Cycle KSI.
Node ID.
Recovery
pg. 39

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents