I know it's a small thing, but shout out to KAMP's purge line. After years of watching my Marlin based printers running long thin lines up and down the side of the build plate, I was a bit startled the first time I saw that chubby caterpillar being deposited on my bed. I didn't even know my hotend could do that. Works great though. If I wasn't so lazy, I'd figure out how to make my Marlin printers do that.
well in cura that's a default option by enabling "Enable Prime Blob" under material settings, which is done by default. you can also rip its startup gcode to recreate this behavior like i'd done
I'm not familiar with adaptive purging but I use some poop pellet mod I found online. It works pretty well and is fun because it makes pellets that are kinda shaped like poop emojis and every once in a while you get to empty the poop tray like it's a diaper for your printer.
The problem I find with the purge line is how its position is calculated. If you have a large brim and a skirt or two the print head runs into that purge line and either jacks the head around or drags it into the first layer. It's as if the position is calculated off the print itself and isn't even aware of the brim and skirt.
Cool feature of purge line is that u can look at it and be sure if the filament is wet or not. It's a way more intelligent indicator then your filament dryer screen 😁
The adaptive line purge should be merged into mainline klipper it is an amazing quality of life feature and works hand in hand with adaptive mesh. The guys at Kamp are knocking it out of the park.
I'm glad someone made a video on klipper's new built in KAMP(-P). Last time i looked into it it was kinda hidden in the klipper docs and wasn't super obvious it was even released
I've been thinking about temporal adaptive meshing. Sometimes the heat soaking in the bed and frame lead to distortion of the bed during the printing that can cause issues. So doing an meshing so that its been done after the bed has reached temperature and then for example with 5 minute intervals after that, which would create a number of meshes. The interpolation could then be done based on the time as well as the 2d cordinates of the mesh. with elegoo max it seems you need to wait 20 minutes for the bed to really heat soak, even after it claims it has reached the target temperature, in order to get a good first layer.
As a heads up, Klipper has a breaking change in it, ACCEL_TO_DECEL is now depreciated, if using klicky, you may find out that your printer will no longer home Z. Klicky Macros have been updated to reflect the issue but there is a chance that if anything is controlling acceleration using ACCEL_TO_DECEL, you will find it won't work.
Hey, so I could NOT find the setting and after some digging in the forums here the solution: You have to add the BED_MESH_CALIBRATE to your start gcode macro so it’s part of the printed gcode, e. g. BED_MESH_CALIBRATE PROFILE=adaptive ADAPTIVE=1 and remove BED_MESH_PROFILE LOAD=... if necessary. ____ So where ever you bed_mesh_profile_load startup sequence is (IE the part that tells the print to use you bed mesh profile) mine was in gcode.cfg. Delete it and replace it with BED_MESH_CALIBRATE PROFILE=adaptive ADAPTIVE=1 which is what he was talking about in the video. Hope this helps.
"relative_reference_index" tells the system which of the probed-points should be considered Z-zero, and isn't used anymore. I think they went to some sort of virtual-point, or whatever's closest to where you actually homed your Z automatically.
Indeed. There was a recent commit removing this. Similarly ACCEL-TO-DECEL functionality was changed recently, so also if you are configuring something on that, you might have to adjust this to the new thing replacing it or just remove it and rely on the defaults.
In your bed mesh section you need to replace relative reference index with zero_reference_position: 175, 175 with the values being the Center of your bed. That is why you needed to adjust z offset. Be careful after you set this up to redo your z offset!!
I just run a 10x10 full bed mesh, save it as default & have it loaded each time the printer is powered on. its extremely rare that i ever need to recalibrate & it saves me ever needing to do a bed mesh before any print. mind you, im using a bed-slinger, so i imagine my bed mesh needs less adjustments compared to something that moves the bed up & down on multiple axis.
Me too I run 9x9 with BLTouch just for every bed sheet. I call them as their names PEI_9x9, PEO_9x9, PET_9x9, ... Just change "bed_mesh_profile load=PXX_9x9" at START_PRINT macro before printing or ... according for every sheet. As my magnetic hot bed is so unpaired i have added some 2x2 cm square paper on lower points directly over hotbed.
Omg! This setup is waaaay easier then the guide you made 1 year ago. (You should add text in description on the older video, that there might be an easier way to achieve adaptive meshing)
@@olmosbananas there is nothing particularly hard in marlin's settings, it's just that it is not organised as neatly and doesn't even come close in terms of design
Hello, thanks for the explanation, everything worked so far, only my purge line only comes after adaptive bed meshing, and I have the filament in my first layer of the nozzle oosing, how do I do the purge line before I mesh.? Thanks
I use a custom script for the bed mesh for over a year now. Nice that it’s now in Klipper but I will use my script as long it works. It’s also adaptive in how much probe point it’s using depending on the size I’m printing.
Thanks for the video! I use KAMP and love it. An interesting idea for a video would be exploring MMU systems for printers. I want a non bambu printer that does Multi material and engineering materials. Only if Qidi had an AMS competitor.
There are a few options out there, and most are pretty well documented. There's the chameleon, ercf (v2 which massively improves its reliability) and tradrack, which is currently in open beta. I'm very interested to see more come out from annex engineering, who make the tradrack, when it comes out of beta into full release. For now I'm building an ercf and it is definitely not quite as optimized as an AMS but does the job for a fraction of the price!
I’ve been rocking the fx30 for my primary for a year now, however new spot has better lighting and I started exporting at 4k instead of 1080p. Definitely noticed and increase in clarity 😊.
I don't get making a bed mesh before every print? I mainly print in ABS/ASA and have a bed mesh made while the bed is at a 100 c, which is stored in Klipper permanently. Every time I have to print something my printer heats up in 3 minutes to 245 nozzle/100 bed and after a single bed probe in the middle of the bed it's starts printing. Normally I don't have to redo the bed mesh.. Note that I print on a G10 / FR4 plate which I don't have to remove or touch by hand; after a very short cooling periode, the prints release entirely from the bed. When I'm inpatient a little light pry with a razor blade does the trick without applying force to the bed itself
It depends a lot on your printer. Some people have issues with springs loosing tension or the knobs unwinding itself. Dirt beteeen the build plate and glass plate. Its like free insurance for a great print, especially with this feature it barely adds any time. Also, you can easily swap glass plates etc
@@rikrikietje Those springs could be an issue, true. My print bed does not have springs and is solidly mounted. Dirt can only accumulate under the build plate if you remove it, which I don't.
Nice, I installed Debian on my Sonic Pad recently and setup Adaptive meshing on my Ender 3 Pro, Biqu B1, and Neptune 3 Max and it's been working great saving me a lot of printing time espcially on my Neptune 3 Max. A lot of things didn't work with the creality neutered klipper.
I realized this last week. Started playing with orca again for the seems and realized it didn't probe the whole bed, even though i forgot to add all the stuff from the other slicer. I thought, Oh cool, a good surprise for once.
Just deals with this a few day ago :-$ you are a few days late !;-) I have a lot (really a lot) of frustration whit canbus and klipper updates !!! obliged 2 reflash the board + can + deinstall and reinstall auto Z calibration, ..... a lot of issues with those updates
Yooo this is sick! As a noob I'm wondering though. Can the amount of points in the mesh change with the size of the model? Is there a way to configure the distance between points to be like 10mm to 40mm or smth? Would it also be possible to use different meshing paterns, like a triangle/hexagon patern instead of squares?
I have an idea for a video. I think a video from you would be super beneficial on how to set your offset of your printhead to the bed whenever you are upgrading print heads . Like for instance I upgraded my Ender 3 do a direct drive and a abl and it thanks it's going off the bed because it doesn't have the right parameters I have it now where it does work but it's definitely not perfect you seem to put things so clearly and understandably that I believe it would be super beneficial for new people
thank you very much for this great informative video, will absolutely look into it because it will save me soo much time on my speed voron(which should logically also have a speedy print start xD)
The issue with KAMP is that the adapted mesh isn't probed with the same accuracy as the whole bed. It just probes a smaller area, but with the same distance between points. Unless something has changed that is. So if you have a 10x10 mesh across the entire bed and need to print something taking up only 1/10th of the bed in x and y it will only probe one point (or fout I guess). It will not probe 10x10 in the small area you are printing.
Actually, right from the cfg.... # The following variables are for adjusting adaptive mesh settings for KAMP. variable_mesh_margin: 12 # Expands the mesh size in millimeters if desired. Leave at 0 to disable. variable_fuzz_amount: 0 # Slightly randomizes mesh points to spread out wear from nozzle-based probes. Leave at 0 to disable.
The parameter relative_reference_index has been deprecated. Thanks for this vid. I just updated klipper & newest KAMP and did not realize that klipper now supported adaptive meshing.
Hello, from here 2:35, is it possible to go back for the klipper version? I will do your tutorial for saving the config on github to start xD But here to return to an earlier version of klipper it is because I have a Lerdge-K card and their tutorial for making the .bin for flash the card did not work for me and I was forced to use theirs... In their procedure they replace the kConfig in the klipper files then generate the new .bin then pass it into a tool which will modify it so that it is compatible with the lerdge card, but never succeeded in doing so :s I installed everything for the KAMP bed mesh, but it makes the whole bed each time while the purge is carried out next to the printing, there is a possibility that my problem is linked to the klipper version???
Hello, I have the Klipper one to install but it still makes the whole bed even though everything is in order even though I have BED_MESH_CALIBRATE ADAPTIVE=1 ADAPTIVE_MARGIN=5
I mentioned KAMP in my live stream yesterday only to discover it is native in Klipper now LOL. I’ll stick with KAMP on the RatRig for now, and will update all my Voron’s to add Adaptive meshing to them while I also add Beacon probes!!! 😊
@@ModBotArmy I did a custom install of Beacon based on their instructions, however I did notice that RatOS has a cfg section for Beacon. I think it is so simple that Klipper will (or should) make it native.
I have installed klipper on my printer ender3 week ago. After initial setup its working fine. I have added bltouch and mesh bed leveling. Every thing work as expected. After following thit video i have to enable adaptive mesh function. I edited printer.cfg and mainsail.cfg and change setting in slicer(prusa).. still adaptive mesh not functioning. Machine execute probing for while bed. Any suggestions.
@@julienlessire18 surprisingly it's resolved but I dont know how. Actually I have stopped using the printers for almost 20-30 days & now when I start using my printer adaptive mesh working. I think I only did an update klipper from mainsail.
I tried this KAMP feature and my Voron Trident started failing all the prints. It turns out that the issue was that the back Z axis motor was doing extra steps and the print bed was getting tilted to the back during the print. Did anyone else experienced this issue?
Is there any advantage to running the native adaptive meshing over KAMP. I have kamp meshing and purging running like a champ. You know what they say, never touch a running system. Cheers
Wait.. I'm so confused. I've been running this on the original branch for a while now?! D: it's a great feature, i wish the probe points were adaptive too.
Looks like that's not all of it. There appears to be more to it than these steps. On the Magneto X enabling Adaptive=1 on the start print macro does enable bed mesh calibration, but it's calibrating the WHOLE bed. Not just the print area. RIP.
Is adaptive Bed Meshing compatible with Tap? Is there a significant benefit enabling this with Tap? I am seeking higher res quality with my newly build Voron 2.4 with Tap.
VERY IMPORTANT: it's not cited in the video, but in order for it to work, you'll need to sepparately clone the KAMP from github, I spent hours trying to figure out what was wrong, since I did everything just like the video. Then I realized that I needed to clone the repo.
The main difference is that Kamp is not apart of klipper but an addon. While now adaptive meshing is in klipper. The logic behind it as far as I can tell is the same or very similar so if your up and running no need to change.
@@kenyajobs1069 yeah! Exactly. It’s more exciting for anyone who never got around to or didn’t want to install an add on. Will still be good for new printer builds. One less thing to setup (unless you want the purging)
The sonic pad isn't just a normal klipper install, they have walled off some features, especially around the updates, so that Creality can better control the firmware. KAMP works just fine though and will give you the same functionality.
Take this from someone who just wasted my entire off day. If you have an Elegoo Printer and you don't really know the coding side of all of this DO NOT UPDATE. Everything will break, you won't be able to find a simple fix and you will end everything with accepting you don't get to have the cool new updates because Elegoo HAS to make everything their version. We are lucky they didn't change the username and Pass for Klipper. @Modbot if you could maybe cover the process of setting up Klipper and the order in which to add all of these extensions (enabling webcam, adaptive bed mesh, etc.) and updating specifically a Elegoo printer to the latest version of Klipper where everything doesn't break I think I'm not alone here.
Not trying to sound bogus but klipper video explanations would take multiple hours and episodes all the information can not be covered in one video. I would urge you to read all klipper documentation before updating to new version. Take advantage of all documentations and or helpful videos. Python basics is a good start to be able to understand a bit better with a good knowledge in printer kinematics to be able to visualize what you are commanding on your printer. Hope that helps.
3:34 You lost me here. Which file is this located in?? I noticed you keep doing this in your videos where you could be showing what file you open to better help us, but you always crop it down and hide where you are actually at. Why do you do this? Why not show what file you opened? Why not give more details on the process?
3:34 is my printer.cfg. I didn’t show it because it’s not guaranteed that yours is there. Depending on how you store and run your macros it could be in a dedicated macro file. That’s why I state anywhere you run bed mesh calibrate. There is no way for me to know your setup.
@@ModBotArmy I cant figure out where mine is... If I do bed mesh calibration, it saves the mesh values in my printer.cfg file at the very bottom in the save section, but I dont have that BED_MESH_CALIBRATE anywhere in my printer.cfg file. I do have the BED_MESH_CALIBRATE in a print_area_bed_mesh.cfg, but its read only and I cannot change it. Not sure what to do.
@@wrxsubaru02 Hey, So i had the same question as you and found a solution in the forums: You have to add the BED_MESH_CALIBRATE to your start gcode macro so it’s part of the printed gcode, e. g. BED_MESH_CALIBRATE PROFILE=adaptive ADAPTIVE=1 and remove BED_MESH_PROFILE LOAD=... if necessary. ____ So where ever you bed_mesh_profile_load startup sequence is (IE the part that tells the print to use you bed mesh profile) mine was in gcode.cfg. Delete it and replace it with BED_MESH_CALIBRATE PROFILE=adaptive ADAPTIVE=1 which is what he was talking about in the video. Hope this helps.
If you can root it to get it on official Klipper then yes. If not then I know for a fact there is a script to get KAMP working so you can at least have that for adaptive meshing!
I don't understand the point of adaptive meshing. Yeah, 3x3 adaptive on a small model will increase accuracy. Now your next big print and 3x3 is not enough. Just use 9x9 whole bed mesh every time and job's done.
I probe every print. It’s cheap insurance. Also depending on temps being ran in an enclosed printer things expand and contract differently at different temps. If that works for your setup then that’s great, but going from a enclosed print that had some heat soaking ABS parts to opening up and printing PLA probing with adaptive meshing is quick and proven to work well.
@@ModBotArmy I also probe before every print. What I'm saying is that the moment you start a large print 3x3 is not sufficient anymore. So unless you only print tiny models one by one all the time adaptive meshing doesn't make any sense.
I covered adaptive meshing almost a year go with KAMP :). ruclips.net/video/HydfV8h4p60/видео.htmlsi=iJdDwgO68eDLoq3V This is not KAMP, its native adaptive meshing.
I know it's a small thing, but shout out to KAMP's purge line. After years of watching my Marlin based printers running long thin lines up and down the side of the build plate, I was a bit startled the first time I saw that chubby caterpillar being deposited on my bed. I didn't even know my hotend could do that. Works great though. If I wasn't so lazy, I'd figure out how to make my Marlin printers do that.
Extrudes a lot of plastic without moving the head much
well in cura that's a default option by enabling "Enable Prime Blob" under material settings, which is done by default.
you can also rip its startup gcode to recreate this behavior like i'd done
I'm not familiar with adaptive purging but I use some poop pellet mod I found online. It works pretty well and is fun because it makes pellets that are kinda shaped like poop emojis and every once in a while you get to empty the poop tray like it's a diaper for your printer.
The problem I find with the purge line is how its position is calculated. If you have a large brim and a skirt or two the print head runs into that purge line and either jacks the head around or drags it into the first layer.
It's as if the position is calculated off the print itself and isn't even aware of the brim and skirt.
Cool feature of purge line is that u can look at it and be sure if the filament is wet or not. It's a way more intelligent indicator then your filament dryer screen 😁
The adaptive line purge should be merged into mainline klipper it is an amazing quality of life feature and works hand in hand with adaptive mesh. The guys at Kamp are knocking it out of the park.
I'm glad someone made a video on klipper's new built in KAMP(-P). Last time i looked into it it was kinda hidden in the klipper docs and wasn't super obvious it was even released
I've been thinking about temporal adaptive meshing. Sometimes the heat soaking in the bed and frame lead to distortion of the bed during the printing that can cause issues. So doing an meshing so that its been done after the bed has reached temperature and then for example with 5 minute intervals after that, which would create a number of meshes. The interpolation could then be done based on the time as well as the 2d cordinates of the mesh. with elegoo max it seems you need to wait 20 minutes for the bed to really heat soak, even after it claims it has reached the target temperature, in order to get a good first layer.
As a heads up, Klipper has a breaking change in it, ACCEL_TO_DECEL is now depreciated, if using klicky, you may find out that your printer will no longer home Z. Klicky Macros have been updated to reflect the issue but there is a chance that if anything is controlling acceleration using ACCEL_TO_DECEL, you will find it won't work.
Great video Daniel! PS I love the shirt! 😊
Are you sponsoring Daniel ? ;-p
@@jeremyholef haha He's awesome!
Hey, so I could NOT find the setting and after some digging in the forums here the solution:
You have to add the BED_MESH_CALIBRATE to your start gcode macro so it’s part of the printed gcode, e. g.
BED_MESH_CALIBRATE PROFILE=adaptive ADAPTIVE=1
and remove BED_MESH_PROFILE LOAD=... if necessary.
____
So where ever you bed_mesh_profile_load startup sequence is (IE the part that tells the print to use you bed mesh profile) mine was in gcode.cfg. Delete it and replace it with BED_MESH_CALIBRATE PROFILE=adaptive ADAPTIVE=1 which is what he was talking about in the video.
Hope this helps.
Thank you for the information it helped me as I could not find it.. I found it in the client_macros.cfg
"relative_reference_index" tells the system which of the probed-points should be considered Z-zero, and isn't used anymore. I think they went to some sort of virtual-point, or whatever's closest to where you actually homed your Z automatically.
Indeed. There was a recent commit removing this. Similarly ACCEL-TO-DECEL functionality was changed recently, so also if you are configuring something on that, you might have to adjust this to the new thing replacing it or just remove it and rely on the defaults.
In your bed mesh section you need to replace relative reference index with zero_reference_position: 175, 175 with the values being the Center of your bed. That is why you needed to adjust z offset. Be careful after you set this up to redo your z offset!!
I just run a 10x10 full bed mesh, save it as default & have it loaded each time the printer is powered on.
its extremely rare that i ever need to recalibrate & it saves me ever needing to do a bed mesh before any print.
mind you, im using a bed-slinger, so i imagine my bed mesh needs less adjustments compared to something that moves the bed up & down on multiple axis.
Me too I run 9x9 with BLTouch just for every bed sheet. I call them as their names PEI_9x9, PEO_9x9, PET_9x9, ...
Just change "bed_mesh_profile load=PXX_9x9" at START_PRINT macro before printing or ... according for every sheet.
As my magnetic hot bed is so unpaired i have added some 2x2 cm square paper on lower points directly over hotbed.
Omg! This setup is waaaay easier then the guide you made 1 year ago. (You should add text in description on the older video, that there might be an easier way to achieve adaptive meshing)
I’m happy to see all the new innovations to printing … but I’ll be happy when there’s a more user friendly interface for doing firmware changes.
compared to marlin, klipper is easy mode
@@olmosbananas there is nothing particularly hard in marlin's settings, it's just that it is not organised as neatly and doesn't even come close in terms of design
I would love a video about KLIPPAIN and its modules, and also TMC tunning on klipper!
Just moving from custom macro over to the built-in adaptive now! Thanks for the heads up!
Hello, thanks for the explanation, everything worked so far, only my purge line only comes after adaptive bed meshing, and I have the filament in my first layer of the nozzle oosing, how do I do the purge line before I mesh.? Thanks
I found out this was default on my qidi max 3. Was pretty happy to see that going.
I use a custom script for the bed mesh for over a year now. Nice that it’s now in Klipper but I will use my script as long it works.
It’s also adaptive in how much probe point it’s using depending on the size I’m printing.
Thanks for the video! I use KAMP and love it.
An interesting idea for a video would be exploring MMU systems for printers. I want a non bambu printer that does Multi material and engineering materials. Only if Qidi had an AMS competitor.
There are a few options out there, and most are pretty well documented. There's the chameleon, ercf (v2 which massively improves its reliability) and tradrack, which is currently in open beta. I'm very interested to see more come out from annex engineering, who make the tradrack, when it comes out of beta into full release.
For now I'm building an ercf and it is definitely not quite as optimized as an AMS but does the job for a fraction of the price!
I have a Qidi x max 3 and am looking to build ERCF for it soon. I think it should be possible
I ended up getting a Q1 Pro, and hope to one day do a ERCF or potentially a AMS like system from qidi if that ever comes to fruition.
Great update to Adaptive Mesh. Do you even use your printers? I look at how clean the belts and the Build plates are and they look brand new.
I noticed our recently bought Qidi Max 3's do that. It's such a great feature 👍🏻👍🏻
Great video as always
Thanks for sharing your expirences with all of us 🙂
Good stuff! Did you upgrade your camera? Looks MUSK crisper and better!
I’ve been rocking the fx30 for my primary for a year now, however new spot has better lighting and I started exporting at 4k instead of 1080p. Definitely noticed and increase in clarity 😊.
Thanks for making this video. It was informative
I don't get making a bed mesh before every print? I mainly print in ABS/ASA and have a bed mesh made while the bed is at a 100 c, which is stored in Klipper permanently.
Every time I have to print something my printer heats up in 3 minutes to 245 nozzle/100 bed and after a single bed probe in the middle of the bed it's starts printing. Normally I don't have to redo the bed mesh..
Note that I print on a G10 / FR4 plate which I don't have to remove or touch by hand; after a very short cooling periode, the prints release entirely from the bed. When I'm inpatient a little light pry with a razor blade does the trick without applying force to the bed itself
It depends a lot on your printer. Some people have issues with springs loosing tension or the knobs unwinding itself. Dirt beteeen the build plate and glass plate. Its like free insurance for a great print, especially with this feature it barely adds any time. Also, you can easily swap glass plates etc
@@rikrikietje Those springs could be an issue, true. My print bed does not have springs and is solidly mounted. Dirt can only accumulate under the build plate if you remove it, which I don't.
Nice, I installed Debian on my Sonic Pad recently and setup Adaptive meshing on my Ender 3 Pro, Biqu B1, and Neptune 3 Max and it's been working great saving me a lot of printing time espcially on my Neptune 3 Max. A lot of things didn't work with the creality neutered klipper.
Orca Slicer 2.0 have adaptive mesh built in, so if you unable to install KAMP, try that out.
I realized this last week. Started playing with orca again for the seems and realized it didn't probe the whole bed, even though i forgot to add all the stuff from the other slicer. I thought, Oh cool, a good surprise for once.
Neither KAMP nor Native was working for me.
This does! Thanks for your help!
I have to set "zero_reference_position" to 150, 150 for it to work on my 300mm voron, or the adaptive mesh will get offset by wrong origin point
Just deals with this a few day ago :-$ you are a few days late !;-) I have a lot (really a lot) of frustration whit canbus and klipper updates !!! obliged 2 reflash the board + can + deinstall and reinstall auto Z calibration, ..... a lot of issues with those updates
Yooo this is sick!
As a noob I'm wondering though. Can the amount of points in the mesh change with the size of the model? Is there a way to configure the distance between points to be like 10mm to 40mm or smth?
Would it also be possible to use different meshing paterns, like a triangle/hexagon patern instead of squares?
I have an idea for a video. I think a video from you would be super beneficial on how to set your offset of your printhead to the bed whenever you are upgrading print heads . Like for instance I upgraded my Ender 3 do a direct drive and a abl and it thanks it's going off the bed because it doesn't have the right parameters I have it now where it does work but it's definitely not perfect you seem to put things so clearly and understandably that I believe it would be super beneficial for new people
Like this? ruclips.net/video/r7xHNO10H_8/видео.htmlsi=SmpuDqgBy04Z1204
@@ModBotArmy yep should have known a RUclipsr of your caliber already have done that!
@@Cody_Spaghetti I always appreciate suggestions 😊
thank you very much for this great informative video, will absolutely look into it because it will save me soo much time on my speed voron(which should logically also have a speedy print start xD)
be great if you can do a detailed view of klippain shake tune. especially when it comes do deciphering the belt tension test for your next vid.
Cool, might add this. I have a beacon probe though so meshes are already pretty quick.
Could you make a video on how to setup klippain. It’s confusion and this would help a lot of people.
Can I use ADAPTIVE PURGING FUNCTION or do I need to install KAMP? which I understand has already been in Klipper for some time? It isn't very clear...
The issue with KAMP is that the adapted mesh isn't probed with the same accuracy as the whole bed. It just probes a smaller area, but with the same distance between points. Unless something has changed that is. So if you have a 10x10 mesh across the entire bed and need to print something taking up only 1/10th of the bed in x and y it will only probe one point (or fout I guess). It will not probe 10x10 in the small area you are printing.
I had this same concern!
Actually, right from the cfg....
# The following variables are for adjusting adaptive mesh settings for KAMP.
variable_mesh_margin: 12 # Expands the mesh size in millimeters if desired. Leave at 0 to disable.
variable_fuzz_amount: 0 # Slightly randomizes mesh points to spread out wear from nozzle-based probes. Leave at 0 to disable.
I could not find alot of things you covered as I have a sonic pad and am unsure how to accomplish this setup but would like to.
The parameter relative_reference_index has been deprecated. Thanks for this vid. I just updated klipper & newest KAMP and did not realize that klipper now supported adaptive meshing.
Ahh! That makes a ton of sense. Thank you 😊
Hello, from here 2:35, is it possible to go back for the klipper version?
I will do your tutorial for saving the config on github to start xD
But here to return to an earlier version of klipper it is because I have a Lerdge-K card and their tutorial for making the .bin for flash the card did not work for me and I was forced to use theirs...
In their procedure they replace the kConfig in the klipper files then generate the new .bin then pass it into a tool which will modify it so that it is compatible with the lerdge card, but never succeeded in doing so :s
I installed everything for the KAMP bed mesh, but it makes the whole bed each time while the purge is carried out next to the printing, there is a possibility that my problem is linked to the klipper version???
When I added the [update_manager] and enable_auto_refresh: True I saved and restarted firmware but I still don't have the update window option
This is with fluidd?
@ModBotArmy yes I rebooted the machine and then it seemed make that error go away but now I keep getting Klippy not connected
Hello, I have the Klipper one to install but it still makes the whole bed even though everything is in order even though I have
BED_MESH_CALIBRATE ADAPTIVE=1 ADAPTIVE_MARGIN=5
Have you updated orca to beta v2 ? is also has some form of adaptive mesh built in, but I have not tried it yet.
I mentioned KAMP in my live stream yesterday only to discover it is native in Klipper now LOL. I’ll stick with KAMP on the RatRig for now, and will update all my Voron’s to add Adaptive meshing to them while I also add Beacon probes!!! 😊
Is Beacon in native Klipper now as well? Or does it still require a custom install? I’d love to see it integrated.
@@ModBotArmy I did a custom install of Beacon based on their instructions, however I did notice that RatOS has a cfg section for Beacon. I think it is so simple that Klipper will (or should) make it native.
Just tried this on my Neptune 4 Pro... now it's bricked. Is there a way to do a reflash to factory?
I have installed klipper on my printer ender3 week ago. After initial setup its working fine. I have added bltouch and mesh bed leveling. Every thing work as expected.
After following thit video i have to enable adaptive mesh function. I edited printer.cfg and mainsail.cfg and change setting in slicer(prusa).. still adaptive mesh not functioning. Machine execute probing for while bed.
Any suggestions.
Same issue, same machine. Did you solved it ?
@@julienlessire18 surprisingly it's resolved but I dont know how. Actually I have stopped using the printers for almost 20-30 days & now when I start using my printer adaptive mesh working. I think I only did an update klipper from mainsail.
I tried this KAMP feature and my Voron Trident started failing all the prints. It turns out that the issue was that the back Z axis motor was doing extra steps and the print bed was getting tilted to the back during the print. Did anyone else experienced this issue?
Is there any advantage to running the native adaptive meshing over KAMP. I have kamp meshing and purging running like a champ. You know what they say, never touch a running system.
Cheers
If your up and running smoothly. I see no reason to swap over as of yet. 👍
@@ModBotArmy thanks
Wait.. I'm so confused.
I've been running this on the original branch for a while now?! D:
it's a great feature, i wish the probe points were adaptive too.
Are you kidding me? Literally 4 hours after I installed KAMP? :D
There is no need to use the built in adaptive mesh. Have fun with KAMP :)
@@timha4102 yes you're right but I like to keep my configuration as simple as possible :) at least I am going to update Klipper in my MCUs.
Looks like that's not all of it. There appears to be more to it than these steps.
On the Magneto X enabling Adaptive=1 on the start print macro does enable bed mesh calibration, but it's calibrating the WHOLE bed. Not just the print area.
RIP.
Is adaptive Bed Meshing compatible with Tap? Is there a significant benefit enabling this with Tap? I am seeking higher res quality with my newly build Voron 2.4 with Tap.
Didn't this feature become a rejected pr in the klippy repo, but was rejected, so the author just made Kamp?
You are the only guy I know with a voron 2.4 and a Rat Rig V3. Which one would you recommend. I looking at both but can't decide which one to go for.
I have v minion 😆 so it’s not a fair comparison. However I love my v minion.
Not sure where I messed up but the line is still purging like normal
But is built-in meshing any better than KAMP version? To be honest I don't see any good reason to switch off KAMP meshing unless I miss anything
This is more intended for new builds or anyone that isn’t already running kamp. Unless Kamp gets depreciated I don’t see why you’d swap yet.
printhead in min 0:26 ?
Wait what do you have to do to run adaptive mesh with KAMP? That part was just breezed over lol
Kamp has a full video on my channel. This was about native adaptive meshing 😊
@@ModBotArmy thanks
VERY IMPORTANT: it's not cited in the video, but in order for it to work, you'll need to sepparately clone the KAMP from github, I spent hours trying to figure out what was wrong, since I did everything just like the video. Then I realized that I needed to clone the repo.
Thank you.. I watched the video 3x trying to figure out where he got the kamp.cfg from ...
Did anyone got it if what's the difference between KAMP and adaptive meshing? Cos I did not.
The main difference is that Kamp is not apart of klipper but an addon. While now adaptive meshing is in klipper. The logic behind it as far as I can tell is the same or very similar so if your up and running no need to change.
@@ModBotArmy oh, so adaptive mesh was added recently to klipper? Good news, thx.
I'll stay with kamp then, thx for mentioning it.
@@kenyajobs1069 yeah! Exactly. It’s more exciting for anyone who never got around to or didn’t want to install an add on. Will still be good for new printer builds. One less thing to setup (unless you want the purging)
@@ModBotArmy good point, purge line is a good indicator of wet filament. Trust it more then my filament dryer's screen data😁
I have the same problem with my z offset now and was not able to fix it yet😢😢
Ive got the same issue, im not sure how to fix it since i also have klicky and its meant to auto set the offset
The sonic pad isn't just a normal klipper install, they have walled off some features, especially around the updates, so that Creality can better control the firmware. KAMP works just fine though and will give you the same functionality.
Make sure you use this in the bed mesh section: zero_reference_position: 175, 175 the numbers must be the middle position of the bed
If you are using Auto Z calibration de-install the script and reinstall the script is solved all the issues for me !
@@jeremyholef reinstalling the script solved the issue. Dont forget to remove the old one before
Has anyone done this running octopi?
lol I JUST set up Kamp and then this video was next in recommended. welp
Take this from someone who just wasted my entire off day. If you have an Elegoo Printer and you don't really know the coding side of all of this DO NOT UPDATE. Everything will break, you won't be able to find a simple fix and you will end everything with accepting you don't get to have the cool new updates because Elegoo HAS to make everything their version. We are lucky they didn't change the username and Pass for Klipper. @Modbot if you could maybe cover the process of setting up Klipper and the order in which to add all of these extensions (enabling webcam, adaptive bed mesh, etc.) and updating specifically a Elegoo printer to the latest version of Klipper where everything doesn't break I think I'm not alone here.
+1 yes please,
Or better push eleggo to release the development environment for building the OS Image and TFT firmware Image myself.
Not trying to sound bogus but klipper video explanations would take multiple hours and episodes all the information can not be covered in one video. I would urge you to read all klipper documentation before updating to new version. Take advantage of all documentations and or helpful videos. Python basics is a good start to be able to understand a bit better with a good knowledge in printer kinematics to be able to visualize what you are commanding on your printer. Hope that helps.
My forced 3 month break from printing is yielding fruit.
Forced by who..?
3:34 You lost me here. Which file is this located in?? I noticed you keep doing this in your videos where you could be showing what file you open to better help us, but you always crop it down and hide where you are actually at. Why do you do this? Why not show what file you opened? Why not give more details on the process?
3:34 is my printer.cfg. I didn’t show it because it’s not guaranteed that yours is there. Depending on how you store and run your macros it could be in a dedicated macro file. That’s why I state anywhere you run bed mesh calibrate. There is no way for me to know your setup.
@@ModBotArmy I cant figure out where mine is... If I do bed mesh calibration, it saves the mesh values in my printer.cfg file at the very bottom in the save section, but I dont have that BED_MESH_CALIBRATE anywhere in my printer.cfg file. I do have the BED_MESH_CALIBRATE in a print_area_bed_mesh.cfg, but its read only and I cannot change it. Not sure what to do.
@@wrxsubaru02 Hey, So i had the same question as you and found a solution in the forums:
You have to add the BED_MESH_CALIBRATE to your start gcode macro so it’s part of the printed gcode, e. g.
BED_MESH_CALIBRATE PROFILE=adaptive ADAPTIVE=1
and remove BED_MESH_PROFILE LOAD=... if necessary.
____
So where ever you bed_mesh_profile_load startup sequence is (IE the part that tells the print to use you bed mesh profile) mine was in gcode.cfg. Delete it and replace it with BED_MESH_CALIBRATE PROFILE=adaptive ADAPTIVE=1 which is what he was talking about in the video. Hope this helps.
Klipper documentation started to fall apart!
wait so does kamp still work?
Yup! Kamp works just fine still
Will this work on k1 Max?
If you can root it to get it on official Klipper then yes. If not then I know for a fact there is a script to get KAMP working so you can at least have that for adaptive meshing!
Im so lost when it comes to the software stuff. I don't know enough to get my sleepy brain wrapped around it. lol
Hello, where should i put line BED_MESH_CALIBRATE ADAPTIVE=1? I cant find it in printer.cfg
Is it in Macro.cfg in the "start print" section?
Kind of makes you wonder why this wasn't the way mesh leveling was done in the first place 🤷🏿♀️
Yeah... does not work for me. All updates are ok, Kamp Adaptive Mesh works, but this not.
I don't understand the point of adaptive meshing. Yeah, 3x3 adaptive on a small model will increase accuracy. Now your next big print and 3x3 is not enough. Just use 9x9 whole bed mesh every time and job's done.
I probe every print. It’s cheap insurance. Also depending on temps being ran in an enclosed printer things expand and contract differently at different temps. If that works for your setup then that’s great, but going from a enclosed print that had some heat soaking ABS parts to opening up and printing PLA probing with adaptive meshing is quick and proven to work well.
@@ModBotArmy I also probe before every print. What I'm saying is that the moment you start a large print 3x3 is not sufficient anymore. So unless you only print tiny models one by one all the time adaptive meshing doesn't make any sense.
Kamp is almost a year and you just discovered it? :D
I covered adaptive meshing almost a year go with KAMP :).
ruclips.net/video/HydfV8h4p60/видео.htmlsi=iJdDwgO68eDLoq3V
This is not KAMP, its native adaptive meshing.
@@ModBotArmyoh great. my apologies
First!