What is the situation with recurring plate scrapes?

Currently i am seeing more and more posts in for example reddit about H2* (and other Bambu Printers) scraping the build plate.

So far i read about three different scenarios:

Nozzle scrapes the plate when nozzle offset calibration was disabled:

https://www.reddit.com/r/BambuLab/comments/1pfqcup/urgent_h2c_users_dont_disable_nozzle_offset/

Nozzle scapres the bed during calibration:

https://www.reddit.com/r/BambuLab/comments/1pkhx0i/this_should_not_happen_h2c/

Nozzle Blocker scrapes the plate when first using the left and then the right nozzle during the next print:

So far i only read about one comment by bambu that was made in a ticket regarding the offset calibration and that its a known issue. Nothing about the other things.

I find it kind of “scary” that there a currently that many scenarios where one could damage the hardware without doing something wrong. I mean, is it smart to disable the offset calibration? Maybe not. Should it damage the hardware? Definitely not.

Is there any word whats going on and when this will be fixed? @SupportAssistant ?`

I have not received my H2C yet but i am already concerned using it.

Hello

Our team is aware of this issue, and based on the reports received through Customer Support, it often happens when certain calibration features are turned off.

To help the printer adjust itself correctly before each job, we recommend keeping the calibration options enabled when starting a print - specifically, the nozzle offset calibration.

At the moment, we plan to issue the Bambu Studio configuration update in the following days, and a new beta firmware which contains a firmware fix is expected to be available by the end of the month, or early January.

Thank you

2 Likes

As mentioned. One Reddit post said it happens DURING calibration. That would be concerning.

It would be a good idea to advise which calibration features are turned off in BambuLabs view, so that users can ensure they are on in future.

I’ve reported more than 30 scenarios where this might occur.

Manual says the advanced nozzle calibration is wasted and overwritten by the standard offset procedure every time you launch a print with offset calibration on/auto. I have no issues yet. I recalibrate it every week. Device does not do any offset calibration before printing :roll_eyes:

The Bambu Studio preset update is now available.
Please make sure to install it when the prompt shows up.

The updates for this preset package are as follows:

  1. Fixed an issue where nozzles scraped the heated bed after selecting the “off” option for nozzle offset calibration during print initiation.
  2. Fixed an issue where the nozzles scraped the heated bed during the automatic dynamic flow calibration process triggered from Bambu Studio.
3 Likes

thanks! is there already something new regarding this topic: Nozzle blocker bent - #30 by sebkoe ?

It’s never clear from that pop-up. Simply clicking “Ok” installs the configurations? It would be better if it said, “Install” and even better if, after installing, it confirmed “Configurations successfully updated.”

A small UI/UX thing, but it would help my confidence.

Also previously mentioned was a firmware update as well as a configuration change for the slicer. What will the firmware update do for this issue exactly, and is the configuration update enough to prevent the issue for now?

Is the advice to just leave all automatic settings on until the firmware update? To avoid manual calibrations?

Appreciate guidance from BambuLab
Cheers

As previously mentioned, this problem usually occurs when the nozzle offset calibration is turned off.

It is recommended is to leave all calibrations options turned on at the start of a print when sending from Studio.
That way, the printer will ensure all the values are calibrated, before starting the print.

My concern is more about not damaging the printer or print sheet.

I’m a little surprised to see such an issue in non-beta software and firmware.

1 Like

Not really weird. Released software is usually tested with a lot of known user scenarios.
But sometimes a certain (unexpected) scenario can cause an issue.

Hopefully, before the next releases, those new scenarios are tested also.

But somewhere, there are always users that are able to create new scenarios that cause new issues.