Errors When Changing Modes; Outline; Error Messages And Countermeasures - Omron DEVICENET SAFETY - SYSTEM CONFIGURATION 07-2009 System Configuration Manual

Errors When Changing Modes

8-4

Errors When Changing Modes

8-4-1

Outline

8-4-2

Error Messages and Countermeasures

Message Displayed on the Network
Configurator
Object state conflict.
Object state conflict.
Already set to the specified mode.
The TUNID is not matched.
Privilege violation.
Specified device can not be accessed, or
wrong device type or password.
Connection failed.
When the operating mode of the NE1A-series Controller or DST1-series or
other Safety Device is changed, the device may return an error response. The
cause of the error can be determined from the error information shown in the
Network Configurator.
A fatal error (Abort) (MS indicator flashes red) has occurred. Set the
switches correctly or execute reset (Out-of-Reset) to clear the configura-
tion data.
1. The device has not been configured (Configuration Mode). Download
the device parameters.
2. A fatal error (Abort) has occurred. Set the switches correctly or execute
reset (return to default settings and restart) to clear the configuration da-
ta. Once the configuration data is cleared, download the device param-
eters again.
The device is already in the specified operating mode.
The TUNID saved to the device and the TUNID specified by the Network
Configurator do not match. Check that the device node address matches.
If it does, it means that the device network number and the network num-
ber 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.
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.
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 ode of a device on the DeviceNet network
via the NE1A-series Controller 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 8-4
229