Keysight N6702 VIs - TCP

[DailyDose]

So I've used the available VIs to communicate with the Keysight Power Supply for sometime now, but it has always been through GPIB.  My latest task is to do it via Ethernet.  On National Instruments website where you can download the (let's call it a) Driver, it says you can use it for Ethernet.  However, each VI is using VISA.  Does anyone have any experience with this?  Do I need to make a whole new set of VIs that are using the TCP VIs or is there a virtual COM port piece of software that's available from Keysight?

[TobyD]

Typically, if you go into NI-MAX and 'Create New VISA TCP/IP Resource' by right clicking on the 'devices and Interfaces --> Network Devices' tree, the instrument will then show up as a valid VISA instrument.

[aeastet]

Key site has LabVIEW software for a lot of their power supplies. They need some work but should get you started. Here is an example:

https://www.keysight.com/main/software.jspx?cc=US&lc=eng&ckey=1629756&nid=-11143.0.00&id=1629756

You could look up your power supply and see if they have something available.

[Mark_Yedinak · Accepted solution]

---

@TobyD wrote:

Typically, if you go into NI-MAX and 'Create New VISA TCP/IP Resource' by right clicking on the 'devices and Interfaces --> Network Devices' tree, the instrument will then show up as a valid VISA instrument.

---

It has been a very long time since I used VISA for TCP connections but it is quite easy to generate the resource name dynamically. The format for a TCP INSTR is "TCPIP[board]::host address[::LAN Device name][::INSTR]" and "TCPIP[board]::host address::port::SOCKET" for a TCP socket connection.

[DailyDose]

---

@Mark_Yedinak wrote:

---

@TobyD wrote:

Typically, if you go into NI-MAX and 'Create New VISA TCP/IP Resource' by right clicking on the 'devices and Interfaces --> Network Devices' tree, the instrument will then show up as a valid VISA instrument.

---

It has been a very long time since I used VISA for TCP connections but it is quite easy to generate the resource name dynamically. The format for a TCP INSTR is "TCPIP[board]::host address[::LAN Device name][::INSTR]" and "TCPIP[board]::host address::port::SOCKET" for a TCP socket connection.

---

This method sounds necessary if I wish to deploy my code onto different and multiple Test Machines with little NI Max configuring.

[DailyDose]

Up and running.  Thank you all!