Go package to communicate with either a Prologix GPIB-ETHERNET (GPIB-LAN) controller or a GPIB-USB (HPIB-USB) controller.

Prologix offers two GPIB controllers that enable a computer to communicate over GPIB using either an Ethernet or USB interface. Both the GPIB-ETHERNET controller and the GPIB-USB controller can operate either in controller mode or device mode. In controller mode, the GPIB-ETHERNET or GPIB-USB is the Controller-In-Charge (CIC) on the GPIB bus. In device mode, the GPIB-ETHERNET or GPIB-USB acts a GPIB device that is either a talker or a listener.

For more information, please see the User Manual and FAQ for either the GPIB-ETHERNET controller or the GPIB-USB controller.

• GPIB-USB Direct Driver: Not implemented
• GPIB Controller Mode: Implemented. Provide an io.ReadWriter from a serial port to use the Prologix GPIB-USB Controller as a Virtual COM Port (VCP) or provide an io.ReadWriter from a network connection to use the Proglogix GPIB-ETHERNET Controller.
• GPIB Device Mode: Not implemented

The prologix package can be used in conjunction with the ivi package, which is a Go-based implementation of the Interchangeable Virtual Instrument (IVI) standard. The IVI Specifications developed by the IVI Foundation provide standardized APIs for programming test instruments.

The main advantage of using the ivi package is not having to learn the SCPI commands for each individual piece of test equipment. For instance, both the Agilent 33220A function generator and the Stanford Research Systems DS345 function generator can be programmed using one standard API with IVI.

The Prologix GPIB controller strips all unescaped LF (\n, ASCII 10), CR (\r, ASCII 13), ESC (ASCII 27), and + (ASCII 43) characters. Therefore, to send binary data including one of those characters, they must be escaped.

• Read(p []byte) (n int, err error) — Use for reading binary or text data from the instrument or Prologix controller.
• Write(p []byte) (n int, err error) — Use to send binary data to the instrument. The CR, LF, ESC, and + characters will be automatically escaped.
• WriteString(s string) (n int, err error — Use to send ASCII data to the instrument or commands to the Prologix controller.
• Command(format string, a ...interface{}) error — Use to send a SCPI command to the instrument that has no response. A newline character will automatically be appended to the SCPI command sent to the instrument.
• Query(cmd string) (string, error) — Use to send a SCPI query command to the instrument and receive a string response. A newline character will automatically be appended to the SCPI command sent to the instrument. If the Prologix controller is not in auto read-after-write mode, then a ++read eos will also be sent before reading.

The GPIB-USB controller communicates with a computer either directly using the D2XX driver or as a Virtual COM Port (VCP) using the FTDI FT245R driver.

The appropriate VCP driver for your operating system can be downloaded from the FTDI VCP Drivers webpage. Alternatively, on macOS you can use Homebrew to install the VCP driver as follows:

$ brew cask install ftdi-vcp-driver

The appropriate D2XX Direct Driver for your operating system can be downloaded from the FTDI D2XX Direct Drivers webpage. Alternatively, on macOS you can use Homebrew to install the D2XX direct driver as follows:

$ brew install libftdi

To contribute, please fork the repository, create a feature branch, and then submit a pull request.

prologix is released under the MIT license. Please see the LICENSE.txt file for more information.