The Ultimate Mod Combo For Your Bambu Lab P1S X1C Coming Soon - Full Setup Tutorial

[@leckiestein]

A very kind member of my Patreon has given me his AMS for development! AMS support coming soon!!! Also, I have purchased my own AMS and X1C, support for X1C is also in the works - just waiting for Bambu to deliver :)

[@xanarchyUK]

Now this is phenomenal work man, I have a P1S myself and I'm just waiting for your AMS update videos and this is going to be such a good upgrade.

[@kylek29]

Very nice! I sketched up that exact area for this mod (edit: the wiper mount) a few months back but got busy, so I never worked on it, same screw mount, and use of the A1 wiper. I will definitely be using yours.

[@schmiddy8433]

As soon as you confirm your code working for AMS I am DEFINITELY buying this!

[@WhiteAle]

Next video can’t come soon enough, I’m ready to add this in now but waiting for the AMS confirmation as well

[@gierintim]

Thank you Legend! I`m learning a lot of your videos :) Already looking forward to the next one. Greetings from the German Printing Community ✌🏼

[@leckiestein]

Awesome, thank you for these kind words!

[@salehzinalabdin]

This work is amazing! I personally own an X1C combo myself. And im deffinetly using your upgrades. Unfortunately i haven't heard of you sooner. Cant wait to ask my dad if i can become your patreon member, and if i can buy the a1 purge wipers. Keep It up!

[@leckiestein]

Right on kiddo! Great hobby and community to be apart of, and the fact you have an X1C, well, your dad clearly knows what he is doing getting you the best of the best learning tools out there!

[@salehzinalabdin]

@ Yessir! Im glad to say i have bought your steinwipe kit on patreon. I have put some comments there with the same username and profile picture just fyi!

[@Theprofessor1212]

This looks great. I hope we can get one for X1 as well.

[@ZipPeLschen]

A small correction regarding the purge line: You’re using OrcaSlicer for your code, but you mention that it also works with BambuSlicer. That’s not entirely accurate, as BambuSlicer unfortunately still doesn’t (stopped to) offer the option for custom pressure advance. This feature is missing in BambuSlicer, at least for the P1S, which is why your purge line can’t be used with BambuSlicer. That aside, great video, well-structured code, and thank you for sharing it.

[@weinstrassendrohnefpv6822]

Can this be fixed with another code working for Bambu Studio?

[@ZipPeLschen]

​@@weinstrassendrohnefpv6822 No, there's not much you can do about that. However, pressure advance (PA) shouldn't be overly praised either. Yes, it's nice to have control over it, but the fixed value you determine in OrcaSlicer is not the ultimate solution. OrcaSlicer now also offers "Adaptive Pressure Advance," which is even better than standard PA, as the PA value would need to adapt dynamically throughout a print based on various shared changes, something that doesn't happen with a fixed value. PA is a very complex topic, and ultimately, the G-code here only shows your fixed value, independent of the model. I would cautiously suggest that if you've configured your PA via the Bambu settings and mainly use Bambu filament, customizable PA is probably "unimportant" for you at this stage. However, if you work a lot with third-party filaments, switching to OrcaSlicer could be worthwhile due to its much more advanced options for filament tuning. Here's a brief explanation from Orca about APA: github.com/SoftFever/OrcaSlicer/wiki/adaptive-pressure-advance wahrscheinlich hätte ich dir sogar auf deutsch antworten können, wa? :)

[@ZipPeLschen]

@@weinstrassendrohnefpv6822 ​ No, there's not much you can do about that. However, pressure advance (PA) shouldn't be overly praised either. Yes, it's nice to have control over it, but the fixed value you determine in OrcaSlicer is not the ultimate solution. OrcaSlicer now also offers "Adaptive Pressure Advance," which is even better than standard PA, as the PA value would need to adapt dynamically throughout a print based on various shared changes, something that doesn't happen with a fixed value. PA is a very complex topic, and ultimately, the G-code here only shows your fixed value, independent of the model. I would cautiously suggest that if you've configured your PA via the Bambu settings and mainly use Bambu filament, customizable PA is probably "unimportant" for you at this stage. However, if you work a lot with third-party filaments, switching to OrcaSlicer could be worthwhile due to its much more advanced options for filament tuning. Deutsch hätte es wohl auch getan, wa :D

[@ZipPeLschen]

@@weinstrassendrohnefpv6822 No, there’s not much you can do about that. However, pressure advance (PA) shouldn’t be overly praised either. Yes, it’s nice to have control over it, but the fixed value you determine in OrcaSlicer is not the ultimate solution. OrcaSlicer now also offers “Adaptive Pressure Advance,” which is even better than standard PA, as the PA value would need to adapt dynamically throughout a print based on various shared changes, something that doesn’t happen with a fixed value. PA is a very complex topic, and ultimately, the G-code here only shows your fixed value, independent of the model. I would cautiously suggest that if you’ve configured your PA via the Bambu settings and mainly use Bambu filament, customizable PA is probably “unimportant” for you at this stage. However, if you work a lot with third-party filaments, switching to OrcaSlicer could be worthwhile due to its much more advanced options for filament settings.

[@leckiestein]

@@ZipPeLschen Hi! you're completely right! Its been a... minute since Ive used Bambu Studio! Months! Once I discovered Orca, I haven't been back to Studio and as a product of likely too many 3am nights in a row putting this video together, I completely forgot about my slightly different routine for Bambu. Good eye! Before Orca, I was still doing the PA test line in Bambu, but I would set the K value in the slicer code based on the filament type of the slice. ie., if Pla use k0.02 or if Petg use k0.035. Its not ideal but it works well for me since I dont print with may materials from many brands. I can revisit this and come up with a work around for those who want to keep with Bu Studio.

[@ThaShady]

Can't wait to test this! Thanks a lot

[@firik117]

I can't wait to try this on my X1C. This is a great idea, bud.

[@MrSivkar]

I like the nozle cleaning - this is on thing I wil try out ....

[@armani4eva1]

Happy for this review been watching your shorts

[@leckiestein]

@@armani4eva1 hey man just wanted to say thanks for following and showing your appreciation :) I hope you have an amazing new year celebration!

[@braixeninfection6312]

4:16 Ah that explains why the dynamic ABL I set a bit ago thanks to your video is no longer working. I had been wondering. It stopped the same time I updated to 1.07.

[@leckiestein]

@@braixeninfection6312 yep it stopped working on mine too but I discovered how to roll back the firmware. Im wondering if the same issue is why it wont work on the x1. Ill have a look when I get mine.

[@KareemThaKid]

I have an X1C with the AMS. I'll be looking forward to when u get your's. the start gcode is so long and inefficient. it'll be exciting to see how you mod it

[@karol.falkiewicz]

I just compared your file with the default one from Bambu for P1S. I saw that you reordered some of the lines, but also added few additional one (not being the part of the features). Do you plan to add to some additional comments on those, or maybe will align it as much as possible to the default g-code?

[@leckiestein]

Hi! Feel free to email me or Patreon DM me the bits of code in question and I will explain its function. Email is on the main page :)

[@レオ-s3u]

Is it applicable to the A1? Or can you also provide a tutorial for the A1?

[@leckiestein]

@@レオ-s3u code can written for the a1 no problem but the issue is that the wiper is on the bed. It wouldnt be effective if the part was higher than a few inches because it would take too long to get down and back up to use the pad. Filament would ooze away in that time

[@damianmroz87]

Do You plan to sell this design on printables or cults?

[@leckiestein]

Hey, thanks for the message. Right now its still under development and only avail. to my Patrons. I dont have a timeline at this moment for if or when I will published to other sites.

[@BuzzBazzJ]

I’m waiting for my P1S Combo order. The Steinwipe is one of the first mods I’m doing as I’ve also ordered more wipers that I was going to make a similar mod to my MK2.5S+, but it died not too long ago, and even with a replacement board bringing it back to life again, it will be moved and/or retired until the kids are old enough to play with it. That said, I will also reach out if there is something you want to test with the code, as I will be wanting to modify and fix the code the second I get the printer up and running😂

[@BuzzBazzJ]

Would it not be better to run the first purge line on the back end of the build plate to avoid long travel from chute and wiper? So far on my Prusa I’ve changed it so it retracts enough to not drip on the plate moving to the first layer, but if the filament is too warm it drips a little. Most of the time now it has been so little that it won’t mess up the print, but before it would get stuck on the head sometimes.

[@leckiestein]

​@@BuzzBazzJ We have lots in common! So many times I would have something completely ripped apart before I even use it. Just ask my wife about the time I bought a brand new sorrento and I wasnt happy with the stereo. No exageration, complete dash seats and door pans out the same day it came off the lot haha.

[@leckiestein]

@@BuzzBazzJ About the purge line, I got you covered. after the wipe cycle, it parts on the plate to cool. I guarantee it will never drip anywhere for the rest of the routine. It only heats to melt temp again once were ready to lay down filament and print. Only place we can put a purge line so its not in the build volume is along that strip where it is. also, its easy to see and take off, Id leave this one. Youll be pleased with the startup vs the prusa.

[@BuzzBazzJ]

@@leckiestein hahah😂 Our first car is a first gen Volvo V70, and before I got proper tools, so that new Bluetooth compatible stereo didn’t come with a harness for soldering, so I did Gods work that day and never fixed it. Still going strong with finger twists and tape as far as I can remember😅

[@leckiestein]

@@BuzzBazzJ Those cars were never fun to put radios in with their optical amplifiers we would have to delete before the module days (I had a car stereo shop for 15 years)

[@TheNerdArmory]

I can't imagine this is too difficult to adapt to an X1C, has anyone confirmed this to work with an X1C too? (Likely someone who is familiar with gcode and has only taken whats necessary and slotted it into the x1's)

[@leckiestein]

Seems one of my Patrons is on the right tack kzbin.infotCIaVxs4Ezs

[@davidolsson]

In orca slicer I get an error on line 693 that the [filament_retraction_length] is not specified? Trying to reference an undefined (nil) element of vector of optional values

[@leckiestein]

@@davidolsson Hi David, this is a linking error because the code requires you to set a parameter for an override for retraction length in the extruder settings. Im not home at the moment but I will send you another message walking you through where to find the override setting when I get home. Then you just enable it and put a value in the field. I find 0.38 works well for me for petg and pla :)

[@davidolsson]

@leckiestein Excellent! I will do this :)

[@leckiestein]

@@davidolsson I just got home and I confirmed this was the case. So in your filament settings, go to the "Settings Override" tab, then for retraction length make sure its enabled and you have a setting there. I did this because I use slightly less retraction on my pla profiles than petg and the startup code reflects this value :)

[@davidolsson]

@@leckiestein Worked like a charm. If there's anything one could wish for being added is a wipe on the stock wiper after softening temp to remove any oozing hanging on since last print.

[@leckiestein]

@ well, there are a few things with that which you can do. I was never a big believer in this first one but honestly it is game changing when you start doing it. Sounds harsh but... Throw away your desiccant dry boxes and get yourself a heated dry box and set your printer up to print from it. After dry blasting a fresh roll of filament for 8 hours or so, then leave the box at about 45°C and don't turn it off unless youre not going to print for a long time. Doing this one thing for PETG especially, really made all the difference. Without changing anything else, I already have virtually no oozing. But to further tune that, I added some additional features. These files aren't available yet but there are some simple commands you can add : At the end of the print I position the nozzle just before the wiper pad so some of the air can reflect up off of the wiper pad while I blast the hot end with the fan until the temp has reached 170 then do a wipe cycle. And in the start up routine, i've already included but not talked about, a better way to manage a dirty start up nozzle. The initial bed probe just needs to be close because all of the proceeding moves happen on the spring plate so there is about a 1 mm give or take room for error. After that it jumps into the precision homing for the Z.

[@EliteMacFreak]

What are you doing differently that hasn't been done via free mods? By putting this wiper where it is, you are creating a requirement for new G-code where the other wiper mods do not.

[@leckiestein]

Great question! While there are certainly other mods out there, the P1 SteinWipe offers a more refined and comprehensive solution tailored to a variety of user needs. Here’s what sets it apart: 1.Custom G-code Integration: Yes, the wiper placement does require new G-code, but this is intentional. By integrating the wiper with startup routines, I’ve been able to add features like pre-homing collision avoidance, reduced filament usage, and optimized nozzle cleaning paths-things that go beyond what other mods offer. 2.User Customization: The SteinSwitch system allows users to toggle features on and off, providing flexibility for different workflows. For instance being able to turn off mech vibrations in the slicer while keeping the feature functioning. This level of control isn’t something I’ve seen in other wiper mods. 3. Comprehensive Support: I’m not just providing hardware-I’ve created a step-by-step tutorial and am actively improving the G-code based on user feedback. This ensures the mod works seamlessly with your machine while minimizing risks. The SteinWipe isn’t just a hardware mod; it’s a full solution aimed at improving both the functionality and experience of using your printer. I hope this helps clarify why I’ve taken this approach! Cheers, Leckiestein

[@nicoleibundgut534]

Is 59 minutes near future?

[@leckiestein]

Near future is up to Bambu! They havent even given me a delivery date yet :(

[@sChruppi]

The idea is great. But drilling extinguishers in my x1 is a no go