Skip to main content
Booster Docs

Log Retrieval

When K1 has issues, follow the steps on this page to retrieve logs and send them to technical support. Logs help locate when the issue occurred, the running state, and related error information.

Privacy and Purpose​

Our company will, without violating any applicable laws and regulations or involving any personal privacy information, collect only data related to the operation of the robots for the purposes of fault detection, problem localization, and statistical analysis.

Upload Logs via App​

  1. After connecting to the robot via the App, go to "Settings".
  2. Tap "Log Upload".
  3. Select the time range to upload, making sure it covers the time when the issue occurred.
  4. The upload takes about 5-10 minutes. During this process, keep the robot powered on and connected to the network. Both the App logs and the robot logs will be uploaded together.
  5. After the upload is complete, contact customer service to report the issue. Our technical staff will retrieve your uploaded log files through the management console.

image.png

img_v3_0213j_2e2f4955-6ddc-476e-91a8-7316c555024g.jpg

Retrieve Logs via Terminal​

Before you start, record the time the issue occurred, the symptoms, and the operation you were performing at the time as accurately as possible. The robot uses the UTC+8 time zone by default; if you are in a different time zone, convert the time before filling in the log time range.

  1. Log in to the robot via terminal.

  2. Confirm the time the issue occurred and prepare the start and end times for the logs. The time format is YYYYMMDD-HHMMSS.

  3. Run the log export command. Common parameters are as follows:

    # -st, --start-time: log start time, format YYYYMMDD-HHMMSS
    # -et, --end-time: log end time, format YYYYMMDD-HHMMSS; defaults to 30000101-000000 if not set
    # -o, --output: output path of the compressed log package
    booster-cli log -st YYYYMMDD-HHMMSS -et YYYYMMDD-HHMMSS -o OUTPUT_PATH

  4. Select a range that covers the time before and after the issue. For example, if the issue occurred around 20200808-120810, you can export logs about 10 seconds before and after:

    booster-cli log -st 20200808-120800 -et 20200808-120820 -o /home/booster/Documents/20200808-120800.zip

  5. On the developer host, copy the log file to your local machine.

    scp booster@192.168.10.102:/home/booster/Documents/20200808-120800.zip ~/Downloads

  6. Send the log package to technical support, along with the symptoms, the time of occurrence, and the reproduction steps.

  7. If overseas users are unable to send log files via a chat tool, you can use WeTransfer to send the log files.

    image.png