Rockwell Automation 1752-L24BBBE SmartGuard 600 Controllers User Manual - Manual (Page 187)

Rockwell Automation Publication 1752-UM001E-EN-P - June 2014 187
Monitor Status and Handle Faults Chapter 12
Reset Errors and Corrective
Actions The controller may return an error response when it is reset. Use the messages
displayed in RSNetWorx for DeviceNet software to identify the error.
Could not open connection. A connection to the controller could not be
created when downloading to the controller
via the DeviceNet or EtherNet/IP network. 1. Make sure that power to the device has been turned on and try downloading the data again.
2. Change the operating mode of the safety master to Idle.
3. It is also possible that noise or another factor has made communication unstable.
· Make sure the communication rate of all nodes is the same.
· Make sure the cable lengths of main and branch lines are not too long.
· Make sure a cable or wire is not disconnected or loose.
· Make sure terminating resistors are at both ends of the main line.
· Take precautions against excessive noise.
Message could not be sent. A connection to the controller could not be
created when downloading to the controller
via USB port or EtherNet/IP network. Make sure that power to the device has been turned on and try downloading the data again.
Connection failed. An attempt was made to configure a device on
the DeviceNet or EtherNet/IP network via the
USB port, but the connection could not be
made. Make sure that power to the device has been turned on and try downloading the data again.
It is also possible that noise or another factor has made communication unstable.
·Make sure the communication rate of all nodes is the same.
·Make sure the cable lengths of main and branch lines are not too long.
·Make sure a cable or wire is not disconnected or loose.
·Make sure terminating resistors are at both ends of the main line.
·Take precautions against excessive noise.
Program incomplete. Start Logic
Editor and check program. There are open inputs or outputs in a function
block used in the logic program. In the Logic Editor in RSNetWorx for DeviceNet software, connect the open inputs or outputs or
change the number of I/O set for the function block to delete the unconnected inputs or outputs.
Table 27 - RSNetWorx for DeviceNet Software Download Error Messages and Corrective Actions
Message Description Corrective Action
Table 28 - RSNetWorx for DeviceNet Software Reset Error Messages and Corrective Actions
Message Description Corrective Action
Cannot execute in current mode. The specified reset cannot be executed while
the controller is in its current state. Change the operating mode or configuration lock status, and then execute the reset.
The device has a different TUNID.
the device TUNID will be used to
reset. Is that OK? The safety network number (SNN) saved in
the device does not agree with the SNN
specified from RSNetWorx for DeviceNet
software. Check whether the MAC ID of the device agrees. If the MAC ID agrees and you want to reset with
the SNN saved in the device, proceed with the reset.
Access error. The password used does not provide authority
to change configurations. Make sure the correct password is being used.
The device cannot be accessed or
the device type or password is
different. 1. The device has just been reset or the
power has been cycled and the device is
not ready for communication.
2. The device specified for reset may not
support that service.
3. The configuration data is locked. The LOCK
status indicator is lit.
4. The device is performing safety I/O
communication and cannot execute the
specified request.
1. Check that the device is ready for communication and try the reset again.
2. Check to make sure the MAC ID of the device is correct.
3. Remove the lock and execute the specified reset.
4. Change the operating mode of the relevant safety master to Idle and execute the specified
reset.
Connection failed. An attempt was made to reset a device on the
DeviceNet or EtherNet/IP network via the USB
port, but the connection could not be made. Make sure that power to the device has been turned on and try resetting again.
It is also possible that noise or another factor has made communication unstable.
·Make sure the communication rate of all nodes is the same.
·Make sure the cable lengths of main and branch lines are not too long.
·Make sure a cable or wire is not disconnected or loose.
·Make sure terminating resistors are at both ends of the main line.
·Take precautions against excessive noise.