IMU Calibration Parameters
Status Reads
Timing
BLE Link
Other
Logging
Logged Data Transfer
Advanced
Flash Lookup Entries
| Bank | Status | Payload Index | EEPROM Pending | CRC Check |
|---|---|---|---|---|
| Run Read Flash Lookup Table to populate. | ||||
Read/Write
Factory Defaults
Production Fields
Production Config Bytes
Read/Write
Operational Config Presets
Sensor Enables
Other sensor enables (not on this hardware model)
Notes
All Operational Config Options
Operational Config Bytes
Streaming Control
Live Stream Stats
| Stream | Achieved Hz | Config Hz | kB/s | Samples | Lost | Loss % |
|---|---|---|---|---|---|---|
| No stream data yet. | ||||||
Algorithm Hub Metrics (live)
Ambient Light Plot (VD6283)
Illuminance Plot (lux, derived)
Colour Temperature Plot (CCT K, derived)
Raw PPG Plot (MAX86176 via hub: green/red/IR)
Skin Temperature Plot (MLX90632)
Ambient Temperature Plot (MLX90632)
Accel 1 Plot
Accel 2 Plot
Gyro Plot
Magnetometer Plot
GSR Plot
PPG Plot
Battery Voltage Plot
DFU Flow
Enables the Nordic DFU service, then automatically cycles the BLE link and reconnects to the same device (no need to re-select it) so the service becomes active. The device does not reboot yet. Skip this if the badge already shows “Active” — and skip it entirely when updating over USB: the USB pathway has no BLE service to enable (the badge still reports the device-level state).
Required on both pathways. Over BLE: after reconnecting with the Nordic DFU service active (Step 1), the buttonless DFU command reboots directly into bootloader mode. Over USB: reboots straight into the bootloader with no Step 1 needed — the sensor reappears as its own USB device (“Verisense-DFU-XXXX”).
Select a firmware .zip package, then click
Begin Update via BLE or
Begin Update via USB to match how the
sensor is reachable. A browser picker opens (Bluetooth
scanner or serial-port list) and the transfer runs against
the bootloader.
Which package do I need?
-
Sensor on V1.x firmware (original
release): use the combined
…_SD_BL_APP.ziponce, over BLE — it upgrades the SoftDevice, the BLE-only bootloader and the application together. After that the sensor is on V2.x and takes application-only packages. (No package upgrades a sensor to the BLE+USB bootloader — that is factory-installed only.) -
Sensor on V2.x or later: always use the
application-only
ASM_IMU_FW_Vx.xx.xxx.zip. The combined package is never needed twice — an up-to-date sensor rejects it with a version error (this is safe and changes nothing on the sensor). - BLE or USB? The same application-only package works over both. USB DFU requires the BLE+USB bootloader, which is factory-installed on newer units and cannot be added over the air — if the USB reboot in Step 2 is refused, update over BLE instead.
Event Log Reader
Event Log Entries
| # | Event ID | Event Name | Timestamp | Battery (mV) |
|---|---|---|---|---|
| Run Read Event Log to populate. | ||||
Test Report
Runs TEST_REPORT (0xFE) on the device. The device sends a rolling text report delimited by the TEST START banner. PASS and FAIL results are highlighted.
Sheet upload settings
A completed report is parsed into named metrics and posted to a write-only endpoint, which appends one row per test to a private spreadsheet (one tab per manufacturing order). Reports run from anywhere other than the deployed console are routed to a DEV tab. Failed uploads are queued here and retried automatically.
Algorithm Hub Firmware (MAX32670)
Factory use. Streams a MAX32670 algorithm-hub
.msbl image to the device and flashes it into the hub
via the Maxim bootloader. This erases and reflashes
the hub and takes ~1–2 minutes; keep the device connected and
still. Only SR68 Pulse+ hardware accepts it — other boards reply
NACK. Run the Test Report first; flash if the MAX32674C line
(WS_TEST_0011 on firmware > 2.00.009; WS_TEST_0010 on older
firmware) reports the hub stuck in bootloader.