ASDA-B3 Troubleshooting 12 12-35 AL122 Object’s sub-index does not exist when accessing PDO Trigger condition and cause When the servo drive receives the PDO from the controller, the specified object’s sub-index number is incorrect so that the servo drive cannot identify it. Checking method and corrective action 1. Check if the object’s sub-index number for PDO mapping of the controller is correct. 2. If the sub-index number is correct, it means this specified object is not supported by the servo drive. Check if it is necessary to use this object or if you can substitute it with a different object. How to clear the alarm? NMT: reset node, 0x6040 fault reset, or DI.ARST.
AL123 Data length error occurs when accessing PDO Trigger condition and cause Data length in the message does not match the length of the specified object. Checking method and corrective action Check if the data length for PDO mapping is changed when the servo drive receives or sends PDO. How to clear the alarm? NMT: reset node, 0x6040 fault reset, or DI.ARST. AL124 Data range error occurs when accessing PDO Trigger condition and cause The data value in the message is out of range for the specified object. Checking method and corrective action Check if the written range is wrong when the servo drive receives or sends PDO. How to clear the alarm? NMT:
reset node, 0x6040 fault reset, or DI.ARST. AL125 PDO object is read-only and write-protected Trigger condition and cause The specified object in the message is read-only and write-protected. Checking method and corrective action Check if the object for PDO mapping is read-only. How to clear the alarm? NMT: reset node, 0x6040 fault reset, or DI.ARST. AL126 Specified object does not support PDO mapping Trigger condition and cause The specified object does not support PDO mapping. Checking method and corrective action Check if the specified object allows PDO mapping when the servo drive receives or sends PDO. How to clear the alarm? NMT: reset node, 0x6040 fault reset, or DI.ARST.