Shared Variable Engine on Windows PC w/o full install of LabVIEW

[M.Shair]

Hi Mr.

have you find a solution to the problem you 've attached about the shared variable in exuctable, because I'm facing the same problem now.

I'll be so thankfull for your cooperation

[LaurenLL]

Hi Mahmoud,

I noticed that you had a later post on another forum saying that you have solved the problem.  It sounds as if you are now able to use shared variables in an executable, but do not hesitate to post on a forum if you still have questions.

Regards,

Lauren

[M.Shair]

Yes.......

Thanx for your concern

[hecmar.arreola]

I've almost abandoned shared variables in executables all together.  Just kinda felt buggy whenever I tried to run the code.  Getting the windows firewall exceptions to work on our Windows Domain was tricky.  Once the shared variables were running inside the executables it was very difficult to debug any problems that may come up.  For sending simple arrays of boolean values or something, that works fine.  But I was trying to send arrays of waveforms and this became more problematic.

I think that remote panels are much easier to develop and maintain.  Very different approach, but accomplishes my objectives of having a remote test system that I access from a different computer.  With shared variables there was a need to maintain a program for each machine (such as a client/server).  I've also had quite a bit of trouble with shared variables on the same machine between VIs of the same project, especially when trying to transfer large data sets such as 2d arrays of waveforms.  The feature is still new as of v8 of LabVIEW, and my hope is that the kinks will be ironed out by v9.

-nic

[Vaibhav]

Hi Nic,

Kind of an old thread, but after working with the shared variables for quite some time, I am finding a basic thing not working. So far I used to deploy the shared variables using just the options in the application installer builder. But now that I tried to work on the basic way (as for versions before LabVIEW 2009), trying to deploy the library using VI server method, I see that similar problem which you were facing.

To be more specific, I am able to deploy the library when I supply an absolute path, but not when a relative path (data folder) in an executable. Although the library is in the same data folder, the .exe won't recognize it when supplying a relative path.

Just curious if you found solution to your problem then as the thread is still open (without any marked solution).

Thanks ahead! 

[T-REX$]

Hi Vaibhav,

This thread is pretty dead, so I don't know if Nic will get back to you. That said, I believe you need to use an invoke node to deploy the libraries programmatically and create a relative path based on the thi's vi path function. If you have further questions on this, you might have better luck in a different thread.

[Vaibhav]

Hi TJ,

Thanks for your reply.

I am using that method, to step-by-step deployment in a controlled manner, but my problem was about that path. It has been resolved now.

Thanks and Have a good day!