Where to find the beta firmware changelog for the A1

Bambu Lab Software Bambu Firmware
1

Hello,
I regularly update my beta firmware on my A1 and I have no idea what has been changed.
This evening it is OTA:01.02.02.42 which has just replaced 01.02.02.40

On the A1 wiki A1 Firmware Release History | Bambu Lab Wiki
we are still at version 01.02.02.00 with very little explanation

I would like to know if there is a place (it could be here) where these things are described ?

2

The public beta release notes communication could be improved. The private beta release notes are well communicated but there seems to be a gap in communication for the public beta release.

From my understanding here are the release notes for OTA:01.02.02.42

Release Notes:

[New Feature]

Added prompt text when enabling head wrap detection.

[Optimization]

Optimize the running logic of head wrapping detection.

[Error Fix]

  • Fixed the problem that the selectable area of the switching AMS tray is too small.
  • Fix device error when actively pausing, hot bed collision occurs after resuming printing.
3

Does that only cover update from 40 → 42?
Is there a list of what was added to go from 00 → 40?

4

Where do you find these informations ?
I’m surprised more people haven’t asked this, I can’t find a topic on it.

5

It seems odd that the firmware is pushed to our machines but we don’t know what features were added. It would make more sense to have a proper QR code for the Beta Testers when the update is pushed to our machines so we know what we are Beta Testing for them and can report issues if we find them.

6

You could always use the slicer.
Device/Update/release notes

1 Like
7

Thanks John,
They weren’t in there when the update was pushed but the note Jon listed above is there now. I believe it only covers the upgrade from .40 and .42 and not all the changes that are included with the .00->.40 upgrade.
Even if it is for the full update from .00->.42, we don’t know what helmet mode is or any other details so would be a lot nicer if they pushed a list of what the new updates contain with more details so the Beta Testers like me could help them figure out if the new code works or not. If they could issue Testing Criteria, that would be even better so we could run it through some standard tests and help them refine the code before the official release is pushed to everyone.

8

Nevermind, just looked.

I agree though, should be notes somewhere.

9

This works! Thanks a lot!