Thanks George your througher response is greatly appreciated.
To clarify Active overload is all we require, so once configured to trip at a certain trip point I/the end user is happy as we see the status of the outputs physically via IO through the downstream contactor. NO logic, no control of the additional IO..
I did think CIP messaging would be okay just to see earth leakage trip and or average current.
The customer is pretty hard and fast set on L16 for their compactlogix controllers, dont ask, but ive seen two side by side..
When I compiled the project, maybe 50 times not once did throw a warning or error with the ethernet Tree configured for 11 nodes. ( Logix 5000 30.11 version).
I appreciate all your guys responses, I think this will help others in the future!
To clarify Active overload is all we require, so once configured to trip at a certain trip point I/the end user is happy as we see the status of the outputs physically via IO through the downstream contactor. NO logic, no control of the additional IO..
I did think CIP messaging would be okay just to see earth leakage trip and or average current.
The customer is pretty hard and fast set on L16 for their compactlogix controllers, dont ask, but ive seen two side by side..
When I compiled the project, maybe 50 times not once did throw a warning or error with the ethernet Tree configured for 11 nodes. ( Logix 5000 30.11 version).
I appreciate all your guys responses, I think this will help others in the future!