LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Synchronising the functions of booleans by their naming

Solved!
Go to solution

Thanks!

 

Have you tried to run it to see if it was functional? For some reason it is not running at all on my computer. When I click the run button, it freezes. And when I run it in debug mode, it stops when the data is being put into the event structure. This made me think that there is something wrong with the event structure. itself. Could the issue be with my version of labview?

I will try to sort it out though, and thank you very much. This has been the most helpful forum I have joined in a while.

 

Regards,

 

Tebello

 

 

0 Kudos
Message 21 of 28
(910 Views)

Hi,

 

yes I tried it and it did work on my machine.

The code stopping when all inputs for the event structure are there is intentional.

The event structure waits for an event to happen thus preventing polling and saving processor time.

Have you tried switching one of the four buttons? It should do something then.

 

I think it should work on your version too.

 

Regards Florian

0 Kudos
Message 22 of 28
(908 Views)

Florian

For event structures and property nodes the snippette tool leaves a bit to be desired.  The Code Capture Tool can address those issues and is compatable with LabVIEW so, available from the tools network.  Here


"Should be" isn't "Is" -Jay
Message 23 of 28
(900 Views)

Thanks Jeff, I'll look into it

 

Regards Florian

0 Kudos
Message 24 of 28
(898 Views)

I did, but nothing happened. I am not sure why this is happening though? 

 

 

0 Kudos
Message 25 of 28
(897 Views)

Florian,

 

Thank you so very much.

It actually works.

 

I just had to save it as an even older version.

 

Thanks so much for everything. I will definitely look for ways to make it work even better and more optimally.

 

Sincerely,

 

Tebello

0 Kudos
Message 26 of 28
(881 Views)

Weird,

 

maybe I'm not aware of some changes between LV2011 and LV2012.

Have you made any changes to the vi? If so repost your version.

 

Try adding a timeout case to the event structure. You'll find it in the first event category (<application>) inside the add case dialogue.

You'll have to wire a constant to the input that's in the top left corner of the event structure. This is the Timeout in ms. I suggest a value of 50.

You should see that this case is executed repeatedly when the vi is running. This case will execute every 50 ms when no events are detected.

Maybe 2011 needed that.

 

Regards

Florian

 

Edit: Disregard the above - you obviously made it work.

0 Kudos
Message 27 of 28
(880 Views)

Glad I "helped" you. Smiley Happy

I'm sure once you've delved a little deeper and gotten the hang of LabVIEW you will look back and think:

"Why the hell did I follow through with this weird suggestion. This could be done so much simpler" Smiley Wink

 

Regards Florian

Message 28 of 28
(874 Views)