We've just released ArduPlane 2.33 for your flying pleasure!
This release adds three new features over the previous release:
The new MAVLink stream handling means that when you ask for a telemetry stream you can now ask for any stream rate that is a multiple of 20ms period. Previously if you asked for 5 Hz for a stream then you got it at 3.3Hz, as we only supported 1, 3.3, 10 and 50 Hz streams. The new stream rate code is much more flexible.
The main motivation behind the new stream rate code is the ability to get the most out of the new 3DR radios. The new radios send information on their buffer state to APM, and the APM code can now adjust the telemetry stream rates to ensure that the internals buffer in the radio doesn't overflow. That allows you to run the serial link to the radio at a much higher baud rate than the radio link is using. So you can adjust the air data rate to improve range without having to reconfigure APM and the radio for a different serial rate.
The end result is that if you have a 3DR radio you no longer need to carefully adjust your MAVLink stream rates to fit in the radio bandwidth. Just ask for a high number and the APM will adjust the timing to whatever fits.
The XBees will continue to be supported, as will any other radio that supports transparent serial and can be connected to the telemetry port.
There will be some features that will only work with the 3DR radios, for example the automatic telemetry rate adjustment, but that won't affect your ability to use an XBee with new firmwares.
I did more testing. I had one serious problem. Not sure if i did something wrong, or something else happened.
I took off manually, than switched to RTL, than the plane rolled over.
Only happened once. I made roughly 4 more flights today, and had no problem at all. Only this strange error happened.
It was a warm day. around 30°C
Attached the logs, and a video.
(On the video i can see that AMP has no clue about roll position. you might see more than i do. i hope. :) )
Here is the video.
And the logs:
I have attached one of my yesterdays log.
I had a few very short failsafe, because I went down to a valley, so there was lots of things between me and my plane. :)
It was fun! :)
Yet another bug of connectivity in Arduplane 2.33, no connectivity issue with Arducopter 2.54 and Arduplane SIM, see the video yourself;
I don't think this is a bug.
Personally, I've never used the update of APM Planner. I only use Arduino to update the firmware of my APM. But every time I update I need to do reset, in order to successfully connect using Mission Planner (or QGround Control). Have you tried to make a reset after update?
Hi Pedro, I faced same connectivity issue when I uploaded the firmware using Arduino and after reseting the board.
No such connectivity issue is observed in uploading the firmware Arducopter 2.54 and Arduplane SIM, using Mission planner and same board.
Having the same problem here, but not when connecting trough usb, only when using xbee, and only when using arduplane 2.33.
No issue with Arducopter etc.
Did 2.34 solve this problem for you?
No have the same issue on 2.34 :(
But still works good on arducopter