This is a discussion to focus the feedback and support of ardupilot on the PixRacer board from

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).

Views: 99087

Reply to This

Replies to This Discussion

Looking forward to getting my PixRacer and testing it out. 

A couple questions... if the PixRacer does %95 of what a Pixhawk does what is the %5 it doesn't? I know it doesn't have as many servo outputs is that about it? It seems to have all the other ports and even supports Taranis Telem native with no Teesny so I hear [ with the correct Lua set up of course ] . Nice! But what are the %5 limitations? 

Even though it doesn't have more than 6 channel servo outputs can the board still take advantage of the higher channel numbers APM copter code allows for added radio control??  For instance you can select ch 7-8 for auto tune etc. Is that still available on the PixRacer even though it only has 6 ch outputs?



The limitation is mainly the 6 PWM outputs, the PH1 has 8 PWM Outputs and 6 AUX Outputs. This is due to the lack of the 2nd MCU that handles IO on to PixHawk1. With PPM / sBus / DSM RC input, you are only limited by the receiver that is connected.

Sweet. I'll be all set then. Thx. 

PhillipK from and I spent some time to narrow in on the issues with ardupilot and PixRacer, in particular the most serious issue is this "Bad Gyro Health" message that appears intermittently.  It may happen more or less with Copter-3.3.3 vs Copter-3.4-dev but it can certainly happen with either firmware.

What we see so far is that IMU1 is appearing as unhealthy in the logs even though it is actually returning data.  So you can see in the graph below that IMU1 is reporting gyro and accel values but the GyrHlt and AcHlt column is all zeros.
So we don't have a solution yet but we're on the case and it's a very high priority to get this sorted out.

Ah, I've created a couple of issues here and here to capture this problem and also a report from PhillipK that the SBUS input isn't working.

You can install px4-v4 (Pixracer) with APM Planner 2.0.19-rc5* (OSX version here) or withQGroundControl**.

*linux and windows versions to follow, but can be build from source

** I know it works with master, not sure if the build as the code in, i'll check

Not only SBUS... PPM (Hott) doesn´t work either. You can see all the stick movements switches/dials @MP but MP keeps on claiming no RC Receiver /RC FS  @ recent Copter-3.4-dev uploaded with QGC daily.

Also recognized : Bad Gyro Health (not always.)

From all us Mac users... Thanks Bill!

As long as I know Pixracer is missing fail-safe co-processor of Pixhawk. Does it mean less reliability?

If you are flying a quad and the main processor stops working it is game over either way. If you stick to stable software releases, your risk is very low as these micro controllers are very reliable.

wow, thanks!  It's not just me, then :) :)

So, if there are only 6 RCout pins then there are no relay pins to set or use?

So no way to turn lights on or off?

Reply to Discussion


© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service