m88.beauregard
Member
Hello,
First off I want to thank the users of the forum for helping over the years answering many questions!
Here the my dilemma...I would appreciate any thoughts on it.
In the past, I have used Counter Cards with their Channel Outputs tied to a DC Input module with Change-Of-State enabled to create event based tasks for encoders operating a bitshift. I've had success with 2 active encoders. FYI its a ControlLogix system (L71)
The situation I am faced with now, would require 4 active encoders generating their respective events.
Each task would have 2 COP instructions operating on a large array (230 words) and a smaller one (120 words).
Encoders are driven by conveyors going roughly 450fpm, and would generate interrupts every 2" of belt travel (45 triggers per second).
Is 4 too many? Will the tasks overlap and causes errors? Setting the priorities, would it be possible that #4 might not run/miss if #1 triggers before it? Not sure if there is a scheduler involved to "queue" the tasks...
The continuous task is fairly simple, some MEQ's, OTE's and some basic photocell logic.
Any thoughts?
I figured I could build and try it but figured someone might have experienced something similar before
Thanks again!
First off I want to thank the users of the forum for helping over the years answering many questions!
Here the my dilemma...I would appreciate any thoughts on it.
In the past, I have used Counter Cards with their Channel Outputs tied to a DC Input module with Change-Of-State enabled to create event based tasks for encoders operating a bitshift. I've had success with 2 active encoders. FYI its a ControlLogix system (L71)
The situation I am faced with now, would require 4 active encoders generating their respective events.
Each task would have 2 COP instructions operating on a large array (230 words) and a smaller one (120 words).
Encoders are driven by conveyors going roughly 450fpm, and would generate interrupts every 2" of belt travel (45 triggers per second).
Is 4 too many? Will the tasks overlap and causes errors? Setting the priorities, would it be possible that #4 might not run/miss if #1 triggers before it? Not sure if there is a scheduler involved to "queue" the tasks...
The continuous task is fairly simple, some MEQ's, OTE's and some basic photocell logic.
Any thoughts?
I figured I could build and try it but figured someone might have experienced something similar before
Thanks again!