You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've integrated the D-RTK module with an M600 and can successfully read and record data onto a Linux-based computer. I purchased the ~$5000 D-RTK module because of it's outstanding sensor specs (2-3cm accuracy), however the OSDK Documentation Appendix says that it saves as a double (as opposed to int32 for regular GPS, which oddly enough, is less accurate) when used with the A3 flight controller! Double only gives four decimal places on the latitude and longitude coordinates, which is +/-10m or so in real life.
How can I change the output so it records into an int32? Alternatively, are the RTK outputs actually stored in the regular GPS variables?
Jeremy
The text was updated successfully, but these errors were encountered:
Double has 15 decimal places. I suppose it is a formatting issue on your side that rounds it down to 4 when converting to a string (printing to stdout, log etc.)
Close this issue now. If you still have more issues related to DJI SDK, please help to fill in this form: https://formcrafts.com/a/dji-developer-feedback-en to report them to DJI Developer Support. Thanks for your understanding and cooperation.
Hello DJI Developers & Community,
I've integrated the D-RTK module with an M600 and can successfully read and record data onto a Linux-based computer. I purchased the ~$5000 D-RTK module because of it's outstanding sensor specs (2-3cm accuracy), however the OSDK Documentation Appendix says that it saves as a double (as opposed to int32 for regular GPS, which oddly enough, is less accurate) when used with the A3 flight controller! Double only gives four decimal places on the latitude and longitude coordinates, which is +/-10m or so in real life.
How can I change the output so it records into an int32? Alternatively, are the RTK outputs actually stored in the regular GPS variables?
Jeremy
The text was updated successfully, but these errors were encountered: