Nidge
Captain
Offline
|
I’ve yet to experience my Spark switching to “ATTI” mode, though it’s not my primary flying machine and I only use it for still photography. However I do fly all my other craft in ATTI (DJI), Stabilised (APM), Balanced (Flyshark) Mode. In this mode the GPS circuits are still reporting the position of the craft but have no influence on its flight characteristics. Even switching in full manual mode ( no self levelling ) the GPS is still functioning but only reporting positional information.
In the case of the Spark, when it forces itself into ATTI mode, it appears it’s still trying to use the GPS and Compass data hence the constant stream of error messages and the often reported erratic behaviour. If this is the case a possible solution would be to invoke a timer or counter whereby after a set number of errors the Spark goes into TRUE ATT-MODE and the GPS/Compass data is ignored completely until the craft is power cycled.
I have four Phantoms, five self built craft using NAZA V2 FC’s, four craft using APM/PIXHAWK FC’s, and a number of other models using proprietary FC’s based around the APM architecture. In the six years I’ve been flying these machines I have never experienced anything close to a flyaway or crash. I appreciate that with many of the reported Spark failures some degree of negligence by the operator can be accounted for, e.g. incorrect calibration of the compass/IMU, flying in too harsh of an environment, etc, but these misgivings should not result in the loss of the craft if the erroneous data can be ignored and the flight controller can be retarded to function in a very basic way, much like any cheap brushless quad, until the operator can safely land and investigate the issue.
Regards.
|
|