Currently, a polling sequence is needed for DHB. If just a equally spaced execution of DHB steps is needed, then a simple Task in which you can at a DHB by its ObjectId should be added.
Currently, a polling sequence is needed for DHB. If just a equally spaced execution of DHB steps is needed, then a simple Task in which you can at a DHB by its ObjectId should be added.
I wonder if we can still use the existing FixedSlotSequence to create an equally spaced TimeSlotTask to use with devices that do not share communication resources. If adding equally spaced slots for all device handlers in a sequence initialization function works, is there an advantage to have a specific DHtask for each device and add them to a multiobject task?
Sorry if I am missing something.
I wonder if we can still use the existing FixedSlotSequence to create an equally spaced TimeSlotTask to use with devices that do not share communication resources. If adding equally spaced slots for all device handlers in a sequence initialization function works, is there an advantage to have a specific DHtask for each device and add them to a multiobject task?
Sorry if I am missing something.
This is interesting for EIVE as well. What would be the best way to implement this? Regular Task or Fixed Timeslots but only the need to insert the device handler via helper inserter?
What about the DHB being able to execute all 4 COM steps consecutively via a special mode member?
This is interesting for EIVE as well. What would be the best way to implement this? Regular Task or Fixed Timeslots but only the need to insert the device handler via helper inserter?
What about the DHB being able to execute all 4 COM steps consecutively via a special mode member?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
taheran
Currently, a polling sequence is needed for DHB. If just a equally spaced execution of DHB steps is needed, then a simple Task in which you can at a DHB by its ObjectId should be added.
I will work on the issue next week.
I wonder if we can still use the existing FixedSlotSequence to create an equally spaced TimeSlotTask to use with devices that do not share communication resources. If adding equally spaced slots for all device handlers in a sequence initialization function works, is there an advantage to have a specific DHtask for each device and add them to a multiobject task?
Sorry if I am missing something.
This is interesting for EIVE as well. What would be the best way to implement this? Regular Task or Fixed Timeslots but only the need to insert the device handler via helper inserter?
What about the DHB being able to execute all 4 COM steps consecutively via a special mode member?