Rover-4.5.5 released!

ArduRover Rover 4.5
1

Rover-4.5.5 has been released and should appear in the ground stations as the official release within a few hours. It will also appear here on firmware.ardupilot.org

The changes vs 4.5.4 are in the ReleaseNotes and copied below

Changes from 4.5.4

  1. Board specific enhancements and bug fixes
  • CubeRed’s second core disabled at boot to avoid spurious writes to RAM
  • CubeRed bootloader’s dual endpoint update method fixed
  • fixed IOMCU transmission errors when using bdshot
  • update relay parameter names on various boards
  • add ASP5033 airspeed in minimal builds
  • added RadiolinkPIX6
  • fix Aocoda-RC H743Dual motor issue
  • use ICM45686 as an ICM20649 alternative in CubeRedPrimary
  1. System level minor enhancements and bug fixes
  • correct use-after-free in script statistics
  • added arming check for eeprom full
  • fixed a block logging issue which caused log messages to be dropped
  • enable Socket SO_REUSEADDR on LwIP
  • removed IST8310 overrun message
  • added Siyi ZT6 support
  • added BTFL sidebar symbols to the OSD
  • added CRSF extended link stats to the OSD
  • use the ESC with the highest RPM in the OSD when only one can be displayed
  • support all Tramp power levels on high power VTXs
  • emit jump count in missions even if no limit
  • improve the bitmask indicating persistent parameters on bootloader flash
  • fix duplicate error condition in the MicroStrain7
  1. Other minor enhancements and bug fixes
  • specify pymonocypher version in more places
  • added DroneCAN dependencies to custom builds

Thanks very much to everyone who has worked so hard on this release including the beta testers!

5 Likes
3

has the Q_AUTOTUNE setting been returned for matek f405-vtol

4

Not sure to what you’re referring. That feature does not exist on Rover firmware.

5

Ouch. It’s a rover. I confused it with an airplane.

6

Why is there never any release notes for Plane? In MP it tells me there is a new version - points me to the release notes here but I never see any for Plane. Am I missing something. If I change the filter to the stable version for Plane as of (2024-08-16) it shows 4.5.2 - which is not correct.

7
8

Hi @ieThis,

The releases are a bit of a manual process and while we are bringing all the vehicles closer together there are still some differences in procedure. I guess you mean that there’s no new topic created for Plane releases? Instead I think what happens for Plane is a new posting is made on this single large thread.

I guess you’d prefer we create a new topic for each release like we do for Copter, Rover and Tracker?

9

Hi

Yes, I usually end up finding that thread after a bit of digging (I could solve that by bookmarking it…)

The process used for Rover/Tracker/Copter seems more optimal as Mission Planner Links to https://discuss.ardupilot.org/tag/stable-release when a new version is available. As those variants are on that page, Plane is not.

image

It seems logical to me that the list of stable release tags would include Plane.

The same is true on the Github releases page https://github.com/ArduPilot/ardupilot/releases - there is currently no release of Plane4.5.5 there.

This hope this doesn’t sound pedantic, I do understand this is a large project that has been running a long time with many developers - so please don’t take it as a criticism.

The bottom line is that often I need to look at the code to understand what a change is really doing - a single sentence in a release note can’t really describe it fully. Just seems there should be a more direct path to the code from a prompt like that in MP, that doesn’t end up with me ignoring it for ages :grinning:

Thanks
Jules.

1 Like
10

Hi @ieThis,

Thanks for the feedback. I’ve gone ahead and created the Plane.4.5.5 release on Github (this was just an oversight I think).

BTW, we’ve also got a “4.5 Backports” project that lists the individual PRs that were included in each point release. We could look at linking this from the Github project and maybe the official release announcement as well.

11

By the way, we discussed this on the weekly dev call earlier today and the answer to why we don’t create a new topic for each Plane release is because when we re-use the old topic, everyone who has ever participated in beta testing gets an email notification (unless they’ve turned them off).

One of our core issues these days is finding enough beta testers so we hope/hoped that more notifications will stir up more participation in the beta releases.

Anyway, we have varying opinions in the team on the best way to handle this so all feedback is welcome!