asyn-gpib

What problem does it solve?

It helps EPICS developers write correct GPIB/SCPI instrument device support so records can reliably send commands and parse responses through the asyn devGpib framework.

Core Features & Use Cases

• Build devGpib-based device support: define DSET macros, implement init_ai, and wire a command table (gpibCmd[]) to EPICS record types.
• Map EPICS records to instrument commands: use gpibCmds[] entries with scanf/printf format strings and optional custom convert routines.
• Use EFAST enum mapping: define EFAST input/output tables (e.g., GPIBEFASTI, GPIBEFASTO) to translate between human-readable strings and instrument responses.
• Create DBD and database integration: provide DBD device declarations (*.dbd) and database records using the GPIB_IO link format with zero-based parameter indices.
• Handle gateway setups: configure VXI-11/LAN-to-GPIB gateways (e.g., vxi11Configure) when the instrument is not directly connected.

Quick Start

Ask the AI to generate a complete devGpib device support skeleton for your instrument by listing the EPICS record types you need, the SCPI/GPIB commands to use for each parameter, and any enumerations that should be handled via EFAST.