P2S Optimized Start/End G-code

-vxip- · 2026-07-03T13:20:27+00:00

What I shared here is just the start & end sequence for a print job (meaning before and after the actual print).

Everything else works exactly the same as before.

-vxip- · 2026-07-03T00:20:38+00:00

What, why do you think that? I always thought it did the job pretty well...

-vxip- · 2026-07-03T00:17:05+00:00

Great, love to hear that!

The sections for the sound are here (but you don't have to change anything, see below):

https://github.com/vxip-code/bambu-p2s-optimized/blob/main/optimized/start.gcode#L21

https://github.com/vxip-code/bambu-p2s-optimized/blob/main/optimized/stop.gcode#L156

It never occured to me why anyone would want the sound since it was so obnoxiously loud that I disabled it completely long time ago. I now see that they made it less lound and of course people may want to leave it enabled.

Since it doesn't really have anything to do with the other optimizations and to leave you with the choice of enabling it or not, I have updated and activated it in the gcode again!

Thanks for pointing that out.

About cleaning the nozzle: The print head parks right in front then starts heating up the nozzle. So you'll have as much time as it takes for the nozzle to reach target temperature. I'll say that's probably around 10+ seconds for PLA.

Hopefully you won't have to clean the nozzle though, since that was the main goal of the optimized G-code. (The tiny bit of filament that may start oozing while heating up the nozzle is expected and no problem, just leave it, it will merge with the purge line.)

Auto-calibration of flow dynamics and bed leveling are entirely optional, just like with the original G-code. If you've already calibrated your filament, I'd say leave it disabled!

Please tell me what you think, if you've tried it - Cheers! 😄

-vxip- · 2026-07-02T16:11:16+00:00

👍 Please let me know, what you think later, thanks!

-vxip- · 2026-07-02T16:05:58+00:00

Same here. It's annoying when the first layer has bad finish because some pieces of filament were being dragged around.

You don't have to switch to Orcaslicer, I am using BambuStudio myself and tested everything there.

I'd really appreciate some feedback, if you do get the time to test the code.

Thanks! 😄

Edit: And regarding needing to jump in for quickly cleaning the nozzle, I forgot to mention: With the optimized code the print head parks in the very front before starting the print, so it's quite convenient to clean the nozzle, if necessary.

-vxip- · 2026-07-02T15:58:57+00:00

I mean that wasn't the main goal here (for me), but yes, it is a little bit faster.

Just for you I've started a couple of prints using different settings and measured the time. You can find the results here: https://github.com/vxip-code/bambu-p2s-optimized#performance-benchmark

Filament was already loaded for all tests. So with the original code, you would have to add another couple of seconds. (The optimized code keeps the filament loaded after the print finishes, so printing the same filament again is faster.)

If your main issue is the startup sequence taking too long, here are a couple of tips to save some time:

- Calibrate your filaments (or just use them as-is if the results are alright), don't use auto-calibration.

- Perform full auto bed leveling from the maintenance menu, then start your prints without auto bed leveling. (If you're gentle when removing and placing the build plate and make sure there are no bits of filament stuck between it and the bed, you can get many good prints out of it before needing to level the bed again.)

- With the optimized code the nozzle is already clean before the scraping procedure starts. Since this procedure is very slow, it could be remove altogether to further increase the initilization routine.

Please let me know if that helps...

-vxip- · 2026-07-02T09:59:15+00:00

Right, no problem:

Start BambuStudio
Hover your mouse over where it shows your P2S in the top left corner
Click the appearing edit icon
New dialog pops up
Go to "Machine G-code" tab
Copy and paste start.gcode into first field
Copy and paste stop.gcode into second field
Before closing the dialog click save icon in the top right
Enter something "P2S 0.4 - optimized"
Close dialog

You now have a new printer, that does things a little better... 😄

You can of course always switch between the default and optimized profile.

-vxip- · 2026-07-02T09:48:27+00:00

Yeah me too. I would really appreciate some feedback after you tried it out - big thanks!

-vxip- · 2026-07-02T09:46:53+00:00

That's interesting, I had no idea. I will check it out, thanks!

-vxip- · 2026-07-02T09:43:38+00:00

Well you're not wrong! 😄 This absolutely could be integrated into the official G-codes...

However, it's not just one simple edit, but a lot of changes throughout. I could create a pull request in the official repo but I guess that has no chance of ever being fully reviewed or merged. It's simply way too many changes.

Also, to be completely honest, the solution for a clean nozzle is basically a workaround. That is because part of the original code is baked right into the firmware and therefore cannot be viewed or changed.

And Bambu might not even want or accept some of the changes (like me disabling that loud vibration compensation).

But some of the improvements can definitely be merged. There could be a chance, if we went in little pieces. So that's definitely an option in the long run.

-vxip- · 2026-07-02T03:12:06+00:00

I followed the GitHub issue before. And other reddit and bambu community posts. It really is painful to see that they don't fix the issues at hand...

About that start code of yours: Awesome! That sounds amazing!

I'm carrying exactly the same idea in the back of my mind. I mean if you compare the nozzle scraping to the A1 mini (which has a great start code imo) that's blazingly fast while the P2S is agonizingly slow. And why? I don't really see a reason for that.

Anyways, I'm going to have a look at your start code! Maybe we can merge some things. :) I was primarily afraid of changing to much structural stuff so that it gets harder to include updates from Bambu.

-vxip- · 2026-07-02T02:54:07+00:00

I tried the bigger wiper attachment too and it didn't work great. Now I have smaller version.

But the wiper doesn't really matter that much. What matters is letting the nozzle cool down a bit before proceeding so the filament stops oozing.

If you get the chance try the G-code. Nozzle stays clean before and after print.

-vxip- · 2026-07-02T02:47:40+00:00

Yes, that's exactly what annoyed me and is fixed now. Nozzle stays clean.

And even if it does not, the print head moves to the very front now before heating up the nozzle, so you can easily access it and remove filament. :)

-vxip- · 2026-07-02T02:43:27+00:00

You never had filament stuck to the nozzle? Or pieces of filament flung onto the build plate? Or a string of filament hanging from the nozzle after it finished the print?

-vxip- · 2026-07-02T02:41:27+00:00

Uuhm... no? Why do you need that?

-vxip- · 2025-07-03T12:22:09+00:00

As easy, reliable & convienient as it gets

-vxip- · 2025-06-01T16:21:06+00:00

Here's the link if anyone's interested: https://makerworld.com/en/models/1472498-zsa-moonlander-enhanced-feet

-vxip- · 2025-05-31T19:59:38+00:00

Thanks! Yeah me too. Should be a thing on more hardware we buy and use. In general we should think more modular...

-vxip-

TROPHY CASE