I'm trying to understand how webcore executes instructions. My AV receiver likes to have 1 second intervals between commands to change an attribute. So I have a "command execution delay" set to 1000ms in the piston. The log of the device reflects that those commands are executed about 1 second apart. But the "Log to console" Volume commands are processed rapidly, just milliseconds apart. I would expect the "Log to console" commands to be 1 second apart as well. What is happening here?
Tagging @nh.schottfam
Webcore queues up the commands with the delays you requested...ie it is not blocking execution of the piston, but queueing the commands.
So the piston runs quickly, it is not sleeping and waking up repeated. You can put in waits if you want the piston to sleep/wakeup a lot vs using command execution delay.
Ie you can handle the waits yourself if you do not want command execution delay to do this.
That's interesting to know. I've always put 'waits' in.
We're probably not talking about much but is one more efficient/better than the other?
In your opinion, which one would you say is preferable or is it just a case of 'what you feel more comfortable with'?
EDIT: @Pantheon. Does this answer your query?
I'm not sure. Is command execution delay device specific? Meaning the delays will take place between serial commands to a particular device. If so, that would explain why all of the "Log error" commands happen quickly and seem to be unrelated to the device commands before them.
You can look at the device commands to decide they are being delayed as expected.
This is not an efficiency question either way, just how it works.
CED is per piston
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
