LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Does vi-server all times uses a network-protocoll

Does the vi-server function uses all time a network protocoll (tcp/ip), even the function is only used in the same LabVIEW-application or EXE?
 
Question behind:
If I have a lot of "real" network-traffic on my machine, does that affect the performance of vi-server?
 
I know, that if I use vi-server to communicate with other application/EXE on the same or a remote machine it uses TCP/IP, but I'm not shure if it also uses it if TPC/IP is disabled to block remote connection.
0 Kudos
Message 1 of 6
(2,970 Views)
Hi zav,

Are you using a Windows machine? If yes, then local connections to the VI Server are done via ActiveX.

I don't know exactly what 'a lot' means when you say that you have "a lot of real traffic", but it would need to really be A LOT of traffic in order for it to impact the VI Server negatvely.

I hope this answers your questions. If you have any more questions about the VI Server, feel free to post them!

best regards,
0 Kudos
Message 2 of 6
(2,946 Views)
Thanks for your response.
 
To be sure I understand you correct:
 
- If I use VI-Server to in LabVIEW (indepent if in developement enviroment or as .exe) on the same machine (even to an other instance of LabVIEW), calls are executed by ActiveX not using TCP/IP or other Network-Protocoll
 
- Using VI-Server connecting to a remote machine, then TCP/IP is used to echange the data.
0 Kudos
Message 3 of 6
(2,920 Views)
As far as I know, ActiveX is only used to display LabVIEW as an ActiveX server. Whenever you open a VI server to another instance (even within the same process) you use only TCP, which you can see by the need to have a port open.

___________________
Try to take over the world!
0 Kudos
Message 4 of 6
(2,918 Views)
Hi zav,

You understood correctly.

I made a simple example VI to test this, and no network connection was registered when accessing the VI server.

Best regards,
0 Kudos
Message 5 of 6
(2,894 Views)

The final answer can only be answered by testing on your machine so lacking those results let me say "depends".

In theory the hardware should be screen network traffic such that only message targeting your machine ever make it "out of the chip". So if the network is not doing a lot of broadcasting and heavily using UDP etc, then your app should never see the traffic.

When openeing acoonection to VI server on your local machine, the TCP/IP stack SHOULD detect the target machine is itself and it should NOT pass the data onto the wire.

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 6 of 6
(2,889 Views)