LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

embed a 32-bit exe in a 64-bit LabVIEW app?

Hi JJ,
I had a similar problem with a need for a 64bit LV app due to large files, and a 64bit driver. I solved it by making a TCP channel and use regular flatten/unlatten vi's using one similar data typedef. The typedef can be read/written (during development) on both 32 and 64bit LV.
The LV data type stays similar.
So: I kept the 64bit LV app, and start the executable when my 32-bit app launches.
Then I send/receive the data I want via the typedef format.
A Queue on both sides allows asynchonous usage.
Then it doesn't matter what runs on the other side. The only thing shared is the data typedef.
I just hope that NI keeps the typedef control vi and the flatten/unflatten code compatible, then it will remain working for any to any LV version.
This helps me to stay with native LV code, no fancy stuff. But not 'embedding' things.

0 Kudos
Message 11 of 13
(490 Views)

@Andre_FR wrote:


I just hope that NI keeps the typedef control vi and the flatten/unflatten code compatible, then it will remain working for any to any LV version.


Until Intel or Apple release a 128-bit CPU and NI decides to support it, you should be fairly safe from changes to that part of LabVIEW. 😁

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 12 of 13
(485 Views)

Hi Andre_FR:

 

I have completed the project that presented this problem but I like your approach and will keep it in my mental bag of tricks.  It seems somewhat akin to Hoovah's suggestion of using network streams but more generic.  Thanks for chiming in with a great suggestion.

 

John B.

0 Kudos
Message 13 of 13
(460 Views)