LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

SubVI with event structure does't work when called from main VI

Solved!
Go to solution

Hello,

I've following problem.

I have this VI: it works alone, but if I call it from a Main VI it doesn't works.

I already tried to use a reference, but it does't work.

 

It quiet strange also because if I open the VI in the Prject tree I can modify it.
If I open the VI direct clicking on it from the main VI it appears everytime in running.

 

I just have more masks who starts normally, but only this give me problem.

 

Thank you in advance for your hellp!

 

Do you have any suggestione?

0 Kudos
Message 1 of 8
(2,575 Views)

Hello,

I've the same problem.

I have this VI: it works alone, but if I call it from a Main VI it doesn't works.

I already tried to use a reference, but it does't work.

 

It quiet strange also because if I open the VI in the Prject tree I can modify it.
If I open the VI direct clicking on it from the main VI it appears everytime in running.

 

Do you have any suggestione?

0 Kudos
Message 2 of 8
(2,585 Views)

Buona sera Ferdinando,

 

Do you have any suggestione?

Do you really need to set that VI to reentrant?

I guess that's the source for this "appears running" problem…

 

if I call it from a Main VI it doesn't works.

How do you know?

In which way it does not work?

Any errors?

To create events for the event structure the frontpanel of your VI has to be open/available to the user!

 

I already tried to use a reference, but it does't work.

A reference for what? What does not work?

What do you want to achieve by using any kind of reference?

 

On your VI:

- I would use much less "value" property nodes! No reason to place terminals in the first frame of a sequence… (Use more wire and shift registers!)

- Some Rube-Goldberg code inside: why do you need to output TRUE/FALSE in a case structure depending on the boolean case selector? (Event case "Quit")

- Bundle related controls in clusters. This will greatly reduce all that effort to enable/disable controls…

- It's a nice mix of German and English in this VI, often referred to as "Denglisch"… 😄

 

Edit:

Please keep discussions in one place! No need to post the same question twice!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 3 of 8
(2,577 Views)

Hi Ferdinando, what about the VI doesn't work? Can you be more specific?

 

I am using LV 2016, if you can do "file >> save for previous version..." i can take a look at it.

0 Kudos
Message 4 of 8
(2,568 Views)

Eheheheh thank you for your suggestions.

I accept your corrections.

The aim was to clos ASAP this SW.

 

I mean it works very well if I start it alone in it's windows in debugging mode.

But if I call it from main VI and I pass some value for tables...

The event structure does'nt works.

I became a mask and that's all.

0 Kudos
Message 5 of 8
(2,564 Views)

Hi Ferdinando,

 

But if I call it from main VI and I pass some value for tables...

How do you pass those values to the "tables"?

 

The event structure does'nt works.

I repeat: the event structure will only react on user interaction! (Or "value signalling" property nodes.)

 

I became a mask and that's all.

Maybe it's easier for you to write German? "Du wurdest zu einer Maske und das ist alles." ???

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 6 of 8
(2,558 Views)
Solution
Accepted by topic author Ferdinando_Vino

This looks suspicious. 

 

2018-12-19_12-06-57.png

aputman
------------------
Heads up! NI has moved LabVIEW to a mandatory SaaS subscription policy, along with a big price increase. Make your voice heard.
Message 7 of 8
(2,540 Views)

You are right, guy!

 

Thanks a lot for your support.

Sometimes, when we're tired and we write code for days... it's an hard work to make bug fixing.

 

You were very nice with me.

Thank you!

 

0 Kudos
Message 8 of 8
(2,493 Views)