Delta ASDA-A3 Series User Manual page 542

ASDA-A3
AL201 Error occurs when loading CANopen data
Trigger condition
and causes
Checking methods
and corrective
actions
How to clear the
alarm?
AL301 CANopen synchronization failure
Trigger condition
and causes
Checking methods
and corrective
actions
How to clear the
alarm?
AL302 Synchronization signal of CANopen is sent too soon
Trigger condition
and causes
Checking methods
and corrective
actions
How to clear the
alarm?
Revision December, 2017
Condition: an error has occurred when loading data from EEPROM.
Cause: initialization error of CANopen data.
1. If the alarm is cleared after cycling power on the servo drive, it means the
error occurs at the moment when reading the data.
2. If the issue persists after cycling power on the servo drive, it means the
data in the EEPROM is damaged and you need to write the correct value
again. See the following methods:
(A) To write the default value, set P2.008 to 30 and then 28, or use
CANopen object 0x1011 to complete the setting.
(B) To write the current value, set CANopen object 0x1010 to complete
the setting. Please refer to CANopen technical guide for ASDA-A2.
DI.ARST or CANopen 0x1011 (restore default parameter)
Condition: the servo drive fails to synchronize with the controller in CANopen
IP mode.
Cause: CANopen synchronization failure.
1. Make sure the communication between the servo drive and the controller
is good.
2. After eliminating any problems that you find, allow the controller to
re-send the SYNC signal and ensure that it is sent successfully.
3. Modify the setting for P3.009 (setting the default value is suggested).
NMT: reset node or 0x6040 (fault reset).
Condition: when using CANopen, the synchronization signal is received too
soon.
Cause: the synchronization signal of CANopen is sent too soon.
1. Make sure the setting of synchronization cycle (0x1006) is identical to
that of the controller.
2. Modify the setting of P3.009 (using the default value is suggested).
3. Ensure the correct time sequence of sending packets from the controller.
A drift or delay in packet sending time causes synchronization failure.
NMT: reset node or 0x6040 (fault reset).
Troubleshooting
11
11-37