SCPI Parser library aims to provide parsing ability of SCPI commands on instrument side. All commands are defined by its patterns eg: "STATus:QUEStionable:EVENt?".
Source codes are published with open source Simplified BSD license.
SCPI parser library is based on these standards
- SCPI-99
- IEEE 488.2-2004
Download source package or clone repository
- v2.1 - https://github.com/j123b567/scpi-parser/archive/v2.1.zip
- v2.0 - https://github.com/j123b567/scpi-parser/archive/v2.0.zip
- v1.2 - https://github.com/j123b567/scpi-parser/archive/v1.2.zip
- latest - https://github.com/j123b567/scpi-parser/archive/master.zip
- git clone https://github.com/j123b567/scpi-parser.git
Library is in folder libscpi and you can use it directly in your embedded project.
You can try to make examples so just run make.
In folder examples there are several examples using console or TCP connection to emulate SCPI instrument.
Version v2.0 2015-01-18
- better AVR support
- implementation of traversal of header tree - it is possible to write CONF:VOLT:DC 1; AC 2 instead of CONF:VOLT:DC 1; CONF:VOLT:AC 2
- resolve issue with multiple commands with result separated by ;
- add support for Multiple Identical Capabilities - e.g. OUT:FREQ, OUT2:FREQ by pattern OUTput#:FREQuency
Version v2.0_beta1 2015-01-18
- parsing more compliant with SCPI-1999
- support all parameter types defined in the spec - separate them and identifie them
- support for Arbitrary program data
- support for tagging command patterns (useful for common handler)
- support for extending any parameter type using SCPI_Parameter
- general support for number or text value (e.g. 1, 6, DEF, INF) not limited to one array of special numbers
- support for optional command headers (Richard.hmm)
Version v1.0 released 2013-06-24
- support basic command pattern matching (no optional keywoards)
- support basic data types (no expressions, no nondecimal numbers, no arbitrary program data, ...)
- last version before refactoring of the parser and before extending parameter handling
Command pattern is defined by well known representation from SCPI instruments. Pattern is case insensitive but uses lower and upper case letters to show short and long form of the command.
Pattern "SYSTem" matches strings "SYST", "syst", "SyStEm", "system", ...
Command pattern is devided by colon ":" to show command hierarchy
Pattern "SYSTem:VERsion?" mathes strings "SYST:version?", "system:ver?", "SYST:VER?", ...
SCPI standard also uses brackets "[]" to define unnecesery parts of command.
Pattern "SYSTem:ERRor[:NEXT]?" matches strings "SYST:ERR?", "system:err?" and also "system:error:next?", ...
Command callbac is defined as function with context parameter, e.g.:
int DMM_MeasureVoltageDcQ(scpi_context_t * context)
The "Q" at the end of the function name indicates, that this function is Query function (command with "?").
The command callback can use predefined function to parse input parameters and to write output.
Reading input parameter is done by functions SCPI_ParamInt, SCPI_ParamDouble, SCPI_ParamString, SCPI_ParamNumber, SCPI_ParamArbitraryBlock, SCPI_ParamCopyText, SCPI_ParamBool and SCPI_ParamChoice
Writing output is done by functions SCPI_ResultInt, SCPI_ResultDouble, SCPI_ResultString, SCPI_ResultText. You can write multiple output variables. They are automaticcaly separated by coma ",".
Source codes are devided into few files to provide better portability to other systems.
libscpi/test/ - Unit test for the library
examples/test-parser - is the basic non-interactive demo of the parser
