LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"How do I write data to PC RAM Memory from LabVIEW 7.0"

you should have a look at the Gtoolbox george does this somehow so it can be done we just have to figure out how he did it. NI should know how to do this but for some reason they are not telling.



Joe.
"NOTHING IS EVER EASY"
0 Kudos
Message 21 of 23
(1,039 Views)
Hey all,
 
Right well I've tried everything here.
Firstly I had the dll idea. Nope
Then I had an idea that you could use queues. Again no. 
I thought about (and implemented) writing the queue reference to a binary file and getting the other vi's to read that reference then deque elements from it.  That also didn't work.
So I'm fresh out of ideas that don't involve changing your architecture.
 
I have even sent this query up to the states to get some feedback of R&D. (I would love to know how to do this as it's really starting to "get on my ..ahem!!" anyway...
Only ways I can think of doing this are.
 
Binary files (if you structure your data correctly then you can dynamically access and update the file very quickly)
 
Putting all of these exe's into the same exe.  (create a main vi that has 2 while loops (or however many you need) then set it to run on startup, hide the front panel (Or have the panel as a switch panel where you can open and close vi's) and place each individual vi in each of the while loops.  Set them to open the front panel when they are run.
This way you can use the globals, queues, functional globals (dll's or vi's) or any other idea that has been placed on this forum.
 
(I have another idea up my sleeve, but I need to investigate before I promise anything)
 
Has anyone else got any further?
 
AdamB
Applications Engineering Team Leader | National Instruments | UK & Ireland
0 Kudos
Message 22 of 23
(1,018 Views)

Hi there,

 

I am new to posting here but I think it is possible to link two separate executables, check attachment.

You can modify them any way you like, including pull down menus with which vi within which executable to link.

 

It is still via TCP not memory and requires enabling VI Server with TCP, but you can do that programmatically.

 

I had some problems with calling localhost, so I replaced it with quick call for IP address.

 

Artur

0 Kudos
Message 23 of 23
(956 Views)