Nidge
Second Officer
United Kingdom
Offline
|
Hi JJB
Firstly my apologies as after reading my comment I agree it wasn’t the clearest.
I do believe the Spark is unique with the the whole Yaw/Compass/GPS issues that you and others have reported. I use a multitude of flight controllers e.g. Naza, Wookong, A2, APM (2.5,2.6.2.8,3.1), PX4, Pixhawk, and various Naze type boards F1 to F7 chipsets. Other than the Naze type FC’s I fly all the others primarily in stabilised/Altitude Hold mode switching to GPS/Loiter/Auto when I want the model to hold a stationary position or perform a Waypoint mission. I have experienced GPS and/or Compass errors, usually when flying in em harsh environments. In such situations the FC will switch out of GPS Hold automatically or I’ll perform the switch myself without any drama. When this happens I still receive GPS and heading information but the relevant components no longer have any effect on the operation of the flight controller itself. This was one of the reasons that when I first took delivery of my Spark I programmed the Sport switch to put the Spark into ATTI mode. However I’m now beginning to wonder that when the Spark is forced into ATTI MODE, either manually by the operator or even when the FC is failing to process conflicting data from the compass/GPS, that these components are still influencing the FC causing the Spark to spazz out and appear uncontrollable?
I did try to contact DJI Tech Support for some clarification but all I received was the usual automated reply and an eternity in the wilderness with the tumbleweeds.
Regards
Nidge. |
|