Two OS0-128 LiDARs failed under same setup: no Ethernet link (no LED), earlier 100 Mbps fallback, and motor shutdown — detailed debugging included

[alex_chua]

@Brahmaiah

Could you confirm if you are using an Ouster Interface Box (I-Box) to connect and power the LiDARs, or if you are using a custom cable/power setup?

Given the symptoms you described (especially the Ethernet link degradation from 100 Mbps to complete failure, and the motor stopping), we highly recommend opening a ticket directly with the Ouster Support team so we can formally investigate this.

If you are still able to connect to the sensors (even intermittently), please try to pull the diagnostics file from the web UI and attach it to your support ticket. You can find instructions on how to retrieve that file here:

Troubleshooting with Ouster & Retrieving Diagnostic File

When working with Ouster to troubleshoot sensor issues (usually through support), it’s strongly recommended to send a diagnostic file as well. This file contains information like firmware and alerts from the sensor. This reduces the amount of questions Ouster has to ask the user. How to Retrieve the Diagnostic File: Sensor Webpage Open a browser (e.g. Chrome) and paste in the sensor hostname or IP link local example: os-000000000000.local (replace 0 with the 12 digit serial number) Go to …