Can you not manually adjust the linkage or change the position of your horn to center it?
apm2.5 is alive (led ALIVE is on), no response neither with 433mhz link. My receiver does not suport sumppm, but avr32u2 seems ok, the otherone looks like fried. Whah kind of controller is that and can it be also changed? I ordered also 32u2, preparing to preflash it...
I am surprised we need to gave up so easy to MediaTek GPS which was performing well in old 2.8.1.
I would say would be better to make Arducopter/Arduplane to be compatible for both GPS, uBlox AND MediaTek.
I did recently ordered an uBlox for my quad, but I was thinking to put the MediaTek on Arduplane.
Now I am confused, is MediaTek not more good for Arducopter only or for Arduplane also?
Well actually i think they are ironing things out in the main code and stick mainly to ublox. When things sellte, mtk will be re-checked and parameters will be adjusted accordingly. That's only my prediction. So stay tuned. BTW i don't know if arduplane is also so much affected by the inertia (vibration and timing sensitive) stuff right now.
I'm not sure but perhaps it's the 3.3v <->5V level converter? you must be pretty handy with the soldering iron if you can replace those chips!
Don't worry, nobody is giving up on anything. As Crash says, it is just a matter of tuning things down a little.... I think. Remember, this is a release candidate, not the release. And there are a bunch of people like Scott putting it on the line to find problems (and they do).
There have been a lot of smart people making incremental changes to the code for a long time now and it is VERY hard and time consuming to get the code to take another step forward. Then there is a very large range of hardware that it needs to be tested on before we can feel confident to release.
Hopefully we can get most of the problems sorted out in the 3.rcX so the support load is a little lighter than 2.9.
Randy,once again thank you for the good work,when the V3 proper comes out,are you going to turn your attention to the PX4,yours,Marty
pour ce très bon travail, trop rapide travail pour moi !! :
j'ai juste eu le temps de tester ArduCopter 3.0. 0 RC4 sur un seul vol,très bon résultats loiter avec du vent mais des problème mission auto
j' ai hâte de pouvoir tester ArduCopter 3.0.0-rc5 quand mon emploi du temps le permettra
Merci encore pour vos efforts, Bravo
I am downloading logs to investigate a suspected "GPS failure" while loitering with 3rc4, and I noticed a new checkbox "is Arducopter?" in the log download dialog. What does that do?
...also, I just noticed some RCMAP_**** parameters and I'm getting excited. Is that for cPPM remapping? If so... WHOOT!!! :)
First, I'd like to thank the dev+test teams for delivering the goods! Sunday I did some 3rc4 testing, and for the most part everything went perfectly. My video shows excellent loiter & circle performance in medium wind (~10mph). I forgot to change circle to auto before I left for the field, so I didn't get to test that. :P Also, I had "a GPS moment" (@4:42 GPS signal drops while in loiter):
All I asked was gradually slow down and left yaw... the rest was commanded by GPS. You know, that loss of control could have ended a lot worse. This is the second time (of ~100 flights) this has happened to the quad, and the first time damaged some parts. Here is proof my uBlox was to blame:
I did have GPS failsafe enabled, but clearly it was never called during that loss of control. In this case I was flying rc4 with a mission loaded; so I am glad it did not enter LAND, but now that rc5 fixes the LAND bug I want my GPS failsafe to work. I haven't looked in to the GPS failsafe part(s) of the code, but I'm very interested in changing it (or parameter ;) ) to be more sensitive... it should not be trying to fly itself around crazy like that.