-
Notifications
You must be signed in to change notification settings - Fork 405
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
Mavic Air 2 'Unrecognised response to calibration command JointCoarse request' Error? #178
Comments
I didn't looked into that in detail. There probably is a one-time command to pair the drone with new gimbal. If you'd like to ask a wider audience for it, repair people are usually discussing things in |
Thanks @mefistotelis, think that you're right in there being a command there somewhere, I hope that someone finds it soon because there'll be many Mavic Air 2 gimbal replacements as Xmas draws in, new consumers tend to crash a lot :) |
Same issue with mini, drone is detected com3 and reconnect like flash storage |
I get the following result with Mavic mini. There is gimbal movement with this command. py comm_og_service_tool.py COM4 WM160 GimbalCalib LinearHall as a result, gimbal calibration is not successful. What could be the reason for this? 2. I tried it with a different gimbal frame. Room doesn't work. Which cable enables the movement of the gimbal? thankyou. |
To see it as com3 or com4, you need to open assistant dji mavic 2 as step 1, then close the assistant and you can operate with the command. |
Hey folks, just tried to use this tool with the Mavic Air 2 following gimbal/camera replacement but upon running each of the two commands, I get this error:
You can see the whole process that I used in this video:
https://www.youtube.com/watch?v=6MMpbMhy20Y
While this procedure HAS fixed the wonky yaw (it's now pointing perfectly forwards) there are multiple 'Incorrect gimbal IMU data' and 'camera calibration required, contact DJI' errors and more within the app upon startup.
Any ideas on how to solve this? Happy to jump onto a call with some of the techies to try to troubleshoot if useful!
The text was updated successfully, but these errors were encountered: