Skip to content

CRASH_LOG_STRING

Jump to bottom
theficus edited this page Dec 23, 2021 · 8 revisions

One or more CRASH_LOG_STRING messages are sent when a ROBOT_POSE command of GET_DEBUG_LOG (0x4) is submitted. When there are no more debug log messages, a CRASH_LOG_FINISH message is sent.

The first byte (0x60) is the message type while the remaining bytes are null-terminated ASCII-encoded text.

CRASH_LOG_STRING structure

Byte(s) Data Type Value Note
1 Byte Always 0x60
2-20 char ASCII log text (null terminated)

Example (No crash log.)

0x604e6f206372617368206c6f672e000000000000

Known debug text

Extracted from firmware via strings command:

  • No Error
  • Calibration Warning Error
  • Min clipped error
  • Undefined error
  • Invalid parameters error
  • Not supported error
  • Interrupt not Cleared
  • Range error
  • Time out error
  • Mode not supported error
  • Buffer too small
  • GPIO not existing
  • GPIO funct not supported
  • Control Interface Error
  • Invalid Command Error
  • Division by zero Error
  • Reference Spad Init Error
  • Not implemented error
  • Unknown Error Code

This project is not approved or endorsed by Petronics. Any information here is provided as-is with no warranty or guarantees.

Clone this wiki locally