Usage of "Elapsed Time" Express VI

I'm trying to program in Labview something like "Action 1" -> Wait 5 seconds -> "Action 2" -> Wait 5 seconds -> "Action 3". The "wait 5 seconds" should not block everything else but other tasks / VIs should continue running. Does anybody have a good solution for this? I tried to use the Elapsed Time Express VI but it does funny things. Can anybody explain to me how to properly use the Elapsed Time Express VI and especially how the reset input works?

As Lynn said, I think all you need is a simple Wait(ms) call, but to answer your specific questions...
The Elapsed Time Express VI tells you if the time you specified for Elapsed Time has expired; it does not actually wait for the time to expire. An example of how you would use this is to include a call to the function in a loop. When the "Time has Elapsed" boolean is true, you perform some action. If not true, you do nothing. This would allow you to use a fast running loop that only did some elapsed time action every so often instead of every time through the loop.
The Reset you asked about is a way to reset the internal state of the VI. The VI keeps state information, which makes sense and is normally what you want it to do. However, you may want to have it
reset on this particular execution, e.g. on the first iteration of a loop that is within an outer loop.
Hope this helps,
Roy

Similar Messages

  • How can I get the Elapsed Time express to output in milliseconds?

    I am trying to get the Elapsed Time express to output in milliseconds or in seconds to three decimal places. I am pretty new at this.
    Thanks in advance!

    I'm not sure I understand your question. The output of the Elapsed Time Express VI is a DBL. It's already a floating point number. The default format for a numeric indicator is 6 digits of precision. You can change this in the properties for the indicator.
    To learn more about LabVIEW it is recommended that you go through the tutorial(s) and look over the material in the NI Developer Zone's Learning Center which provides links to other materials and other tutorials. You can also take the online courses for free.
    Attachments:
    Example_VI.png ‏4 KB

  • Problems implementi​ng the elapsed time express vi into my vi

    I am trying to implement the Elapsed Time Express VI into my VI so that my VI runs for a specified amount of time. I currently have the express VI working, but now that I have implemented it into my VI, my graphing functions do not work. If anyone has any suggestions, I would greatly appreciate your help. I have attached my VI for reference.
    -Kelly
    Attachments:
    Inj&Sam_C348_C_wrt_File_and_Timed.vi ‏405 KB

    The way you have your VI configured, the outer while loop will only run once. It will run, but will not be able to continue until the inner loop has completed. The inner loop will continue to acquire data until the desired time has passed. A this time a true will be written to the stop terminal on the inner loop, and then passed to the stop terminal on the outer while loop, stopping it when it has only run through one iteration. I'm not sure what you are trying to do, but my guess is that you want your second while loop to be outside of the first one. You can then stop them both by using a local variable or some synchronization mechanism.
    Regards,
    Ryan K.

  • Triggering Elapsed time measurements

    Hi everyone, can anyone help me with this problem?
    I am trying to create a system for measuring the time between triggers
    from my oscilliscope as part of a larger program. I have implemented a
    while loop, which aquires data from the oscilliscope for each
    itteration of 'i'. The visa commands in this include a 'wait for
    trigger' VI, which only allows the aquisition to occur, and hence 'i'
    to increase, once the oscilliscope has triggered from my experimental
    data. Hence, theoretically every cycle of my system is captutured.
    I have used an 'elapsed time' express VI to measure the time that the
    program has been running for. However, i want this VI to reset every
    time my while loop iterates to give an exact measure of the time since
    the p
    revious trigger. The input for resetting appears to require a
    boolean pulse to do this, as the conection of a boolean constant cause
    the time data to be permanantly reset. My oscilliscope drivers do not
    have any kind of boolean output for this kind of syncronisation. Does
    anyone know a way in which i can produce such a boolean pulse every
    time my while loop itterates?
    Please could you reply to this group as my registered email is no
    longer valid
    Thanks
    Tom

    See your other post

  • Comparing two elapsed timer readings

    Hi everyone,
    I'm a new user of Labview, so I'm teaching myself as I go along really. I've come up against a problem though. I'm trying to compare two timer readings from elapsed timers. Eventually I am hoping to swap these timers for a pair of light beams inputted through a DAQ chassis. Initially though I wanted to get the content of my program correct, without having to have the equipment connected to my laptop.
    I have attached my progress so far, apologies if my query has an obvious solution. As I say I'm a bit of an beginner! How would I take the two elasped timers log the times found off the timers, compare which one has a greater value and consequently start a new timer depending on this. I would then like to log this time in data form.
    I've tried to compare the two elasped timers with greater than booleans etc but I cant seem to get it to work?
    As I say I hope to use this idea in a time gate sort of application where depending on which light beam is broken first depends on which timer is started. Hope my explanation is clear.
    Any help is much appreciated,
    Thanks very much!
    Attachments:
    FYP.vi ‏15 KB

    PT-
    Looking at your code you have a few problems that you will need to address.  Read the LabVIEW help section titled "Caveats and Recommendations when Using Events in LabVIEW."  You have some latching booleans controls that are incorrectly placed.  The terminals should be in the event case that handles the value change event.  
    Why two event structures?  One structure is a better Idea you can handle all your events with 1 loop (and avoid stopping the loops independantly- this can lead to a condition where the vi becomes unresponsive.
    The lower loop compares the start times to two different timestamps.  This is introducing potential errors since there is timing relationship between the calls to the system timer.  and the lower case structures are rather insane- in english they resolve to "if started return how long its been since started else return 0"  Check the NI website there is a CLD practice exam solution (Car Wash) that has a pretty good example and discussion of using the elapsed timer express vi.  It might point you in a better direction than where you are going.
    Why not use the time terminals in the event structure?  thats the time the event fired.  But, you might want the time the event was handled I don't Know-  (hint-comment your code and write SOMETHING in the vi documentation.  Eventually you'll be writing more complex code so start developing good habits now)  (good habits--)  
    Come on back when you've looked at some of the examples and I'ld be glad to help you more.  
    Jeff

  • Elapsed Timer Too Long?

    Is there a limit to the duration I can input into an elapsed timer VI? In my program the user can specify a duration of up to 24 hrs. My program is supposed to hold current conditions for the specified durations. When the user sets it 1, 2, 3 or four hours it holds the current conditions fine. When they set it to 24 hours the current conditions are not held for 24 hours. Is this too long of a duration for this VI (86,400 seconds)?
    thanks.

    rchaoua wrote:
    The question regarding maximum duration a elapsed time VI has still not been answered.
    You can convert the "elapsed time" express VI to a plain VI by "right-click...open front panel" and inspect the code yourself. There are no secrets! You can see that it converts the timestamp to DBL and operates on the lower precision DBL values. This should be sufficient for much more than 24 hours, so something else is wrong in your case.
    Can you attach an example that shows the incorrect behavior (=premature elapsation?).
    rchaoua wrote:
    But I have another question; Can you have multiple elapsed time VI in a single piece of code and not have it affect the other elapsed VIs?  I have three elapsed timers in my code (in different panels) and get the sneaking supsicion that they are not behaving nicely with each other. But I am not sure. I was hoping someone has expereince with this scenario and could shed some light.
    The crucial subVIs are reentrant and thus there should be no interaction between multiple instances of the "elapsed time" express VI. Each will keep it's own state. Why do you suspect that they interact?
    LabVIEW Champion . Do more with less code and in less time .

  • How can i reset elapsed time VI

    I am using the elapsed time express VI along with an "in range" comparison VI as the exit control for a torque test.  If the voltage signal from the torque transducer is within the specified range for the target time, the loop exits.  If the voltage signal is out of range, the elapsed time resets to zero.
    My problem arises when i exit the loop prematurely due to excessive torque.  Like if torque reaches the transducer limit, I want to exit the loop to prevent damage.  When i exit the loop like this, the elapsed time VI continues counting even though the loop has been stopped.  The next time the program enters the state, it exits immediately (because torque is initially zero, and the timer has passed the set time).  After that iteration the program behaves as i expect it to, because the VI has reinitialized I assume.  I have been stuck on this problem for several days, and I'm going to start breaking company computers if i can't fix it.
    So my question(s)... is there a way to reset the elapsed time VI upon entering the while loop?  is there a way to reset the VI from the 'torque limit' state immediately following the exit?  I also use a 'resume test' button so the user can restart the test after checking the unit,hardware,etc.  can i wire something to that button press to restart the elapsed time VI?
    My 7.1 vi is attached, the elapsed time problem being in the 'exercise' state.  immediately following an 'exercise' torque limit, it goes to the 'torque limit' state, which i thought could be used to reinitialize the elapsed time somehow. 
    Thanks,
    Evan
    Attachments:
    DB6483 Test.vi ‏2932 KB

    I have a similar problem ,
    I use a elapsed tiem function ,with a target of 1s time.
    i want to caluclate mean of samples in this 1 second
    but what i see i get 8-9 mean values in 1 second
    i also wired my i of while loop to auto reset with case structure,but even then i see so many average sample values in a second
    to be more precise i want data like this:
    when my DAQ board gives some 1000 samples per second. i need mean of these 1000 samples,but not all 1000 sanmples.
    for this i included a elapsed time vi with taget of 1s. (didnt forget to reset after 1s).
    but what i see is it gives values like this
    12:12:01     d1 d2 d3
    12:12:01     d1 d2 d3
    but i expect like
    12:12:01   d1 d2 d3
    12:12:02   d1:d2:d3
     did i go any where wrong in my Vi.
    how can get out of it!

  • Problem Regarding Duration of Test(Elapsed timer)

    Hi All,
    I am doing positive negative pressure cycle test in which positive negative cycle going on continously & shown on graph.
    I have to show duration of test as cycle starts in HH/MM/SS format continously as test is going on upto a fixed no. of cycles.
    I have taken elapsed time express vi in my  main loop for showing this. As in my program there are various loops one inside another in main loop.
    So my problem is this timer is not showing elapsed time in continous updating mode but it shows elapsed time when i press exit button. I know why it is not showing because it is going into another loop in my main loop.
    Can anybody suggest me how to show my duration of test in continous updating mode?
    Thanks & Regards,
    Vipin Ahuja

    A slightly more robust elapsed test timer than the previously linked FGV was presented as a small part of the community nugget series on application development.  Once initiallized with a refnum to the GUI's elapsed time indicator, this Resouce Module can be called from anywhere or everywhere in the application to update the GUI.  
    A modification of the vi was also presented HERE as a GUI Element Resource Module, GERM, in a nugget I co-authored with Richard Sorrellis (AKA Broken Arrow)
    Jeff
    Attachments:
    Format Rel Time (STR).vi ‏12 KB
    Exec Timer Meth.ctl ‏11 KB
    Execution Timer.vi ‏29 KB

  • Elapsed Timer in secs

    Hello,
    I would like to continuously update the elapsed timer indicator every second.  I do not understand why the program is not working?  Can you offer some assistance to help me display the elaspsed time (in seconds).  
    Thanks,
    hiNi.
    P.S. I know that there is an elapsed timer express VI, but I would like to know how to show the elapsed time without the express VI. THANKS!
    Solved!
    Go to Solution.
    Attachments:
    Elapsed Timer.llb ‏27 KB

    Why every second?  Why not with each iteration of your loop?
    Since your loop iterates every 100ms, you could make a counter using another shift register.  When the counter reaches 10, get your elaspsed time.
    Give these VIs a try to see if they do what you want.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    Elapsed Timer.llb ‏23 KB

  • *Fix* Usage and Standby Times are the same - iPhone 4S 7.0.4

    I'd like to share my experience here because I actually found the solution on here but I'm actually having trouble finding it again.
    I had three problems:
    1. My standby and usage times were always reporting the same values, thus draining my battery faster than usual. This is not normal behavior; whenever the screen is off it should report standby times, and after the phone is unlocked it is considered usage. They should never be recording in tangent.
    2. Whenever I would try to turn off my phone by holding down the power button, the phone would basically restart itself, showing the Apple logo boot screen and then restarting. The only caveat was that it would turn off if it was plugged in and being charged. But take it off the charger and try to replicate it turning off and it would restart.
    3. The sound would sometimes think that it was connected to a Dock, so when I went to the Airplay options, they were listed as Dock Connector, Airport Express and Apple TV. There would be no volume slider in the Control Center, and when pressing the volume buttons, there would be no dots, just the bell with a line through it.
    Many people might be having genuine battery issues, where you have an older phone and your battery is just really bad and needs to be replaced. My 4S was still under AppleCare in December 2013 and the battery was pretty bad, so I had it replaced in an Apple Store. So for me, the battery life itself was not the problem.
    I tried a lot of things to try and fix the above problem but none of them helped. This includes chatting with Apple support (I was surprised they didn't steer me in an obvious direction, considering the large amount of folks who were having these kinds of problems, but they played dumb), restoring fresh and restoring icloud and itunes backups, all kinds of combinations of settings for Mail, iCloud, etc., but nothing worked. I probably restored my phone at least ten times in my troubleshooting efforts. The isolated test of restoring my phone fresh, setting it up to the start screen, making sure the battery was charged 100% and taking it off the charger waiting about 10 minutes. Then I would check standby and usage times.
    I had read about fixes for the phone not being able to turn completely off, and it had something to do with cleaning the charging port. I attempted to clean the port with compressed air and other methods, but it never fixed this problem. Then I read a post on Apple Support about a guy who had the exact same problems as I did, then said he changed out his charging port and this fixed it. Well, it was $40 so I paid someone to do it in 45 minutes.
    After I got my phone back the problem didn't appeared to be fixed, but after a restore and even with an icloud backup restored with it, I looked down at my phone and presto chango, the times where separate and working as they should. Last night with wifi off while I was sleeping, the battery only went down 3%. I know this is turning out to be a narrative, but I spent a lot of time trying to figure out what the problem was and it was a frustrating process. I'm happy it's resolved.
    Apple Support thought it was a corrupt install package from iTunes, or some kind of software glitch or maybe some part of iCloud constantly trying to call home, but it was a combination of both hardware and software. Because of the bad charging port, for some reason the phone thought it was still being used and thus was still treating standby as usage.
    I would encourage those that are having this problem to do a test and see if your phone will turn off when you want it to. If it resets automatically and if your standby usage times are the same, replacing the charging port might fix it.

    Ever since iOS7.0.6. and still on iOS7.1 both me and my wife had huge battery drain on our iPhone 4S and stand-by was equal to usage time. We finally found the solution to a post of another user on the Dutch Tweakers forum. There seem to be a bug within a certain Dutch coupon app called 'Scoupy' which drained the battery completely although GPS setting was turned of and also 'refresh on background' was off.
    Scoupy said that a fix for their app is send for approval to the App Store. We removed the app and our usage/stand-by time is again as normal (higher stand-by time then usage time) and best of all a 'normal' battery use as it was the case on iOS7.0.4. I hope this could help someone. I'm wondering if the iBeacon changes in iOS7.0.6/7.1 together with a bug in the Scoupy app could be the cause? Maybe this is also with our similar apps you have on your phone.

  • CPU time and ELAPSED time in tkprof question

    Hi,
    I have a statment that is running more than 3 HR.
    I run 10046 event and found that the CPU time and the ELAPSED time is almost the same:
    call count cpu elapsed disk query current rows
    Parse 2 0.00 0.00 0 0 0 0
    Execute 2 0.00 0.00 0 3 0 1
    Fetch 97 10175.76 10094.81 11216 56387604 0 1441
    total 101 10175.76 10094.82 11216 56387607 0 1442
    Is that can indicate of a problem in the machine ?
    The TOP activity also shows 99% cpu usage.
    CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
    6 ? 24700 oracle 232 20 5448M 13184K run 195:34 99.18 99.00 oraclepcr
    Thanks

    Hi,
    Thank you for your replay.
    Its version 10204 on HP-UX with 24GB and 8 CPUs.
    No i dont have any MERGE JOIN CARTESIAN.
    The reason that i didnt upload the plan is because its too long...far too long ....
    call count cpu elapsed disk query current rows
    Parse 1 42.20 41.38 0 0 0 0
    Execute 1 0.00 0.00 0 0 0 0
    Fetch 5 444.12 447.27 1153 2486187 0 61
    total 7 486.32 488.65 1153 2486187 0 61
    Misses in library cache during parse: 1
    Optimizer mode: ALL_ROWS
    Parsing user id: 65 (PSSYS)
    Rows Execution Plan
    0 SELECT STATEMENT MODE: ALL_ROWS
    0 UNION-ALL
    0 CONCATENATION
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS
    0 NESTED LOOPS (OUTER)
    0 HASH JOIN (OUTER)
    0 HASH JOIN (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS
    0 NESTED LOOPS
    (OUTER)
    0 NESTED LOOPS
    (OUTER)
    0 NESTED LOOPS
    (OUTER)
    0 NESTED LOOPS
    (OUTER)
    0 NESTED
    LOOPS (OUTER)
    0 FILTER
    0 HASH
    JOIN (OUTER)
    0
    TABLE ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'PS_RD_COMPANY'
    (TABLE)
    0
    NESTED LOOPS
    0
    NESTED LOOPS (OUTER)
    0
    NESTED LOOPS
    0
    NESTED LOOPS
    0
    HASH JOIN
    0
    TABLE ACCESS MODE:
    ANALYZED (FULL) OF 'PS_PROD
    _ITEM' (TABLE)
    0
    TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID)
    OF 'PS_RO_LINE' (TABLE)
    0
    NESTED LOOPS
    0
    HASH JOIN
    0
    INDEX MOD
    E: ANALYZED (FULL SCAN)
    OF 'PS0RO_DEFN_HDSTAT'
    (INDEX)
    0
    TABLE ACCES
    S MODE: ANALYZED (BY
    INDEX ROWID) OF 'PS_RO_H
    EADER' (TABLE)
    0
    INDEX
    MODE: ANALYZED (RANGE
    SCAN) OF 'PSERO_HEADER'
    (INDEX)
    0
    INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'PSARO_LINE' (INDEX (UNIQ
    UE))
    0
    TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'PS_RO_BOID' (TABLE)
    0
    INDEX MODE: ANALYZ
    ED (UNIQUE SCAN) OF 'PS_RO_
    BOID' (INDEX (UNIQUE))
    0
    TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'PS_RF_INST_PROD' (TABLE)
    0
    INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'PS_RF_INST_
    PROD' (INDEX (UNIQUE))
    0
    TABLE ACCESS MODE: ANALYZED
    (BY INDEX ROWID) OF 'PS_RD_PER
    SON' (TABLE)
    0
    INDEX MODE: ANALYZED
    (UNIQUE SCAN) OF 'PS_RD_PERSO
    N' (INDEX (UNIQUE))
    0
    INDEX MODE: ANALYZED (RANGE
    SCAN) OF 'PS0RD_COMPANY' (INDEX)
    0 VIEW
    OF 'XLATTABLE_VW' (VIEW)
    0
    NESTED LOOPS
    0
    TABLE ACCESS MODE: ANALYZED
    (FULL) OF 'PSXLATITEM' (TABLE)
    0
    INDEX MODE: ANALYZED (UNIQUE
    SCAN) OF 'PS_PSXLATDEFN' (INDEX
    (UNIQUE))
    0 TABLE
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'PS_RSF_INDUSTRY' (TABLE)
    0 INDEX
    MODE: ANALYZED (RANGE SCAN) OF
    'PS3RSF_INDUSTRY' (INDEX)
    0 TABLE
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'NAP_CATALOG_NUM' (TABLE)
    0 INDEX
    MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_NAP_CATALOG_NUM' (INDEX (UNIQUE)
    0 MAT_VIEW
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX
    MODE: ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX
    MODE: ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS
    MODE: ANALYZED (BY INDEX ROWID) OF
    'IP_CONNECTION_TYPES' (MAT_VIEW)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'IP_CONNECTION_TYPES_X1' (INDEX)
    0 TABLE ACCESS
    MODE: ANALYZED (BY INDEX ROWID) OF
    'NAP_INTERNET' (TABLE)
    0 INDEX MODE:
    ANALYZED (UNIQUE SCAN) OF
    'PS_NAP_INTERNET' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'PS_RF_INST_PROD' (TABLE)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'PS_RF_INST_PROD' (INDEX (UNIQUE))
    0 MAT_VIEW ACCESS
    MODE: ANALYZED (BY INDEX ROWID) OF
    'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'NAP_CATALOG_NUM' (TABLE)
    0 INDEX MODE: ANALYZED
    (UNIQUE SCAN) OF 'PS_NAP_CATALOG_NUM'
    (INDEX (UNIQUE))
    0 MAT_VIEW ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF 'BB_CODE_TABLE'
    (MAT_VIEW)
    0 INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF 'BB_CODE_TABLE'
    (MAT_VIEW)
    0 INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'IP_CONNECTION_TYPES' (MAT_VIEW)
    0 INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'IP_CONNECTION_TYPES_X1'
    (INDEX)
    0 MAT_VIEW ACCESS MODE: ANALYZED
    (FULL) OF 'IP_PIRSUM_CODE' (MAT_VIEW)
    0 MAT_VIEW ACCESS MODE: ANALYZED
    (FULL) OF 'IP_PIRSUM_CODE' (MAT_VIEW)
    0 TABLE ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'PS_BO_NAME' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN)
    OF 'PS_BO_NAME' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'PS_BO_CM' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN)
    OF 'PS_BO_CM' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'PS_BO_CM_USE' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PS_BO_CM_USE' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'PS_CM' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_CM' (INDEX (UNIQUE))
    0 MAT_VIEW ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 INDEX MODE: ANALYZED (FULL SCAN) OF
    'PSHBO_NAME' (INDEX)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PS1RD_PERSON' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RB_WORKER' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_RB_WORKER' (INDEX (UNIQUE))
    0 INDEX MODE: ANALYZED (FULL SCAN) OF 'PSHBO_NAME'
    (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RD_PERSON' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PS1RD_PERSON' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RF_GRP_MEMBER' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PSARF_GRP_MEMBER' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RF_PROVIDER_GRP' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_RF_PROVIDER_GRP' (INDEX (UNIQUE))
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS
    0 NESTED LOOPS (OUTER)
    0 HASH JOIN (OUTER)
    0 HASH JOIN (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS
    0 NESTED LOOPS
    (OUTER)
    0 NESTED LOOPS
    (OUTER)
    0 NESTED LOOPS
    (OUTER)
    0 NESTED LOOPS
    (OUTER)
    0 NESTED
    LOOPS (OUTER)
    0 FILTER
    0 HASH
    JOIN (OUTER)
    0
    TABLE ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'PS_RD_COMPANY'
    (TABLE)
    0
    NESTED LOOPS
    0
    NESTED LOOPS
    0
    NESTED LOOPS (OUTER)
    0
    NESTED LOOPS
    0
    HASH JOIN
    0
    TABLE ACCESS MODE:
    ANALYZED (FULL) OF 'PS_PROD
    _ITEM' (TABLE)
    0
    TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID)
    OF 'PS_RO_LINE' (TABLE)
    0
    NESTED LOOPS
    0
    HASH JOIN
    0
    INDEX MOD
    E: ANALYZED (FULL SCAN)
    OF 'PS0RO_DEFN_HDSTAT'
    (INDEX)
    0
    TABLE ACCES
    S MODE: ANALYZED (BY
    INDEX ROWID) OF 'PS_RO_H
    EADER' (TABLE)
    0
    INDEX
    MODE: ANALYZED (RANGE
    SCAN) OF 'PSERO_HEADER'
    (INDEX)
    0
    INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'PSARO_LINE' (INDEX (UNIQ
    UE))
    0
    TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'PS_RO_BOID' (TABLE)
    0
    INDEX MODE: ANALYZ
    ED (UNIQUE SCAN) OF 'PS_RO_
    BOID' (INDEX (UNIQUE))
    0
    TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'PS_RD_PERSON' (TABLE)
    0
    INDEX MODE: ANALYZED
    (UNIQUE SCAN) OF 'PS_RD_PERS
    ON' (INDEX (UNIQUE))
    0
    TABLE ACCESS MODE: ANALYZED
    (BY INDEX ROWID) OF 'PS_RF_INS
    T_PROD' (TABLE)
    0
    INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'PS_RF_INST_P
    ROD' (INDEX (UNIQUE))
    0
    INDEX MODE: ANALYZED (RANGE
    SCAN) OF 'PS0RD_COMPANY' (INDEX)
    0 VIEW
    OF 'XLATTABLE_VW' (VIEW)
    0
    NESTED LOOPS
    0
    TABLE ACCESS MODE: ANALYZED
    (FULL) OF 'PSXLATITEM' (TABLE)
    0
    INDEX MODE: ANALYZED (UNIQUE
    SCAN) OF 'PS_PSXLATDEFN' (INDEX
    (UNIQUE))
    0 TABLE
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'PS_RSF_INDUSTRY' (TABLE)
    0 INDEX
    MODE: ANALYZED (RANGE SCAN) OF
    'PS3RSF_INDUSTRY' (INDEX)
    0 TABLE
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'NAP_CATALOG_NUM' (TABLE)
    0 INDEX
    MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_NAP_CATALOG_NUM' (INDEX (UNIQUE)
    0 MAT_VIEW
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX
    MODE: ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX
    MODE: ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS
    MODE: ANALYZED (BY INDEX ROWID) OF
    'IP_CONNECTION_TYPES' (MAT_VIEW)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'IP_CONNECTION_TYPES_X1' (INDEX)
    0 TABLE ACCESS
    MODE: ANALYZED (BY INDEX ROWID) OF
    'NAP_INTERNET' (TABLE)
    0 INDEX MODE:
    ANALYZED (UNIQUE SCAN) OF
    'PS_NAP_INTERNET' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'PS_RF_INST_PROD' (TABLE)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'PS_RF_INST_PROD' (INDEX (UNIQUE))
    0 MAT_VIEW ACCESS
    MODE: ANALYZED (BY INDEX ROWID) OF
    'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'NAP_CATALOG_NUM' (TABLE)
    0 INDEX MODE: ANALYZED
    (UNIQUE SCAN) OF 'PS_NAP_CATALOG_NUM'
    (INDEX (UNIQUE))
    0 MAT_VIEW ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF 'BB_CODE_TABLE'
    (MAT_VIEW)
    0 INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF 'BB_CODE_TABLE'
    (MAT_VIEW)
    0 INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'IP_CONNECTION_TYPES' (MAT_VIEW)
    0 INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'IP_CONNECTION_TYPES_X1'
    (INDEX)
    0 MAT_VIEW ACCESS MODE: ANALYZED
    (FULL) OF 'IP_PIRSUM_CODE' (MAT_VIEW)
    0 MAT_VIEW ACCESS MODE: ANALYZED
    (FULL) OF 'IP_PIRSUM_CODE' (MAT_VIEW)
    0 TABLE ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'PS_BO_NAME' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN)
    OF 'PS_BO_NAME' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'PS_BO_CM' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN)
    OF 'PS_BO_CM' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'PS_BO_CM_USE' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PS_BO_CM_USE' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'PS_CM' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_CM' (INDEX (UNIQUE))
    0 MAT_VIEW ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 INDEX MODE: ANALYZED (FULL SCAN) OF
    'PSHBO_NAME' (INDEX)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PS1RD_PERSON' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RB_WORKER' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_RB_WORKER' (INDEX (UNIQUE))
    0 INDEX MODE: ANALYZED (FULL SCAN) OF 'PSHBO_NAME'
    (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RD_PERSON' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PS1RD_PERSON' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RF_GRP_MEMBER' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PSARF_GRP_MEMBER' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RF_PROVIDER_GRP' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_RF_PROVIDER_GRP' (INDEX (UNIQUE))
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 HASH JOIN (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS
    0 NESTED LOOPS (OUTER)
    0 FILTER
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS (OUTER)
    0 NESTED LOOPS
    (OUTER)
    0 NESTED LOOPS
    0 NESTED LOOPS
    (OUTER)
    0 NESTED LOOPS
    (OUTER)
    0 NESTED
    LOOPS (OUTER)
    0 NESTED
    LOOPS
    0 NESTED
    LOOPS (OUTER)
    0
    NESTED LOOPS
    0
    HASH JOIN
    0
    TABLE ACCESS MODE: ANALYZED
    (FULL) OF 'PS_PROD_ITEM' (TABLE)
    0
    TABLE ACCESS MODE: ANALYZED
    (BY INDEX ROWID) OF 'PS_RO_LINE
    ' (TABLE)
    0
    NESTED LOOPS
    0
    HASH JOIN
    0
    INDEX MODE: ANALYZED
    (FULL SCAN) OF 'PS0RO_DEFN_H
    DSTAT' (INDEX)
    0
    TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'PS_RO_HEADER' (TABLE)
    0
    INDEX MODE: ANALYZ
    ED (RANGE SCAN) OF 'PSERO_H
    EADER' (INDEX)
    0
    INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'PSARO_LINE'
    (INDEX (UNIQUE))
    0
    TABLE ACCESS MODE: ANALYZED
    (BY INDEX ROWID) OF 'PS_RO_BOID'
    (TABLE)
    0
    INDEX MODE: ANALYZED (UNIQUE
    SCAN) OF 'PS_RO_BOID' (INDEX
    (UNIQUE))
    0
    TABLE ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'PS_RD_PERSON'
    (TABLE)
    0
    INDEX MODE: ANALYZED (UNIQUE
    SCAN) OF 'PS_RD_PERSON' (INDEX
    (UNIQUE))
    0 TABLE
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'PS_RF_INST_PROD' (TABLE)
    0
    INDEX MODE: ANALYZED (RANGE
    SCAN) OF 'PS_RF_INST_PROD' (INDEX
    (UNIQUE))
    0 TABLE
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'PS_BO_NAME' (TABLE)
    0 INDEX
    MODE: ANALYZED (RANGE SCAN) OF
    'PS_BO_NAME' (INDEX (UNIQUE))
    0 TABLE
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'NAP_CATALOG_NUM' (TABLE)
    0 INDEX
    MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_NAP_CATALOG_NUM' (INDEX (UNIQUE)
    0 MAT_VIEW
    ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'IP_CONNECTION_TYPES'
    (MAT_VIEW)
    0 INDEX
    MODE: ANALYZED (RANGE SCAN) OF
    'IP_CONNECTION_TYPES_X1' (INDEX)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'PS_NAP_IP_DEBIT' (INDEX (UNIQUE))
    0 SORT
    (AGGREGATE)
    0 INDEX
    MODE: ANALYZED (RANGE SCAN) OF
    'PS_NAP_IP_DEBIT' (INDEX (UNIQUE))
    0 TABLE ACCESS
    MODE: ANALYZED (BY INDEX ROWID) OF
    'NAP_CATALOG_NUM' (TABLE)
    0 INDEX MODE:
    ANALYZED (UNIQUE SCAN) OF
    'PS_NAP_CATALOG_NUM' (INDEX (UNIQUE))
    0 MAT_VIEW ACCESS
    MODE: ANALYZED (BY INDEX ROWID) OF
    'IP_CONNECTION_TYPES' (MAT_VIEW)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'IP_CONNECTION_TYPES_X1' (INDEX)
    0 TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'PS_RD_COMPANY' (TABLE)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF 'PS0RD_COMPANY'
    (INDEX)
    0 VIEW PUSHED PREDICATE
    OF 'XLATTABLE_VW' (VIEW)
    0 NESTED LOOPS
    0 TABLE ACCESS
    MODE: ANALYZED (BY INDEX ROWID) OF
    'PSXLATITEM' (TABLE)
    0 INDEX MODE:
    ANALYZED (RANGE SCAN) OF
    'PSBPSXLATITEM' (INDEX)
    0 INDEX MODE:
    ANALYZED (UNIQUE SCAN) OF
    'PS_PSXLATDEFN' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF
    'PS_RSF_INDUSTRY' (TABLE)
    0 INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'PS3RSF_INDUSTRY' (INDEX)
    0 TABLE ACCESS MODE:
    ANALYZED (BY INDEX ROWID) OF 'PS_BO_CM'
    (TABLE)
    0 INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'PS_BO_CM' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE: ANALYZED
    (BY INDEX ROWID) OF 'PS_BO_CM_USE' (TABLE)
    0 INDEX MODE: ANALYZED
    (RANGE SCAN) OF 'PS_BO_CM_USE' (INDEX (UNIQUE)
    0 TABLE ACCESS MODE: ANALYZED
    (BY INDEX ROWID) OF 'PS_CM' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE
    SCAN) OF 'PS_CM' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'NAP_INTERNET' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE
    SCAN) OF 'PS_NAP_INTERNET' (INDEX (UNIQUE))
    0 MAT_VIEW ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX MODE: ANALYZED (RANGE SCAN)
    OF 'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX MODE: ANALYZED (RANGE SCAN)
    OF 'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS MODE: ANALYZED (BY
    INDEX ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS MODE: ANALYZED (FULL) OF
    'IP_PIRSUM_CODE' (MAT_VIEW)
    0 MAT_VIEW ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 MAT_VIEW ACCESS MODE: ANALYZED (BY INDEX
    ROWID) OF 'BB_CODE_TABLE' (MAT_VIEW)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'BB_CODE_TABLE_I' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID)
    OF 'PS_BO_NAME' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PS_BO_NAME_IDX1' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RD_PERSON' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PS1RD_PERSON' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RF_GRP_MEMBER' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PSARF_GRP_MEMBER' (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RF_PROVIDER_GRP' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF
    'PS_RF_PROVIDER_GRP' (INDEX (UNIQUE))
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_BO_NAME' (TABLE)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF
    'PS_BO_NAME_IDX1' (INDEX)
    0 INDEX MODE: ANALYZED (RANGE SCAN) OF 'PS1RD_PERSON'
    (INDEX)
    0 TABLE ACCESS MODE: ANALYZED (BY INDEX ROWID) OF
    'PS_RB_WORKER' (TABLE)
    0 INDEX MODE: ANALYZED (UNIQUE SCAN) OF 'PS_RB_WORKER'
    (INDEX (UNIQUE))

  • Elapsed Time delay only works once in state machine

    Hello.  I'm having problems using the elapsed time delay to show the seconds remaining on a wait step in a simple state machine.  I would like to have a front panel count down showing the time left for the step.  I thought the elapsed time delay was the way to do this.  The problem is the vi runs correctly the first time through.  But then after that the timing does not seem to reset back to the times I had set.  If I remove the elapsed time delay and just stick a wait time in the state, the vi runs as I would expect.  This just doesn't give the user an idea of the time remaining.  What am I missing when using the elapsed time delay, or is this just the wrong tool for the job?
    A smaller issue is that I would like to move the tasks, in this case the LED's outside the loop so I don't have to repeat code.  But when I tried moving them outside with only leaving the constants inside the state they did not work as I expected.  If you have tasks like the operation of a set of booleans that you are used in several states, what is the cleanest way to do this without repeating code?
    Thanks for the help.
    Danny
    Solved!
    Go to Solution.
    Attachments:
    Elapsed Time Delay.vi ‏39 KB

    The problem is that the Auto Reset on the express VI resets the start time of the timer as soon as the time has completed.  So you are essentially restarting the #1 timer immediately and then go on to #2.  Once #2 is completed, #1 has already passed 10 seconds as well.
    What you need to do is use the reset input for the express VI, but only have that be true the first time it is called.  By using a shift register and the implies function on those loops, you can do that.
    As for the duplication of states, don't have a state 1 and a state 2.  Just have a Run state.  Use a shift register to maintain a value for what your next state will be and a case structure to based on that to show what booleans should be lit and what the next state will be.
    Message Edited by Ravens Fan on 06-12-2009 10:56 AM
    Attachments:
    Example_VI_BD.png ‏2 KB

  • Ayuda con elapsed time

    Que tal a todos espero me puedan ayudar con la siguiente cuestión.
    Tengo un VI en el cual un termometro apaga a A1 y B2 cuando llega a 80 o más, cuando A1 y B2 se apagan B1 debe encender por 20 segundos, me gustaría que me apoyarán con que pasado el tiempo del elapsed time B1 se apague hasta que el termometro se vuelva a manipular.
    Espero haberme explicado de manera correcta.
    Buenas noches, y espero su apoyo
    Attachments:
    practica.vi ‏137 KB

    Saludos Fer_Ruiz,
    Para hacer eso será necesario que utilices un Event Structure con un valor de timeout aceptable para tu aplicación (tal vez 100 ms), esta estructura nos permite monitorear eventos de usuario sobre los controles (en este caso sobre el control "Temperatura"). Una opción que se me ocurre es que escribas en alguna variable booleana al dispararse el evento Value Change de Temperatura, y que esta misma variable la utilices para condicionar el evento dónde utilizas el Express VI Elapsed Time, el cuál por cierto no te recomiendo utilizar ya que consume el 100% de un núcleo de tu procesador y por lo tanto no sería eficiente. Tal vez podrías utilizar una Variable Funcional Global que incluya alguna función de temporización junto con un contador para generar ese retardo de 20 segundos.
    Event Structure:
    http://zone.ni.com/reference/en-XX/help/371361K-01/glang/event_structure/
    Quedo al pendiente de tus comentarios, saludos.
    David P.
    National Instruments
    Applications Engineer
    www.ni.com/soporte

  • Elapsed Time in my V$SQL

    Hi,
    Can someone answer this please?. I'm bit perplexed by the elapsed time in my v$sql
    UPDATE ods_router_tables SET last_data_received = :b1, last_data_received_dst = :b3 WHERE
    table_name = :b2 AND NVL(last_data_received,TO_DATE('01-JAN-1980','DD-MON-YYYY')) < :b1
    Executions: 2786327
    Disk reads: 0
    Buffer gets: 6023381
    Rows processed: 423713
    Optimizer cost: 1
    Sorts: 0
    CPU Time: 898500000
    Elapsed Time: 1.84467440681166E19
    This table is quite small, only 44 records and if i run the statement in Sql plus, it runs in a
    flash. But why this enormous Elapsed time in V$SQL. Is my conversion of this time to
    seconds/execution correct?
    Elapsed time in seconds/execution: 1.84467440681166E19/1000000/2786327=6620451 seconds!
    I guess there is something seriously wrong here. I'm running on a 4 CPU server. DB version is 9.2.
    I see similar figures in some of the innocent looking Insert statements as well.
    thanks in advance,
    Sunil

    ELAPSED_TIME in v$sql also includes all wait times for that sql. Is it possible that update is waiting for locks some time? See the following case.
    SQL> create table test2 as select * from dual;
    Table created.
    SQL> update test2 set dummy='A';
    1 row updated.From another session try to update the same row.
    SQL> update test2 set dummy='B';Wait for some time. Then rollback the first session.
    SQL> rollback;
    Rollback complete.Now look at v$sql.
    SQL> select sql_text,executions,elapsed_time from v$sql where sql_text like 'update%test2%';
    SQL_TEXT
    EXECUTIONS ELAPSED_TIME
    update test2 set dummy='B'
             1     29413712
    update test2 set dummy='A'
             1         2506The first update's elapsed time is very small. The second update's elapsed time is high because of the wait for the lock.

  • Why am I being charged data usage during the times my phone is not being used?

    I got a notice on my phone that my number has used all of its allowed data usage for the month.  I looked at my current usage and seen that I was being charged for data usage during the times that I am not using my phone.  I figured it up and it adds up to be more than the amount that you say I am over.  Explain please.

    Ok, what all should I turn off on my 5s and I should get any additional fees waived.  I just got this new phone about a week before Thanksgiving and never got a notice till it was full.  I have never went over before.  I also have never been told that I could be charged data even if I am not using my phone and I should make these changes to prevent this.
    Also, the phone was 2 days late getting to me.  So in addition to any additional fees that I may occur from the overage I should get a credit for the delay in my phone being sent.  Oh, and it probably would have been longer had I not called to see where it was at, which the guy that helped me put in the order and was to follow up the next day with a phone call to let me know what the status was and never did.

Maybe you are looking for

  • Windows Vista can't find audio device

    I successfuly installed windows vista Beta 2 on my macBookpro, but I don't have sound. windows says No Audio output device is installed. Any suggestions? Help! MBP 17''   Mac OS X (10.4.6)   2G Ram 100G HD 7200 rpm

  • Can't copy files to Xserve Raid

    Hello, I'm having serious issues copying files to my work's Xserve Raid. When I try to copy files to it, it stalls for several minutes trying to copy, but making no progress, before giving an error saying: "The Finder cannot complete the operation be

  • Is Pages a good 'reader' app for Word documents ?

    In doing a few searches in this forum on the subject I find some conflicting reports ( what a surprise ) so I am compelled to ask : How good a job does Pages do in reading Word documents particularly Word documments from PCs? Most of our word proc ne

  • Form Based Authentication in SharePoint 2013: Getting The remote server returned an error: (500) Internal Server Error

    Hi  I configured forms based authentication mode in Sharepoint 2013 site. When i tried to log in with windows authentication prompt it throws the following error The remote server returned an error: (500) Internal Server Error [WebException: The remo

  • Podcasts don't work :/

    Hello. Why can I not upload any podcasts onto my Shuffle? I have tried several times to add various podcasts when uploading but they never work on the Shuffle. Only songs. Is this a problem that only my Shuffle has, or aren't they allowed podcast upl