Current version

M4 (Milestone Four)

Status

Completed, ready for production

File repository

https://github.com/eez-open/psu-firmware/tree/master/doc

License

CC BY-SA 4.0

Contributions

C4.1 (Collective Code Construction Contract)

 

This manual contains reference information for programming open hardware/open source EEZ programmable PSU (Power Supply Unit) over the remote interface using the SCPI programming language.

The SCPI (Standard Commands for Programmable Instruments, often pronounced “skippy”) is an open standard freely available on the IVI Foundation web pages. Current version is SCPI 1999.0.

SCPI is pure software standard and SCPI syntax is ASCII text, and therefore can be attached to any computer language, such as C, C++, etc.

 

The physical communications link is not defined by SCPI. While originally created for IEEE 488 (GPIB), it can also be used with RS-232, Ethernet, USB, VXIbus, HiSLIP, etc. The EEZ PSU supports Serial (via USB) and Ethernet communication.

Application software that use SCPI commands is called Controller and SCPI enabled device such as PSU is called Instrument.

 

Please note that IEEE 488 standard documents are still not freely available, and if it is mentioned in this manual that is solely for reference purposes for one who wants to conduct a further research for better understanding or possible modification/improvement of the PSU remote control.

1.1. About SCPI

SCPI 1999.0 standard document says (Section 1.3) that the goal of SCPI is to reduce Automatic Test Equipment (ATE) program development time. SCPI accomplishes this goal by providing a consistent programming environment for instrument control and data usage. This consistent programming environment is achieved by the use of defined program messages, instrument responses, and data formats across all SCPI instruments, regardless of manufacturer.

A consistent program environment uses the same commands and parameters to control instruments that have the same functionality.

SCPI programming consistency is both vertical and horizontal. Vertical programming consistency defines program messages within an instrument class. An example of vertical consistency is using the same command for reading DC voltage from several different multimeters. Horizontal consistency is using the same command to control similar functions across instrument classes. For example, the trigger command would be the same for an identical trigger function found among counters, oscilloscopes, function generators, etc.

A key to consistent programming is the reduction of multiple ways to control similar instrument functions. The philosophy of SCPI is for the same instrument functions to be controlled by the same SCPI commands. To simplify learning, SCPI uses industry-standard names and terms that are manufacturer and customer supported.

SCPI is designed to be expanded with new defined commands in the future without causing programming problems. As new instruments are introduced, the intent is to maintain program compatibility with existing SCPI instruments.

 

 

Additional links:

Implementation links:

 

 

Files:
SCPI reference guide M4 HOT UPDATED

This manual contains reference information for programming open hardware/open source EEZ bench power supply over the remote interface using the SCPI programming language.

License CC BY-SA 4.0 Author This email address is being protected from spambots. You need JavaScript enabled to view it. Website Website Date Tuesday, 29 December 2015 15:14 Language  English File Size 1.15 MB Download 675 Download

 

Joomla templates by a4joomla