-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FlightRecord: Altitude resolution, RTK accuracy and samplingRate #27
Comments
Agent comment from xiaorong.zheng in Zendesk ticket #100337:
b. The
|
Thank you for the reply! Regarding 3: (from M300 RTK specs):
|
Agent comment from xiaorong.zheng in Zendesk ticket #100337: °°° |
Thank you for the clarification. Which SDK solution would be most suitable for extracting/storing information with max. speed (>=50Hz)?
In general, I understand that the internal clock runs up to 400 Hz, min. requirement would be 50Hz for the above information (following this article RTK information is only send with 5Hz to a payload sdk) |
Agent comment from xiaorong.zheng in Zendesk ticket #100337: By the way, if you're working with the Payload SDK, you'll be happy to know that subscription frequencies can exceed 50Hz. For a comprehensive walkthrough and exploration, feel free to explore the Payload SDK tutorial resources available at: https://developer.dji.com/doc/payload-sdk-tutorial/en/tutorial-map.html °°° |
Dear DJI Developer Team,
I would like to request some information regarding the following questions:
Is it possible to extract the FlightRecord information with a
samplingRate
faster than 10 Hz? For the Matrice 300, the internal TimeSync should provide most of the included information with at least 50Hz.Can the flightRecord parser extract information
a) Whether the drone was using RTK-Network corrected coordinates to navigate.
b) Whether the stored
"aircraftLocation"
variable uses this more accurate position.Could you provide a fix, so that the
altitude
variable not only contains one decimal place, but uses the available RTK-network corrected altitude which should have an accuracy of around 0.02m and an even better resolution.Best regards and thanks in advance
David
The text was updated successfully, but these errors were encountered: