High Speed LAN Instrument Protocol

<h2 id="benefits">Benefits</h2>
<p>HiSLIP fixes several problems with the VXI-11 protocol (which synchronously sends GPIB commands via <a href="/facts/SunRPC/oSR4C7hH">SunRPC</a>):
</p>
<ul><li>New asynchronous “overlap mode” to help applications fully utilize <a href="/facts/Ethernet/nMfhU8tU">Ethernet</a> performance</li>
<li>Support for both shared and exclusive instrument locking</li>
<li>Support for <a href="/facts/IPv6/d4dg7kIL">IPv6</a></li></ul>
<h2 id="features">Features</h2>
<p>HiSLIP can operate in two different modes:
</p>
<ul><li>In “overlap mode”, input and output data are buffered between the client and server and a series of independent queries can be sent by a client without having to wait for each to complete before sending the next. The responses are sent back in the order in which the queries were sent. This asynchronous operation helps applications to fully utilize <a href="/facts/Ethernet/nMfhU8tU">Ethernet</a> performance.</li>
<li>There is also a slower “synchronized mode”, in which a client is required to read the result of each query before it can send another. It is intended for backwards compatibility with the capabilities of <a href="/facts/GPIB/JdmHrwJB">GPIB</a>, VXI-11, and USB-TMC instruments.</li></ul>
<p>HiSLIP clients (VISA libraries) have to support both modes. HiSLIP servers (instruments) need to support at least one of them, but can also support both.
</p><p>A HiSLIP client contacts a server by opening <i>two</i> TCP connections, both to port 4880, and sends packetized messages on both:
</p>
<ul><li>The “synchronous channel” carries normal bi-directional ASCII command traffic (e.g., <a href="/facts/Standard_Commands_for_Programmable_Instruments/pz4SLcVw">SCPI</a>), and synchronous GPIB meta-messages (END, triggers, etc.).</li>
<li>The “asynchronous channel” carries GPIB-like meta-messages that need to be treated at higher priority and independent of the data path (e.g., device clear, service request).</li></ul>
<h2 id="usage">Usage</h2>
<p>To migrate from VXI-11 to HiSLIP, a user of a VISA library and instrument that support both merely has to change the VISA resource string used to address the instrument. The shortest possible version of a VXI-11 VISA resource string is TCPIP::<IP address|hostname>::<HiSLIP Server>[,port#]::INSTR. To use the HiSLIP communication channel, such a VISA resource string needs to be changed to: TCPIP::<IP address|hostname>::<HiSLIP device name>::INSTR.  If the HiSLIP server is using a port other than the default of 4880, then it must be specified in the resource string as:  TCPIP::IP address|hostname>::<HiSLIP device name>[,port#]::INSTR.
</p>

<h2 id="external-links">External links</h2>
<ul><li><a href="http://www.rohde-schwarz.de/appnote/1MA208">http://www.rohde-schwarz.de/appnote/1MA208</a> Fast Remote Instrument Control with HiSLIP - Application Note</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>"IVI-6.1: High-Speed LAN Instrument Protocol (HiSLIP)" (PDF). IVI Foundation. <a href="https://www.ivifoundation.org/downloads/Protocol%20Specifications/IVI-6.1_HiSLIP-2.0-2020-04-23.pdf" target="_blank">https://www.ivifoundation.org/downloads/Protocol%20Specifications/IVI-6.1_HiSLIP-2.0-2020-04-23.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>"VXI-11 Bus Specification". VXI Bus Consortium. <a href="http://www.vxibus.org/?q=node/206" target="_blank">http://www.vxibus.org/?q=node/206</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
</ol>

High Speed LAN Instrument Protocol open-in-new

High Speed LAN Instrument Protocol