Hello everyone,
It's been a long time since I created a new thread, but I had nothing unusual worth sharing happen during my flights.. Until yesterday.
So I hadn't flown my Typhoon H in a while; 2 whole months actually, since my last flight was on january 31. Yesterday I decided to dust off the aircraft, charge the batteries and take it out for a spin.
Using my no-longer-good-to-fly battery I performed the mandatory Accelerometer calib, Compass Calib (facing north) and Gimbal calibration after such a long time of being on the ground; The whole process took exactly 5 minutes (but I most definitely forgot the alleged 12.5 min wait for GPS almanac update)
I flew 5 batteries one after another and everything was almost completely uneventful, except that during the 4th flight I got a vibration on my ground station and the displayed message "Warning: Obstacle Avoidance has failed".
I have to mention I never use the obstacle avoidance feature; in fact I must have flipped the switch around 5 or 6 times on the almost 2 years I've owned the typhoon H just to test it, so other than the rareness of the message itself it meant nothing of concern at the moment. I brought the H close, flipped the OBS Avoid switch on and off a couple of times, and it apparently worked without any issue, the message didn't show again. So I resumed flying normally until I used all the batteries and called it a day.
Upon checking the flight log data, I came across a very unusual telemetry log at the moment I got the weird "OBS Avoid. failed" message. On a single row, for a fraction of a 10th of a second the following relevant data was logged:
All these value changes might look super scary, but again it was on a single data row, for a fraction of a second. The aircraft did not twitch, it did not become unresponsive in any way and it did not fly away. It was completely unnoticeable during flight except for the triggered "Obstacle Avoidance has Failed" message.
My thoughts:
So what do you think? Could this be related to my failure to wait for 12,5 min for GPS almanac update after 2 months powered off? I'm very interested in your opinion on this particular event.
I hope you are all doing great!
Greetings!
Telemetry data log screenshot:
Internal Resistance of battery being used:
Flight paths (Take off spot was on the roof of the building):
It's been a long time since I created a new thread, but I had nothing unusual worth sharing happen during my flights.. Until yesterday.
So I hadn't flown my Typhoon H in a while; 2 whole months actually, since my last flight was on january 31. Yesterday I decided to dust off the aircraft, charge the batteries and take it out for a spin.
Using my no-longer-good-to-fly battery I performed the mandatory Accelerometer calib, Compass Calib (facing north) and Gimbal calibration after such a long time of being on the ground; The whole process took exactly 5 minutes (but I most definitely forgot the alleged 12.5 min wait for GPS almanac update)
I flew 5 batteries one after another and everything was almost completely uneventful, except that during the 4th flight I got a vibration on my ground station and the displayed message "Warning: Obstacle Avoidance has failed".
I have to mention I never use the obstacle avoidance feature; in fact I must have flipped the switch around 5 or 6 times on the almost 2 years I've owned the typhoon H just to test it, so other than the rareness of the message itself it meant nothing of concern at the moment. I brought the H close, flipped the OBS Avoid switch on and off a couple of times, and it apparently worked without any issue, the message didn't show again. So I resumed flying normally until I used all the batteries and called it a day.
Upon checking the flight log data, I came across a very unusual telemetry log at the moment I got the weird "OBS Avoid. failed" message. On a single row, for a fraction of a 10th of a second the following relevant data was logged:
- Battery voltage went from 15.2v to 5.0v
- Current showed a value other than 0.0 (87.0)
- air speed (tas) from 2.75 m/s (9.9 km/h) to 426.34 m/s (1534.9 km/h) (lol
) - GPS sat count from 20 to 6
- press_compass_status from 85 to 3: "Mag fail GPS fail RealSense error Sonar error"
- Flight mode from 3 (Angle+GPS) to 5 (Angle no GPS)
- Error flag: 8 "Complete Motor ESC Failure"
- GPS accuracy from .4m to 8.0m
All these value changes might look super scary, but again it was on a single data row, for a fraction of a second. The aircraft did not twitch, it did not become unresponsive in any way and it did not fly away. It was completely unnoticeable during flight except for the triggered "Obstacle Avoidance has Failed" message.
My thoughts:
- I doubt this will be a recurring event; I believe this was a very unusual glitch of some sort.
- I've been monitoring my batteries closely and I seriously doubt the voltage drop was real, had it been real the aircraft would've definitely blacked out mid-air. (Also battery shows no signs of degradation on any cells, internal resistance of every cell is <=7mΩ, and no puffing)
- I'm leaning towards the "mid-flight updated GPS almanac" hypothesis based on: the satellite count flicker, unrealistic (GPS based) groundspeed spike, GPS flight mode "super fast reset" and lastly: GPS accuracy variation.
So what do you think? Could this be related to my failure to wait for 12,5 min for GPS almanac update after 2 months powered off? I'm very interested in your opinion on this particular event.
I hope you are all doing great!
Greetings!
Telemetry data log screenshot:
Internal Resistance of battery being used:
Flight paths (Take off spot was on the roof of the building):
Last edited:
