Pulse width calibration check for sensors

Pulse width calibration check for sensors

This document provides instructions for verifying whether a sensor received pulse width calibration at the factory.

  • Note that pulse width calibration is applicable only to sensors of revision Rev7 or higher. This calibration feature was initially implemented with the release of firmware FW3.1.

What does pulse width calibration affect:

  • Signal value uplift from non-calibrated sensors

  • Calibrated Reflectivity (cal-ref) value uplift from non-calibrated sensors

  • More accurate distance measurement to retroreflectors

  • Improved blooming performance (false positive and false negative)

 Instructions

UPDATED: Easy method, just go to http://analytics:5001/sensor_report/ and select Pulse Width Cal.

image-20251002-183023.png
  1. Install MySQL Workbench

  2. Set up MySQL Workbench profile

    • Click on the. “+” icon

    • Fill in the following information

If you do not have the shared password on lastpass, please contact @Krishtof Korda

  1. Accessing the database

    • Click on the created profile

You need to be connected to VPN (Global protect; Default profile)

  1. Setting default database (Schema) for query

    • Right click “Otter2” and “set as default Schema”

    • This step only needs to be done once, next time you fire up the program, you can directly start query.

  2. Query for Pulse width calibration results

    • Paste the command below into line 1 and click on the lightning bolt icon

    • select * from pulse_width_calibration_results where serial_number = "122450000149"
  3. Understanding Query results

    • Location ID

      • 12 - San Francisco

      • 99 - Thailand

    • recipe_id

      • values that sensors are calibrated to

      • as of May 12, 2025, it is observed to be “5”

    • mfg_version

      • Python code that was used for pulse_width_calibration

*Other information in the results are self explanatory.

TBC, if “recipe_id” stays the same, signal and CalRef should be consistent between compared sensors.

 

Troubleshooting: