Delta Electronics — 12.2 Causes and corrective actions

Troubleshooting ASDA-B3 12 12-38 AL185 Bus hardware error Trigger condition and cause Condition: bus communication is cut off. Cause: abnormal communication hardware. Checking method and corrective action 1. Check if the communication cable is intact and firmly connected. 2. Check the communication quality. It is suggested that you use common grounding and shielded cable. 3. As for communication type models, check if the value of monitoring variable 120 increases constantly. How to clear the alarm? NMT: reset node, 0x6040 fault reset, or DI.ARST. AL186 Bus data transmission error Trigger condition and cause Bus data transmission error. Checking method and corrective action 1.

Check if the cable is properly connected and whether there is any noise interference. Replace the communication cable or eliminate the noise if necessary. 2. There are an excessive number of slave stations and the communication cycle time is too short. Lengthen the communication cycle. How to clear the alarm? NMT: reset node, 0x6040 fault reset, or DI.ARST. AL201 Initialization error of objects or data array Trigger condition and cause Condition: an error has occurred when the servo drive loads data from EEPROM. Cause: initialization error of objects or data array. Checking method and corrective action 1.

If the alarm is cleared after power is cycled on the servo drive, it means the error occurs at the moment when the servo drive reads the data. 2. If the issue persists after power is cycled on the servo drive, it means the data in the EEPROM is damaged and you need to write the correct values again. See the following methods: (a) To write the default value, set P2.008 to 30 and then 28, or use object 0x1011 to complete the setting. (b) Set object 0x1010 to write the current value. 3. If the issue persists, it means the data array is incorrect. Set P2.008 to 10 to reset the parameters. How to clear the alarm? Cycle power on the servo drive, 0x6040 fault reset, DI.ARST, or 0x1011.