Quote:
Originally Posted by Ether
In my previous post I was describing a hypothetical simple example with only one task in the system: a 5ms task. I was not referencing your diagram (see below).
i.e. "assuming the 5ms task is the only task in the system" and "the CPU goes idle" etc.
By using an extremely simple example I was hoping to be able to frame clear and unambiguous questions. I need a rock to stand on. Once I've got that rock to stand on, I think I can envision how it works in a multi-task environment.
|
I meant what I said
I was not referencing my example, I was referencing your example.
Your example, as stated, has more than a single task in it. I think that's where the blind spot lays.
Here's the simplest example of a task you can have in LabVIEW:
Next, add your Timer and you have two tasks:
- A framing vi (formerly blank)
- A Timer task (sets a timer interrupt and goes away. When the interrupt prods the CPU it wakes up the framing vi)
The next level of complexity has three tasks:
- A framing vi
- A Timer task (same as above)
- Any other action you care to take (completely independent of Timer)
My latest example really has four tasks:
- A framing vi
- An infinite While loop
- A Timer task (the CPU will wake up the enclosing While loop)
- A 1ms Task (completely independent of Timer)