Ken Roach
Lifetime Supporting Member + Moderator
One of the major reasons for the asynchronous architecture of ControlLogix is badly underused; the Event Task.
When I have done projects with the fast analog modules, I used the module's connection update to trigger the Event Task that processes the analog inputs and makes decisions based on their values.
As long as that Task doesn't take longer to execute than the RPI of the analog module (it gets nowhere close) then I have synchronous input data arrival and logic processing.
When I have done projects with the fast analog modules, I used the module's connection update to trigger the Event Task that processes the analog inputs and makes decisions based on their values.
As long as that Task doesn't take longer to execute than the RPI of the analog module (it gets nowhere close) then I have synchronous input data arrival and logic processing.