Test controller, GPIB and Modbus interfaces

This page is used to configure GPIB interfaces and Modbus interfaces (RS485 adapters). The GPIB interfaces are not standardized and a specific brand/model must be selected. For modbus a RS485 adapter is used and they are fairly standard.
Contents
What is on the screen
How to use a interface
Notes on interfaces
AR488
AR488Lan
Kofen
Prologix USB
Prologix Ethernet
National instruments GPIB-232CR
Modbus
Main page
What is on the screen

The table has a line for each interface:
- Type is the name from the "Add interface" combobox and each one represent one interface
- Id is the id used to reference this interface in the "Load devices" page, it is recommended to use a single letter.
- Connection is the way the interface communicate with the computer, either socket (Network) or serial.
- Address is the actual address used to communicate with the interface, either a ip address or a serial port.
- Baudrate is only used for serial port and specifies the baudrate for the interface or for the full bus when using modbus.
- Settings are specific settings for the interface, these are interface specific, use ; between settings.
Add is used to add new interfaces, select a name in the combobox and press the Add button to add it to the table.
Remove is used to remove interfaces from the table, click on the line to remove (i.e. select it) and press the remove button.
How to use a interface
Interfaces are used on the "Load devices" page.

The interface type must be either GPIB or Modbus to use them, it may often be necessary to click on the device type and select that interface.

To reference a specific interface use the id letter in the address column, followed by a colon and the local bus address
Notes on interfaces
AR488
A DIY interface that is basically a Arduino processor and a GPIB connector with very little extra.
It is sometimes possible to find premade versions of it.
https://github.com/Twilight-Logic/AR488
Elements from setting is copied to the interface at startup with ++ before each of them.
AR488Lan
The same, but assumes the Arduino uses lan interface.
Elements from setting is copied to the interface at startup with ++ before each of them.
Except a elements called "Port=" will be taken as a request to the driver to use the specified port on the interface.
For this interface it is very likely a "port=" setting will be used to specify the actual port used by the adapter.
Kofen
A implementation of the AR488 with a lan interface.
https://www.eevblog.com/forum/projects/poe-ethernet-gpib-adapter-open-source-project-now-public
https://github.com/Kofen/PoE_Ethernet_GPIB_Adapter
Elements from setting is copied to the interface at startup with ++ before each of them.
Except a elements called "Port=" will be taken as a request to the driver to use the specified port.
Prologix USB
A professional GPIB adapter and rather expensive.
https://prologix.biz/
Elements from setting is copied to the interface at startup with ++ before each of them.
Prologix Ethernet
A professional GPIB adapter and rather expensive.
https://prologix.biz/
Elements from setting is copied to the interface at startup with ++ before each of them.
National instruments GPIB-232CR
A old serial interface GPIB adapter from National instruments.
Elements from setting is copied to the interface at startup.
Modbus

This is basically any RS485 adapter, they can either be used directly as a serial port that connect to one modbus device at modbus address 1 or with this interface to connect to multiple devices.
Having multiple devices on one modbus will reduce the max sample rate TC can do, because each device must communicate in sequence, not all devices in parallel (As TC usually does).
When used with one device it makes it possible to access this device at any modbus address.
Settings are not used.