Problem?
Aircraft disconnected from controller after take-off. For extended description of issue see below.
Was unit in a crash?
Yes, into a door approx 1m off the ground ~2mths ago. Appeared unaffected afterward aside from cosmetic scratching/marks. Still functioned fine and no alerts/errors.
What have you tried so far?
Checking logs, trying to understand what happened. Recalibrated IMU and compass. No noticeable change to behaviour as there were no warnings/alerts previously.
What device are you using ( iphone , ipad, Samsung , etc)?
Galaxy S5 attached to RC.
What firmware are you running ( aircraft, remote controller)?
All latest firmwares..
What Go app version are you using?
GO4.
Any modification? (if so what)
FCC mod
Did you change anything or install any apps? (if so what)
Negative.
Do you have a video or pictures of the problem? (if so post link)
Negative.
Hi all,
First time poster after spending many weeks reading and trying to absorb as much as from the forum and teach myself.
Had a little bit of a nervy experience during flight today, wondering if the log boffins could interpret what was happening/happened in the MA?
First flight went ok manually landed and swapped out to a fresh battery.
Second take-off was another vert ascend , wait few seconds then ascend more until I noticed the MA "twitch" in air, and slowly start drifting and yawing left about 30deg before nerves kicked in and I brought it straight back down and landed, seemingly in full control.
I have read this can be due to IMU calibration, I have previously done a calibration after never having done one since owning it and reading it's recommended so ensure all is par for course. This was done maybe a month a go and I've flown on several other occasions in the last month with no reason for concern.
Third take off today was when it really tested my nerves - I took off and hovered at 2-3m for a few seconds as I like to ensure nothing is wrong.
Then proceed upwards and forwards simultaneously, got about 40ish metres up and 130ish metres out and then got the "Aircraft disconnected" notification, no remote input response I waiting to see if it would reconnect, then the MA started the RTH sequence set 50m altitude and come back.
The most anxious part was waiting to see if it would land on the little jetty I was out on, or miss it and want to plop into the water.
Crisis was averted and it landed less than a foot next to where it took-off from.
Now I am trying to understand what happened, why it happened, and how to avoid it in the future...
There were a couple of other motor startups in-between the flights where I never really took-off, but I've included them in-case they allude to an issue.
Further information is I was in FCC mode auto Wi-Fi settings with 5.8GHz chosen freq. Wind was steady at reportedly ~2.2m/s or around 10km/h Though it was gradually picking up the longer I was there.
I've just returned home and performed another IMU calibration and compass calibration. Nothing unusual observed before or after calibration..
Apologies in advance for my metric-ness.
If I'm an idiot and missed something obvious, tell me I'm an idiot - I will wear it with shame/pride and know what not to to again.
Aircraft disconnected from controller after take-off. For extended description of issue see below.
Was unit in a crash?
Yes, into a door approx 1m off the ground ~2mths ago. Appeared unaffected afterward aside from cosmetic scratching/marks. Still functioned fine and no alerts/errors.
What have you tried so far?
Checking logs, trying to understand what happened. Recalibrated IMU and compass. No noticeable change to behaviour as there were no warnings/alerts previously.
What device are you using ( iphone , ipad, Samsung , etc)?
Galaxy S5 attached to RC.
What firmware are you running ( aircraft, remote controller)?
All latest firmwares..
What Go app version are you using?
GO4.
Any modification? (if so what)
FCC mod
Did you change anything or install any apps? (if so what)
Negative.
Do you have a video or pictures of the problem? (if so post link)
Negative.
Hi all,
First time poster after spending many weeks reading and trying to absorb as much as from the forum and teach myself.
Had a little bit of a nervy experience during flight today, wondering if the log boffins could interpret what was happening/happened in the MA?
First flight went ok manually landed and swapped out to a fresh battery.
Second take-off was another vert ascend , wait few seconds then ascend more until I noticed the MA "twitch" in air, and slowly start drifting and yawing left about 30deg before nerves kicked in and I brought it straight back down and landed, seemingly in full control.
I have read this can be due to IMU calibration, I have previously done a calibration after never having done one since owning it and reading it's recommended so ensure all is par for course. This was done maybe a month a go and I've flown on several other occasions in the last month with no reason for concern.
Third take off today was when it really tested my nerves - I took off and hovered at 2-3m for a few seconds as I like to ensure nothing is wrong.
Then proceed upwards and forwards simultaneously, got about 40ish metres up and 130ish metres out and then got the "Aircraft disconnected" notification, no remote input response I waiting to see if it would reconnect, then the MA started the RTH sequence set 50m altitude and come back.
The most anxious part was waiting to see if it would land on the little jetty I was out on, or miss it and want to plop into the water.
Crisis was averted and it landed less than a foot next to where it took-off from.
Now I am trying to understand what happened, why it happened, and how to avoid it in the future...
There were a couple of other motor startups in-between the flights where I never really took-off, but I've included them in-case they allude to an issue.
Further information is I was in FCC mode auto Wi-Fi settings with 5.8GHz chosen freq. Wind was steady at reportedly ~2.2m/s or around 10km/h Though it was gradually picking up the longer I was there.
I've just returned home and performed another IMU calibration and compass calibration. Nothing unusual observed before or after calibration..
Apologies in advance for my metric-ness.
If I'm an idiot and missed something obvious, tell me I'm an idiot - I will wear it with shame/pride and know what not to to again.
Attachments
-
DJIFlightRecord_2018-12-21_[14-02-18].txt14.3 KB · Views: 3
-
DJIFlightRecord_2018-12-21_[13-56-09].txt68.8 KB · Views: 0
-
DJIFlightRecord_2018-12-21_[13-54-10].txt12.1 KB · Views: 0
-
DJIFlightRecord_2018-12-21_[13-52-34].txt93.2 KB · Views: 0
-
DJIFlightRecord_2018-12-21_[13-40-29].txt1.2 MB · Views: 0
-
18-12-21-03-22-39_FLY086.DAT856.3 KB · Views: 0
-
18-12-21-03-16-11_FLY085.DAT256 bytes · Views: 0
-
18-12-21-01-59-27_FLY084.DAT1.1 MB · Views: 0
-
18-12-21-01-51-35_FLY084.DAT1.9 MB · Views: 0
-
18-12-21-01-38-47_FLY083.DAT3.7 MB · Views: 0
Last edited: