This frustrates me a lot and I am surprised that no one has said anything.
I like the Bambu printers because they are fast, but why does the firmware artificially slow the process down?
During the leveling process and the first layer checking the nozzle is cooled to 140C only to then have it wait for it to heat back up to print temperature.
So it’s continuously waiting for it to cool and then heat. It does this a few times.
There is no good reason for this especially when it has to do a mini purge any way before printing.
Either fix this or allow the ability to set “leave heater on”!
I often I do quick 5 min prints no leveling or flow control and this process wastes another 5 min!
The temperature is set low to prevent oozing during the leveling process. If you have the nozzle at the temperature to print your filament, you will experience various levels of oozing and will end up getting a poor leveling mesh.
4 Likes
That not true because it still does a mini purge and nozzle wipe before it continues printing.
Doing this is quicker than waiting all that time for it to cool and then reheat.
Not to mention the uncontrolled oozing during this process anyway.
So this is not a valid argument.
It’s not an argument, that’s why it cools the nozzle down while it’s doing the bed leveling. It does a purge and wipe before printing to prime the nozzle and then clean the nozzle before starting the print. This is all to ensure you have the best possible start to your print. If you are unhappy with that, then there may be ways to modify the start gcode, but that’s not something I’ve personally investigated.
1 Like
I’ve looked into that. On my older printers editing G-code or post process G-code editing is easy, but from what I have seen it is a firm ware thing that happens automatically as part of the start for the printer while it is doing its stuff so one has no control over it.
What you describe is correct and designed exactly to mitigate print quality issues due to oozing. temperature cycling does none of that (except maybe save a few micrograms of filament.)
If some one at Bambu or in the community feels strongly about this process then at the very least we should have a tick box to disable this option at the start just like be do for flow control and bed leveling.
That would make every one happy I am sure.
Thanks
I poked around a bit and you are probably right, it’s a firmware setting and you probably won’t be able to make the change. Unfortunately that’s a limitation of Bambu printers having closed source firmware.
I’d be curious if it’s possible if one were to use the x1plus firmware that you would be able to make changes to the leveling behavior. I really need to read up more on that firmware to understand what’s possible.
You might be better served putting in a feature request since you’re looking for adding the ability to have more control.
3 Likes
Good idea, thanks.
I will look at doing that.
you can edit the gcode to have <1m start before print. I got mine from 4 - 6:30 to 30 - 1 minute depending on the print size.
And how do you edit the .3mf file?
You also don’t want the nozzle at printing temp melting holes into the PEI bed when homing Z.
Ok I’m going to put this into perspective. Starting a print with Pa6-GF
Bed 100, nozzle 70 wait
then nozzle 265 wait (could have done this together)
then cool to 250 wait
reheat to 265 wait
then cool to 245 for bed leveling
then cool to 140 wait, then check bed type
(I dont level as I see no point in doing this every time)
heat to 265 wait
cool to 140 but dont wait, bed height check
at around 200 back to 265 wait,
cool to 140 and wait,
heat to 265 then purge and wipe and print first layer
cool to 140 and wait, check first layer
heat to 265 and wait…
Now start printing!
This as absurd!
I guess no one ever watches this but looks like each step in the process has been written by a different programmer in isolation.
1 Like
no, you edit machine start gcode in Bambu Studio… if you search for it you will find a few. I made a combo of all and that’s the result 30 sec initiation before print.
Awesome, Thank you for that.
I found it.