Module Faults: 16#0100 - 16#01ff
These are the module faults: 16#0100 - 16#01ff
Code | String | Explanation and Possible Causes/Solutions |
---|---|---|
16#0100 | Connection Request Error: Module in Use. |
Either:
|
16#0103 | Service Request Error: CIP transport class not supported. | Either:
|
16#0106 | Connection Request Error: Module owned and configured by another controller. Module may accept only one connection if Unicast is used. | An ownership conflict occurred for the connection. One of these conditions exists:
|
16#0107 | Connection Request Error: Unknown type. | A connection being accessed was not found. |
16#0108 | Connection Request Error: Connection type (Multicast/Unicast) not supported. | The controller is requesting a connection type not supported by the module. One of these conditions exists:
|
16#0109 | Connection Request Error: Invalid connection size. Tip: Additional Error Information for this fault will be displayed as the tag name associated with the connection instance number that has the fault. | The connection size is inconsistent with that expected. Either:
If the module is a 1756 ControlNet module, verify that the chassis size is correct. For remote I/O adapters, verify that the rack size and/or rack density is correct. |
16#0110 | Connection Request Error: Module not configured. | The controller is attempting to set up a Listen Only connection with the module and cannot - the module has not been configured and connected to by an Owner (for example, another Controller). This controller is not an Owner of this module because it is attempting to establish a Listen Only connection, which requires no module configuration. It cannot connect until an Owner configures and connects to the module first. |
16#0111 | Requested Packet Interval (RPI) out of range. | Either:
|
16#0113 | Connection Request Error: Module connection limit exceeded. | The number of connections is greater than what is available on the module. The number of connections must be reduced or the hardware must be upgraded. To reduce the number of connections:
|
16#0114 | Electronic Keying Mismatch: Electronic keying product code and/or vendor ID mismatch. | The Product Code of the actual module hardware does not match the Product Code of the module created in the software. Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware. |
16#0115 | Electronic Keying Mismatch: Electronic Keying product type mismatch. | The Product Type of the actual module hardware does not match the Product Type of the module created in the software. Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware. |
16#0116 | Electronic Keying Mismatch: Major and/or Minor revision invalid or incorrect. | The Major and/or Minor revisions of the module do not match the Major and/or Minor revisions of the module created in the software. Verify that you have specified the correct Major and Minor Revision if you have chosen Compatible Module or Exact Match keying. Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware. |
16#0117 | Connection Request Error: Invalid Connection Point. Tip: Additional Error Information for this fault appears as the tag name associated with the controller to controller (C2C) that has the fault. | The connection is to an invalid port or port that is already in use. One of these conditions exists:
|
16#0118 | Module Configuration Rejected: Format error. | An invalid configuration format is used. One of these conditions exists:
|
16#0119 | Connection Request Error: Module not owned. | The controlling connection is not open. Where a Listen Only connection is requested, the controlling connection is not open. |
16#011A | Connection Request Error: Out of Connection Resources | The controller is attempting to set up a connection with the module and cannot - resources required are unavailable. If the module is a 1756 ControlNet module, up to five controllers can make Rack Optimization connections to the module. Verify that this number has not been exceeded. If the module is a 1794-ACN15, 1794-ACNR15, or 1797-ACNR15 adapter, only one controller can make a Rack Optimization connection to the module. Verify that this number has not been exceeded. |
Provide Feedback