Having a problem with OpenSolo 3.0 and uncommanded yaw. Tried to upload both .bin and .txt logs. BIN extension was rejected, text file's size was rejected. .
I updated my green cube Solo a couple of days ago to 3.0 and did a test flight yesterday cut short by a problem. Update was flawless. Followed instructions and did NOT load any parameter files. Before flight I calibrated level and compass.
I took off in FLY with GPS lock to default height and let it sit a minute to observer hover. I then took it about 30 away and about 40 feet up and noticed a slight CCW twitch. I corrected that and it twitched again. I then let it hover and observed that as it was facing north,it was twitching every 10 seconds or so in a CCW direction, almost as if in Pano mode. It would yaw about 10 degrees, then hold ten seconds, then yaw, hold, etc.
All of this was uncommanded/ with hands OFF sticks. When it got approximately due west, the yaw stopped. I then attempted again to take the bird out a little bit, continued to observe erratic flight with uncommanded movements, so I decided to end the flight. I had to time the landing in between yaws to avoid a flip.
The logs show a lot of different messages. There are several "EKF2 IMU0 and IMU1 in flight yaw alignment complete" messages and every 10 seconds through the whole flight EKF2 IMU0 and IMU1 compass switching messages, the timing of which seems to correlate with the yaw movements.
I really hope this is not hardware-related. It's a brand-new main board, brand new compass and green cube with only about 90 minutes flight time.
I did notice ever since RC2 that when I connect through Solex or Mission Planner, it frequently tells me "Already got parameter xxxx". Most of the time it's momentary, sometimes it hangs for several minutes and sometimes I observe it actually looping, trying to repeatedly load the same parameters. When connecting to Mission Planner, I also frequently see "Bad Logging" messages. I have only had it airborne twice since RC2 due to work, weather, timing, etc., so it's hard to tell, but I suspect my parameters have somehow gotten corrupt, perhaps during the upgrade to RC2. But with several hundred, I have no idea what to look for.
Autoanalysis of the dataflash log shows slow loop lines, duplicate data chunk warnings and a few other anomalies about mia parameters:
No of lines 140602
Duration 0:06:37
Vehicletype ArduCopter
Firmware Version V3.5.4
Firmware Hash 0b76dc76
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = UNKNOWN - No ATUN log data
Test: Brownout = GOOD -
Test: Compass = GOOD - mag_field interference within limits (5.18%)
Test: Dupe Log Data = FAIL - Duplicate data chunks found in log (12403 and 18040)
Test: Empty = GOOD -
Test: Event/Failsafe = GOOD -
Test: GPS = FAIL - Min satellites: 0, Max HDop: 99.99
Test: IMU Mismatch = GOOD - (Mismatch: 0.25, WARN: 0.75, FAIL: 1.50)
Test: Motor Balance = GOOD - Motor channel averages = [1400, 1374, 1383, 1376]
Average motor output = 1383
Difference between min and max motor averages = 26
Test: NaNs = GOOD -
Test: OpticalFlow = FAIL - FAIL: no optical flow data
Test: Parameters = FAIL - 'THR_MIN' not found
Test: PM = FAIL - 30 slow loop lines found, max 50.64% on line 64563
Test: Pitch/Roll = UNKNOWN - 'BarAlt'
Test: Thrust = GOOD -
Test: VCC = GOOD -
I never saw any of these issues prior to RC2 and review log data from every flight on a religious basis. Does the 3.0 install completely obliterate parameters and then rewrite a new set, or does it simply change the affected ones from what's already there? Would another factory reset restore the correct ones? Perhaps someone with a working green cube solo on 3.0 (without any custom changes) send me a parameter file to test with?
At this point, somewhat confused.
Thanks
I updated my green cube Solo a couple of days ago to 3.0 and did a test flight yesterday cut short by a problem. Update was flawless. Followed instructions and did NOT load any parameter files. Before flight I calibrated level and compass.
I took off in FLY with GPS lock to default height and let it sit a minute to observer hover. I then took it about 30 away and about 40 feet up and noticed a slight CCW twitch. I corrected that and it twitched again. I then let it hover and observed that as it was facing north,it was twitching every 10 seconds or so in a CCW direction, almost as if in Pano mode. It would yaw about 10 degrees, then hold ten seconds, then yaw, hold, etc.
All of this was uncommanded/ with hands OFF sticks. When it got approximately due west, the yaw stopped. I then attempted again to take the bird out a little bit, continued to observe erratic flight with uncommanded movements, so I decided to end the flight. I had to time the landing in between yaws to avoid a flip.
The logs show a lot of different messages. There are several "EKF2 IMU0 and IMU1 in flight yaw alignment complete" messages and every 10 seconds through the whole flight EKF2 IMU0 and IMU1 compass switching messages, the timing of which seems to correlate with the yaw movements.
I really hope this is not hardware-related. It's a brand-new main board, brand new compass and green cube with only about 90 minutes flight time.
I did notice ever since RC2 that when I connect through Solex or Mission Planner, it frequently tells me "Already got parameter xxxx". Most of the time it's momentary, sometimes it hangs for several minutes and sometimes I observe it actually looping, trying to repeatedly load the same parameters. When connecting to Mission Planner, I also frequently see "Bad Logging" messages. I have only had it airborne twice since RC2 due to work, weather, timing, etc., so it's hard to tell, but I suspect my parameters have somehow gotten corrupt, perhaps during the upgrade to RC2. But with several hundred, I have no idea what to look for.
Autoanalysis of the dataflash log shows slow loop lines, duplicate data chunk warnings and a few other anomalies about mia parameters:
No of lines 140602
Duration 0:06:37
Vehicletype ArduCopter
Firmware Version V3.5.4
Firmware Hash 0b76dc76
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = UNKNOWN - No ATUN log data
Test: Brownout = GOOD -
Test: Compass = GOOD - mag_field interference within limits (5.18%)
Test: Dupe Log Data = FAIL - Duplicate data chunks found in log (12403 and 18040)
Test: Empty = GOOD -
Test: Event/Failsafe = GOOD -
Test: GPS = FAIL - Min satellites: 0, Max HDop: 99.99
Test: IMU Mismatch = GOOD - (Mismatch: 0.25, WARN: 0.75, FAIL: 1.50)
Test: Motor Balance = GOOD - Motor channel averages = [1400, 1374, 1383, 1376]
Average motor output = 1383
Difference between min and max motor averages = 26
Test: NaNs = GOOD -
Test: OpticalFlow = FAIL - FAIL: no optical flow data
Test: Parameters = FAIL - 'THR_MIN' not found
Test: PM = FAIL - 30 slow loop lines found, max 50.64% on line 64563
Test: Pitch/Roll = UNKNOWN - 'BarAlt'
Test: Thrust = GOOD -
Test: VCC = GOOD -
I never saw any of these issues prior to RC2 and review log data from every flight on a religious basis. Does the 3.0 install completely obliterate parameters and then rewrite a new set, or does it simply change the affected ones from what's already there? Would another factory reset restore the correct ones? Perhaps someone with a working green cube solo on 3.0 (without any custom changes) send me a parameter file to test with?
At this point, somewhat confused.
Thanks
Last edited:
