18 Troubleshooting
The sensor HTTP server page http://os1-991900123456.local/ has Dashboard, Diagnostics, Documenta-
tion and Reset Configuration buttons:
Dashboard: Current page that lists some basic sensor information, and allows sensor firmware
upgrade.
Diagnostics: Diagnostic information and system journal that can be downloaded and included
whencontacting Ousterforservice.
Documentation: SensorUser Guide
Reset Configuration: Sensor factoryconfiguration thatcan beresetto ifdesired. Thiswill erase
anycustomconfigurationthat youset onthe sensorpreviously.
Many initial problems with the OS1are associated with the sensornot properly being assigned an IP
address by a network switch or DHCP server on a client computer. Check your networking settings,
the stepsin Section 5, and that all wires arefirmly connected if yoususpect this problem. Note that
if the sensor is not connected via gigabit Ethernet, it will stop sending data and will output an error
codeif itfails toachievea 1000Mb/s+full duplexlink.
To checkforhardwareerrors,use theget_alerts commandasdescribed inTheTCPAPIGuide.
If the watchdog is triggered (when various temperature limits are exceeded or uplink/downlink has
failed), an alert code will be appended to the end of TCP command get_alerts. The sensor has a
limited-sizebufferthatwill recordthe firstfewalertsdetectedby thesensor.
Thealertsreportedhavethefollowingformat:
{
"category": "Category of the alert: e.g. OVERTEMP, UDP_TRANSMISSION",
"level": "Level of alert: e.g. NOTICE, WARNING, ERROR",
"realtime": "The timestamp of the alert in nanoseconds",
"active": "Whether the alert is active or not: <true/false>",
"msg": "A description of the alert",
"cursor": "The sequential number of the alert, starting from 0 counting up",
"id": "The hexadecimal identification code of the alert: e.g. 0x01000017",
"msg_verbose": "Any additional verbose description that the alert may present"
}
Example showing active and logged forced temperature sensor failures occuring at timestamps
1569712873477772800, 1569712879991844096, 1569712884968876544 (nanoseconds). The first
loggederrorthen resolvesitselfat 1569713260229536000. The examplehas beenJSONformatted:
{
"active": [
{
"category": "OVERTEMP",
"level": "ERROR",
"realtime": "1569712879991844096",
"active": true,
(continuesonnext page)
53
To Next Page
Loading...
