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
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
Hi all,
I have some serious problem with accel calibration on my Pixracer with loaded latest AC3.4 master. I can't calibrate accel. The message is "Calibration failed", nothing more. I have tried with Mission Planner (USB, WiFi), Tower (WiFi), QGC (USB, WiFi). Same result for all applications.
Strange thing, when connecting via QGC I see "Vehicle 1" and "Vehicle 200" - to see parameters I need to choose "Vehicle 1". When connecting with Mission Planner, I see "Getting Params 1" and shortly after this, see "Getting Params 200" - this never can be downloaded. What's this?
Just short remark: If using PX4 stack, I can calibrate accel without any problems.
No idea what could be wrong :(
I wasn't able to calibrate the accelerometer using MP with the dev firmware, but I could when I switched over to APM Planner.
BTW, MOT_PWM_TYPE=2 didn't work for me. What ever I set it to it didn't work, I could arm but that's about it.
Switching back to 3.3.4, I was able to get the motors to spin but it was low speed spin or full blast... nothing in between, so not flyable at all.
I have 30a BLHeli ESCs with PWM input turned off, so getting OneShot working would be awesome.
I cannot try before Friday , I'm out for work.
This is strange. I'm only able to calibrate accel if using latest available beta file for Pixracer, if I'm right this is ArduCopter-v4.px4 file generated on 2016-02-25 at 01:38 with size 611K.
Any newer ArduCopter-v4.px4 file from master branch does not allow me to calibrate accel.
I use 3.3.4 and was able to calibrate accellerometers, at first it was not possible but after completing other mandatory settings and then doing level I tried again and it works.
No MOT_PWM_TYPE in that version.
-
53
-
54
-
55
-
56
-
57
of 110 Next