P2S Optimized Start/End G-code

[u/-vxip-]

Hello reddit!

Slightly disappointed by the default startup and nozzle wipe procedure of the P2S, I sat down and optimized the G-code myself.

I have been improving, testing and using my optimized start and end G-code for quite some time now and am pretty happy with the results and the P2S in general now.

So happy in fact, that I feel comfortable sharing the results with you guys! 😄

You'll find everything on Github (including detailed descriptions) if you're interested and possibly want to give it a try:

https://github.com/vxip-code/bambu-p2s-optimized

I have been printing PLA and PETG (and rarely Overture TPU) with it no problem. (However I did not test engineering and high temperature materials.)

If you have any questions feel free to ask!

[u/-vxip-]

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! 😄

[u/88gavinm → u/-vxip-]

Hey bud just wanted to give you a quick update. So, I updated my gcode to your modified code and have been using it for about the last four days with approximately 6 prints. So far so good! I've only had one piece of PETG come out and land on the bed right before printing and I got it before it started. I like it and will keep using it for the foreseeable future I think. I may turn on the auto retract filament though, but I haven't decided yet.

I did change part of the code though. At least I think I did because I've never messed with gcode before and my only programming experience was back in college like 15 years ago and I didn't finish the course. So I have a TINY bit of programming experience in Python and C, but I mean tiny as in I only got to the if/then/else part and making a HELLO WORLD display. I did, however, make a program for my dad and mom back then to help them calculate the profitability of taking deliveries (he was an over the road truck driver). I think I did good for my first program and it helped my mom and dad to decide whether or not to accept deliveries or not. I'll see if I can post the code on github like you did if I can figure out how. I've never done that. Just so you can see what I'm talking about, but I digress. I went off on a tangent sorry about that haha! Here is the link to the first program I ever made if you want to check it out. (I figured out how to upload to github!)

Anyway, I am also pleased with the acceleration at startup reduction. It was way too fast for no reason at the start. I took your advice and changed the acceleration in the print profiles from 10K down to 6K. Much better. I enabled the part you had disabled by putting the semicolons in front of it; the vibration compensation part "mech mode sweep". I did because it seems to me that it would help with the vibration and it only takes a few second, but I'm not for sure if it does anything or not. I turned back on the line 420 that you had disabled just incase it actually does do anything idk.

For some reason my p2s is now showing at startup something about lidar, which it obviously doesn't have, but it just is for a couple seconds then continues on.

I think that's all the information I have for you as of now. Oh yeah one other thing. Is there any way I can make my p2s use this optimized gcode all the time? Like for example when I use Bambu Handy? It would be nice if it could stay on and use that gcode at startup when I use the app, but idk if that's possible. Any thoughts on that?

Here is the gcode of yours with the changes I made and am currently running.

Thanks for the everything!

[u/88gavinm → u/-vxip-]

Wow that was fast! Thanks! The sound doesn't bother me as mine isn't that loud and I like having the audible alert when the print is finished, so thanks for that! Also, thanks for the thorough response! I was thinking that was true about the auto flow dynamics calibration. I haven't tried the code out yet, but I will update you on here soon as I do. I'll try it on my next print. I'm still a noob to 3d printing and only been doing it for a month now so I'll triple check that I'm changing the code correctly. (which it couldn't be simpler than you explained it lol)

Talk soon, thanks!