Home > Community > Discussion Forums

Real-Time Measurement and Control

Showing results for 
Search instead for 
Do you mean 
Posts: 89
Accepted Solution

Connecting cRio 9074's second ethernet port to another device via VISA

[ Edited ]

I am trying to connect a Yokogawa DAQ system to a cRio 9074 via the second ethernet port. I have enabled the second ethernet port of the cRio with a static IP address in the same subnet as the DAQ system. I have installed NI-VISA and NI-SERIAL on the cRio. I can compile the code on the cRio and I am sure the code works when I connect the DAQ to a PC. I get an error on the VISA Open VI.


Am I missing something or is it not possible to connect to the second ethernet port of the cRio this way?


Thank you,

Active Participant
Posts: 287

Re: Connecting cRio 9074's second ethernet port to another device via VISA



According to the theory behind NI-VISA, there is no restriction here because it can communicate using Ethernet.  However, I haven't found any applications that use the second ethernet port as a peripheral connection using NI VISA.  According to my investigation, this second port is used to communicate with a private network or an additional LabVIEW Real Time target. Besides, this second port does not support Shared Variables because the Shared Variable Engine is bound to one port (the first one).


However, you can use the serial port to communicate with your instrument using NI VISA.




Anuar Rojas

Anuar R.
National Instruments México y Latinoamérica
Ingeniería de Aplicaciones
Accepted by topic author jarcTek
‎08-27-2015 06:09 PM
Posts: 89

Re: Connecting cRio 9074's second ethernet port to another device via VISA

Thank you for your reply. I found the same information that you are providing but decided to give it a try.

A couple of minutes ago I was able to stablish the communication between the cRio's 2nd Ethernet port and the Yokogawa DAQ. I managed to do this using VISA commands. To communicate with the host PC, I get the information from the DAQ with the cRIO as mentioned above, and then use shared variables to publish the data to the network connected via the first ethernet port.


If someone wants to replicate this just make sure that both ethernet ports are configured with IP addresses on different subnets and configured for TCP communication. If further details are needed just send me a message.