Ouster Firmware 3.2 adds on-sensor 3D zones and synced IMU

The 3D Zone Monitor lets operators define up to 128 zones of any shape and size, with 16 monitored at the same time. Each zone triggers on a configurable point count, frame count and mode, either occupancy or vacancy. The sensor runs the function without extra compute or software. Ouster SDK 0.16.0 and later read and write zone configurations.

A new 8-bit Window data field reports the condition of the optical window. It separates water droplets, low-reflectivity smudges such as mud, and high-reflectivity blockages such as electrical tape, so host systems can trigger a cleaning cycle or a maintenance stop.

For motion compensation, the IMU now samples at 640 Hz and is time-synced with the lidar data, so the host can deskew lidar packets within a single frame. The default is 8 IMU packets per frame, interleaved between lidar packets.

Signal processing also changes. The sensor produces fewer false detections near retroreflective items like road signs and high-visibility vests, and calibrated reflectivity values stay more consistent from near to far.

Integration changes include a redesigned Web UI, an on-device OpenAPI v3.1.1 specification, multicast routing with TTL above 1 and static default gateways.

Support for the legacy TCP command server ends, so integrations must move to the HTTP API. The $ character in HTTP endpoint syntax breaks existing setups for NMEA users.

Why it matters

Ouster supplies lidar sensors, including the OS1, OS2 and OSDome listed in the directory. For teams that use lidar SLAM as a navigation source where satellite signals are unreliable, a time-synced, higher-rate IMU stream reduces deskewing work in the host software.

Window blockage reporting targets platforms operating in rain, mud and dust, where a dirty window otherwise degrades the point cloud without a clear fault.

The removal of the TCP command server needs attention first: integrators with existing control scripts must migrate to the HTTP API before upgrading.