06-05-2013 10:15 AM
I'm using the elapsed time express in a flatted sequence of my vi. I've found if the error code cluster has an error in it passed from a previous vi, the elapsed time express hangs up. You can try it w the LV2012 shipping example of elapsed time. Make the status a "red x" and give it an error
code of "-1".
Why doesn't the express just feed it on to the next error cluster?? Why would it hang up and stop counting/timing ??
06-05-2013 10:39 AM
Can you post an example of where this is happening?
I don't see any probem with the Elapsed Time express VI hanging up when there is an incoming error.