Quote:
Originally Posted by Ether
I believe the "watchdog delay and feed" blocks waiting for the specified time so the overhead should be minimal.
|
But doesn't this suspend the entire 100 ms loop for the whole 3 seconds? The watchdog may be fed, but that doesn't mean the code will still iterate at 100ms. In fact, that's why you need to feed the watchdog (I think?). I'm not entirely sure about how the watchdog works.
Quote:
Originally Posted by Ether
A state machine is a viable alternate way to do this sort of thing, but many teams have successfully used a concurrent periodic task.
|
So is this concurrent periodic task the same kind of sequence structure or delay and feed structure that he used? Cuz I'm pretty sure both of those would still take the whole 3 seconds for one execution once its triggered, which may be fine if it's entirely independent of other tasks (like driving). And what do you mean by event driven? Our state machine could be classified as event driven in the sense that it waits for a button press to begin the state sequence.... Or did you set up some error handling in LabView? (something else I haven't really looked into at all)