LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can't build the enclosed VI.

The enclosed VI will build and execute but it can't seem to read global variables.  Another program that writes to these globals is running at the same time.

 

When I run both programs in develop mode everything is fine.

 

Any ideas?

 

Thanks,

Mark

 

 

0 Kudos
Message 1 of 5
(2,462 Views)

You, of course, cannot share global variables between two different exe's. They each run in their own application instance. There are many different approaches to share communication between applications. See this.

Message 2 of 5
(2,460 Views)

Thanks for the answer.  I'm not happy though.

The reason I had to separate the routines is because LabVIEW won't let me open and close subvi windows in an executable.  Something to do with security issues.

 

I'll read up on the information you pointed me to.

 

Thanks for saving me time.

0 Kudos
Message 3 of 5
(2,451 Views)

@Mark Levine wrote:

Thanks for the answer.  I'm not happy though.


Well, the universe displeases a lot of people. It doesn't seem to care too much about us though, as it cheerily goes on its merry way to a nice Big Chill end. I hope it's happy when it gets there.

 


The reason I had to separate the routines is because LabVIEW won't let me open and close subvi windows in an executable.  Something to do with security issues.

Can you provide more details on what you are specifically trying to do? Are you talking about problem when getting a reference to an executable?

Message 4 of 5
(2,447 Views)

Never mind.

 

I've included the subVI in the main program so I don't have to worry about passing globals.

 

Then I changed the subVI properties to open the front panel when called.  When I did that the executable was able to open and close the subVIs under program control.

 

 

0 Kudos
Message 5 of 5
(2,440 Views)