CODEWITHSUNDEEP
cipclabview
Salvatore
Salvatore

Reputation: 1185

Best Labview IPC

I need to make labview communicate with a C/C++ application. Both the applications run on the same machine. What is the IPC mechanism with lower overhead and highest speed available in LabView?

Upvotes: 1

Views: 1165

Answers (3)

Kamran Bigdely
Kamran Bigdely

Reputation: 8456

NI has provided a thorough document explaining that: Using External Code in LabVIEW [pdf]. In brief, you can use:

  1. Shared Libraries (on windows they are called DLLs). According to the above document, any language can be used to write DLLs as long as the DLLs can be called using one of the calling conventions LabVIEW supports, either stdcall or C."

  2. Code Interface Node (CIN), which is a block diagram node that links C/C++ source code to LabVIEW.

  3. .NET technology.

Note that "Shared Libraries" and "Code Interface Node" are supported on Windows, Max OS X, Linux and Solaris.

Upvotes: 1

crlanglois
crlanglois

Reputation: 3609

TCP, UDP, ActiveX, DDE, file transactions, or perhaps just directly calling a dll are the solutions that come to mind.

First I'd just call a dll if you can manage with that. Assuming you're tied in to using two separate applications then:

I'd use TCP or UDP. File transactions are clunky but easy to implement, DDE is older but might be viable (I'd recommend against it).

Basic TCP/IP in Labview

TCP/IP and UDP in Labview

Calling a dll from Labview

Upvotes: 3

Jonathan
Jonathan

Reputation: 1508

Have you investigated straight up TCP or UDP?

It'll make it easy if you ever need to separate the applications onto different machines later on down the road. Implementation is pretty straight forward too, although it may not be the fastest throughput.

What speeds are we talking about here?

Upvotes: 2

Related Questions