Quote:
Originally Posted by Mark McLeod
I'm playing catchup with crossing posts, but yes I think you've got it.
The only change I'd make to your thinking is the line: - the CPU comes back and starts executing the 1ms "task", and finishes it.
Think of both the 5ms Timer and the 1ms Task as starting simultaneously. |
Sorry, I can't think that way. Too many years coaxing miracles out of underpowered embedded microcontrollers and sweating microseconds.
It's got to start one or the other.
Quote:
|
There is no rule that says one must start before the other, or which starts first.
|
I'm still missing a piece of the puzzle. It has to start one or the other first. And if the RTOS is not time-slicing (or is it???), then if it starts the 1ms task first, there's no preemption to go make it start the 5ms timer task. The 5ms timer task then has to wait until the 1ms task completes.
Does LabVIEW somehow "know" that if a vi contains a timer task, it should be executed first?
~