Hi everybody,
today I decided to test failsafe for the first time. I flew away about 100 metres and "parked it in the air", then flipped the fail-safe switch at about 5 metres altitude. It started by descending a meter or so, then went up to 20 metres, turned towards the take off point and came back. Waited for some time at 20 meters altitude and the started to descend. Fast.:livid: Actually since I never had seen it perform this I didn´t know what to expect and by the time I realized that it would hit the ground in a not very controlled manner it was too late. It was not that it turned off the motors 20 metres up, but it didn´t seem to give enough throttle to descend slow and easy. The quad hit the ground hard enough to let the propeller protection ring hit the props and both the protection and my new Tiger carbon props were destroyed. Luckily the cameras did survive.
After a few seconds on the ground the motors were revving up again and it did a few jumps before it settled. Quite scaring actually as the whole fail-safe operation not seemed to be performed under control at all :confusion:
I did have a good and solid satellite status and no error messages/codes. I had just flown two full batteries using GPS, IOC etc. without any problems. My radio is a DX8 and I programmed the fail safe function for TX lost with 50% throttle even though I guess it doesn´t matter since the Naza takes over control? The fail-safe switch have been verified functioning for all flight modes prior to this test in the software assistant. Battery status was good (verified with both timer and OSD).
I got the impression that the Naza miscalculated either the starting point altitude or that the quad was too heavy to slow down when it came closer to ground. It feels like I have enough powerful motors when I´m flying and they do not get very hot. It is consuming around 30A when hovering and I use a Zippy 3S 5800mAh 30C battery. The quad is a 500XT with Tiger motors and an all-up-weight of about 2 kg.
I have Naza-M GPS v1 with firmware 3.12
Any ideas what might have been the problem or seen anything like this before?
today I decided to test failsafe for the first time. I flew away about 100 metres and "parked it in the air", then flipped the fail-safe switch at about 5 metres altitude. It started by descending a meter or so, then went up to 20 metres, turned towards the take off point and came back. Waited for some time at 20 meters altitude and the started to descend. Fast.:livid: Actually since I never had seen it perform this I didn´t know what to expect and by the time I realized that it would hit the ground in a not very controlled manner it was too late. It was not that it turned off the motors 20 metres up, but it didn´t seem to give enough throttle to descend slow and easy. The quad hit the ground hard enough to let the propeller protection ring hit the props and both the protection and my new Tiger carbon props were destroyed. Luckily the cameras did survive.
After a few seconds on the ground the motors were revving up again and it did a few jumps before it settled. Quite scaring actually as the whole fail-safe operation not seemed to be performed under control at all :confusion:
I did have a good and solid satellite status and no error messages/codes. I had just flown two full batteries using GPS, IOC etc. without any problems. My radio is a DX8 and I programmed the fail safe function for TX lost with 50% throttle even though I guess it doesn´t matter since the Naza takes over control? The fail-safe switch have been verified functioning for all flight modes prior to this test in the software assistant. Battery status was good (verified with both timer and OSD).
I got the impression that the Naza miscalculated either the starting point altitude or that the quad was too heavy to slow down when it came closer to ground. It feels like I have enough powerful motors when I´m flying and they do not get very hot. It is consuming around 30A when hovering and I use a Zippy 3S 5800mAh 30C battery. The quad is a 500XT with Tiger motors and an all-up-weight of about 2 kg.
I have Naza-M GPS v1 with firmware 3.12
Any ideas what might have been the problem or seen anything like this before?
Last edited by a moderator: