Serial Terminal
The Serial Terminal panel has two sections: a UDP log monitor (always visible) and an optional serial monitor. It is the primary interface for sending raw commands to the device and reading its responses.
UDP Log Monitor (top section)
Displays the text the device sends on port 55153:
- Replies to commands you send:
OK <COMMAND> …orERR <COMMAND> <reason>lines, and the data lines of read commands (e.g.STATUS,FLAG TAKE 1) - Events (
EVT …): headstage connected or lost, settings changed, board taken over… - Output from
sayandlog variableblocks running on the device - Spontaneous status messages and error notifications
The app's own background requests (for example the periodic state read) are not shown here, so the terminal only shows what you asked for and what the board says on its own.
| Control | Description |
|---|---|
| Clear button | Empties the log display |
| Command input | Type any UDP command and press Enter or click Send to dispatch it to port 55152 (a leading #<n> correlation id is repeated in the reply) |
| ↑ / ↓ arrow keys | Navigate through command history (up to 200 previous commands) |
Serial Monitor (bottom section, collapsible)
Monitors a USB serial port connected to the device, if applicable.
| Control | Description |
|---|---|
| Port selector | Lists available serial ports |
| Baud rate | Enter the desired baud rate (e.g. 115200) |
| Open / Close | Connect or disconnect from the port |
| Clear | Clear the serial display |
Telemetry Plotter
If the device sends lines matching the format time <name> (<unit>): <v1> <v2> ..., the terminal automatically parses them as time series. A Plot button appears when telemetry data is detected. Clicking it opens a modal with:
- A chart with a time axis
- Variable selector and per-series checkboxes
- Y-axis scaling
Replay Mode
In replay mode, the terminal displays "Terminal unavailable in replay" — commands cannot be sent during playback.
Tips
- Use the terminal to test commands interactively before encoding them in a Studio program.
- The command history makes it easy to run the same sequence repeatedly.
- Watch for
VM_*error messages — they appear here when a Studio program crashes.