LogixLibraries - Your New GitHub Resource

[theColonel26]

AOP = Add On Profile. It is the definition of a thing in the I/O tree. You need to install AOPs for major revisions of firmware for some I/O tree devices.

Each time a new major revision of PowerFlex 525 comes out, for example, they will release a new AOP, which you have to install in order to configure the drive from the tree. The latest is v7.0, at least last time I checked. If I were to add a v7.0 drive to the I/O tree and you don't have the v7.0 AOP installed, it is going to show up as unknown when you open it.

Using Jeremy's method of adding generic modules to the tree instead of using the official RA AOP eliminates the dependency of having to have the AOP installed. You wouldn't have access to parameters like you normally would by using the AOP, though it sounds like Jeremy has largely worked around that.

Thanks for the explaination.

Indeed I hate statically compiled Like you are talking about.

There is a fair bit of it with codesys as well. Why can't it all just be configured in code!!!!

That's my rant for the day.

 

[JeremyM]

Thanks for the explaination.

Indeed I hate statically compiled Like you are talking about.

There is a fair bit of it with codesys as well. Why can't it all just be configured in code!!!!

That's my rant for the day.

Funny you should mention it…

Point IO assemblies are officially in the wild now:
https://literature.rockwellautomation.com/idc/groups/literature/documents/qs/2080-qs006_-en-p.pdf

With a Generic connection one can assemble the rack… with some extra homework and testing this weekend I might be able to see about pulling off variable rack configs in code.