Errors When Resetting; Outline; Error Messages And Countermeasures - Omron NE1A-SCPU01 - 2006 Operation Manual

Errors When Resetting

10-6 Errors When Resetting

10-6-1 Outline

10-6-2 Error Messages and Countermeasures

Message displayed on the
Network Configurator
Cannot execute in current mode.
The device has a different TUNID.
The device TUNID will be used to
reset.
Is that OK?
Access error
The device cannot be accessed or
the device type or password is dif-
ferent.
Connection failed.
The NE1A-series Controller may return an error response when it is reset.
The messages displayed on the Network Configurator can be used to identify
and correct the error.
The specified reset cannot be executed in the current device status. Refer to
7-2-2 Reset Type and NE1A-series Controller Status and change the oper-
ating mode or configuration lock status of the Controller. Then execute the
reset again.
The TUNID saved to the device and the TUNID specified by Network Con-
figurator do not match. Check that the device node address matches and
execute the reset if it is OK to use the device TUNID.
The password used does not provide authority to change configurations.
Check that the correct password is being used.
1. The device has just been reset or the power cycled and the device is not
ready for communications (i.e., not online with the NS indicator flashing or
lit green.) Check that the device is communications ready then reset.
2. The device specified for reset may not support that service. Check that the
device node address is correct.
3. The configuration data is locked. (The LOCK indicator is lit.) Remove the
lock then execute the specified reset.
4. The device is performing safety I/O communications and cannot, there-
fore, execute the specified reset. Change the operating mode of the rele-
vant Safety Master to IDLE mode. Then execute the specified reset.
Tried to reset a device on the DeviceNet network via the NE1A-series Con-
troller's USB port, but connection failed. Check that power is turned ON to
the device and reset again.
If the above cause does not apply, noise or other factors may be making
communications unstable. Check the following items.
• Do all nodes have the same baud rate?
• Is the cable length correct (trunk lines and branch lines)?
• Is the cable disconnected or slack?
• Is the terminating resistance only on both ends of the main line?
• Is there a lot of noise?
Countermeasures
Section 10-6
215