ROBOR / INTEGRATION

Check firmware and software versions

Separate released firmware from development builds and first identify what is installed on your device.

Common interface variants

The base model provides USB + RS-232, suffix _1 provides USB + CAN, and _2 provides USB + RS-485. The same rule applies to V2 and V3, with USB common to all variants. Use the manual, pinout and protocol for the selected model.

Record three identifiers

Record the model, installed firmware and PC software versions. A latest-version label in the application does not identify the firmware installed on the device.

Before updating

Confirm the official release matches the model and bootloader. Preserve settings, calibration records and receive logs. Do not use development or pending-validation builds for routine updates.

Check again after reconnecting

Read the connection rate and output selection. Do not assume all streaming settings persist after power cycling. Check model-specific persistence and apply the required output configuration at connection time.

Release-record snapshot

The table reflects a release and firmware/UI source review on 2026-10-20, not completed hardware tests of every device, interface and bootloader combination. Ask support for the official release appropriate for your device.

Experimental features

GuardedVQF is experimental and disabled by default. Its inclusion in a released version does not establish validated field performance. Evaluate it separately from the default filter.

iAHRS-V2

Firmware release
2.1.21
Bootloader in the release record
BL1
Shared PC software
1.21.0
Validation scope
Supports configurable V2_1 CAN node IDs and bit rates. Use the signed application BIN for your device.

iAHRS-V3

Firmware release
3.0.15
Bootloader in the release record
3.0.0
Shared PC software
1.21.0
Validation scope
V3 firmware remains at 3.0.15; do not use the V2 BIN.
Contact ROBORManuals and STEP files