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
Agree and if I have well understand EKF has been a way to solve vibrations problem of 3DR Iris .
I really do not see any advantage with EKF onlt problems and for what ?
Vibrations are not a problem if you design a good frame and take care of motors and props balancing.
The last two auto missions I flew thank goodness I heard my Taranis tell me, "EKF variance... mode landing"!!! This is with 3.4 so I can't complain. Not sure if the same issue happens in 3.3 or what. External compass has low offsets... only using one gps. So not sure what more I could do. Don't really trust it now :[ This is with a 3dr Pixhawk not pixracer.
I think this is not good at all..
GPS cannot be trusted! In my 2 years of flying now, GPS has given me more problems than anything else.. It's fine when flying 100 meters above everything, but as soon as I come down around trees or buildings to land or fly for fun, GPS is a complete mess.. drifts 20 meters any random direction at any moment...
I'd think GPS would be the very last thing the flight controller should consider in any mode... and it shouldn't even know it exists in manual modes! (But Im not a developer and really don't know how EKF works, so maybe my opinion doesn't mean much....)
Yes, I believe 3.3 has it as well. I think you can turn it off by setting AHRS_GPS_USE = 0.
I wish I could message you a cold beer for condolences :[ Hope somebody can help sort out what it was for ya.
I have tried ever combination of firmware available past present beta. All I get is spektrum not supported or bind failed. I think the bind failure was closer to the correct firmware. I have orange receivers and original spectrum DSMX and DSM2. I never had seen the receiver go into bind mode.
The system will work automatically fine in PPM or SBUS. But it’s now about I just want to know what is not working. There is something I am just missing. Anybody got any tips. IS it windows 10 or something.
Just thought I would share one of my High School teams final project with the racer group. We have been upgrading firmware when it looked like major stability changes were made and I just uploaded todays latest build. This quad is a bit larger than some of the samples I have seen at 350cm and a bit heavy. The team designed and built this using a box of parts I supplied. The center plates are acrylic cut on a laser and carbon tubes set in 3d printed blocks. This has flown well from the first flight about a month ago and after some very basic adjustments and the latest FW it flies extremely well. After lowering throttle mid to 60 it is stable as a rock, holds altitude even in fairly windy conditions. Thanks to the hardware and firmware developers. This has been a great experience for my Students and they learned a significant amount over the last couple of months.
IMG_5931.JPG
Now that's some teaching!!! NICE!!!! Both my parents were teachers there was a saying, "Don't let an education get in the way of learning". It's awesome when they get BOTH :]
great, glad you enjoyed it!
Today I tried APM:Copter V3.4-dev (388a6683) and my ESCs are still not starting after the boot. With PX4 I am getting 5 long beeps during the boot (I am running on 5s). With APM two long beeps and then continues short beeps. I believe it is indicating that PWM is out of range. As far as I understood, if I have ESC calibrated successfully on the same hardware with PX4 I don't need to recalibrate. Is there anything that I can try to make it work with APM?
-
41
-
42
-
43
-
44
-
45
of 110 Next