the Zero-distance calibration of ddfs

RE: the Zero-distance calibration of ddfs

tesc — Tue, 04 Mar 2025 11:50:43 GMT

Hi,

Please create a new ticket for this new question. While it may be somewhat related to the original question, it is better to have it as a new question where it is more easily found by others, and where it will not potentially clutter this thread with back-and-forth on something which was not directly related to the original question.

Regards,
Terje

RE: the Zero-distance calibration of ddfs

Usha — Fri, 28 Feb 2025 06:13:54 GMT

I am measuring the distance between two devices placed 60 cm apart, but the reported distance fluctuates between 0.88 m and 1.43 m. What could be causing this variation, and how can I accurately calibrate the offset?

RE: the Zero-distance calibration of ddfs

tesc — Thu, 18 Jul 2024 10:58:50 GMT

Hi,

There will be an (unknown) offset it the distance estimates, which can be calibrated. The suggestion in the readme file is to place the devices (between which you do the distance calculations) a known distance apart, nominally 60 cm, and perform several distance measurements at that distance. If the average result from those measurements is 64 cm, then that means there is an offset of 4 cm. If the average results from those measurements is 58 cm, then that means there is an offset of 2 cm in the other direction. This offset should be taken into account for all measurements, so for the two example values I listed here, you should subtract 4 (for the 64 cm measurement) or add 2 (for the 58 cm calibration measurement). This offset will depend on the hardware, and the environment may also affect measurements.

Even though the calibration is named "zero-distance calibration", the calibration cannot be done at a distance of 0 cm. That is why the suggestion is to do the calibration at 60 cm, which is near but still not too near. You can then use the same offset regardless of what distance you measure. The offset must be added (or subtracted) on all measurements that you receive from the library. (There is no offset compensation within the library itself.)

Regards,
Terje