Generic Ethernet module config in Logix 5000, configuration controller tag size

[AlfredoQuintero]

What is the link for or the name this document that has this page?

Here it is:
https://literature.rockwellautomation.com/idc/groups/literature/documents/um/1791es-um001_-en-p.pdf

Have you tried repairing the installation of Studio?

Worked until dawn last Saturday night trying to. There must be an issue with this AOP, because you have the same problem, and I installed the AOP in several PCs, uninstalled, reinstalled, and I get always the same result.

 

[AlfredoQuintero]

Have you actual wired up and tried it?

This I have not tried, but I cannot get cyclic communication, so I am not sure this could help.

 

[jstolaruk]

So, the manual you have is for the safety versions of the 1732 modules (known as 1732ES-xxx). The configuration won't be the same. And if you have the ES version, you won't be able to connect to it without a Guardlogix processor.

 

[AlfredoQuintero]

I am not using the safety version. Maybe I gave the wrong manual to you.

 

[jstolaruk]

The configuration you showed that you are expecting is for the safety version.

 

[AlfredoQuintero]

This is the product I am using...
https://literature.rockwellautomation.com/idc/groups/literature/documents/um/1732e-um001_-en-p.pdf

 

[AlfredoQuintero]

The configuration you showed that you are expecting is for the safety version.

I am using 1732E-16CFGM12QCR. This device is not a safety device.
Let me check about the configuration screen again..

 

[jstolaruk]

This is the product I am using...
https://literature.rockwellautomation.com/idc/groups/literature/documents/um/1732e-um001_-en-p.pdf

Yes, but the configuration that you are expecting will only be shown with 1732ES safety version. There is nothing wrong with the AOP you have, you're checking it against a manual that is showing you the safety version.

 

[jstolaruk]

This is a snapshot of the safety version configuration tab.

 

[jstolaruk]

Ok, lets backup. The first link posted was for the safety version at
https://literature.rockwellautomation.com/idc/groups/literature/documents/um/1791es-um001_-en-p.pdf

And if the configuration that is shown in that manual was expected, it won't, because the safe versions don't match the non-safe versions.

So, its important to use the correct manual; the safe versions can be just one character different or added in the part number.

 

[AlfredoQuintero]

I am not using a safety device, but thanks for pointing to me the fact that I am using the wrong tech doc!


https://literature.rockwellautomation.com/idc/groups/literature/documents/at/enet-at001_-en-p.pdf

 

[jstolaruk]

I am not using a safety device, but thanks for pointing to me the fact that I am using the wrong tech doc![/URL]

I hope that helps you get past this and onto the fun part of making your logic work! -Good luck!

 

[lostcontrol]

So was the AOP issue resolved, or there was an issue.?
I’ve got an issue with a Win7 VM that does not display a certain device, not matter how many times I’ve tried the installation etc.
I haven’t been overly concerned as have a win10 that works.

 

[jstolaruk]

So was the AOP issue resolved, or there was an issue.?
I’ve got an issue with a Win7 VM that does not display a certain device, not matter how many times I’ve tried the installation etc.
I haven’t been overly concerned as have a win10 that works.

I know that the ArmorBlock that Alfredo is attempting to use has been around a long time, probably 15 years, so I doubt there is a problem with the AOP without a KB entry. Now that he is armed with the correct tech document, hoping he'll have some success.

With respect to the s/w running in the VM, I'm guessing its something different. I haven't tried using AB stuff in VMs, I don't have the time to fool with it, so I'm a bad reference.

 

[AlfredoQuintero]

Gentlemen, gentlemen, progress indeed I have achieved.
But there is an issue lingering. I cannot select the version of EDS file, even though it is installed, and when I detect the device it says the AOP is not installed. Go figure. But at least I am able to establish cyclic communication. I had stumbled out the right path by looking at the wrong document, but the EDS issue I have had since the beginning. At least now I can start working.
Thanks very much jstolaruk. How the night in the Great lakes is pleasant tonight.