This is a discussion to focus the feedback and support of ardupilot on the PixRacer board from AUAV.co.
We believe that all teething problems encountered are now resolved and so we recommend people load Copter-3.3.4 which is available for all multicopters through the Mission Planner's (and other GCS's) Install Firmware screens. Note that because regular Pixhawks are still on Copter-3.3.3 the install icon may show Copter-3.3.3 but rest assured, Copter-3.3.4 will be installed (you can check the version by looking at the very top of the Mission Planner).
Replies
3.4 isn't in beta test yet, Randy announced that is comming soon; following this post you can see that they are working hard to do it.
Hi,
I am trying to troubleshoot issues with my ESC and PixRacer. Yesterday I solderd all the connections to my Splash Drone. I believe it is XWing 40A ESCs.
And as soon as I connect power it beeps constantly every second. It is doing the same if I disconnect them from FC. The ESC calibration procedure will make them beep faster, but no reaction on the throttle. Tried diferent APM versions and no diference. ESC and motors are functional, I just swapped the controllers and PDB with ASCP4.
What are the steps to troubleshoot that?
Today I loaded px4 stack and tried to calibrate everything and ESC calibration worked. I can arm and start motors. Is something with APM stack, not the hardware.
Tridge and I played around with the onboard compass calibrator this morning and found at least two issues.
#1. the COMPASS_CAL_FIT parameter is set too low by default (it's 8 but maybe 20 would be better) meaning the calibration is too strict. Maybe some people here could help us figure out what the default should by by running the onbaord calibrator and tells us what "fit" values are reported for the two compasses. For me compass #1 was 15.6, #2 was 44.5.
So anyway.. if people could try increasing that compass-cal-fit parameter to 20 and then do an onboard calibration and report the "fit" values they see that'd help us get this default set better, thanks!
Allen,
Also I'd like to check that you're using the OnBoard compass calibrator. I've highlighted below how to kick this off from the Mission Planner.
1: Don't select anything
2: Just do the onboard calibration, which is the box in the above pic.
3: after you do step 2, it will show you the values he's asking for.. which is what he's pointing to in the pic above.
4: Enter a higher number. If you do a compass calibration first, it will show you what you actually get (as per # 3 above), then you could enter that.. But then you'll probably have to calibrate again.
Otherwise, just enter a higher number.. 20 or 40, then calibrate.
Chopper,
You're using Copter-3.3.4 it looks like from the menu bar of MP. Onboard compass cal is only available in Copter-3.4 which is still in "alpha" testing but can be downloaded by pushing Ctrl-Q on the MP's Install Firmware page.
Hmm. Very weird. Can you try raising that COMPASS_CAL_FIT number to something really high, like "40" and see what happens?
as a side note, I did a comparison of the resulting "fit"ness of the compass calibration on a Pixhawk vs a PixRacer and found the numbers were far lower (i.e. far better) on a regular Pixhawk. Pixhawk fitness was less than "4" for both internal and external compasses. For Pixracer the numbers were (as mentioned above) 15.6 and 44. Note that these numbers are not necessarily linear so I'm not saying the regular Pixhawk's compass is 4x better than the Pixracer.. I'm just pointing out that there's a hardware difference that is coming into play here.
Hi Thomas,
I think this is a bug and I am looking into it.
Could you attach a parameter file with your parameters before and after a calibration?
Thanks for your patience!!
-
46
-
47
-
48
-
49
-
50
of 110 Next