View unanswered posts It is currently Tue May 24, 2016 6:43 am

Reply to topic  [ 2 posts ] 
 APM:Plane 2.78 released 
Author Message

Joined: Tue Jul 02, 2013 3:46 pm
Posts: 329
I've just released APM:Plane 2.78. This is a bug fix release for a number of important issues found in the 2.77 release.
The changes in this release are
Fixed sensor start-up on the APM1
I'm embarrassed to say that I didn't test the APM1 for the 2.77 release as my APM1 had died. It was a trivial fix, and the APM1 is working again in 2.78
Pixhawk Barometer fix
Fixed a potentially serious bug on Pixhawk if the board is flown in high temperature environments. If the board temperature gets above 65 degrees C then some boards would get bad barometric readings, thus giving bad altitude readings. This fix was a change in the GPIO settings on the SPI bus used to talk to the MS5611 barometer. Many thanks to Darrell Burkey for supplying the log file that found this bug.
Fixed LED behavior on Pixhawk
The large 3 color LED should now correctly display the failsafe and GPS status
Improved PX4 and Pixhawk compass calibration
We now run a strap calibration on every boot which improves compass accuracy by a small amount
Added RSSI_RANGE parameter
This allows you to scale your RSSI input to match your receiver
Fixed GPS health status in MAVLink
The GPS health bit will now show as unhealthy if the GPS does not have 3D lock. Thanks to Iskess for reporting this issue!
Thanks to everyone who gave feedback on 2.77, much appreciated!
Happy flying!

Wed Jan 29, 2014 8:47 pm

Joined: Tue Jul 02, 2013 3:46 pm
Posts: 329
I've just released a bug fix for 2.78, which is called 2.78b. This fixes a bug in the new RSSI_RANGE option spotted by forum member Valince.
The bug was that RSSI_RANGE used the same parameter key in EEPROM as the RC1 parameter set. That is an important bug, as setting RSSI_RANGE would cause the RC1_MIN parameter to be reset to its default value of 1100 on the next boot. Additionally, setting RC1_MIN would cause RSSI_RANGE to reset to its default value of 5.0.
Many thanks to Valince for spotting this bug!
I've now pushed a change to our parameter handling code to automatically check for this type of error on every boot, so it can't happen again in the future.
Cheers, Tridge

Thu Jan 30, 2014 7:20 pm
Display posts from previous:  Sort by  
Reply to topic   [ 2 posts ] 

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software for PTF.