CubeBlack can not detect its baro

Getting auto-analysis fixed up would be a big help - especially for us novices.

Even though it’s out of date, it still reports optical flow settings. Helpful - more so if I had high confidence in them.

A bit off topic - but do you know who supports MavExplorer? I like MavExplorer’s MagFit tool - but I have to use a revision that’s 5 or 6 revisions out of date - MagFit doesn’t seem to work on the newer revisions.

1 Like

It should be working…

I posted on your post about this issue. Also what Discord link isnt working? We need to replace all of those links soon anyways…

Just checked Auto-Analysis. Yes - seems to be working again.

I noticed that it’s not reporting motor balance they way it used to. Now it shows: “Test: Motor Balance = UNKNOWN - ‘QUAD/X’”

I’ll have to spend more time to verify other details. But looks really promising - please extend my thanks to those who did the work to bring it back to life!

I’m not sure what “not working” Discord link you’re referring to.

I’ll check MagFit on the latest MavExplorer. I’ve been using 1.8.39.

Just installed and tried the magfit tool on the latest MavProxy/MavExplorer.

Seems it’s all sorted out now. I’m not sure how long it’s been since I’ve tried to use the latest version - probably 3 or 4 months.

Thanks to the MavProxy/MavExplorer developers!

Here’s my test results from an old BIN file I grabbed:

C:\Users\joest\AppData\Local.mavproxy\Rover.xml Unicode strings with encoding declaration are not supported. Please use bytes input or XML fragments without declaration.
Attitude source ATT
Earth field: Vector3(227.68, -22.42, 430.26) strength 487 declination -5.6 degrees
Extracted 529 points
Current: Vector3(-125.39, -278.06, 493.29) diag: Vector3(1.01, 1.07, 0.80) offdiag: Vector3(0.01, 0.00, 0.06) cmot: Vector3(-0.50, 2.54, 0.23) scale: 1.00
Optimization terminated successfully (Exit mode 0)
Current function value: 3.7936059694116366
Iterations: 52
Function evaluations: 749
Gradient evaluations: 52
New: Vector3(-119.72, -253.13, 492.31) diag: Vector3(1.00, 1.07, 0.80) offdiag: Vector3(0.02, -0.02, 0.05) cmot: Vector3(0.56, 2.07, 0.01) scale: 1.00
COMPASS_OFS_X -119
COMPASS_OFS_Y -253
COMPASS_OFS_Z 492
COMPASS_DIA_X 1.000
COMPASS_DIA_Y 1.068
COMPASS_DIA_Z 0.800
COMPASS_ODI_X 0.022
COMPASS_ODI_Y -0.023
COMPASS_ODI_Z 0.047
COMPASS_MOT_X 0.564
COMPASS_MOT_Y 2.065
COMPASS_MOT_Z 0.008
COMPASS_SCALE 1.00
COMPASS_MOTCT 2
MAV>

Good to hear.

Ahh this is a rover. I was like that is really nice mag data… You may want to be sure you did a bunch of circuits to get good data for the fitting tool. I have seen rovers with much worse fits :wink:

Nope - a copter. Why did you think rover?

Because your initial calibration was pretty darn good then.

I was thinking a rover maybe because with those you wont have as much 3D dimensional changes. And so calibration errors in some axes may not show up as easily since you are not moving much in those axes.

Thanks for the compliment on the compass calibration. I don’t know when this flight took place, but I’ve used either MagFit or “compass learn” to do the calibration. So the credit is due to the developers - all I did is push the button…

1 Like