Error Code 1005 after changing batteries
Hello. Looking to get some assistance as this is very important to me and the future of me using dronelink.
I am new to this so today was my first flight. I created a basic mission. everything was going well. 1st I never got any errors/notifcations about low battery, if I have not paused mission myself and flew drone back to check my Inspire 2 would have fallen out of the sky. So thats something else I would like to learn on how to setup because I cannot risk damaging my 7k drone over a $100 app.
Now, after I changed the batteries out I started the drone up again and hit "play" to continue the mission. As soon as my drone gets setup and ready to go I got the gimbal error. I tried several times and same issue. I ever tried to reset the gimbal orientation thinking it would help but no luck. So as of right now, I am limited to only 1 short flight mission otherwise I have to restart which makes large plans useless.
Please help.
Gimbal Orientation Failed: • Please try again by tapping the play button. • If it happens a second time, try restarting the drone. • If it keeps happening, you may need to reorder/remove this component or make it not required. Gimbal Orientation | Pitch 0° | Roll -6° | The parameters are invalid. Please review and submit the request.(code:-1005)
And let me know how I can help as well. DJI Inspire 2. Zenmuse X7 camera with 16mm lens.
Never crashed or damaged my hardware. Works flawlessly in DJI software.
Comments
27 comments
Sergey. Are you on the most current drone firmware ? Which device are you using and which version of DL ? This info may help to assist you better.
If you don’t feel confortable you can first train to DL with a less expensive drone.
As I noted in your other post. Regardless of the app you are using, your drone should not crash when the battery becomes low. In the DJI Go 4 app (for the Inspire 2) you can set up the percentages that the drone will automatically take action, and what action to take - Land or RTH. By default, these values are set up very conservatively - e.g. RTH at 30%.
As for the error, sometimes they are not as useful as they can be - often because they are just reporting what the DJI SDK is putting out. However, I have experienced issues in the past where something in the mission caused the gimbal to be set to not go higher than 0deg. This is a problem when it was taking 360 photos as it needed to go to +30deg.
The best option would be to post a link to the mission so that we can see it and give some better input.
As a side note - I think stéphane GARNIER's advice is solid.
I agree on practicing with a cheaper drone. But the problem of this topic is more the issue of not being able to continue a flight.
https://app.dronelink.com/sergey-poltavskiy/my-first-project/plan/fMJxyej7WWE9NYFx4tUU/J5gLdD3VaDRLiu1bEglm
As far as firmware goes. I made sure to update my drone/camera to latest/greatest firmware before flying. I will double check here shortly once more to see if maybe something is out of date and report back.
Apprecaite you all taking the time to help.
Link to mission.
Attached is also the screenshot of my hiccups.
Hey Mike,
Looked into the versions.
I am on the latest drone Firmware. I tried the app on ipad while having these issues. Latest version of the DL app as I just purchased it last week and wanted to test it this weekend.
Looks like it is having a problem with setting the gimbal back to where it was when the mission disengaged. My guess is it has to do with the 6 degrees of roll. Can you share your mission plan? Moving to bug reports.
Hey Jim. Sorry was out of town for work.
I shared a link above to the plan. Was that not accurate way of sharing? Pasting again just in case,
https://app.dronelink.com/sergey-poltavskiy/my-first-project/plan/fMJxyej7WWE9NYFx4tUU/J5gLdD3VaDRLiu1bEglm
It looks like it is trying to restore the gimbal to 0 pitch / -6 roll, but the mission plan has the map set to -60 pitch (no roll). Did you roll the gimbal wheel while the mission was running and change the pitch / roll?
Jim McAndrew so I am very new to using the software and I am sure I might be doing something wrong.
But here is a breakdown of my process in a nutshell.
1. Take drone out of the case, carry drone to empty area for sale launch and place. I do not manipulate anything.
2. Start controller
3. Start Drone
4. Start Droneline
5. Select mission
6. Click on the mission plan and click start
7. When I felt the drone was loosing battery without notifying me I took over flight and manually flew it to me
8. Landed drone, replaced batteries
9. Selected the mission again and clicked on continue or resume whichever the option was.
Throughout the process of I did not touch the camera one bit, adjust camera angle or anything.
This issue also happens if I was to take over flight and just press resume again without even landing drone. Something about the plan just does not want it to continue.
I do not mean this with any negativity in mind, but how much was the Inspire 2 tested on before listed as a compatible drone? I will also try to create another misison plan and test it maybe tomorrow with a -45 pitch to see if that helps.
We don't test the Inspire 2 directly - we use the M300 but the SDK is the same for both. It appears that the gimbal telemetry must be incorrect because for some reason Dronelink thinks it needs to return it to -6 roll for some reason.
Barry Houldsworth you seeing this behavior on your I2?
@jim
Still traveling...I'll check when I get back at the end of the month.
Appreciate you Jim McAndrew and Barry Houldsworth for helping me out here. Hopefully we can pinpoint the source of the issue and find a fix.
Have a wonderful weekend you two!
Just wanted to bump this thread? I am still looking to find out what is going on because without this feature being functional its quite useless to me since the Inspire 2 eats batteries so fast I wouldn't be able to get any scan done in time and since I cannot conintue a scan it makes the whole app useless for me.
Thanks in advance and appreciate your help!
Hi Sergey Poltavskiy
I've been back to back since I came back from vacation so I have not had a chance to try this. However, I should have some time later this week. A few questions/comments for clarification:
Since you said the issue occurs even if you cancel and restart it doesn't seem to be related to battery changes at all so if I get a chance I will just start the mission, stop it, and try to restart.
If I get a chance this week I will post my results here.
Barry
Barry Houldsworth Thank you sir. I honestly did not do any manual adjustments at all. Since I am new to using Dronelink I am trying to do as little as I can and just try to trust the system.
So thats why the roll error keeps confusing me as I did not set it up in Dronelink or my camera.
I thought maybe somehow the app error is reading the 60degree pitch as a 6 degree roll, but no clue what or why.
Yeah at this point I can validate its not battery related, its something about the resume ability. I tried as well to cancle and restart and it didn't work, so yeah, no point in draining a battery.
If there is anything I can do on my end to help please let me know. Due to my lack of knoledge I am still extremely new and useless.
Let me run this when I can. I'm currently staying with some friends but will try in the next couple of days (weather permitting).
No problem at all and no rush Barry. I am usually slammed during the week with client projects so weekends are my only time for fun lol.
Sergey Poltavskiy
I was able to get around to testing this yesterday and I encounter the same error. No problem running the mission but then as soon as I try to continue I get the 1005 gimbal roll error.
I tried using the classic dashboard and the modern dashboard with the same results.
I also tried just a simple waypoint mission and that also gave the same error on resuming.
I have reported my findings to Jim. I know that he's super busy with the new SDK for the M3E just recently released, so I can see that needs to take priority, but hopefully, he will get to it soon.
Barry Houldsworth
Thank you so much for finding the time to test this. I am so glad you ran into the same issue so we can rule out operator error.
I totally understand the priority situation and hope he can find the time to look into this as soon as he can.
Thank you all so much for the assistance and looking into this!
We pushed out an experimental fix for this issue, but you will probably need to start the mission over to test it (resuming an old mission might result in the same error).
Is this in the general release or beta?
Happy to try it again and let you know.
It is on production, should just see "kernel upgraded".
OK - great. I did see that when I just started the app.
I need to charge batteries so it might not be today but I will test when I can and get back to you.
Jim McAndrew Sergey Poltavskiy
Just tested it using both my test mission and Sergey's mapping mission and everything now resumes without issue.
Thanks!
Barry Houldsworth
Thank you so much for taking the time to do this. I will have to find some free time hopefully this weekend and get out to test my stuff. I assume if its working for you it will work for me. Cant wait to have a proper end result lol.
Thank you again, both of you!
Sergey Poltavskiy
The battery indicator is still not working in the modern dashboard, so I would suggest using the classic until that is resolved.
Please sign in to leave a comment.