Skip to content
Rob Carruthers edited this page Aug 23, 2023 · 30 revisions

Welcome to the lxi-tools wiki!

Supported devices

Any LXI certified or compatible device should work with lxi-tools. For reports of successfully tested devices, please refer to the tested instruments list.

Background information

LXI is a standard for the programming of test instruments across ethernet.

In practice, this consists of device discovery, querying and programming.

In lxi-tools discovery occurs via liblxi which can use either MDNS (preferred and faster method; reference implementation; in the market since 2008) or the older VXI-11 (2000) protocol.

Querying and programming occur over various carrier protocols (such as raw TCP, VXI-11 (including vendor-specific "derivatives" like RSIB) or — rarely used and not yet supportedHiSLIP) that encapsulate SCPI, a relatively ill-defined family of simple text-based protocols with very poor standardization across vendors (see SCPI-1999 specification). Areas where vendors tend to differ include fundamental areas such as channel specification, device modes and channel states.

Note that while SCPI was historically often used across alternate (non-ethernet) interfaces, such as IEEE-488.1 (GPIB), RS-232, RS-422, and USB, lxi-tools only supports LXI communication which by definition occurs via ethernet. Ethernet is superior to the alternate buses in that it provides higher signal integrity, supports longer cable runs, is cheaper, is ubiquitous, and LXI being based upon TCP/IP supports global routing so your instruments can be located in other rooms, buildings, cities or countries.

Additional instrument information

Organised by manufacturer and product series.

Fluke

Hameg

Hantek

Keysight

Note: Keysight have a terrible record of refusing to support their equipment.

Rigol

Rohde & Schwarz

Siglent

Undocumented, old or unsupported instruments

If you cannot find documentation on an instrument, you could try the following:

  • Obtain a vendor driver or driver-shim. For example, IVI appears to be some sort of thin windows library API to SCPI translation layer and there is a list of official IVI drivers that may provide clues as to how to obtain commercial driver software for those instruments.
    • Analyse windows driver software directly (for example using strings, a dissassembly or resource extraction tool such as dumpbin /SECTION:.text /DISASM target.dll > strings.txt, or a disassembler)
    • Capture communication between the instrument and commercial driver GUIs or IVI drivers using a tool like Wireshark or tcpdump
  • Analyse device firmware directly, for example using binwalk
  • Analyze similar devices and look for similar command patterns

Should you have success breathing life in to undocumented, old or unsupported instruments, please consider sharing your knowledge in this wiki.