dji-dev
commented
3 years ago Agent comment from DJI SDK in Zendesk ticket #56188:
尊敬的开发者，感谢您联系DJI 大疆创新
由于github不是我们主要的咨询渠道，您的问题可能跟进不及时。我们建议您通过填写表单（ https://djisdksupport.zendesk.com/hc/zh-cn/requests/new ）向我们反馈问题。或者您也可以在论坛发帖，与其它开发者交流。论坛链接：https://djisdksupport.zendesk.com/hc/zh-cn/community/topics
Dear developer, thank you for contacting DJI.
Since github is not our main consultation channel, your questions may not be followed up in time. We recommend that you fill in the form (https://djisdksupport.zendesk.com/hc/en-us/requests/new) to report problems to us. Or you can post in the forum to communicate with other developers. Forum link: https://djisdksupport.zendesk.com/hc/zh-cn/community/topics
°°°
IuliuNovac
Hi,
We have a M300 with the H20T camera, where we calibrated the RGB data from the images from OSDK with the Telemetry obtained from the OSDK. There is a significant deviation and inconsistency between the calibrated telemetry data and raw telemetry. The major issue is the rotation in Yaw. We have conducted the calibration as follows: We gathered telemetry data, then generated three sets of datasets for latitude, longitude, altitude , roll, pitch and Yaw. The only variation was the Yaw, where the first one is yaw of the gimbal, second is yaw of the gimbal minus drone yaw,third is the gimbal yaw plus drone yaw. Afterwords we used the said datasets with identical images and calibrated in Pix4d. The results show almost identical values for latitude, longitude, altitude , roll, pitch and yaw for all three calibration. But the issue is that they vary quite a bit from the input yaw, where gimbal yaw alone has the least standard deviation.
The data is combined in a excel file, where you can see the deviation. Moreover, there doesn't seem to be a deviation in time-step between the pictures and the telemetry CalibrationPix4dcomparison.xlsx .