Tbs discovery pro go pro imu zip file#
Tbs discovery pro go pro imu pro#

Managed to find a quiet spot that would also provide some soft landing in a field in case of something literally going south. Not exactly sure what the issue is with this one as the Graph and the Log appear to be within the limits of what can be considered flyable? I also use an external GPS on a Stand located at the rear ~14cm away from the nearest ESC.

Tbs discovery pro go pro imu pro#

While the FC is located inside the Quad ( TBS Discovery PRO ) the ESC’s are not with a ~10cm distance between them. (Mismatch: 0.76, WARN: 0.75, FAIL: 1.50)ĭoing a quick search it appears the first one might be a problem related to the FC being to close too the ESC’s? Test: IMU Mismatch = WARN - Check vibration or accelerometer calibration. Test: GPS = FAIL - Min satellites: 0, Max HDop: 99.99 Test: Compass = WARN - Moderate change in mag_field (26.93%)Max mag field length (590.07) > recommended (550.00) Log File C:/Users/XXX/AppData/Local/Temp/ It appears that either the balancing of the Props or the Cable not being under tension solved most of the alarming issues concerning Vibration? I’ve added a new Logfile where the Quad was just hovering in Stabilize Mode and while it was still tethered, because you know… t(h)rust issues, I ensured the Cable was not under tension.Ĭlick Image for larger Picture Part of the Pixhawk System also included the change from a 400kV/15x5 to a 1000kV/9.5x5 powertrain and being a tad spoiled from the superior quality of the 15x5 Props that never required balancing I grossly neglected to balance the 9.5x5 ones which I now did. Thanks for taking the time to help me solve this issue! Might be worth looking at the Pixhawk mounting see if it can be improved at all. 99% certain switching to stabilise would have stopped it trying to go up. Z axis vibrations do see to be spiking quite high which could account for the altitude gain and why the stick input was ignored. Should I attempt a 30sec Stabilize test and post another Log where the Quad wasn’t desperately trying to climb while being tied to a tensioned string?

Test: Thrust = FAIL - Avg climb rate -572.37 cm/s for throttle avg 960įrom what I’m understanding it appears that I’m looking at a Vibration issue? Test: PM = FAIL - 17 slow loop lines found, max 12.95% on line 926 Test: IMU Mismatch = FAIL - Check vibration or accelerometer calibration. Test: Compass = GOOD - mag_field interference within limits (11.24%)Max mag field length (555.70) > recommended (550.00)

Test: Autotune = UNKNOWN - No ATUN log data

Tbs discovery pro go pro imu zip file#

I attached a ZIP File with Log Files that matched the Date and Time of the Event, as I’m not entirely sure which one is needed I added all of them.Īs suggested I took a peek into the LogAnalyzer and this is what I got: Why do Loiter and Altitude Hold Throttle not react when I’m trying to lower them. Why was Loiter shooting up up and into the sky. I’d actually prefer to forget all about it as it basically whacked into the ground 3-4 times before I could reel it in close enough for me to keep it on the ground and reach for the Safety Switch to turn off the motors.Īnd without the Props attached and GPS Check disabled I checked the Flight Modes and observed that both Loiter and Altitude Hold would drastically increase speed ( compared to Position Hold Mode ) when Throttle is applied but would not lower it when Throttle is taken away unless the Stick is just barely above the arming point and even then only after quite a delay. I managed to get it down in one piece with the help of the string attached to it but the sight of how that worked out was not a work of art, not at all. I slowly raised the throttle and while it started nice the thing suddenly started climbing like mad into the sky until the string stopped it with me trying to get bring it back under control by lowering the throttle which wouldn’t do a thing at all - It kept angrily screaming in the sky pulling at the string. With 18 GPS in the Skies I felt confident and started in Loiter Mode as it’s the first mode. My house must be a bunker which is why I’m unable to test any mode relying on GPS so my test today was outdoors in the wilderness without a soul around ( and again with the Quad on a leash ).

This was tested in my bedroom with the Quad tied to the bed preventing it from crashing into anything else but the soft mattress. Slowly lowering the Throttle has the Motors slowly spinning slower. Slowly raising the Throttle has the Motors slowly spinning faster. The Quad arms fine, gets smoothly off the ground, is super stable and very responsive while in Position Hold Mode.Įspecially Throttle is working like I’m expecting it: I’ve recently done the change from NAZA-M V2 to Pixhawk and I’m having some troubles with it…