Thank you RickP!
Thank you Bruno!
I'm with 3.0.rc4. Randy, excellent loiter am with mtk gps is excellent, that if no wind for the moments rtl herror as 2 meters, hold alt excellent.
Ok, so the ppm encoder (the AVR 32u2 chip) is also responsible for handling the usb communication. It definitely sounds like it's fried. It's possible to program the 2560 with an FTDI cable but I think basically the board is toast...or at least that 32u2 chip is and unless you're pretty handy with smd soldering and have a replacement...best to just get a new board.
Ok, glad that it's working well and thanks for the feedback. If you find any issues, please don't hesitate to raise them. We've found two small bugs so far (1 already corrected) so there will be an -rc5 but hopefully it will have only a few minor changes from -rc4 and I suspect we will quickly move from -rc5 to the official release.
Thank you very much.
The new RCmapper in master has wrong init values for the Copter. They are 1 off. Roll should return a 0 from the mapper instead of 1 and pitch should return 1 instead of 2.
When loading rc4 the radio calibration will be wrong. In my copy I updated
-AP_GROUPINFO("ROLL", 0, RCMapper, _ch_roll, 1),
+AP_GROUPINFO("ROLL", 0, RCMapper, _ch_roll, 0),
I'll test flight with master hopefully later today.
In the new RC4 release,
6) RTL returns to initial yaw heading before descending
Does this also apply to guided mode?
I'm still on v2.9.1b...But will be testing RC4 in a few days.
One thing I noticed in Guided mode, is that soon as its activated, the copter turns torwards me.
It would be nice if it just stayed oriented in the same direction when Guided mode was first activated.
Also in Guided mode. The copter seems to drop to about 3 feet off the ground and hover there.
Is there a separate Alt for Guided mode setting?
Basically what happens now, is that I activate Guided mode,
the copter turns towards me and drops to 3 feet into a hover.
Thanks for the info. Tridge has also found the problem and you should see a fix shortly.
By the way, I've created a branch for the AC3.0 release. This will insulate the release from changes in master but it means pulling and testing "latest" from the mission planner or firmware.diydrones.com is probably not the right place to go. Better to go to the github link above.
That was my bug - I've pushed a fix, and autotest is running over it now.
Thanks for letting us know!
Thank Tridge for the quick fiix. I'll be using the github link. I might try your version today, however there is a fair amount of wind currently.
Thank you for the quick fix,when will it be in mission planner please