Rover 4.7.0-beta5 available for beta testing!

Rover-4.7.0-beta5 has been released for beta testing and can be downloaded using Mission Planner, QGC or directly downloaded from firmware.ardupilot.org.

If you’re using QGC, the daily build has been updated to better handle the parameter changes in 4.7 and will soon be available.

The list of changes vs 4.7.0-beta4 are in the ReleaseNotes and copied below.

  1. Board specific changes
  1. Library changes
  • AP_Logger: Named Value Float dataflash logging drops fixed (@tridge, PR:32975)
  • AP_Logger: LOG_MAV_RATEMAX default changed to 10 (@tridge, PR:33030)
  • AP_Logger: logging over MAVLink speed significantly improved (@tridge, PR:33020)
  • AP_NavEKF3: barometer offset logging added (@rmackay, PR:32931)
  • AP_NavEKF3: bugfix to prevent covariance state corruption (@tpwrules, PR:32177)
  • HAL_ChibiOS: Oneshot pulse corruption upon safety-enable fixed (@tridge, PR:32979)
  1. Copter specific changes
  • Increment data added for several parameters (@ES-Alexander, PR:32949)
  • Weathervaning bugfix to properly stop weathervaning (@IamPete1, PR:33019)
  • Land and Payload place waypoints fixed to use correct altitude and spline waypoints (@lthall, PR:32634)
  1. Helicopter specific changes
  • PID scaling support fixed (@lthall, PR:32725)
  1. Sub specific changes
  • Increment data added for several parameters (@ES-Alexander, PR:32949)

We are getting reasonably close to the official release but there will be a beta6 to resolve some outstanding issues.

All testing and feedback is greatly appreciated!

1 Like

Thank you dev’s for all the work. Although I’m not the most active user, I do love playing with self navigating rovers.

In the last few firmwares, and this 4.7 Beta5 I miss the NTF_DISPLAY_TYPE parameter? I think the option of having a tiny oled monitor displaying important info is really helpful.

And now that I mentioned it. Would it be a lot of work to incorporate a different oled driver? That way you can use 128x64 1.3” Oled displays instead of the ‘ol puny 0.96”.

Edit* I encountered this when using a SpeedyBee Wing F405 V1.

Edit2* Is it not included to save memory?

With that Flight Controller, yes. Use the Custom Firmware Builder and enable I2C Displays and try that.

oh WOW! Didn’t know about that feature. LOVE it! Thank you! I just did a build to my specifications.

1 Like