PXI
Datasockets to view data on networked PC generated on LabviewRealtime PXI?
Hi,
the Datasocket server can only run under Windows, so it would need to be on the network on one of the normal PC's. Publishing data to that server should work fine, as long as the rt setup does have the datasocket support installed (under MAX, remote systems, find the appropriate one select install software, and make sure the datasocket support for realtime is selected.)
You only need one copy of the server running, but it then depends on your network access, and how much data you want to pass around the system etc. You may find that you want to split the data into 3 servers because you need system redundancy or to logically split up the data on a per system basis, i.e. stop certain PC's being able to see certain data.
I'd recommend TCP or UDP to remove the
need for the third party server, however, with both of these, the issue is then handling converting all your data to ascii, and being able to retireve it sensibly. This is the part datasocket takes care of for you. Also, if the setup is merely monitoring data out of the realtime PXI setup, you could run the PXI as the server, whereby the PC's make a request on the data. This under TCP is going to require a multi-client server setup. If you used udp, however, and weren't bothered about getting responses back, you could simply broadcast out on a specific port the data, and each PC could listen for that port, thereby simplifying the system.
UDP will be fastest, TCP more stable (because it handles for lost packets), and Datasocket easy to implement, but possibly slowest depending on how you decide to handle the data otherwise.
Hope that helps
Sacha Emery
National Instruments (UK)
the Datasocket server can only run under Windows, so it would need to be on the network on one of the normal PC's. Publishing data to that server should work fine, as long as the rt setup does have the datasocket support installed (under MAX, remote systems, find the appropriate one select install software, and make sure the datasocket support for realtime is selected.)
You only need one copy of the server running, but it then depends on your network access, and how much data you want to pass around the system etc. You may find that you want to split the data into 3 servers because you need system redundancy or to logically split up the data on a per system basis, i.e. stop certain PC's being able to see certain data.
I'd recommend TCP or UDP to remove the
need for the third party server, however, with both of these, the issue is then handling converting all your data to ascii, and being able to retireve it sensibly. This is the part datasocket takes care of for you. Also, if the setup is merely monitoring data out of the realtime PXI setup, you could run the PXI as the server, whereby the PC's make a request on the data. This under TCP is going to require a multi-client server setup. If you used udp, however, and weren't bothered about getting responses back, you could simply broadcast out on a specific port the data, and each PC could listen for that port, thereby simplifying the system.
UDP will be fastest, TCP more stable (because it handles for lost packets), and Datasocket easy to implement, but possibly slowest depending on how you decide to handle the data otherwise.
Hope that helps
Sacha Emery
National Instruments (UK)
