-
Notifications
You must be signed in to change notification settings - Fork 146
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
Link to Aircraft : Not Linking #442
Comments
Agent comment from SHENRONG.LE in Zendesk ticket #121467: What are the instructions being executed? What does a link mean? Thank you for your email and have a nice life! °°° |
According to the Logcat this is the error: |
Agent comment from SHENRONG.LE in Zendesk ticket #121467: The information you provided did not pinpoint the problem,
Thank you for your email and have a nice life! °°° |
This occurs once the sample app opens. It shows Registration Status: Registered but it can not seem to connect to my aircraft (Mavic 3T). I get this same CORE error on the landing dashboard, the Widget List --> RC Pairing Widget and the Default Layout --> Link to Aircraft . I ensure the Remote controller does connect correctly to the Mavic 3T and the firmware has been fully updated |
Agent comment from SHENRONG.LE in Zendesk ticket #121467: Is your app on the remote? Thank you for your understanding and support, I wish you a happy life! °°° |
The app is on a Pixel 7. It ran successfully and opens on the phone it just does not connect to Aircraft. |
Agent comment from SHENRONG.LE in Zendesk ticket #121467: You need to run it on the remote, otherwise you won't be able to connect to the drone Thank you for your understanding and support, I wish you a happy life! °°° |
I am Using the 5.11.0 release of the sample MSDK. I have the app successfully running on a Google Pixel 7. I am attempting to Link to a Mavic 3T. However, when I click to link I get the error "ErrorImp{error Type='CORE', errorCod.." I dont see the rest of the error and I do not know how to try to troubleshoot this error.
The text was updated successfully, but these errors were encountered: