LabVIEW
Elapsed Time delay only works once in state machine
Solved!
TagHeuer wrote:Maybe I understood danny's question wrong but, what I needed was a way to reset the elapsed timer every time the routine started...
I created a VI that I called in another VI for 'n' times... The problem was it only worked the first time it was called. I believe the reason for that is what you explained Danny some posts back (the timer's autoreset thing).
Anyways, I've cracked my head for a while here and found a very simple solution that worked just fine...
All I needed was a routine that output True in the first time it ran, and then maintained false for the rest of the time...
This is how I got it to work!
How do you call this VI multiple times, since there is no way to stop it? Is it set to reentrant?
Anyway, that shift register and case structure is overkill and totally pointless, why not simply do a "=0" on the iteration count [i] and wire the result to the "reset" input?
Your loop also needs a small wait. You don't want to burn all available CPU just to check every nanosecond if the time has elapsed, especially since you seem to run several instances at once, you'll run into problems because without a wait each loop will spin many times before releasing control to something else.
altenbach wrote:
How do you call this VI multiple times, since there is no way to stop it? Is it set to reentrant?
Anyway, that shift register and case structure is overkill and totally pointless, why not simply do a "=0" on the iteration count [i] and wire the result to the "reset" input?
Your loop also needs a small wait. You don't want to burn all available CPU just to check every nanosecond if the time has elapsed, especially since you seem to run several instances at once, you'll run into problems because without a wait each loop will spin many times before releasing control to something else.
Also remember that this timing method do have resolution around 17 msec. This depends on Labview version and OS type.
Hey All,
Actually I'v taken only the part I was Issuing about...
The program is more comnplex and it's shown bellow...
I Believe I need that structure for it to work...
I've attached a Picture and the VI, but to open the second one you need the LEGO Mindstorms Toolkit to open...
Thx!
OK, that's quite different to what you showed above and makes a bit more sense. Still, that T/F case structure is silly, right?
It's is difficult to comment furhter without seeing the rest of the cases, etc.
