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
I just did an Accel calibration and it worked just fine. I used latest 3.4 dev build from today.
Several things do not work with 3.3.4.
1) Pixracer has two internal compasses only usable with 3.4
2) Must not have done enough dancing with the copter.
5) Only works with 3.4 dev
6) WiFi only works with 3.4 dev
7) Different shunt values. 3=13.69 and 6=48.19 to start.
8) Only if your cable is to short.
Also write down your compass offsets after your done to make sure they don't change later.
Michael, you seem to be a lucky man :). I use MP 1.3.37 build 1.1.5960.18090 and latest 3.4 dev build from today. Accel calibration is not possible. Getting always "Calibration Failed" message and after that HUD display is dancing with message: "Error pos vert variance" and "Bad AHRS". EKF Status shows "Position Vert" full red. Any idea what does it mean?
I can calibrate Accel only with stable/beta 3.3.4-pixracer version. I give up for now :(.
I decided to give ArduCopter a next chance. Loaded latest MP beta and latest AC 3.4dev today, then V frame selected, then compasses calibration (all axes green values), then RC calibration - RC1-4 from 100 to 1900. Then started ACC calibration: level, left, right, down, up, back and... calibration failed .... fu.......ck... again? :(
Even more, I see "PreArm: RC not calibrated" but I did RC calibration a few times. I have FrSky X4RSB working in SBUS mode.
I have stated this problem before I am in the same boat as you . I have never been able to ACC calibrate in MP without a fail. Only ACC I can calibrate in MP is LEVEL. The only full ACC calibration I can do is using QGC, so this is what I have done to get the ACC calibrated. then I go back to MP. It has worked for me.
My problem is I cannot calibrate ACC even using QGC. But if I use AC 3.3.4 beta I can calibrate ACC in MP or QGC.
Just want to mention,
I have been able to calibrate my gyros with 3.4dev in MP.
BUT, occasionally my HUD dances/spins around, too. And then the EKF meter position and velocity, etc, all go up into the red.. This is while just sitting on my workbench. It''ll be fine for several minutes, then I notice the HUD getting wobbly, then it starts spinning and EKF goes into the red.. Then it settles down again.
Plus the other issue where autopilot assisted modes do not work, as per my logs a page or two back.
Scott, I had what I think was the same issue.
I moved my electronics around and it seems to have eliminated the problem, specifically moved my stackable ESC away from the FC using some standoffs.
I am also using the onboard-calibration now and just external compass checked when I calibrate.
I should have mentioned, I think my GPS may have something to do w/ my HUD spinning issue..
Not positive, but I noticed my purple track in the MP HUD jumped about 50 meters at the time it was spinning..
The GPS glitching like that is not new... I'm using an RTFQ GPS at the moment, and they all have this issue for me in any version of pixhawk and APM.
But, the HUD spinning and EKF going red when it happens is new.
Thanks for the interference advice.. My ESC's are away, but my telemetry modem is right on top of the pixracer.. and the power board is directly under it....
This is really strange. I don't suspect my board is affected because I can calibrate Accel in AC stable/beta 3.3.4 version, also PX4 stack calibration is working fine. I'm a noob user only but there is for sure something suspicious in AC 3.4dev version.
Thanks for suggestions Michael .
I will give a try to 3.4 asap