Everyone should have a RX that has built-in failsafe, but what happens when communication between the RX and flight board fail?
The CC code currently doesn't have a radio failsafe. There's no baro so a smart descent becomes difficult. Cutting the motors is not the proper way IMHO and I do understand that there is a lot more involved than most people consider.
I'd like to hear from the end users on what they think the copter should do if the board lost communication with the RX. Then we can listen to the developers on why that's not possible or smart.
MK uses a predefined gas value for a time period that is probably only good for a couple hundred feet altitude depending on the gas value set. After 24 seconds max it cuts the motors.
I think the user should be able to pick which channels the CC board will watch. If one of those channels goes dark, the failsafe should activate. The reason for picking the channels is because I use a head tracker and I don't want one of those channels activating crash mode. The same would be true for the other non-flight related channels.
The channels should go to a user defined value that suits the craft.
MKs estimate hover gas by averaging gas values during periods of low Z movement. Should the failsafe gas value be some percent below the calculated hover gas and revert to a predefined value if hover gas is not sane?
Can the Z ACC be watched so that an improperly set throttle will not rocket the craft into the sky?
Can the ACC be watched so that it turns off the motors at the first impact?
Maybe the motors should be cut if the craft is tumbling?
Different people want different things and I think there should be options to choose.
Maybe there's a better way? What do you guys think?
The CC code currently doesn't have a radio failsafe. There's no baro so a smart descent becomes difficult. Cutting the motors is not the proper way IMHO and I do understand that there is a lot more involved than most people consider.
I'd like to hear from the end users on what they think the copter should do if the board lost communication with the RX. Then we can listen to the developers on why that's not possible or smart.
MK uses a predefined gas value for a time period that is probably only good for a couple hundred feet altitude depending on the gas value set. After 24 seconds max it cuts the motors.
I think the user should be able to pick which channels the CC board will watch. If one of those channels goes dark, the failsafe should activate. The reason for picking the channels is because I use a head tracker and I don't want one of those channels activating crash mode. The same would be true for the other non-flight related channels.
The channels should go to a user defined value that suits the craft.
MKs estimate hover gas by averaging gas values during periods of low Z movement. Should the failsafe gas value be some percent below the calculated hover gas and revert to a predefined value if hover gas is not sane?
Can the Z ACC be watched so that an improperly set throttle will not rocket the craft into the sky?
Can the ACC be watched so that it turns off the motors at the first impact?
Maybe the motors should be cut if the craft is tumbling?
Different people want different things and I think there should be options to choose.
Maybe there's a better way? What do you guys think?