Ouster Diagnostic Companion / Public-source demonstration
LiDAR connects, but no point cloud.
An Ouster OS1 Rev7 bench diagnostic guide for field-service and software-integration teams.
This original decision sequence reorganizes public Ouster guidance. It is not an official manufacturer diagnostic procedure or a robot return-to-service test.
Use the hardware, supplied power, and interface-box configuration defined in the companion procedure. Keep the robot out of scope. Do not open the sensor or change operational-system configuration.
1. Establish the symptom
- Record the sensor serial number, firmware, SDK version, host interface, and exact failure.
- Check the interface-box VIN indication.
- Open the sensor dashboard at
http://os-<serial-number>.local/. - Confirm that the displayed identity matches the intended sensor.
No: Follow the companion procedure's power and host-network checks. Record the result before changing settings.
Yes: Continue below. Dashboard access proves web connectivity, not UDP data reception.
2. Preserve the configuration
- Record the UDP destination and LiDAR data port.
- Record active alerts from Diagnostics.
- Confirm authorization to redirect data to the bench host.
The SDK visualizer automatically sets the UDP destination while retaining the configured LiDAR port. Do not run it against an operational robot sensor without the system owner's approval.
3. Start the receiver
Replace the hostname placeholder with the actual serial-number hostname or IP address:
ouster-cli source os-<serial-number>.local vizYes: Perform the qualitative live-scene check in the companion procedure. Recheck Diagnostics and record remaining alerts.
No: Compare the configured UDP destination and LiDAR port with the receiving host. Follow Ouster's OS-specific networking guide; ask the network owner to review firewall rules.
4. Interpret the evidence
A UDP_TRANSMISSION alert may occur when the host is not yet listening. Recheck after starting the receiver. Preserve the complete alert ID and message; the name alone is not enough to identify its cause.
For a persistent thermal or internal fault, stop the check and escalate. Do not bypass thermal protections, open the sensor, or introduce an unapproved firmware update.
5. Handoff or escalate
Attach the symptom, equipment identity, software versions, relevant network settings, full alert details, diagnostics download, and checks already performed. Record configuration changes and restore the owner-approved settings before handoff.
A successful point-cloud display does not establish range accuracy, sensor alignment, calibration, or safe autonomous operation.
Manufacturer sources
- Quick Start Guide: dashboard and diagnostics
- SDK Visualize: command and configuration effect
- Alerts and Errors: UDP and internal faults
- Host Networking
The companion PDF covers a bench connection and live-data check, not robot installation or calibration.
All writing samples