The miniSMU MS01 uses a command-based interface for operation, following SCPI (Standard Commands for Programmable Instruments) conventions. This section explains the command structure and provides an overview of the available commands.

Command Syntax Overview

Commands are sent to the device through the software interface. The general structure of commands follows this pattern: COMMAND[:SUBCOMMAND] [PARAMETER]

For queries that request information from the device, append a question mark to the command: COMMAND[:SUBCOMMAND]?

Command Structure Elements

Common Command Reference

The following table provides a reference for the most frequently used commands:

System Commands

System commands control device-wide settings and status:

Source and Output Commands

These commands control the output settings for each channel. Replace x with the channel number (1 or 2):

Measurement Commands

These commands perform measurements. Replace x with the channel number (1 or 2):

Data Streaming Commands

For continuous data acquisition:

Data is sent in batches with a CSV format with the following structure:

1,1751313180797,3.713e-02,-7.441e-10,0

Data Format Fields

Command Separators and Terminators

• Commands are typically terminated with a newline character \n
• Command responses are typically terminated with a newline character

Command Execution Notes

• Commands are executed in sequence as received
• Some commands may take time to complete (e.g., WiFi scanning)
• Setting commands generally respond with OK as an acknowledgment
• Query commands will always return a response

Error Messages

If a command encounters an error, the device may return an error message:

• Syntax errors (SOUR:VOLT example): Invalid SOUR:VOLT command
• Unknown command: Invalid input format

Software Interface

While you can use these commands directly in advanced programming scenarios, the miniSMU software provides a graphical interface that issues these commands behind the scenes. The software interface includes:

• Input fields for setting voltage and current values
• Buttons for enabling/disabling outputs
• Displays for measurement readings
• Configuration panels for protection settings
• Data visualisation for streaming measurements

Understanding the command structure is particularly valuable when:

• Creating automated test sequences
• Developing custom software interfaces
• Troubleshooting device behavior
• Performing advanced operations not covered in the basic software interface

The next sections will cover more specific operations using these commands, including device identification, configuring outputs, and performing measurements.