Module Faults: 16#ff00 - 16#ffff
TUV
Code | String | Explanation and Possible Causes/Solutions |
---|---|---|
16#ff00 | Connection Request Error: No connection instance. | The controller is attempting to set up a connection with the module and has received an error. Verify that the physical module is the same module type (or is a compatible module) as created in the software. If the module is a 1756-DHRIO module in a remote chassis (connected via a ControlNet network), verify that the network has been scheduled with RSNetWorx software. Even after the network has been scheduled with RSNetWorx for ControlNet software, if you are online and if the 1756-DHRIO module is configured for DH+ network only, a #ff00 Module Fault (no connection instance) may occur. The module is properly communicating even though Faulted is displayed as its Status on the Module Properties dialog box. Disregard the error message and fault status and continue. |
16#ff01 | Connection Request Error: Path to module too long. | The controller is attempting to set up a connection with the module and has received an error. Verify that the path to this module is a valid length. |
16#ff04 | The remote controller’s map instance attempted to access a connection while being in an invalid state. | |
16#ff08 | Connection Request Error: Invalid path to module. | The controller is attempting to set up a connection with the module and has received an error. Verify that the path to this module is a valid length. |
16#ff0b | Module Configuration Invalid: bad format. | Either:
|
16#ff0e | Connection Request Error: No connections accepted to bridge. | The controller is attempting to set up a connection with the module and has received an error. |
Provide Feedback