02-16-2016 05:19 AM
Hi all,
I'm developping a vi for my internship that collects data from different voltage based measurements connected to NI cDAQ boxes, firewire cameras, USB microscopes and a Fiber Bragg Grating scanner connected zith USB. The cDAQ boxes are relatively easy and the cams should work with the IMAQdx extension. The FBG scanner comes with Labview based software that is converted to an .exe file. I have searched the forums and found out it's not possible to retrieve the .vi from the .exe file. Since I'd like to get everything in one application I was wondering if it is possible to run the .exe file inside a tab so that the user can acces the FBG software within the .vi I'm developping. That way the user can get all the measurements by switching between the tab control tabs. I've already studied the example with the windows calculator but I'd rather have the .exe run within tab control. Any suggestions are welcome.
Thanks in advance
Cedric1993
02-16-2016 05:30 AM
02-16-2016 06:22 AM
I'm limited in time so rewriting the whole software for the scanner in labview isn't possible. Also I'm a newbie concerning labview so I doubt I'd be able to pull it off anyway. I'll check out the "hack" and container options you mentioned and contact the manufacturer of the software to see if they can help me out with the vi of their program. Otherwise I'll have to run the 2 programs seperately. Thank you for the quick reply though.
02-16-2016 10:10 AM
This might help.
02-17-2016 09:20 AM
I found out the executable had something called shared variables which I should be able to access from the .vi I'm writing. Don't really know how it works yet but I'll probably be able to figure it out. Other problems to figure out first though. Thanks for the help.
02-17-2016 11:18 AM
Hi Cedric,
For the usefulness of others, you probably should unmark your selected solution. It does not address the problem that was posed, it simply says "actually, I don't need to do that anymore." Also, if someone knows a better way of doing what you are asking, they may not even look at the thread and chime in because they see the question was already "solved."
02-18-2016 05:49 AM
@Cedric1993 wrote:I found out the executable had something called shared variables which I should be able to access from the .vi I'm writing. Don't really know how it works yet but I'll probably be able to figure it out. Other problems to figure out first though. Thanks for the help.
If you open up the 'NI distributed system manager' - you should be able to see the shared variables (they might only be there while the executable is running):
You should be able to access the variables from LabVIEW by one of two methods:
1) Binding the shared variable to local shared variable library in your project:
2) Programmatic access (the bottom example, the top example is once you've done the binding above, you can drag the variable to your block diagram):
02-19-2016 01:43 AM
@Sam_Sharp wrote:
@Cedric1993 wrote:I found out the executable had something called shared variables which I should be able to access from the .vi I'm writing. Don't really know how it works yet but I'll probably be able to figure it out. Other problems to figure out first though. Thanks for the help.
If you open up the 'NI distributed system manager' - you should be able to see the shared variables (they might only be there while the executable is running):
You should be able to access the variables from LabVIEW by one of two methods:
1) Binding the shared variable to local shared variable library in your project:
2) Programmatic access (the bottom example, the top example is once you've done the binding above, you can drag the variable to your block diagram):
Hey Sam_Sharp,
Thanks again for the help. I was able to get the variables in my .vi and once I have the hardware at my disposal I'll check if it works out but I guess it should work just fine 🙂