Network and remote operation
R&S
®
NRPM
94
Mannual 1425.8663.02 ─ 08
uses two TCP sockets for a single connection - the first for fast data transfer, the
second one for non-sequential control commands (e.g.
Device Clear
or
SRQ
).
HiSLIP has the following characteristics:
●
High performance as with raw socket network connections
●
Compatible IEEE 488.2 support for Message Exchange Protocol, Device
Clear, Serial Poll, Remote/Local, Trigger, and Service Request
●
Uses a single IANA registered port (4880), which simplifies the configuration
of firewalls
●
Supports simultaneous access of multiple users by providing versatile locking
mechanisms
●
Usable for IPv6 or IPv4 networks
The HiSLIP data is sent to the device using the "fire and forget" method with
immediate return. Opposed to VXI-11, where each operation is blocked until
a VXI-11 device handshake returns. Thus, a successful return of a VISA
operation such as
viWrite()
does not guarantee that the sensor module
has finished (or even started) executing the requested command. It just indi-
cates that the command has been delivered to the TCP/IP buffers.
For more information see also the application note at:
http://www.rohde-schwarz.com/appnote/1MA208
.
9.1.2.4
Socket communication
An alternative way for remote control of the software is to establish a simple
TCP/IP connection to the device using the standard network drivers of your oper-
ating system. The so-called "socket" on Linux, "winsock" on Windows. The socket
communication, also referred to as "raw Ethernet communication", does not nec-
essarily require a VISA installation on the remote controller side.
Socket connections are established on a specially defined port. The socket
address is a combination of the IP address or hostname of the sensor module
and the number of the port configured for remote control. The sensor modules
use port number 5025 for this purpose.
Remote control interfaces and protocols
