Today after the new Bambu Studio update, 2 of my P2S’s are not cooling their nozzles down as per usual after printing is finished, just staying at 220c. Im waiting for a print to finish to see if number three is doing it also, but its not hardware, to coincidental, two on the same day, and after an update.
Did you edit the Start / End gcode in any way? That might be one of the reasons this would happen for all three printers.
I suggest opening a ticket so our team can further investigate, and also ensure you include a sliced model that causes this issue and the printer logs.
I have never in my life gone anywhere near G-Code.
I’ve got 3 of the P2S, and I used a few well used prints, and only today after an update did all 3 P2S printers show this problem. This is not a ticket problem, you need to look at your new studio update.
And another note, when doing a print from the G-Code demo’s on the printer, like the bed scraper, the hot end cools itself down as per usual, so its Bambu Studio that is causing the problem. You don’t need a ticket from me, you have all the information you need to let the engineers know where to look.
I also just noticed that my nozzle has been maintaining 38ºC all day for some reason, so I just manually changed it to 0ºC and it’s now going down to ambient. Seems some glitches have been introduced during the lates updates to Bambu Studio and P2S firmware.
I wanted to pitch in and mention that I have the exact same issue on my P2S after updating Bambu Studio to the most recent version. I’ll probably downgrade to an earlier version until this is fixed…
I can see the end gcode for ps2 in my version of studio, turn off hotend 6 items in total turn off, you will probaly be better getting in touch with support via a ticket as suggested by @SupportAssistant if you havent changed anything in the code and your firmware is updated
so your P2S does cool off?
i have not updated yet cause i dont want my nozzle to stay hot after printing especially since i often print while im out the House
@SupportAssistant Dont know if its relevant but its turning off the hotend before retracting filament in the end gcode setting , where most of the printers perform this after pulling back filament and it does appear a few settings are in an incorrect order compared to the other printers
I just noticed the same after my last print using Bambu Studio. I had to set heatbed and nozzle to 0 on the printer itself to make sure it cools down for the night. Hopefully a quick fix soon.
ich habe auch das problme das das hotend nicht abkühlt und bei c.a 220 grad stehen bleibt erst wenn ich es manuell einstelle schatet es ab hoffentlich wirds schnell gefixt
Having the same issue only after the most recent update, I’ve never touched the G code. Barely even knew what that was until I experienced this issue. Haven’t seen any other articles online complaining about the same problem.
Having the same issue also after recent update, noticed this morning my P2S nozzle was sitting at 220C after finishing a print overnight. Had to manually set it to 0C for it to start cooling down.
I also have the same issue after update to latest firmware. Had a print going since last night, left for work this morning, print finished around 9AM. Got home from work (9 Hours after print finished) to hear the fan still running and nozzle still at 255 Celsius. Good thing my house didn’t burn down, would have been quite a lawsuit. Bambu, PLEASE FIX ASAP!!!
Also having the same issue. I logged a bug for this. Please resolve ASAP!!! Ran a print the other day and then realized the next evening that the hotend was sitting at 255C!!! It was on for over 24hrs. This issue needs to get resolved ASAP. Please implement better regression testing.
Add mine to the list. G-code has not been altered by me and after the print, it stays at full temp for a long time, eventually it resets to 38c and stays there. I have to manually change it to 0 like everyone else has mentioned. I did the firmware a few days ago, and this problem didn’t happen then, however, I updated Bambu studio last night and found the issue this morning after an overnight print. Did a few more prints today and the issue persisted. Seems to be an issue with studio and not the firmware.