Remote Call by Reference Performance

[viScience]

I am trying to optimize my cRIO -> PC remote call performance.
Does anyone know what is going on under the hood when a remote call is executed.
Here are some things I am wondering about:

1. How is connector data bundled up and converted to a TCP/IP payload
2. What is the structure of the VI Server Protocol
3. What is the threading model of the VI Server
4. What would a transaction timeline look like

TIA

[MikeS81]

Hi sachsm,

i can't answer your questions, but i think you can see a part of the structure using a lan sniffing tool. To increase your performance you can build your own TCP/IP communication and send only commands to your cRIO. There you can run the function you want and send the result back to your host. I think it should be faster and you know what happens.

Hope it helps.

Mike

[Anna_K.]

Hello Sachsm,

I've tried to find specific answers to your questions, I've come accross a couple links that you can browse through.

A Simple TCP/IP Messaging Protocol for LabVIEW

https://www.ni.com/en/support/downloads/tools-network/download.simple-messaging-reference-library.ht...

VI Server: Configuration Page

https://www.ni.com/docs/en-US/bundle/labview-api-ref/page/resource/dialog/preferencesdialog/preferen...

Building VI Server Applications

https://www.ni.com/docs/en-US/bundle/labview/page/building-vi-server-applications.html

I hope you might find these helpful.