Integration notes

JP150PCB 1.3PCB 1.42026-11-02Jan PřibyslavskýThis page does not apply to the product or PCB revision chosen in the header.

Behaviour of firmware 26.10.1 that host software must handle. The protocol page has the general rules; Changes by release lists, for every release, the commands added and removed and the behaviour changes, generated from the firmware's command tables.

Matching answers

Answers carry the command as their prefix (AMP:VOL:32), and several commands are prefixes of longer ones: SYS:INPUT of SYS:INPUT:ENABLE, SYS:TRIG? of SYS:TRIG:MODE?, BT:TWS:PAIR of BT:TWS:PAIR:START, SYS:BOOTLOADER of SYS:BOOTLOADER:INFO?, SYS:NVM:EEPROM:STATE? of SYS:NVM:EEPROM:PENDING?, BT:TWS:SCAN? of BT:TWS:SCAN:COUNT?. A matcher that pairs answers with requests by prefix must match the whole prefix up to the value, and must know that some setters answer with the prefix of their query (SYS:INPUT:OK). Answers marked extensible in the reference (SYS:BOOTLOADER:INFO?, SYS:NVM:EEPROM:PENDING?) may grow by fields at the end: read the fields you know and ignore the rest.

A command the firmware does not know draws no answer at all. On a module whose board the firmware does not support, every command outside the reduced set answers the line ERR:BOARD:UNSUPPORTED without a prefix; the reduced set is marked in the command reference.

Timing

The control interface runs the commands in order, and a few of them hold it for a while:

Command	Holds the interface for
SYS:POWER:MODE NORMAL from PWRSTAGE_OFF, SLEEP or STANDBY	about 350 ms plus the power-stage initialisation
AMPx:FAULT:RECOVER	the 5 ms reset pulse
BT:TWS:PAIR	up to 15 s (use BT:TWS:PAIR:START and poll BT:TWS:PAIR:STATUS?)
BT:TWS:PAIR:START	about 0.7 s
BT:TWS:PEERLIST?, BT:AT	the module's settle time, 0.5 s for BT:AT
SYS:NVM:DEFAULTS	up to about 2.2 s, then the module restarts 500 ms after the answer
SYS:NVM:FLASH:SAVE, SYS:NVM:FLASH:ERASE	1 to 2 s when a flash sector is erased
DSP:FLASH:ERASE, DSP:FLASH:CRC?	up to 8 s per 64 KB erased; about 16 s per MB checked
*RST, SYS:BOOTLOADER	the answer comes first; the restart follows within about 1 s

A host allows for these in its timeouts rather than treating them as a lost connection.

Stored settings

The settings-memory layout changed from version 3 to version 6 in 26.10.1. On the first start of 26.10.1 the stored settings are rebuilt once (SYS:NVM:EEPROM:STATE? answers NODATA on that start, OK from the next one): the input enable mask returns to all inputs enabled, the automatic power-down to its defaults (off, 1800 s, PWRSTAGE_OFF, threshold 5), the DSP self boot to on and the 12 V trigger to OFF / SLEEP / priority 1. Master volume, channel volumes, the selected input and the TWS fallback role are kept.

The autosave writes a setting once it has stayed unchanged for its debounce: 0.1 s for the self boot and the trigger settings, 1 s for the input enable flags and the fallback role, 2 s for the input, 3 s for the volumes, 5 s for the automatic power-down settings. SYS:NVM:EEPROM:PENDING? answers 1 while a write is outstanding; *RST and SYS:BOOTLOADER write pending settings first.

SYS:NVM:DEFAULTS returns the user settings to their defaults and restarts the module: the volumes, the input enable mask, the automatic power-down settings, the DSP self boot and the three trigger settings. The selected input, the TWS fallback role, the board identity, the Bluetooth and Wi-Fi pairings and the DSP program are kept. The answer can take about 2 s; the module restarts 500 ms after it.

Finding the module

The firmware's virtual COM port enumerates under USB 16D0:15B8 (firmware before 26.10.1: 0483:5741) and the bootloader's update mode under 16D0:15B7. UART1 runs at 115200 8N1 and serves the same commands. *IDN? identifies a module; SYS:BOARD:TYPE? tells whether the board is supported.