@@kyleisah So a standard startskript without mesh bed leveling is enough? Is the adaptive leveling trigger when i start the print? These (EXCLUDE_OBJECT_DEFINE NAME=A_Drive_Frame_Upper_x1_stl CENTER=142.137,149.181 POLYGON=[[114.09,124.7],[114.09,175.303],[175.91,175.303],[175.91,124.7]]) are the parameters that are needed in the gcode right?
@@second_one-e2e you will need to have BED_MESH_CALIBRATE defined somewhere in your print start macro for it to make a mesh. Same with the adaptive purge. The adaptive bed mesh macro replaces the BED_MESH_CALIBRATE macro with one that uses the exclude object definitions to define the size of the mesh. :)
Hi there, I managed to set up the adaptive mesh, however, I would like to set the number of probing points manually. Is there any way possible to do it?
This video is pointless cause you already have so many things already set up before starting this. Like im so lost plus they changed the installation method so i dont know what to do at this point other than try to find another people who can help
This is such a good mesh and purge setup. Thanks for the walk through, super helpful. Huge thanks to Kyleisah and the others for putting this together. Glad to see a setup that requires LESS code and hoops to jump through to make work.🤘
Has anyone been able to do this on a SV06 with Clipper Upgrade? I am having a hard time figuring out which bed mesh values to block out in order for the adaptive meshing to work. with the new updated repository looks like you have to have the KAMP_Settings.cfg file downloaded but when I go into the console command to ender ssh, then cd like the directions provide the console doesn't recognize those commands. Would greatly appreciate any help :)
Works great with Cura. With SuperSlicer it keeps probing the entire bed. Can`t figure out why. Label objects is checked and exclude objects works fine. Ideas anyone?
i installed with moonranker update now i noticed thats more work and not working nicely so i deside to deinstall but how? i deleted the KAMP folder and the shortcut inside configs folder alsow the include code from printer.cfg is that all ??
Creative criticism: 100% appreciate this video. I did not know this was possible. But it would have been more helpful to start a little more from step one. You already has some of the configuration set up. Again, I wouldn't known this was even possible, but for me starting from a stock Klipper, there are more steps I will need to do to get this working.
Hey, thanks for the video! So this always does like 5x5 mesh for example but you cant specify meshing at 15mm blocks for example so its more point on a bigger print and less on a small print? Did you say at the start there are other systems that do that?
I actually like your umbilical set up. Would you mind telling me what you're using? Seems like some sort of M12 airplane connector? Is that the EBB36? Yours is muuuuuuch cleaner looking than my mess. If you can point me in the right direction I'd appreciate it.
It is a little bit pitty that you shown this not for a VORON with stock inductive probe. Maybe you can made a video to clarifications which changes are to do with a stock VORON? Best regards Martin
I thought you said that you used a 5x mesh, that adaptive mesh only did three? or did I miss something? I thought the point of AM was to do the same number of probes 5x5 or what ever in a smaller space, if it is just ignoring the probes outside of the print area how is that improving the accuracy of the mesh?
The number of points set is the maximum- if you're probing a small area it may use less points. You'll still get a more accurate mesh for the part of the bed in use than a full bed mesh.
Why not just let superslicer pass the dimensions in? That gcode parser that is used for exclude object is slow enough that it causes a timeout when sending your gcode to the printer (moonraker) over the network from the slicer.
I can't comment on why the code is written this way, but I've never experienced a timeout uploading gcode from SuperSlicer to my printer. What slicer are you using? -Allen
Great Video, I noticed with the bed calibrate that you also load the profile; is that necessary wouldn't it also conflict if there was a default profile already saved?
The new mesh is used instead of the default, making sure that your mesh is correct for the conditions in the printer right after meshing. Your build plate or other variables could be different from your stored default.
awesome video! I'm definitely going to implement this. Noticed you're running an umbilical with what appears to be a toolhead board. What board are you running and what cover is that?
Thank you for an interesting and useful video! I have this question. Prusaslicer has a service variable `layer` that is used in many slicer macros. However, Klipper does not understand this construct and ignores it. Question - how do I get a layer counter in Klipper? Thanks!))
Great Buddha! Thank you kind person! This is what I was looking for, but where, where is this magnificence described? There is nothing like this in the documentation for Klipper commands and macros(((... But anyway, thanks again a lot!!!)))
@@burbycianburbycianovich9274 You're welcome! I pulled the code from my slicer settings but don't remember where I found it. Go forth and spread the knowledge :) Allen
I read a discussion where someone said Cura labels objects by default and KAMP works for them. You could also check out this link for a preprocessor: github.com/kageurufu/preprocess_cancellation
@@west3dprinting219 When I tried it nothing worked right. It did not do the adaptive bed mesh but it did the adaptive purge but got the "over the max extrusion" thing even on 5 max cross sections. But I'm also having issues with the adaptive purge in prusa slicer but the adaptive mesh works so, I havent figured it all out either
I have a [bed_mesh] in my printer.cfg, do i need to get rid of that or keep it? This worked well the first time i ran it but it is now doing a mesh for the whole bed, even for a pressure advance tower.
You don't need to remove the old bed mesh, KAMP renames it. Best way to get help would be to contact Kyleisah on the Voron Discord or on his Github page.
Take a look at your console. You may see a line stating something along the lines of... 0 points, clamping to bed mesh [(X_Value,Y_Value) (X_Value,Y_Value)] For me the issue was one of the troubleshooting steps on the GitHub. My start macro was placed before exclude_object in the gcode if you view. This means that the adaptive mesh isn't able to determine the coordinates of the object for bed mesh calibrate. Make sure you have something in your custom gcode in your slicer. Mine looks like this... M117 START_PRINT Once I got that sorted it's been working perfectly. Hope this helps.
@@bellyhold thanks for the reply, I found out that I had checked the label objects box in Prusa slicer, then I switched profiles without realizing that the setting didn't carry over. Had about 20 printing profiles that I had to go through to check that box, now everything works great.
@@bellyholdis it on an SV06? Would you mind sharing a snippet of that code? I am too having issues with this and since they re did how the installation is no UA-cam video has been created that I know of going over the file paths and what not. My console reader doesn’t recognize the commands cd or ssh so I can’t download the file path directory. Thank you!
How can I set a max position so it doesn’t try to move out of range?
Love the "That... should be everything?" haha! Almost like you weren't expecting it to be that easy. 😄
I wasn't! Thanks again for the great work.
What do i need to paste in the slicer start gcode? Either I'm stupid or there is no step on the github.
@@second_one-e2e what do you mean? There are no parameters that need passing, this all works from definitions made by [exclude_object].
@@kyleisah So a standard startskript without mesh bed leveling is enough? Is the adaptive leveling trigger when i start the print? These (EXCLUDE_OBJECT_DEFINE NAME=A_Drive_Frame_Upper_x1_stl CENTER=142.137,149.181 POLYGON=[[114.09,124.7],[114.09,175.303],[175.91,175.303],[175.91,124.7]]) are the parameters that are needed in the gcode right?
@@second_one-e2e you will need to have BED_MESH_CALIBRATE defined somewhere in your print start macro for it to make a mesh. Same with the adaptive purge. The adaptive bed mesh macro replaces the BED_MESH_CALIBRATE macro with one that uses the exclude object definitions to define the size of the mesh. :)
Hi there, I managed to set up the adaptive mesh, however, I would like to set the number of probing points manually. Is there any way possible to do it?
This video is pointless cause you already have so many things already set up before starting this. Like im so lost plus they changed the installation method so i dont know what to do at this point other than try to find another people who can help
Agreed.
This is such a good mesh and purge setup. Thanks for the walk through, super helpful. Huge thanks to Kyleisah and the others for putting this together. Glad to see a setup that requires LESS code and hoops to jump through to make work.🤘
to comment or uncomment (it is cycling )just select lines by dragging and and use clrt+/
Has anyone been able to do this on a SV06 with Clipper Upgrade? I am having a hard time figuring out which bed mesh values to block out in order for the adaptive meshing to work. with the new updated repository looks like you have to have the KAMP_Settings.cfg file downloaded but when I go into the console command to ender ssh, then cd like the directions provide the console doesn't recognize those commands. Would greatly appreciate any help :)
Omg I need this in my life! Thanks. Great vid. I can't wait to start purging lil voron logos on each print!
Works great with Cura. With SuperSlicer it keeps probing the entire bed. Can`t figure out why. Label objects is checked and exclude objects works fine. Ideas anyone?
i installed with moonranker update now i noticed thats more work and not working nicely so i deside to deinstall but how? i deleted the KAMP folder and the shortcut inside configs folder alsow the include code from printer.cfg is that all ??
That should do it
If I print the same thing is there a means to stop KAMP ?
I followed along your video. When I print just a small voron cube it is messing whole bed not just where print will be.
Creative criticism: 100% appreciate this video. I did not know this was possible. But it would have been more helpful to start a little more from step one. You already has some of the configuration set up. Again, I wouldn't known this was even possible, but for me starting from a stock Klipper, there are more steps I will need to do to get this working.
Hey, thanks for the video! So this always does like 5x5 mesh for example but you cant specify meshing at 15mm blocks for example so its more point on a bigger print and less on a small print? Did you say at the start there are other systems that do that?
The FLsun v400 was 400mms right out of the box
I run it on ender 3 s1. This is mind blowing 😍 Thank you !
can you please share the start code macro?
I actually like your umbilical set up. Would you mind telling me what you're using? Seems like some sort of M12 airplane connector? Is that the EBB36? Yours is muuuuuuch cleaner looking than my mess. If you can point me in the right direction I'd appreciate it.
Running the Mellow SB2040, parts are in my repo at github.com/allenrowand/voron_mods/tree/main/v2.4 -Allen
I know my next project now. Thanks!
It is a little bit pitty that you shown this not for a VORON with stock inductive probe. Maybe you can made a video to clarifications which changes are to do with a stock VORON? Best regards Martin
This will work on any Voron regardless of the probe type. -Allen
I thought you said that you used a 5x mesh, that adaptive mesh only did three? or did I miss something? I thought the point of AM was to do the same number of probes 5x5 or what ever in a smaller space, if it is just ignoring the probes outside of the print area how is that improving the accuracy of the mesh?
The number of points set is the maximum- if you're probing a small area it may use less points. You'll still get a more accurate mesh for the part of the bed in use than a full bed mesh.
Why not just let superslicer pass the dimensions in? That gcode parser that is used for exclude object is slow enough that it causes a timeout when sending your gcode to the printer (moonraker) over the network from the slicer.
I can't comment on why the code is written this way, but I've never experienced a timeout uploading gcode from SuperSlicer to my printer. What slicer are you using? -Allen
Great video ... and I really like that cable mount solution you have in your Toolhead ... can you share some link where you got that ?
github.com/allenrowand/voron_mods/tree/main/v2.4/Umbilical%20parts
Great Video, I noticed with the bed calibrate that you also load the profile; is that necessary wouldn't it also conflict if there was a default profile already saved?
The new mesh is used instead of the default, making sure that your mesh is correct for the conditions in the printer right after meshing. Your build plate or other variables could be different from your stored default.
awesome video! I'm definitely going to implement this.
Noticed you're running an umbilical with what appears to be a toolhead board. What board are you running and what cover is that?
Thanks! It's a Mellow SB2040, the cover is linked in our CANBUS video in the allenrowand repo
Very useful material, many thanks.
Also, can you share your print_start.cfg and print_end.cfg ? Please ?
They're at github.com/allenrowand
Thanks op
can we get a video on the deez nozzle please? i have mine on order
Hey! we are still evaluating results of this nozzle and will put on our list to do an overview video once we feel we are well prepared!
Very happy that I did this 2 weeks ago. So fast and very easy to clean up.
this worked great thanks
Thank you for an interesting and useful video! I have this question. Prusaslicer has a service variable `layer` that is used in many slicer macros. However, Klipper does not understand this construct and ignores it. Question - how do I get a layer counter in Klipper? Thanks!))
In your printer settings add this to your "after layer change gcode":
;AFTER_LAYER_CHANGE
;[layer_z]
M117 Layer {layer_num+1}/[total_layer_count]
Great Buddha! Thank you kind person! This is what I was looking for, but where, where is this magnificence described? There is nothing like this in the documentation for Klipper commands and macros(((... But anyway, thanks again a lot!!!)))
@@burbycianburbycianovich9274 You're welcome! I pulled the code from my slicer settings but don't remember where I found it. Go forth and spread the knowledge :) Allen
Hello, would it be possible to provide your configuration files, I really like how you have separate configurations, thank you
If you search for "github voron config" you'll find tons of configurations that are probably better than mine. -Allen
+1 for posting your config files... they look very clean and organized.
Has somebody tried this with cura? Is it even possible? There is no object labeling as far as I'm aware.
I read a discussion where someone said Cura labels objects by default and KAMP works for them. You could also check out this link for a preprocessor: github.com/kageurufu/preprocess_cancellation
@@west3dprinting219 When I tried it nothing worked right. It did not do the adaptive bed mesh but it did the adaptive purge but got the "over the max extrusion" thing even on 5 max cross sections. But I'm also having issues with the adaptive purge in prusa slicer but the adaptive mesh works so, I havent figured it all out either
Yes, works well with Cura
I have a [bed_mesh] in my printer.cfg, do i need to get rid of that or keep it? This worked well the first time i ran it but it is now doing a mesh for the whole bed, even for a pressure advance tower.
You don't need to remove the old bed mesh, KAMP renames it. Best way to get help would be to contact Kyleisah on the Voron Discord or on his Github page.
Take a look at your console. You may see a line stating something along the lines of... 0 points, clamping to bed mesh [(X_Value,Y_Value) (X_Value,Y_Value)] For me the issue was one of the troubleshooting steps on the GitHub. My start macro was placed before exclude_object in the gcode if you view. This means that the adaptive mesh isn't able to determine the coordinates of the object for bed mesh calibrate.
Make sure you have something in your custom gcode in your slicer. Mine looks like this... M117 START_PRINT
Once I got that sorted it's been working perfectly. Hope this helps.
@@bellyhold thanks for the reply, I found out that I had checked the label objects box in Prusa slicer, then I switched profiles without realizing that the setting didn't carry over. Had about 20 printing profiles that I had to go through to check that box, now everything works great.
@@bellyholdis it on an SV06? Would you mind sharing a snippet of that code? I am too having issues with this and since they re did how the installation is no UA-cam video has been created that I know of going over the file paths and what not. My console reader doesn’t recognize the commands cd or ssh so I can’t download the file path directory. Thank you!
slick, I so want a voron sadly not affordable at the moment. Cheers for the Vid, and taking the risk of mashing your bed :)
Great Stuff thanks for putting this together!
Thanks, glad you enjoyed it!