04-14-2009 02:26 PM
Solved! Go to Solution.
04-14-2009 03:20 PM
If you are refering to the test panels in MAX, then the answer is you can not change their code and the way they work.
If you want to simply create a VI that runs for 10 seconds and closes you could simply have a 10second wait then call the close front panel method or abort, or just code it to complete and if its called as a subVI the main VI can then continue on.
04-14-2009 03:26 PM
Evan,
Your user icon does not appear on the web page. Probably because it is hosted on some oddball 3rd party website http://xs38.xs.to/pics/05291/yingyang.gif.
You should post your icon image file in the thread http://forums.ni.com/ni/board/message?board.id=130&thread.id=702 and have your profile point to the image file there.
04-14-2009 03:36 PM
04-14-2009 06:06 PM
If you don't mean a Test Panel in MAX, you might consider the JKI Please Wait Dialog in the LAVA Code Repository.
04-14-2009 10:44 PM
OMHG^ (oh my holy god above):smileysurprised:
I'll post a decent wait routine from work tomorrow.
NI --- will you buy, or rent, an horologist?
jc- do you know what KIND of "time" you are "waiting" Again, "Time" is measured in SI seconds and equal to a specific number of transisitions between two hyperfine states of the valence electron on a specific isotope of a Cesium atom. NIST submitts their approximation of "Time" to an international body for correction on a (ir)regular basis
"Civil Time" (local day-time) is a legal, not measurably traceable, term and is coordinated globaly. "Civil Time" as a legal term and has no scientific measurement related to "Time."
Assuming (big assumption) that you care nothing about "Civil Time" (time of day) nor "Time" (a root dimension), an OS system mS timer has a value that is useful for these types of applications.
LabVIEW has two independant type definitions "Time Stamp", a cluster derivitive from local "Civil Time" represented by the OS System clock (the calaibration is left to the OS) and "mStimer.value", derived directly from the OS mStimer dependant only on OS procesess (the calaibration is non-existant)
That being said, the mS timer of a PC is a U32 int. Add U32 int + unk (coerced to an XXInt) and the result may be greater than the largest possible "mStimer.value". once every so many weeks the mStimer rolls over----- Now if you are "Waiting" for mStimer.value to be greater than +inf..........(that could take forever) Smile everybody its happened to me! and the reason I became an amature horologist (plz don't tell my wife- she's still waiting)
Of course, simple math can predict an overflow of a U32. I do it all the "Time" with the Delay vi I wrote to avoid waiting forever.
Who else has written one?
is NI stuck in this same loop with the fix for Wait +(mS).vi?
04-15-2009 12:11 AM
Jeff at home wrote:OMHG^ (oh my holy god above):smileysurprised:
I'll post a decent wait routine from work tomorrow.
NI --- will you buy, or rent, an horologist?
jc- do you know what KIND of "time" you are "waiting" Again, "Time" is measured in SI seconds and equal to a specific number of transisitions between two hyperfine states of the valence electron on a specific isotope of a Cesium atom. NIST submitts their approximation of "Time" to an international body for correction on a (ir)regular basis
"Civil Time" (local day-time) is a legal, not measurably traceable, term and is coordinated globaly. "Civil Time" as a legal term and has no scientific measurement related to "Time."
.........
.......
Huh?
04-15-2009 12:27 AM
Ravens fan-
I appreciate that you are not a big supporter of the preeminant NFL Vikings!!!!
However, what is "0 seconds"?