The LAN (Local Area Network) remote control system provides two methods: controlling the E5061B using the SICL-LAN server and controlling the E5061B using the telnet server.
Use a LAN cable to connect between the E5061B and the external controller (computer). The following figure shows the overview of the system configuration of the LAN remote control system.
Configuration of the LAN remote control system
E5061B
External controller (PC or workstation that can be connected to LAN)
Other devices (other instruments and/or peripherals that serve your purpose)
LAN cables
In the control system using the SICL-LAN server, communication between the external controller (client) and the E5061B (server) is performed using the SICL-LAN protocol. Communication is performed using SICL (Standard Instrument Control Library). You can control the E5061B by programming using SICL or VISA with the C language in the UNIX environment, or Visual C++, Visual Basic, or VEE in the Windows environment.
To communicate with the external controller, follow these steps to turn ON the SICL-LAN server of the E5061B in advance.
System > Misc Setup > Network Setup > Enable [ON]
In order to establish communication with/ the E5061B using the TCP/IP protocol, you need to set the I/O interface of the external controller in advance. This section shows the setting procedure when using the external controller in the Windows environment.
You must install the Keysight I/O Libraries on your PC in advance. Use Keysight I/O Libraries Suite 14.2 or later.
From your PC's Start menu, click Program > Keysight Connection Expert to open the Keysight Connection Expert setting screen.
In Instrument Tab, click +Add icon, then select LAN Instrument.
In Add a LAN device dialog box, select Enter Address tab, then type the IP address of the E5061B and click OK. You can change settings as necessary. For details, refer to the Keysight I/O Libraries Suite documentation.
You can control the E5061B by programming using SICL with the C language in the UNIX environment, or Visual C++ or Visual Basic in the Windows environment.
In the control system over telnet server, communications are performed through connection between the sockets provided by the processes of the external controller and the E5061B to establish a network path between them.
A socket is an endpoint for network connection; port 5024 and port 5025 are provided for the sockets for the E5061B. Port 5024 is provided for conversational control using telnet (user interface program for the TELNET protocol) and port 5025 for control from a program.
To use telnet, port 5024 and 5025 should be opened through Windows firewall.
To communicate with the external controller, follow these steps to turn on the telnet server of the E5061B in advance.
System > Misc Setup > Network Setup > Enable [ON]
When the telnet server is turned ON for the first time, the windows firewall setting dialog box appears. Select Unblock and click OK. If you select Keep Blocking on firewall setting, you need to unblock for the remote server in Windows firewall to use the telnet server.
You can use telnet to perform conversational control by sending SCPI commands to the E5061B on a message-by-message basis. For telnet, the socket of port 5024 is used for communications.
In this example, in order to show you the control procedure using telnet, you control the E5061B (IP address: 192.168.0.2 and host name: e5061b) from the external controller in the Windows environment.
Open the MS-DOS command prompt screen.
At the MS-DOS prompt, type telnet 192.168.0.2 5024 and press the return key.
The telnet screen opens.
Type a command and press the return key; it is sent to the E5061B and executed. If you enter a command that queries some data, the query response is displayed below the line you have entered the command.
The following figure shows the screen after using the :SYST:PRES command to reset, the :SENS{1-4}:FREQ:STAR command and :SENS{1-4}:FREQ:STOP commands to set the sweep start value and stop value to 1 GHz and 2 GHz respectively, and checking the settings.
Example of control using telnet
Press ] while holding down Ctl in the telnet screen to break the connection with the E5061B. The telnet prompt appears. At the telnet prompt, type quit and press the Enter key. The connection to the E5061B breaks and telnet ends.
When controlling the E5061B from a program on the external controller, use the socket of port 5025 for connection. To use the socket, press System > Misc Setup > Network Setup > Mode > Socket Server.
It is not possible to turn on both Web server and Socket server.
Some functions such as service requests that are available in the GPIB remote control system are not available in control over telnet server.
You can control the E5061B by socket programming using the C language in the UNIX environment, or Visual C++ or Visual Basic in the Windows environment.
For socket programming, the library for network connection on the TCP/IP protocol is required. For the UNIX environment, BSD (Berkeley Software Distribution) Sockets API is available; for the Windows environment, WinSock (WinSock1.1 and WinSock2.0) is created by porting BSD Sockets to Windows and expanding is available.
For more information on the control method, see a sample program for control using WinSock described in "Controlling Using Telnet Server".
LXI (LAN eXtensions for Instrumentation) is the LAN-based successor to GPIB and combines the advantages of Ethernet with the simplicity and familiarity of GPIB. The key features of LXI are as follows:
The speed, simplicity, worldwide reach, low cost, ongoing enhancement and backward compatibility of LAN.
Quick, easy configuration through the intuitive web interface built into compliant instruments.
Simplified programming and greater software reuse through IVI drivers.
The ability to create hybrid systems that include LXI, GPIB, VXI, PXI, CANbus, etc.
Enhanced system performance and event handling via hardware- and LAN-based triggering modes.
Synchronization of local and remote instruments through the IEEE 1588 precision time protocol.
For more information on LXI, refer to www.lxistandard.org