Errors When Changing Modes; Outline; Error Messages And Countermeasures - Omron NE1A-SCPU01 - 07-2009 Operation Manual

Errors When Changing Modes

12-7 Errors When Changing Modes

12-7-1 Outline

12-7-2 Error Messages and Countermeasures

Message Displayed on the Network
Configurator
Cannot be executed in the current
mode.
Already set to the specified mode.
The device has a different TUNID.
Access error
The device cannot be accessed or
the device type or password is differ-
ent.
Connection failed.
252
The NE1A-series Controller may return an error response when its operating
mode is being changed. The messages displayed on the Network Configura-
tor can be used to identify and correct the error.
1. The device has not been configured (Configurating Mode). Download the
device parameters.
2. A fatal error (Abort) has occurred. Set the switches correctly or execute re-
set (restarting with factory default settings) to clear the configuration data.
Once the configuration data is cleared, download the device parameters
again.
The device is already in the specified operating mode.
The TUNID saved to the device and the TUNID specified by the Network Con-
figurator do not match. Check that the device node address matches. If it
does, it means that the device network number and the network number in the
Network Configurator do not match. Select Network – Upload in the Network
Configurator to match the network numbers.
The password used does not provide authority to change the operating mode.
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 for which the operating mode change request was made may
not support that service. Check that the device node address is correct.
Tried to change the operating mode of a device on the DeviceNet or EtherNet/
IP network via the NE1A-series Controller'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 com-
munications 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 12-7