First flights 4.0.0(209), observastions & glitches
So today i got down my local field and flew a few missions using 4.0.0 (209), and really liking the layout, especially the fact that i can see the tablets navigation bar and also get to its controls, all on screen messages are nice and clear with appropriate coloured backgrounds, ok that's the main observations for now, so onto the glitches that i experienced.
ESC short circuited: solution: Restart drone
Ok this one occured after completing the first mission, the drone had returned to above the home point, and was starting to land, about 10 foot up i hit the RTH button on the controller to cancel the landing, before starting the next mission, when i clicked on the next mission to start it, ther drone flew to the star point but wouldn't go any further, so i bought it home, landed it and the message cleared, I then restarted and flew the next mission without a problem.
The message can be seen in the first of the following images:
On getting home i checked the UAV airdata logs to see if they had any info round about that time in the flight, and was surprised to see notification high lighhted in the second photo, at no point did i change the max altitude whic if you read that message the drone is actualy flying about 11 foot higher than the supposed max altitude has been changed to.
Not asked if i wanted to start a new version
So after, initially flying the Parallel lines mission in the photo below, I decided to change the height of the second leg from 40 to 100 feet, so landed the drone, opened the editor from within the app and made the changes with noquestion of did i want to start a new version .
So after made the changes, i flew the mission with no problem.
Complete freeze up of the app
After flying the parallel lines mission with the changed altitude, I let the drone come home and cancelled the landing and let the drone hover, i then decided to try the on the line functions and got the message in the photo below about them not being supported in the Modern dashboard yet.
I then decided to change the speed of the second leg in the parallel lines mission (got asked if i wanted a new version, which i said yes), afer making the edit i loaded the mission up, hit the start button and nothing happened, the drone just sat there, changed to classic and tried from there and just a message about weak signal (I'm stood facing the drone with it hovering at about 4 foot right in front of me). i switched back to modern, tried another mission, still no joy, so decided to land manually, once landed i tried taking off again both by starting a mission and also by pressing the take off button in the app.
I then decided to close all apps on the tablet and restarted Dronelink and everything was good again
Comments
11 comments
Greetings, I think we have to wait for a new update which is more mature, hopefully it will be soon to get the most out of the new modern interface.
Yep, seems like a lack of maturity, this is my understanding.
Thanks for the feedback!
My guess is it has something to do with the RTH and DJI setting it automatically during that process. You can test it outside of Dronelink in any other app that generates logs to confirm it isn’t DL.
Were you in expert mode? This is more of a web app issue (not the native flight dashboard beta).
We just report any errors that come from the DJI SDK.
Are you have to reproduce this?
I was in Jim mode ;)
I'll see if i can see it using litchi next time I'm out, not seen anything like it in the other logs from yesterday
I'll try to and report back
You're welcome, you guys are doing a great job
PS
Any chance of an attitude indicator?
Attitude of what? Drone? Gimbal?
Drone, something similar to this in DJI fly or the one bottom right in classic
👍
I just tested this in Jim mode and got the new version prompt, are you able to reproduce this?
Nope, just tried several times, and got new version prompt every time, so reckon put this one to bed
Jim McAndrew, updates from today's flights
Tried to reproduce this while out today, by trying several of the things I'd done yesterday, just before it happened, and was unable to, however one of the things i had tried yesterday was accessing the on the fly functions and when i tried today I couldn't clear the message panel afterwards as per screenshot below.
However i was able to load and launch a mapping which subsequently failed as per this screenshot and the mission itself here https://app.dronelink.com/martin-reading/mission/NTtkCkQg2uH8U20JjhdF
After getting that message I brought the drone home, landed it closed and reopened dronelink and continued the mission with no further real problems other than near the end I noticed the gimbal was at -78, rather than the -90 specified in the Mission
Please sign in to leave a comment.