From 11:00 PM CST Friday, Feb 14th - 6:30 PM CST Saturday, Feb 15th, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CST Friday, Feb 14th - 6:30 PM CST Saturday, Feb 15th, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
12-07-2017 12:05 PM
Is this a bug or why does the exact copy of the timer placed in two different events act differently?
Solved! Go to Solution.
12-07-2017 12:49 PM
I cannot view your file but I assume you are dropping two separate instances of the Express VI? Each clone behaves independently, so if you set a time target on one it does not effect the time target of the other, for example.
12-07-2017 01:16 PM
Here is a screen shot of the two cases and the front panel shown twice. Please forgive the quick and crappy editing but can you see this JPG? Im not sure if what you are saying applies here
12-07-2017 01:29 PM
Because your Init case only runs one time. It never gets back around to check the Elapsed Time again!
12-07-2017 01:29 PM
@JeffreyS wrote:
Im not sure if what you are saying applies here
What was said completely applies here. Each instance of the Elapsed Time keeps its own state (start time, reset time, etc). So your init will never see the time elapsed as written.
12-07-2017 01:50 PM
Thanks for replying both of you.
Yes, i changed the event enum to flip back to the init event and they both go on now. Say I have a while loop and this timer is set to 10 seconds. That is all fine and good. Will the 10 seconds be effected if I send the program through a 1000 different loops before coming back? ie: will the timer's 10 seconds take longer than 10 seconds. Why even create a timer this way?