Since BBL changed the H2D start G-code with Bambu Studio 2.5.0 I guess they messed something up.
My H2D is now showing completely wrong information during init phase.
Examples:
Actual: Homing, checking build plate. Display: Changing filament
Actual: Moving around, seemingly without any plan. Display: Calibrating dynamic flow
Actual: Flushing (or might be flow calibration). Display: Cleaning nozzle tip
Actual: Still flushing (or might be flow calibration). Display: Auto bed levelling
Actual: Nozzle tip cleaning. Display: Vibration compensation
and so on…
@SupportAssistant
Is that a known bug with BB Studio 2.5.0 ? If not, I took a video that I could share.
Besides: My H2D was always generous with wasting filament during init phase. The new start G-code has seemingly increased the waste even more.
That’s for sure.
The reason why I noticed this is because of the excessive time it took during init, bed levelling twice, spilling a lot of filament into the poop bucket, seemingly random head movements.
It extruded some filament to the poop shoot, did other stuff, went back to the poop shoot and extruded again…
So that whole init behavior seems significantly changed with Studio 2.5.0.
That’s why I checked the display because I was really curious what the device is doing and then I saw that the display is showing bs.
@SupportAssistant Additionally, I noticed that the info in Bambu Studio and the Handy App are correct!
Only the messages on the Printers UI are out of sync.
I checked the gcode, but those strings don’t appear in there.
If I click on the message in the UI, it shows a sequence of messages and what the current one is. I guess this sequence is hardcoded in the firmware and now needs an update.
The strings are most likely hardcoded in the printer and my guess is these claim lines in the start g-code are calling the text to be displayed:
e.g.
M1002 gcode_claim_action : 29
I consider this unlikely b/c it would be a nightmare to maintain.
Every single order change during init would require a firmware update.
Word. I swear you could shave a whole minute from the startup procedure just by dropping all unneeded or repeated details here and there. They do add up.
IMHO the repeated homing of XY is dumbest of all. If you can print in 48h without re-homing XY, just why would you need to do it several times during init?
2nd homing is to pick up new Z-level after heat soak of the bed.
A bit silly to home X/Y again. I fully agree with that.
On the other hand, optimizing the time would not have a high priority for me. In relation to the time of an average print job, it’s a very small percentage.
That could be a feature, actually.
I noticed this behavior as well and I guess this might be the line causing it:
M972 S34 P0 T5000 ; heatbed plate offset detection
Hmm, it didn’t do this prior to the 2.5.0 update. It also goes so fast that I wonder if it really does something. Additionally, I also noticed it’s doing that prime line way faster than before.
I’m new to this printer, so I’m observing it to understand what it does; it’s really very disturbing that the sequence display doesn’t match, it really doesn’t help.
Yes, it’s not critical, but never say that a bug in the user interface isn’t serious; that would be a mistake! Apple, for example, understood this, hence the quality of their UI, and I’m sure this applies to Bambu as well.
