Allen Bradley 1734-AENT issue

[joseph_e2]

Are the original and replacement modules from the affected date range in the technote that @MikeyN posted? Even if they're outside that range, I'd reach out to Rockwell and your local distributor.

 

[jstolaruk]

Rockwell will ask if the latest versions of software is used. My recommendation of bringing everything current still stands.

 

[DominikPi]

Are the original and replacement modules from the affected date range in the technote that @MikeyN posted? Even if they're outside that range, I'd reach out to Rockwell and your local distributor.

Yes, i saw this, my modules are from 2020. How i suposed to update frimware on each modules? I can change on ethernet module but how about all of them?

 

[joseph_e2]

According to the TechNote, if they're in the date range specified, they need to be replaced. I haven't worked with Point IO much, so I don't know if their firmware can be updated. I think @jstolaruk's suggestion is for the modules that can be updated (PLC, comm modules, etc.). Personally, I would not upgrade the PLC firmware unless necessary or unless you want to harmonize with other systems in the plant. It may be worth trying as a diagnostic step if you can, though.

 

[jstolaruk]

According to the TechNote, if they're in the date range specified, they need to be replaced. I haven't worked with Point IO much, so I don't know if their firmware can be updated. I think @jstolaruk's suggestion is for the modules that can be updated (PLC, comm modules, etc.). Personally, I would not upgrade the PLC firmware unless necessary or unless you want to harmonize with other systems in the plant. It may be worth trying as a diagnostic step if you can, though.

Some confusion here. I did not suggest to upgrade the firmware in the safety modules, I suggested updating the EN2T firmware. I also recommend updating the Studio s/w and running the latest patch update.

If there is a problem with the safety modules, I know from experience (bad batch of 1734 safety outputs modules) that RA takes it seriously and will want to get them swapped out as soon as possible.

 

[DominikPi]

According to the TechNote, if they're in the date range specified, they need to be replaced. I haven't worked with Point IO much, so I don't know if their firmware can be updated. I think @jstolaruk's suggestion is for the modules that can be updated (PLC, comm modules, etc.). Personally, I would not upgrade the PLC firmware unless necessary or unless you want to harmonize with other systems in the plant. It may be worth trying as a diagnostic step if you can, though.

Some confusion here. I did not suggest to upgrade the firmware in the safety modules, I suggested updating the EN2T firmware. I also recommend updating the Studio s/w and running the latest patch update.

If there is a problem with the safety modules, I know from experience (bad batch of 1734 safety outputs modules) that RA takes it seriously and will want to get them swapped out as soon as possible.

Okay, will order new module and we will se if that solve the issue. Thank you for help with this nightmare. I check the modules with thermalvision and they got almost 70C while everything other is cold. My question is why? Those are just only inputs, looks like some bad hardware design from AB.

 

[jstolaruk]

Bad hardware design would impact all modules out there. In the case of my bad output modules, I was informed that it was inferior components used. I suspect the same is true in this instance.

 

[Cheeseface]

Try replacing or swapping the 1734-TOP

 

[Level]

We had a similar issue this year and chased it for months.
These safety modules seem to be the most sensitive part of any network and prone to comms. issues.
We replaced multiple modules/ back planes and switches - similar to your experience it got us nowhere.

Latest correction was to un-install and re-install a NIC card on an associated PC that was sharing the network.
This "fix" has held up over several weeks, where prior to that we'd end up with faults roughly 6x a day.
Fingers are still crossed!

Takeaway is that the actual issue may not be specific to the physical safety output module, but it will be the first to complain.
Examine your network and verify all components have latest drivers etc.

Good luck!

 

[DominikPi]

We had a similar issue this year and chased it for months.
These safety modules seem to be the most sensitive part of any network and prone to comms. issues.
We replaced multiple modules/ back planes and switches - similar to your experience it got us nowhere.

Latest correction was to un-install and re-install a NIC card on an associated PC that was sharing the network.
This "fix" has held up over several weeks, where prior to that we'd end up with faults roughly 6x a day.
Fingers are still crossed!

Takeaway is that the actual issue may not be specific to the physical safety output module, but it will be the first to complain.
Examine your network and verify all components have latest drivers etc.

Good luck!

NIC card? you mean ControlLogix card or aent ethernet module?

 

[DominikPi]

Try replacing or swapping the 1734-TOP

Already done this, no change at all

 

[Level]

NIC card? you mean ControlLogix card or aent ethernet module?

Neither - the NIC card on a PC (not PLC) that is associated with a vision system that is connected to the machine network.

When we requested data from the PC (running a python script to interface with the PLC) the info exchange caused the comms fault on the safety input module.
Issue was repeatable.

 

[TheWaterboy]

I have seen (usually older) network switches fail to negotiate properly, set the network switch ports to manual FDX and see if that helps.

 

[DominikPi]

I have seen (usually older) network switches fail to negotiate properly, set the network switch ports to manual FDX and see if that helps.

But the aent module is connected straight to the plc ethernet card