Using Wookiee or Matt's script will not help you to determine which log you need. I sometimes get the last 10 or so telemetry logs and play them back in Mission Planner or APM Planner 2 to determine when the crash/event occurred.
Flyaway
- Thread starter mike.rombough
- Start date
I would suspect maybe compass interference...get the last 10 or so tlogs and the last 10 or so dataflash logs and put them on Dropbox or Google Play and I will look at them.
I've seen a Solo go from flying fine to completely nuts because of some rebar in concrete where it took off from...
I like to run it through the LogAnalyzer just to get an idea of what's going on:
Log File C:\Users\Dave\AppData\Local\Temp\tmp13A.tmp.log
Size (kb) 129715.3916015625
No of lines 1827661
Duration 1:00:36
Vehicletype ArduCopter
Firmware Version solo-1.3.1
Firmware Hash 7e9206cc
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = NA -
Test: Brownout = GOOD -
Test: Compass = WARN - Moderate change in mag_field (28.78%)
Max mag field length (662.23) > recommended (550.00)
Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = FAIL - ERRs found: FLT_MODE FS_THR
Test: GPS = GOOD -
Test: IMU Mismatch = GOOD - (Mismatch: 0.24, WARN: 0.75, FAIL: 1.50)
Test: Motor Balance = WARN - Motor channel averages = [1539, 1405, 1517, 1432]
Average motor output = 1473
Difference between min and max motor averages = 134
Test: Parameters = GOOD -
Test: PM = NA -
Test: Pitch/Roll = NA -
Test: Thrust = NA -
Test: VCC = GOOD -
So I'm thinking compass interference might be a good place to start...
Log File C:\Users\Dave\AppData\Local\Temp\tmp13A.tmp.log
Size (kb) 129715.3916015625
No of lines 1827661
Duration 1:00:36
Vehicletype ArduCopter
Firmware Version solo-1.3.1
Firmware Hash 7e9206cc
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = NA -
Test: Brownout = GOOD -
Test: Compass = WARN - Moderate change in mag_field (28.78%)
Max mag field length (662.23) > recommended (550.00)
Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = FAIL - ERRs found: FLT_MODE FS_THR
Test: GPS = GOOD -
Test: IMU Mismatch = GOOD - (Mismatch: 0.24, WARN: 0.75, FAIL: 1.50)
Test: Motor Balance = WARN - Motor channel averages = [1539, 1405, 1517, 1432]
Average motor output = 1473
Difference between min and max motor averages = 134
Test: Parameters = GOOD -
Test: PM = NA -
Test: Pitch/Roll = NA -
Test: Thrust = NA -
Test: VCC = GOOD -
So I'm thinking compass interference might be a good place to start...
- Joined
- Jun 6, 2017
- Messages
- 189
- Reaction score
- 29
- Age
- 20
Good question. It was a sidewalk, so I'm guessing the leg with the compass got within a few inches of the rebar and that was enough. The 1.3.1 firmware doesn't handle that very well (Solo never recovers from the interference) and so that's one of the reasons I was pushing for folks to upgrade the firmware.
Well, maybe nothing to worry about unless it is consistently lower on all your flights. If so, could mean you have a motor pod that needs to be replaced.
Well Mike...without spending too much time on it I'm convinced you should not be flying in that area--way too much compass interference for the Solo.
I'm not sure if it would have helped in this situation, but I would consider upgrading the firmware so that Solo has a fighting chance to right itself and possibly avoid a flyaway.
I'm not sure if it would have helped in this situation, but I would consider upgrading the firmware so that Solo has a fighting chance to right itself and possibly avoid a flyaway.
After landing, be sure to hold down the left stick until getting the "Disarmed" message. It takes longer with the new FW.
Ok was a great flight. I was out a a park on the Niagara escarpment going to take a look at the logs now and make sure all is well thank you guys for all your help
Similar threads
- Locked
New Posts
-
Free Music / SFX Resource for Your Videos - Over 2000 Tracks- Latest: Eric Matyas
-
-
-
-
Members online
No members online now.