thetechnobear
lvl.3
Flight distance : 2804810 ft
Spain
Offline
|
Ive just landed after a nasty bug occured in the googles.
I was flying around in M mode, when I suddenly noticed by altitude and speed were not updaing in the goggles.
controller was working fine, and video signal was fine - RC/HD and 4 bars, and I was flying pretty close
given there was a malfunction, I obviously decided to land...
so I switch to N mode to cruise back, the drone correctly switched to N mode..
however, the goggles did not show this .. so it was obvious now the whole telemetry data had frozen.
it landed fine, and was showing 40% battery left.
(everything in the OSD was still frozen)
now on the ground, I could 'reboot' the goggles.
as soon as they rebooted, the telemetry corrected itself... showing N mode, altitude etc.
however, the worrying part was ... the battery was at 20%, not 40% as shown on the goggles.
as I say, the drone and controller, and video were fine - it was just the telemery data that froze.
edit: observations
- just checked flight in dji fly app... and also shows data stopped around the time I saw the OSD stop.
- I did not get any battery alerts or notifications about RTH due to battery (which is a bit concerning)
Im downloading the aircraft logs... though not sure how to inspect this
|
|