Device commands

A command is a single instruction sent directly to a connected device, without the structure of a full protocol. Where a protocol is a measurement recipe that returns scientific data, a command is a quick direct message: check the battery, read the firmware version, wake the device, or send one low-level instruction while setting up.

Open workbooks (opens in a new tab)

What a command cell holds

A command cell carries one instruction in one of three formats:

• String — a raw console command such as hello (the device replies when it is ready) or battery (charge as a percent). This is the common case for MultispeQ.
• JSON — a structured instruction for devices that accept it.
• YAML — the same, written in YAML.

The content is sent to the connected device as-is, so it must be a valid instruction for that device. A command cell is separate from a protocol cell: older mobile apps that only understand protocol cells simply skip command cells and keep working.

When to use a command instead of a protocol

• Confirm a device is connected and responding (hello).
• Read device state such as battery or firmware during setup.
• Send a calibration or spot-reading instruction that a driver supports directly, where a full protocol is unnecessary.

For an actual measurement that produces analysis-ready data, use a protocol. See Writing protocols to author one, and Multi-device measurements for how a command cell can be routed to a specific connected device.