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
Personally, if I didn't have a background in IT and EE, I'd have thrown the thing on the ground and stomped on it and cussed a lot....
But, I'm used to finding bugs and solving problems for people.. (it's what I do for a living).
From a beginners perspective, it would be impossible to know what is a bug and what is a configuration error or hardware error, etc..
What I don't understand is why me and a couple others are saying we have these issues, and can reproduce them w/ multiple configs and different flight controllers.. then a few other people are posting saying 3.4 is all good and no problems whatsoever... I don't understand what the difference is there..
But from the beginning, PX4 was the only software they said worked 100%.. Everyone using APM knows they're testers.
for me i can t even calibrate my acc...so yes it s full buggy so i come back with my pixhawck and waiting
I made just the opposite experience.
With Pixracer I started with QGC/PX4 and never spent so much time (days) to configure a System and no succes.
Back to MP/AC everything was done within 30 min.as usal with Pixhawk and China Clones.
Because AC has no solution for VTOL I stopped my Project with Caipirinha Tailsitter.
And the same here, other fly with a Tailsitter, strange...
I guess you're using the onboard compass calibration on the bottom right of the MP's compass calibration screen (as opposed to the MP based calibration on the bottom left of the same screen)?
If it's the onboard calibrator could you try increasing COMPASS_CAL_FIT parameter? Maybe make it 20 or 30? Actually maybe just keep increasing it until it works and then report here how high it needed to be. This parameter controls how lenient the compass calibration needs to be to pass.
Hi, please check compass_dev_ID3 263178 default orientation settings.
X offset -659, while compass#1 and #2 have acceptable offsets suggests wrong orientation my external compass sits right above the pixracer.
Also, since compass_dev_id 66826 and 263178 are internal and unique to the chips used, I suggest to tie orientation settings to the specific I2C addresses instead of the way it is done right now.
Thanks!
If possible I think we should move the Copter-3.4 beta testing to the new ArduPilot discourse server. This replaces the old APM-Forum but is far better to work with.
for me this beta doesn t working..i can t arrive to pass the first step of acc calibration..
no problem with official version and latest mission planner.
each time i have th same error acc failed...what wrong with this beta?
@titeuf007, if you post a link to a tlog we may be able to work out why accel calibration is failing
how can i made this?
I've had a problem calibrating acc on the last build as well on one PC, on the other it calibrated from the first time. Also, telemetry via wifi module is extremely slow, the first builds I've tried were rather fast...
-
31
-
32
-
33
-
34
-
35
of 110 Next