LiDAR Filament Calibrations do not work in FW 1.00.09.01

I updated to FW 1.00.09.01 and perhaps the most annoying problem I’ve run in to - the automatic Flow Rate and PA calibrations do not function.

I have a new filament loaded in AMS slot B1. I tell it to run a flow rate calibration against B1 after choosing the material profile I want it to update.

It runs through the normal heating and homing procedure, then parks over the purge chute and pauses for a minute before trying to run the test without any filament loaded at all. If I manually load filament before running the calibration, it will cut and unload before the pause, and attempt to run the test without any filament loaded.

If I load the filament in the external spool and start the calibration, it simply does nothing. Studio just sits waiting for a result to be delivered and the printer will eventually go to sleep.

The exact same behavior is exhibited when attempting a PA (“dynamics”) auto calibration.

Normal printing, manual calibration prints, etc - all work fine. Nicer even than before. However it seems anything related to the automatic tests is completely broken though.

I’ve power cycled everything, restarted everything, no change in behavior. Tried different materials, different AMS slots, no change. Doesn’t matter if it’s generic or BBL filament, the exact same issues persist.

Anyone else? Any tips I’m missing?

1 Like

I’m using version 1.09.00.01, which I believe you’re referring to as well.

I’ve completed all calibrations without any issues on this version. However, I’ve encountered a couple of other problems. One is a desynchronization between the printer and Handy—Handy might show the fans running at 30%, while the printer itself reports 100%.

Another issue is related to AMS. Even though I have a K-value stored for “Support for PA/PET,” I can’t apply it directly from the printer interface—I have to set it through Bambu Studio.

Have you noticed any other issues with this release?

I have the same Problem, when i would like to start autocalibration external. While sending the job, BambuStudio does nothing. Internal i did not test it. The Problem starts with FW 1.00.09.01.

1 Like

I wonder if your firmware update became a little bit corrupt during its update process.

I’m fully updated and have no issues with the lidar filament calibrations.

Maybe try downgrading firmware, power cycling, then redoing the update. Make sure your internet connection is strong and you don’t have any other connections pulling large amounts of bandwidth during the update.

There is a checksum validation that occurs while installing firmware; it should prevent this. Either way I’ve done so and the problem persists.

For giggles I tried a calibration print while I had it back at 1.08.02 and it did work

Hmm. That’s pretty strange. The only other idea I can think of, short of sending the logs into Bambu, is maybe trying to do an offline SD card firmware update.

I’ve downgraded and re-upgraded with no effect. I’ll open a ticket to see if I can get anything from support.

1 Like

I’m also having problems with calibration. When I select automatic filament calibration, the printer just does it without filament, meaning it’s idle. Only manual filament calibration works.

yep, got same issue… any feedback from BambuLab ?

Starting with FW 1.00.09.01 I also have same problem with calibration. Any solution?

They asked me to downgrade again to confirm if it actually works or not before moving forward with any troubleshooting in 1.09. So I’ve rolled back (again) to 1.08.02 and it works, went ahead and collected logs anticipating they’ll ask for them later. Waiting to see what their next move is.

1 Like

Samer problem here but for me I had to downgrade and update twice to make it works.

Yesterday, for some reason, everything works fine in the last version, after power off and power on, same problem again

Got a reply today:

The report for bug is loged. Our team is working on it and it will be fixed in future release

Are you OK if I will proceed with marking the ticket as “Resolved.”

So… I guess that’s where we’re at. I asked if there’s any ETA on the next firmware release but I doubt I’ll get a solid answer.