LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

how to use datasocket in labview real time to send data aquired using daq hardware?

Problem in using Datasocket with Real Time:
I am using Labview 6.1 with Real Time.
I used to work with datasocket and it was working fine.I generate some signals in Computer A and send it through the Datasocket Server to Computer B.I used the Datasocket Read And Datasocket Write VIs for this.I plot some graphs in computer B with the live data coming from Computer A.I used the DataSocket server of Computer A.
Everything was fine.Now the problem is , when I am aquiring some signals on the computer A using NI DAQ and hardware PCI 7030/ 6040E and use the Datasocket, I am not getting any data on the Computer B.
I used the Execution Target as DAQ Board on Computer A and labVIEW for Windows
in Computer B.I could not set the Execution Target as Real Time Engine on Network.Is it necessary ?When that option is selected it is asking for some host name and password.which password it means?Is there any Remote Device option to be set up?Can anybody help?
R.Padmakumar
thalvain@yahoo.co.in
0 Kudos
Message 1 of 2
(3,157 Views)
Hi My. Padmakumar,
First, the netwok option in Switch execution target refers to the RT PXI or RT FP modules connecting to the host PC through network cable, you are using RT DAQ, so this does not apply to you.
Second, what being involved here are three computers, unbelievable isn't it? The RT DAQ itself is actually a mother board with CPU, memory and a DAQ daughter board on top. So, you really need to send the information back to Computer A first, then send the data from Computer A to Somputer B, there you can use either Datasocket or any other network functions you prefer. To transfer the data from the RT DAQ to computer A, unfortunately the Dasocket option is not available to the RT DAQ, you can either use TCP/IP, or VI server, or shared memory, I recommen
d using shared memory, sicne that way you can still keep real time without much more programming, for using TCP/IP, then you will have to have another loop running in parallel that can take care of the communication task, the communication issue is a whole chapter in RT,attached is a link that can provide you with more useful information, if there is further question, you can respond to this email.

XD Gao
Application Engineer,
National Instruments
0 Kudos
Message 2 of 2
(3,156 Views)