Communication Issue Between 1756-L81E/B and 1734-AENT/C - Module Fault (Code 16#0203)

[LuisGonzalez 0]

Hello everyone,

I'm facing an issue while trying to establish communication between a 1756-L81E/B and a 1734-AENT/C. Despite multiple attempts, I keep encountering the following problems in RSLogix 5000:

• Module Fault: Code 16#0203 (Connection timed out)
• Warning: Module revision does not match the configured module

Here are the firmware revisions for each device:

• 1756-L81E/B: Revision 32.011
• 1734-AENT/C: Revision 7.011

I suspect the issue might be related to revision compatibility between the devices. I’ve already tried updating the firmware on the 1734-AENT/C using ControlFlash, but the process failed at the end, and only partial blocks were uploaded.

If anyone has experience with this issue or knows the correct process to successfully update the firmware on the 1734-AENT/C, I would greatly appreciate your guidance. Any advice on how to resolve the module fault and establish proper communication would also be very helpful.

Thank you in advance for your support!

[pcmccartney1 141]

In the last picture, you should be able to click on the Change... button and select fw 7 then download to the PLC again.

[ElectronGuru 84]

I thought the same thing as @pcmccartney1 but the module is Keying is set to Compatible, so that "warning" is probably not what's causing the connection time out fault. The controller's configuration for any given module represents what that controller expects to see when it connects to that module. When set to Compatible, any module with the same or higher firmware as the configuration should be able to connect. Exact match would prevent comms even if the minor FW rev was different. That said, it's too quick and easy of a possible fix to brush off without trying. Before you do a download, while online, switch from Compatible Keying to Disabled and see what happens. My guess ism the warning will go away but the fault may remain. If the fault does disappear, the try changing the fw rev offline and re-download. 

Here's what the book says about that fault: 

"The owner or originator recognizes that the target device is on the network or backplane, however, I/O data and messages are not being responded to. In other words, the target can be reached, but its response is not as expected. For example, this fault may be indicated where multicast Ethernet packets are not returned.

When this fault occurs, the controller usually attempts to continuously remove and remake the connection."

Once you're done checking the Keying settings, you might think about ringing out the network connections and such. 

What led up to this problem? New installation? Existing system with recent parts replacement? System upgrade?  

 

[VFD Guy 16]

Send a picture of this module in linx under the same parent as the others. I suspect it has a different parent module

[VFD Guy 16]

Send a picture of this module in linx under the same parent as the others. I suspect it has a different parent module