Desktop appQnbot Studio

Logs & calibration files

Configure Debug recording, manage history logs, and maintain calibration files.

Latest documentation

Logs & calibration files

Debug parameters & logs

Debug locates issues in the device serial port, glove data, calibration, motion retargeting, algorithm output, and buffers. Enable it only when a problem needs to be reproduced, and restore the normal configuration afterwards.

Figure 8-1 Debug parameter configuration

Recording modules

ModuleIdentifierRecommended use
SerialserialDevice discovery, disconnection, serial send/receive anomalies
GlovegloveParsed glove data and input stability
CalibrationcalibrationCalibration steps, results, and reproduction
RetargetingretargetingMapping of hand motion onto the target model
OutputoutputAlgorithm results and model drive output
BufferbufferBacklog, latency, throughput, and data pacing issues

Levels & sampling interval

  • Summary: suitable for routine troubleshooting, balancing information volume and file size.
  • Full: records fuller context for hard-to-reproduce or multi-module correlation issues.
  • Raw: keeps raw-level data and grows fastest; use it only when technical support explicitly requests it.
  • Sampling interval: the example unit on the parameter page is ms. Smaller values record more densely; the exact semantics and valid range are governed by the delivered version.
  1. Select only the modules related to the problem; avoid enabling everything without a purpose.
  2. Choose Summary / Full / Raw and set the sampling interval.
  3. Confirm the save directory; click "Choose" to change the location when necessary.
  4. Click "Confirm" to save the configuration, then reproduce the problem.
  5. After reproducing, stop the task and turn off high-detail Debug.

Figure 8-2 Debug history file list

History file management

  • The list contains the file name, creation time, file size, and actions.
  • Click "Download" to export a diagnostic file; when submitting a support request, also state the problem time, device SN, hand, model name, and reproduction steps.
  • Before clicking "Delete", confirm that the file has been backed up and is no longer needed for analysis.
  • Use the paging control to browse older records; regular cleanup prevents disk space from shrinking continuously.

Data protection: logs may contain device serial numbers, account environment, raw sensor data, or path information. Transfer them only to authorized personnel and follow the project's data retention requirements.

Calibration file management

Figure 9-1 Calibration file list

List fields

  • Device name: the glove model the calibration belongs to.
  • SN: uniquely identifies the device and should match the currently connected device.
  • Hand: the hand that the calibration data belongs to.
  • Calibration time: used to judge whether the record is the most recent.
  • Actions: re-calibrate and delete calibration.

Re-calibration

  1. Locate the record that matches the current device SN and hand.
  2. Click "Re-calibrate". If gesture data already exists, the system prompts for overwrite.
  3. Confirm that the current task has stopped, and click "Confirm overwrite" when the overwrite is really intended.
  4. Repeat the 8-step wizard and verify the result on the simulation page.

Irreversible operation: the system states clearly that re-recording completely overwrites the existing gesture data and cannot be undone. If the project requires keeping history, back up or export it first using the delivery mechanism.

Deleting a calibration

After deletion, the device and hand may no longer obtain the correct motion mapping and must be re-calibrated to recover. Before deleting, verify the device SN and the left/right hand again to avoid deleting records of another operator or another device by mistake.