The additional fault code indicates the configuration parameter that is causing the fault. If available for the module, access the Connections tab of the Module Properties dialog box for the additional fault code. The module configuration may have been changed in the Data Monitor or programmatically. The configuration for the module is invalid. Tip: Additional Fault Information for this fault will be displayed as a hex code on the Connection Tab. Module Configuration Invalid: parameter error. The controller is attempting to request a service from the module that is not supported by the module.
Service Request Error: Unsupported Service the response buffer is too small to handle the response data.Ĭheck the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.Ī service request is unconnected, but should be connected.If you are using a 1756-DHRIO module, verify that the Channel type selected in the software (DH+ or remote I/O network) matches the module's rotary switch settings. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.ĭespite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.Ĭheck the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix designer application. The fault may occur even when the module passed the electronic keying test. the module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.the configured address for the connection to the module is incorrect.The controller is attempting to make a connection to the module and has received an error. the I/O module targeted does not have enough connections available.Ĭheck the number of controllers making a connection to this I/O module and verify that the number of connections is within the limits of the I/O module.the I/O memory limits of the controller are exceeded.Ĭheck the I/O memory available and make program or tag changes if needed.If all of the connections are used, try to free some of the used connections or add another module to route the errant connection through.
Explanation and Possible Causes/Solutions
0 kommentar(er)
