10-28-2013 07:28 AM
No, you don't.
What you have to do is to implement the TCP/IP server on the Labview side and the client on the C side.
And you have to choose a protocol for the tranferred data.
At the end you'll have two executables talking to each other.
As a side benefit the two executables could run on two different machines.
Regards,
Marco
10-29-2013 02:50 AM
What part is it that you need to do from within LabVIEW?
If it is only the acquisition which is part of the NI-IMAQdx driver. You could just call those acquisition functions directly from C.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark
10-29-2013 07:46 PM
@A.Rohde wrote:
If it is only the acquisition which is part of the NI-IMAQdx driver. You could just call those acquisition functions directly from C.
Oesen's license is for CVI 2.1 though, which looks ancient. Does that include NI-IMAQdx support?
10-30-2013 12:59 AM
From his post it sounded more like he was interested in creating a component i LabVIEW and ship and to his friends computer. So I don't think that the CVI compiler is the one to be used, but we need more info here. So I doubt that it would make a difference.
But if he can create a LabVIEW DLL which includes call to the IMAQ dll then there should be no problem in calling the IMAQ dll seperately as well.
I'm a huge LabVIEW fan so I don't normally recommend people to avoid LabVIEW but in this case it sounds like a big overhead to create a LabVIEW module for calling the vision functions from C when you can already call the native vision functions directly.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark
10-30-2013 07:14 AM
Hi Anders.
I didn't know that i directly could call those acquisations from C. Due to my personal experience, it is long time ago I worked with C, so I prefer to do this solution in LabVIEW, otherwise my 2 weeks of working will be lost.