LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
manu.NET

Make "Mechanical actions" works in assynchronous launched VI's ...

Status: Declined
Programming issue. Pushed to forums.

Hello,

 

When you launch a HMI VI assynchrounously using the "Run VI", the mechanical actions of the controls are not taken in account.

When i launch the same VI directly using the run button ... all works fine !

 

For example i wanted to use a "Switch until release" ... The value of the control should stay true until i release the mouse button.

in assynchronous running mode, the control doens't keep the "true" value until the mouse button is released ...

the control value automatically change to false value even if the mouse button is pressed !

 

It seems that there is a different behavior between ...

 

  • A normal run
  • An assynchronous run

=> The events are not handled the same way in both execution mode.

 

It should be nice to make the mechanical actions works in both cases ...

Or if the problem is linked to the LabView inner architecture, to explain this particular behaviour in the Labview Help.

 

One of my collegue gets also a problem like mine using FPGA IRQ methods calls ...

 

  • The Wait IRQ works fine in a "Main VI" launched by the Run button.
  • The same code generates an error, if the VI is launched assynchronously.

 

I think that the behaviour difference of the 2 run mode (Direct run or assynchronous run) should be described in detail in LabView Help ...

 

Manu.

Manu.net
7 Comments
AristosQueue (NI)
NI Employee (retired)

Really? I don't observe this. Please post a link to VIs that demonstrate this behavior.

manu.NET
Active Participant

Hello Aristos Queue

 

You're right ... With a simple test there is no problem.

My application is a little bit more complicated .... My problem should come from somewhere else.

 

I will try to find out what's my problem !

 

Manu.net

 

Manu.net
AristosQueue (NI)
NI Employee (retired)

I'm going to close this idea. Please repost in the main discussion forums if you think you've found a LV bug or need an AE's help to work out the issue.

manu.NET
Active Participant

Ok it's better like this ... i would have done it if i could ....

 

BOUUHHHH manu ... check your problems before posting !!!!! Smiley Sad

 

I have also a support open about this problem.

 

Thanks.

 

Manu.net

 

Manu.net
MichaelAivaliotis
Active Participant

Can someone close this idea?



Michael Aivaliotis
VI Shots LLC
manu.NET
Active Participant

Hello,

 

I have found the origin of my problem !

It is not linked to the Synchronous / assynchronous VI execution mode, but to the setBusy/UnsetBusy VI's.

 

When i click on one of my buttons (with switch until release mechanichal action)  located on the front panel of an assynchronous launched VI ... a command is send to motions ... an an event is thrown to my application main window in order to lock it's front panel unsing the setBusy VI. The SetBusy VI has an effect on my main window ... but also on the mechanical behaviour of other windows  ... even assynchrounous launched VI's !

 

Manu.

 

Manu.net
G-Money
NI Employee (retired)
Status changed to: Declined
Programming issue. Pushed to forums.