This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OPT3101-SDK: distance issue

Part Number: OPT3101-SDK
Other Parts Discussed in Thread: OPT3101EVM, OPT3101

Hi Team,

Using the OPT3101EVM with the MSP430F5529LP hardware, open the INLAB_step_1 condition in the SDK to compile.

The calibration distance parameters are not modified and default is 10mm, 20mm, 80mm, 120mm. After calibration, there is a problem with the output data distance and the threshold can be exceeded and the actual value is significantly different. The customer would like to know is it expected that the measured distance will vary significantly after this step calibration is performed?

The next calibration steps will allow for proper distance measurement. Fixed at 120 mm from the white object, the output data is as follows:

Could you help check this case? Thanks.

Best Regards,

Cherry

  • Cherry,

    The OPT3101 is ITOF (Indirect Time of Flight) not DTOF (Direct Time of Flight) it is much more accurate and stable method of determining distance because it is not dependent on reflection percentages, colors , ambient light or signal amplitudes that can be inaccurately represented. The I_Phase and Q_Phase creates a phase angle that is used to determine the distance. The I and Q are complex numbers. I and Q Data is a signal representation much more precise than just using a series of samples of the momentary amplitude of the signal.

    Because the distance is calculated from the I/Q phase data and not directly from a timed ping, the calibration will need to be completed. Then compare the distance accuracy and let me know if the customer has a problem.