I’m experiencing an issue with my P2S printer where, after the model finishes printing, the extruder stays at the last printed position for about 1–2 seconds. Because of this pause, it leaves artifact on the finished model.
Has anyone else encountered this issue?
If so, I’d appreciate any insights into what might be causing it or how to fix it.
Thanks!
This isn’t normal behavior.
What program are you using to slice models for your printer. If you are using Bambu Studio are you able to post the “Machine end G-code” in the Printer settings?
Below is an an example of where you would find this (image of the X1C instead of the P2S but it is in the same location)
Timelapse recording maybe? Do you have that enabled?
From machine end g-code of my H2C:
;===== machine: H2C end =====
;====== date: 20251111 ======
G392 S0 ;turn off nozzle clog detect
M993 A0 B0 C0 ; nozzle cam detection not allowed.
M400 ; wait for buffer to clear
G92 E0 ; zero the extruder
G1 E-0.8 F1800 ; retract
M400
M211 Z1
G1 Z{max_layer_z + 0.4} F900 ; lower z a little
M640.2 R0
M1002 judge_flag timelapse_record_flag
M622 J1
G150.3
M400 ; wait all motion done
M991 S0 P-1 ;end smooth timelapse at safe pos
M400 S5 ;wait for last picture to be taken
M623 ;end of "timelapse_record_flag"
M400 S5 is a 5 second wait. From what I can tell it hasn’t moved the toolhead away from the print yet, just raised it a bit (lowered bed) and relieved the extrusion pressure.
EDIT: G150.3 should move to some dedicated parking spot apparently? So I could be wrong about it hovering over the print.
Personally I’ve disabled timelapse (in the dialog when sending to printer) since it causes unnecessary moves, pauses, and similar shenanigans.
-Max
Not as of yet but will be on the lookout.
;======== P2S end gcode ==========
;===== 2026/01/05 =====
M400 ; wait for buffer to clear
G92 E0 ; zero the extruder
G1 E-0.8 F1800 ; retract
G0 Z{max_layer_z + 0.8} F900
; pull back filament to AMS
M620 S65535
T65535
G150.2
M621 S65535
G150.3
M400 ; wait all motion done
M1002 judge_flag timelapse_record_flag
M622 J1
M991 S0 P-1 ;end smooth timelapse at safe pos
M400 S5 ;wait for last picture to be taken
M623 ;end of "timelapse_record_flag"
M104 S0 ; turn off hotend
M140 S0 ; turn off bed
M106 S0 ; turn off fan
M106 P2 S0 ; turn off remote part cooling fan
M106 P3 S0 ; turn off chamber cooling fan
M106 P10 S0 ; turn off left aux fan
M400 ; wait all motion done
M17 S
M17 Z0.4 ; lower z motor current to reduce impact if there is something in the bottom
{if (80.0 - max_layer_z/2) > 0}
{if (max_layer_z + 80.0 - max_layer_z/2) < 256}
G1 Z{max_layer_z + 80.0 - max_layer_z/2} F600
G1 Z{max_layer_z + 78.0 - max_layer_z/2}
{else}
G1 Z256 F600
G1 Z256
{endif}
{else}
{if (max_layer_z + 4.0) < 256}
G1 Z{max_layer_z + 4.0} F600
G1 Z{max_layer_z + 2.0}
{else}
G1 Z256 F600
G1 Z256
{endif}
{endif}
M400 P100
M17 R ; restore z current
M220 S100 ; Reset feedrate magnitude
M201.2 K1.0 ; Reset acc magnitude
M73.2 R1.0 ;Reset left time magnitude
M1002 set_gcode_claim_speed_level : 0
M1015.3 S0 ;disable clog detect
M1015.4 S0 K0 ;disable air printing detect
;=====printer finish air purification=========
M622.1 S0
M1002 judge_flag print_finish_air_filt_flag
M622 J1
M1002 gcode_claim_action : 66
M145 P1
M106 P2 S255
M400 S180
M106 P2 S0
M623
M622 J2
M1002 gcode_claim_action : 66
M145 P0
M106 P3 S255
M400 S180
M106 P3 S0
M623
;=====printer finish air purification=========
;=====printer finish sound=========
M17
M400 S1
M1006 S1
M1006 A53 B10 L50 C53 D10 M50 E53 F10 N50
M1006 A57 B10 L50 C57 D10 M50 E57 F10 N50
M1006 A0 B15 L0 C0 D15 M0 E0 F15 N0
M1006 A53 B10 L50 C53 D10 M50 E53 F10 N50
M1006 A57 B10 L50 C57 D10 M50 E57 F10 N50
M1006 A0 B15 L0 C0 D15 M0 E0 F15 N0
M1006 A48 B10 L50 C48 D10 M50 E48 F10 N50
M1006 A0 B15 L0 C0 D15 M0 E0 F15 N0
M1006 A60 B10 L50 C60 D10 M50 E60 F10 N50
M1006 W
;=====printer finish sound=========
M400
M18
@JonRaymond here’s my end gcode
@MaxThreeD timelapse is off
Thanks a lot for your involvement.
UPD: From my 2 days of observations, it doesn’t happen every time — about 2 out of 4 prints
Do you have an USB drive installed? If you do, does removing it change the pausing delay?
No, I don’t use a USB drive.
I want to create a test matrix and disable printer features one by one (AI detection, etc.) to check which one affects this issue.
I believe I’ll come back in 2–3 days with the results.
I have the same happening on my machine. Stock P2S machine gcode. No usb drive, no timelapse, all AI detections turned off.
My workaround has been to add a square and make it as tiny as possible so it still prints, then i put it last in the printing order (Per object printing required). It’s like 1 layer, 3x3mm. Printed in not even one second and since it’s the last model it gets that blob/artefact.
Probably worth creating a ticket as it seems there might be a bug in the firmware.
Thank you or reporting this problem.
For everyone who is experiencing this problem - Please open a ticket and share details about the issue including pictures and the printer log.
Our dev team will be able to quickly troubleshoot the issue and patch it ASAP.
Those are unfortunately the only parts i had on hand with those marks.
Not sure how similar the ones are for @John_The_Mesh
Yep, almost the same view 
Same issue here on my new P2S. Newest firmware and Bambu Studio. Quite a contrast with how it and my A1 finishes prints. The A1 nozzle moves away immediately at the end while the P2S nozzle just sits for a bit, leaving a blob on the print.
What do you mean here?
Is this a fact or a personal conspiracy theory?
does disabling via the app not achieve the same result?
No conspiracy, everything it does is a result of the G-code specified in the machine’s “Time lapse G-code” settings. Which depends on the type of timelapse selected and if it was enabled to begin with, and I imagine may vary by printer.
Sorry I’m not familiar with the Handy app at all. The option to enable or disable timelapse entirely is available from both Bambu Studio and via the printer UI itself when sending/starting a print, so I can only assume it would also be present in the app, but 
.
-Max
Same issue here since the beginning. (ordered on day 1) I had timelapse active for quite some time, then disabled it. Didn’t change anything. I would make sense it pauses to create the end photo / timelapse – but that would be a very dumb design imho. 
I rarely watch the end of a print, so I’m not sure how often it happens. But yesterday I’ve got a blob again.
There was another thread about this issue:
https://forum.bambulab.com/t/problem-with-end-of-print/210002
I think there are two interesting commands in the end code:
>> G0 Z{max_layer_z + 0.8} F900
Shortly after print end, Z axis will be moved by +0,8mm. We could set this value to maybe 5mm, so the nozzle got more room to the top surface of the print.
>> M400 S5
A 5 sek. wait for the end picture to be taken. Could be set to 0, so the toolhead does not wait for the picture.
Both changes could solve the issue.
I’m glad I found this thread because the exact same thing is happening on my P2S. I honestly thought it was just “how the printer finishes a job” until I read everyone’s posts here.
In my case, the nozzle pause at the end leaves a tiny but unnecessary mark/artifact on the top surface. I don’t mind the pause itself if it’s doing something useful, but does it really have to pause while still touching the print? That’s the part that causes the blemish.
Just adding my voice so the team knows it’s affecting more users.
Can anyone else confirm? It seems that the latest 1.02.00.00 firmware update from 2026-04-09 may have fixed this issue. I haven’t been paying attention to every print, but it seems like the print head now immediately pulls away when finished.
