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).
@ Scott W
I have same Problems with parameter saving...
and "forgotten" Parameters after reboot....
You can read here my Posts in german Forum...
I will translate in english an post it here later...
I follow with attention this thread because I have a pixracer in mind for build a 250 racer cuad, what esc are you reccomend for this little guys?
sorry the OT question.
I have reproduced the parameter corruption issue on my Pixracer. I can confirm the problem does happen with master, not just the beta releases.
I have also reproduced the problem with px4 master, so the problem is not ArduPilot specific (I have given instructions on how to reproduce on px4 master in the PX4/Hardware gitter channel).
I am working on narrowing down the issue. I have shown that the issue only happens with the ms5611 baro driver is started, which points the finger at a likely SPI bus corruption problem (as the ms5611 and FRAM storage are on the same SPI bus on Pixracer, a key difference from other boards).
These types of issues can be quite tricky to track down, but I will see what I can do.
I have pushed a fix for the parameter corruption problem to ArduPilot master. Randy is preparing a new beta release now that will have the fix.
Copter-3.3.4-rc3-pixracer is now available through the mission planner's beta firmware link. Only one change compared with the previous version (Copter-3.3.4-rc2) which is the parameter fix.
If this version tests out well then we will make it the official version in a day or two.
Thanks for your testing especially to Scott W who uncovered the issue!
My latest version of MP does not show 3.3.4-rc3 in Beta Firmware section.
I had to load 3.3.4-rc3 manualy using load custom firmware. Saving parameters seems to be working fine.
I could not calibrate accel. After pressing Calibrate Accel got quickly all this lines you see below:
Also, after booting Pixracer, the blue LED close to USB port is not blinking (it is OFF).
Although it says "APM:Copter V3.3.3-rc2 Quad" if you look at the very top of the mission planner (in the screen shot above), you'll see that it's actually loaded Copter V3.3.4-rc3. The discrepancy happens because we've got two different versions of the software in the beta area. So the regular Pixhawks are on V3.3.3-rc2 but the pixracer version is running ahead to V3.3.4-rc3. MP can't show both unfortunately perhaps because it doesn't actually check what board is plugged in until the vehicle icon is pushed.
During the accel calibration it may have been working correctly but you were perhaps not able to see the messages because other messages were also being sent out from the flight controller. I was able to do an accel calibration just now.. perhaps just do some of the other calibrations (RC, compass, etc) and then come back and do the accel cal last.
I was a bit confused reading your previous post but now everything is clear regarding version.
Regarding accel calibration, I will do this step at the end, doing first RC, compass, etc, and see what will happen.
We've pushed out Copter-3.3.4-pixracer to the mission planner as the official release (for pixracer) for all multicopters and the tradheli. You should find that you can load the firmware from the regular icon's on Mission Planner's Install Firmware screen (i.e. no need to use the beta firmware or latest anymore).
We've included octa-quad and octa builds as well although in practice I can't see how you could fly these with the pixracer because of the 6 pwm output limit. The Tri and Heli users will also have some trouble because they may require ch7 output. In Copter-3.4 (and in latest) we allow remapping the motor outputs so once that goes out they will be ok. Until then, if people run across tri and heli users who want to use the pixracer, please refer them here and we will give them a hand getting it working.
Thanks for your testing feedback and patience!
Wahoo...mine is on order, when I get it in my Sub250g Ill send you some pics and feedback on how it works on a micro
Can anyone tell me what the status is on support for pixracer for arduplane? Is it fully supported?