Inputs (buttons) on USB interface board /event case

[Matt V]

Hi,

For some a simple question I think, but not for me. I want the input buttons on the USB interface board control the event case, so when I press an input button on the board a new event case will start. Does somebody know how?

Thanks a lot!

Matt

[GerdW]

Hi Matt,

you should use a "value (signalling)" property node of "Input" to generate events for your digital inputs...

[Matt V]

Thanks for your quick response, I will try that now...

[Dennis_Knutson]

That VI makes no sense. You have a value change event for an indicator. Why don't you try doing a read inside the timeout event? Be sure to set the timeout value to a reasonable rate. If you want to fire another event when the input changes, you could write to a Value(Signaling) property of the control.

[Matt V]

Hi GerdW,

it's still not working properly, because of the signalling property node the event starts before i even press a button.. And if I place the property node in the event it is not working at all.. Maybe I do something wrong?

[Dennis_Knutson]

Of course it's firing the event before you do anything. What do you think is supposed to happen? And putting it inside the event is also silly. If you want to read the board, DON'T create a value change event for it? What part of my suggestion don't you understand?

[Matt V]

I'm not placing it in the time out event because it should start when I press a button on the interfaceboard...

[GerdW]

Hi Matt,

you really should read the context help on event structure and "value (signalling)" property node...

See attachment for a rough sketch. You need to refine that even further...

[Matt V]

hmmmm.... Not make a value change event for it? What I want is that the rest of the program(try to make a capacitor capacity test) starts when I press a button on the board, thats why I wanted to start a new event with it..So what is now a clever thing to do? 

[Dennis_Knutson]

Pay attention. Gerd's example is exactly what I told you to do. A user event is not at all the same thing as a hardware event so your event structure as written is senseless.