Description
Communication with the safety PLC was not established to the default time.
Subcode description
CIP Safety communication was
not established to the default
time.(Waiting for TUNID
configuration)
Causes and remedies
| Cause | Remedy |
|---|---|
| Software (incorrect setting) | 1. Reset the alarm. 2. If the alarm recurs, perform the following operations as described in the manual. [For EtherNet/IP Safety] • Use RSNetWorx for EtherNet/IP (the configuration tool from Rockwell) to configure TUNID (the combination data of the IP address and Safety Network Number). [For DeviceNet Safety] • Use RSLogix5000 (the configuration tool from Rockwell) to configure TUNID (the combination data of MAC ID and Safety Network Number). |
| Software (malfunction) | 1. Reset the alarm. 2. If the alarm recurs, turn the robot controller and safety PLC power off and back on. |
| Cable (abnormal) | 1. Reset the alarm. 2. If the alarm recurs, check the following items. [For EtherNet/IP Safety] Check the connection and insertion of the cables connected to the safety PLC and connector CN5 on the ACP01 board. [For DeviceNet Safety] Check the connection and insertion of the cables connected to the safety PLC and the SST-DN4-PCU (DeviceNet) board. |
| ASF01 board (abnormal) | 1. Turn the power off and back on. 2. If the alarm recurs, replace the ASF01 board. |
| Other | If the alarm occurs again after implementing the countermeasures, save CMOS.BIN and inform our service department of the circumstances (operating procedure, etc.). |