That's my point. If the St location was incorrect, it could have gone to where it thought it was.
My H+ just flew away using 750 firmware! Can't find drone anywhere! **Now with updated Telemetry***
- Thread starter JackMTaco
- Start date
Is it possible to determine what location was stored for takeoff? I've been looking at the telemetry information and if it took the first location it registered with at startup, that would put it off the east coast of Florida...
Good question. The time stamp when it reports the location is stored might coincide with the time stamp of the telemetry. Are you looking at the telemetry file lat\long?
h-elsner
Premium Pilot
- Joined
- Mar 23, 2016
- Messages
- 1,947
- Reaction score
- 1,641
- Location
- Bavaria / Germany
- Website
- h-elsner.mooo.com
Thank you for letting us se FlightLogs from this strange case. There are a lot of issues:
- Copter switched to Manual mode. I don't know how Manual mode will be switched on at H plus with the new firmware, but I guess it was not the pilot who has done this accidently. The only reason is that GPS stops working without reason (HW error?).
- Copter did not response on RTH at all, strange.
- The values from accelerator are nonsense at the end. This may the reason for the for the "CRITICAL NAVIGATION FAILURE". In tas as well as in hSpeed the values goes up to 45m/s while coordinates and time interval say ~13m/s. Values from accelerator shows some kind of saw tooth, never seen this before.
- From 12:12:48 on there is no more reaction on the stick movement by the copter, before it is.
- Copter flies away with around 13m/s. The speed remains relative constant. But pitch, roll are near zero???
- There is a gap in the telemetry for 7sec. Sensor file says RC lost for 4sec. I would expect it loiter during this time, but inside this 7sec gap it took 97m --> 13,8m/s, same speed without a stop.
You can 'play' the flight in GoogleEarth by Telemetry00098.kml
Here are the messages from Sensor file:
D:\temp\FlightLog_JackMTaco\Sensor\Sensor_00107.txt
88 CRITICAL: MANUAL CONTROL LOST : 4,change to auto loiter
226 INFO: (3,27)FUSE OPTICAL FLOW
227 INFO: (3,26)ANGLE MODE
1628 CRITICAL: CAUTION: Avionics power low: 4.66 Volt
1629 INFO: Armed by RC.
1640 INFO: [logger] file: /fs/microsd/log/2018-09-02/17_11_0
1720 INFO: (3,14)home: 39.2060390, -77.2675487, 153.45
1723 INFO: (3,25)SPORT MODE
1754 INFO: Takeoff detected.
2565 INFO: (1,7)Warn geomagnetic field is disturbed.
2948 EMERGENCY: CRITICAL NAVIGATION FAILURE - CHECK SENSOR CALIBR
2952 CRITICAL: Failsafe enabled: no local position
2953 INFO: Failsafe mode on.
2954 CRITICAL: No valid position. Switching to manual mode
3425 INFO: (1,7)Warn geomagnetic field is disturbed.
3690 INFO: (3,26)ANGLE MODE
3691 INFO: Failsafe mode off.
3694 CRITICAL: Failsafe enabled: no local position
3695 INFO: Failsafe mode on.
3696 CRITICAL: No valid position. Switching to manual mode
3779 INFO: (1,7)Warn geomagnetic field is disturbed.
3927 INFO: (3,51) BEGIN TO RTL
3928 INFO: Failsafe mode off.
3931 CRITICAL: Failsafe enabled: no global position
3932 INFO: Failsafe mode on.
3933 CRITICAL: No valid position. Switching to manual mode
4241 INFO: (1,7)Warn geomagnetic field is disturbed.
4643 INFO: (3,26)ANGLE MODE
4644 INFO: Failsafe mode off.
4646 CRITICAL: Failsafe enabled: no local position
4647 INFO: Failsafe mode on.
4648 CRITICAL: No valid position. Switching to manual mode
4848 INFO: (3,51) BEGIN TO RTL
4850 INFO: Failsafe mode off.
4852 CRITICAL: Failsafe enabled: no global position
4853 INFO: Failsafe mode on.
4854 CRITICAL: No valid position. Switching to manual mode
4980 INFO: (3,26)ANGLE MODE
4982 INFO: Failsafe mode off.
4983 CRITICAL: Failsafe enabled: no local position
4984 INFO: Failsafe mode on.
4985 CRITICAL: No valid position. Switching to manual mode
6728 INFO: (3,51) BEGIN TO RTL
6732 INFO: Failsafe mode off.
6733 CRITICAL: Failsafe enabled: no global position
6734 INFO: Failsafe mode on.
6736 CRITICAL: No valid position. Switching to manual mode
7130 INFO: (3,26)ANGLE MODE
7131 INFO: Failsafe mode off.
7132 CRITICAL: Failsafe enabled: no local position
7133 INFO: Failsafe mode on.
7134 CRITICAL: No valid position. Switching to manual mode
7135 INFO: (3,25)SPORT MODE
7136 INFO: Failsafe mode off.
7137 CRITICAL: Failsafe enabled: no local position
7140 INFO: Failsafe mode on.
7141 CRITICAL: No valid position. Switching to manual mode
7573 INFO: (1,7)Warn geomagnetic field is disturbed.
7763 INFO: (3,26)ANGLE MODE
7764 INFO: Failsafe mode off.
7767 CRITICAL: Failsafe enabled: no local position
7768 INFO: Failsafe mode on.
7769 CRITICAL: No valid position. Switching to manual mode
7770 INFO: (3,51) BEGIN TO RTL
7771 INFO: Failsafe mode off.
7773 CRITICAL: Failsafe enabled: no global position
7774 INFO: Failsafe mode on.
7775 CRITICAL: No valid position. Switching to manual mode
8096 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=152203ms). 2:32,203 from boot time
8099 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter delta 1,202 sec
8163 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=153405ms). 2:33,405 from boot time
8164 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter
8346 CRITICAL: (1,62)MANUAL CONTROL LOST : change to rc lost sta
8347 CRITICAL: No valid position. Switching to manual mode
8382 INFO: (3,63)Manual control regained after 4091ms. 4,1 sec
8383 CRITICAL: No valid position. Switching to manual mode
8427 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=157751ms). 2:37,751 from boot time
8428 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter delta 0,843 sec
8477 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=158594ms). 2:38,594 from boot time
8478 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter delta 13,945 sec
9281 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=172539ms). 2:52,539 from boot time
9282 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter
9748 MAVlink Datensätze
From my point of view this is a system error and Yuneec needs to replace it.
br HE
- Copter switched to Manual mode. I don't know how Manual mode will be switched on at H plus with the new firmware, but I guess it was not the pilot who has done this accidently. The only reason is that GPS stops working without reason (HW error?).
- Copter did not response on RTH at all, strange.
- The values from accelerator are nonsense at the end. This may the reason for the for the "CRITICAL NAVIGATION FAILURE". In tas as well as in hSpeed the values goes up to 45m/s while coordinates and time interval say ~13m/s. Values from accelerator shows some kind of saw tooth, never seen this before.
- From 12:12:48 on there is no more reaction on the stick movement by the copter, before it is.
- Copter flies away with around 13m/s. The speed remains relative constant. But pitch, roll are near zero???
- There is a gap in the telemetry for 7sec. Sensor file says RC lost for 4sec. I would expect it loiter during this time, but inside this 7sec gap it took 97m --> 13,8m/s, same speed without a stop.
You can 'play' the flight in GoogleEarth by Telemetry00098.kml
Here are the messages from Sensor file:
D:\temp\FlightLog_JackMTaco\Sensor\Sensor_00107.txt
88 CRITICAL: MANUAL CONTROL LOST : 4,change to auto loiter
226 INFO: (3,27)FUSE OPTICAL FLOW
227 INFO: (3,26)ANGLE MODE
1628 CRITICAL: CAUTION: Avionics power low: 4.66 Volt
1629 INFO: Armed by RC.
1640 INFO: [logger] file: /fs/microsd/log/2018-09-02/17_11_0
1720 INFO: (3,14)home: 39.2060390, -77.2675487, 153.45
1723 INFO: (3,25)SPORT MODE
1754 INFO: Takeoff detected.
2565 INFO: (1,7)Warn geomagnetic field is disturbed.
2948 EMERGENCY: CRITICAL NAVIGATION FAILURE - CHECK SENSOR CALIBR
2952 CRITICAL: Failsafe enabled: no local position
2953 INFO: Failsafe mode on.
2954 CRITICAL: No valid position. Switching to manual mode
3425 INFO: (1,7)Warn geomagnetic field is disturbed.
3690 INFO: (3,26)ANGLE MODE
3691 INFO: Failsafe mode off.
3694 CRITICAL: Failsafe enabled: no local position
3695 INFO: Failsafe mode on.
3696 CRITICAL: No valid position. Switching to manual mode
3779 INFO: (1,7)Warn geomagnetic field is disturbed.
3927 INFO: (3,51) BEGIN TO RTL
3928 INFO: Failsafe mode off.
3931 CRITICAL: Failsafe enabled: no global position
3932 INFO: Failsafe mode on.
3933 CRITICAL: No valid position. Switching to manual mode
4241 INFO: (1,7)Warn geomagnetic field is disturbed.
4643 INFO: (3,26)ANGLE MODE
4644 INFO: Failsafe mode off.
4646 CRITICAL: Failsafe enabled: no local position
4647 INFO: Failsafe mode on.
4648 CRITICAL: No valid position. Switching to manual mode
4848 INFO: (3,51) BEGIN TO RTL
4850 INFO: Failsafe mode off.
4852 CRITICAL: Failsafe enabled: no global position
4853 INFO: Failsafe mode on.
4854 CRITICAL: No valid position. Switching to manual mode
4980 INFO: (3,26)ANGLE MODE
4982 INFO: Failsafe mode off.
4983 CRITICAL: Failsafe enabled: no local position
4984 INFO: Failsafe mode on.
4985 CRITICAL: No valid position. Switching to manual mode
6728 INFO: (3,51) BEGIN TO RTL
6732 INFO: Failsafe mode off.
6733 CRITICAL: Failsafe enabled: no global position
6734 INFO: Failsafe mode on.
6736 CRITICAL: No valid position. Switching to manual mode
7130 INFO: (3,26)ANGLE MODE
7131 INFO: Failsafe mode off.
7132 CRITICAL: Failsafe enabled: no local position
7133 INFO: Failsafe mode on.
7134 CRITICAL: No valid position. Switching to manual mode
7135 INFO: (3,25)SPORT MODE
7136 INFO: Failsafe mode off.
7137 CRITICAL: Failsafe enabled: no local position
7140 INFO: Failsafe mode on.
7141 CRITICAL: No valid position. Switching to manual mode
7573 INFO: (1,7)Warn geomagnetic field is disturbed.
7763 INFO: (3,26)ANGLE MODE
7764 INFO: Failsafe mode off.
7767 CRITICAL: Failsafe enabled: no local position
7768 INFO: Failsafe mode on.
7769 CRITICAL: No valid position. Switching to manual mode
7770 INFO: (3,51) BEGIN TO RTL
7771 INFO: Failsafe mode off.
7773 CRITICAL: Failsafe enabled: no global position
7774 INFO: Failsafe mode on.
7775 CRITICAL: No valid position. Switching to manual mode
8096 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=152203ms). 2:32,203 from boot time
8099 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter delta 1,202 sec
8163 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=153405ms). 2:33,405 from boot time
8164 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter
8346 CRITICAL: (1,62)MANUAL CONTROL LOST : change to rc lost sta
8347 CRITICAL: No valid position. Switching to manual mode
8382 INFO: (3,63)Manual control regained after 4091ms. 4,1 sec
8383 CRITICAL: No valid position. Switching to manual mode
8427 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=157751ms). 2:37,751 from boot time
8428 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter delta 0,843 sec
8477 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=158594ms). 2:38,594 from boot time
8478 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter delta 13,945 sec
9281 CRITICAL: MANUAL CONTROL THE INTERRUPTION(at t=172539ms). 2:52,539 from boot time
9282 CRITICAL: MANUAL CONTROL LOST : 12,change to auto loiter
9748 MAVlink Datensätze
From my point of view this is a system error and Yuneec needs to replace it.
br HE
Last edited:
good analysis, we will have to start by going to see the roofs of the surrounding buildings
- Joined
- Feb 24, 2017
- Messages
- 2,997
- Reaction score
- 3,185
- Location
- Central Florida
- Website
- copperdawg.com
I've contacted the local drone group I am in on Facbook and some have offered to help look with their drones. Do you really think it would be o a rooftop where the last signal coordinate is?
if you do not find it on the ground in this end-of-transmission zone, you have to look on the roofs, and with a drone it's quite easy. Finally I'll start there if it was for me
Oliver,
I'm waiting for someone with their drone to come by and look at the roofs you mention. I already checked the parking lots of those buildings 4 times since Saturday just to make sure it wasn't on the ground or in the trees anywhere. (There's a lot of trees unfortunately). The green box I think has a better chance if the drone indeed was at 73m high (240ft). I had the camera locked at the time to the front of the drone so that picture has me more inclined to think the green building is the better chance.
The one thing that has me doubtful of it landing on the roof is the fact that it wouldn't RTL when commanded and it didn't auto return either when it first lost radio contact nor did it try to land when it lost radio contact, the fact that it left in a such a controlled manner has me thinking that it just continued heading in that direction at full speed. As H-Elsner pointed out the entire flight path from Google Earth, you can see the path that the drone took when I lifted off to the point that I realized there was a problem. You can see that I managed to regain some control of it when it started drifting and I controlled it enough to bring it back to me in a wide loop before it just completed stopped responding to me inputs. You can see the black line (ST16S and Me) started running around the building down the street trying to regain radio/video feed as it took off.
I'm waiting for someone with their drone to come by and look at the roofs you mention. I already checked the parking lots of those buildings 4 times since Saturday just to make sure it wasn't on the ground or in the trees anywhere. (There's a lot of trees unfortunately). The green box I think has a better chance if the drone indeed was at 73m high (240ft). I had the camera locked at the time to the front of the drone so that picture has me more inclined to think the green building is the better chance.
The one thing that has me doubtful of it landing on the roof is the fact that it wouldn't RTL when commanded and it didn't auto return either when it first lost radio contact nor did it try to land when it lost radio contact, the fact that it left in a such a controlled manner has me thinking that it just continued heading in that direction at full speed. As H-Elsner pointed out the entire flight path from Google Earth, you can see the path that the drone took when I lifted off to the point that I realized there was a problem. You can see that I managed to regain some control of it when it started drifting and I controlled it enough to bring it back to me in a wide loop before it just completed stopped responding to me inputs. You can see the black line (ST16S and Me) started running around the building down the street trying to regain radio/video feed as it took off.
Last edited:
Jack, this is your first contact with CS, so let me interject here... your experience with CS is quite standard, and there is a specific methodology that will be effective.
1) Never expect any real response via email... it will not happen.
2) Yuneec CS in the US has a total of only 2 people manning the telephone support. The only effective means of working with them is to get in the queue for an appointment callback or use the live chat when available.
3) Like any telephone CS center they will be busiest on a Monday following a normal weekend, or the day following a holiday. In that regard, some slack must be given today.
I don't believe anyone specified a roof location as where it safely landed. But given the trajectory of flight, it is possible a roof is where it crashed after the battery ran out or encountered obstacles that ended the flight.
I understand about the call center issue and I know Monday's are the busiest. It is frustration speaking. I just got off the phone with them to explain what has happened, they are going to follow up with me at my scheduled appointment time this afternoon but have already said if everything I stated is true about the log, this should be a 1 for 1 swap replacement.
In regards to the roof. I know they didn't specify a roof location but merely a suggestion. I was stating that if it didn't RTL when commanded and didn't return home when it lost radio signal the first time, I don't think it would have loitered till battery failure since it was already speeding off in straight direction. I'm still going to go look of the roofs though.
I suspect you have looked in this area, the roofs are still a chance.
Regarding the RTL, if the GPS chip is defective or the management of its signals not operational by the H PLUS auto pilot, I wonder why the machine will return to its starting point because he does not know where he is. And did he receive the order from the ST16S?
In addition, he continues to advance as if he kept in memory a previous order of the RC or he decided to join an unknown landing point.
Regarding the RTL, if the GPS chip is defective or the management of its signals not operational by the H PLUS auto pilot, I wonder why the machine will return to its starting point because he does not know where he is. And did he receive the order from the ST16S?
In addition, he continues to advance as if he kept in memory a previous order of the RC or he decided to join an unknown landing point.
I understand the frustration... been there done that. Once you have the appointment they will instruct you to send them the logs via email... once they have reviewed them they will make their determination... likely that yes, you will be sent a replacement, given the info that h-elsner and others have given here. Of course, Yuneec will let you know.
And the difficulty will be to know what really happened ...
That is one of the reasons I want to find it. Not to just get it sent off but to have them look at it and determine what the issue was so that they can address it in a firmware/hardware fix. If I don't find it, it'll probably be found when fall starts. =(
And the difficulty will be to know what really happened ...
Those records will be ultimately stored in a large federal warehouse... 2 aisles down from the Lost Ark of the Covenent.
Last edited:
Similar threads
