ImHereToCrash
Second Officer
Flight distance : 5381368 ft
United States
Offline
|
whoa, your log is crazy. .. few things stand out to me with your fly away. first and foremost, with hardware errors like Compass, IMU, GPS errors any combination of them, never click return to home button! your spark is completely confused and will get lost the spark only has a single IMU and Compass stack, no references once it gets mixed up. land it ASAP or manually bring it somewhere safe ASAP and figure it out.
you stated you flew up 100 feet with controller then spark disobeyed you.. this point where you should click land or bring it back down best you can, reaim controller.. to face it.. dont fly again until you use OTG from RC to the phone or tablet you are using.. and turn off wifi/BT on the device.. and reset/recalibrated the wifi on the spark and RC together with a "relinking"
you started flying before a complete GPS lock, this is a no no unless you are highly experienced or are willing to take a complete loss.
then you quickly got compass errors.. at this point you should have manually turned it around and landed it asap and figure that out.. compass errors are pretty much your spark telling you..no shouting at you that it is confused.. it uses the compass to determine direction, not the GPS. with no sense of direction, can't expect much..
then you got a bunch of gps nomatch errors, this isn't entirely clear at what it means, but when this occurs, do not keep flying.. bring it down...manually..
again, not to shout at you, this is to everyone may not understand it that it is important to understand.. any hardware level errors on the spark or other drones.. like GPS, Compass, IMU, Battery, ETC. never click RTH buttons.. manually fly it to nearest safe landing spot, land it..and meet it up or have someone pick it up... with any errors it means your spark is confused about some aspect. even a simple compass error is fairly RIP if you leave it up to your spark to try to figure out how to get back to you.
|
|