Enquing Button Strings

[ADrexelDragon]

Tejinder,

Thank you for this information. I have used this elapsed time express vi before but was not sure if it would work in this case. I have been having troubles using the time to determine the time length at which the button was pressed. If you run this vi, it shows the Time On correctly the second press. How do I negate the first time?

[Tejinder_G.]

You may want to use the reset button on the elapsed time VI. 

If I unbundle your cluster and use the button itself to reset the elapsed time VI, it works pretty well.

[ADrexelDragon]

That works only for the one button. I tried to incorporate your idea to do it with all the buttons but was unable. I am not sure why this does not work. It should separate each one independently. Correct? Do I need 8 separate elapsed time vi? Should it be inside the case structure?

[Online_Courses]

Message Edited by Online Courses on 03-31-2010 12:02 AM

[Online_Courses]

Message Edited by Online Courses on 03-31-2010 12:04 AM

[jareds]

If you're trying to find the elapsed time for each individual button, then you'll need an Elapsed Time VI for each button.  On the other hand, if you're looking to have one time measurement for them all, then using one with a case structure should be fine.

[ADrexelDragon]

jareds,

Thank you for your input. It was the information I needed. Would be easier to group my information(random #, start time, elapsed time) into separate clusters?

[Tejinder_G.]

It really depends on your preference and what you think would be easier for your application, but if you've got a case structure that will modify values for each button, and you have many cases, then it may be cleaner to have a cluster of clusters so that you limit the number of wires on your block diagram.  This way you can unbundle only the values you want to modify at that time.