How to speed up bed leveling?
-
@Derek-F chatGPT don't know much
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m558-set-z-probe-typeOwns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@Derek-F said in How to speed up bed leveling?:
I can edit the H value in the following line to H5. Found in web console/settings/System Editor/config.g
M558 P5 X0 Y0 Z1 H10 F300 T6000
My understanding is that this will start the probe 5mm lower. Is that correct? ie: shorten the vertical distance moved.Yes, see @jay_s_uk's answer. You could probably set it lower if you have some kind of bed/gantry levelling first, see https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_auto_levelling. I have mine set to H3.
G29 is invoked in my slicer (Prusa Slicer 2.8.0) under Printers/Custom G code/Start G-code. Since there is no matrix defined, it looks like I need to get into the firmware and edit the G29_probegrid section. However, this seems a daunting task requiring much more than simply editing a figure (ie: obtaining source code, installing editing software on my PC, compiling, uploading). Is there any gcode I can use in my slicer or the System Editor that will enable me to speed up movement between probe points?
No, you don't need to hack the firmware! Just use M557, set it in config.g or mesh.g. I find it expedient to home Z before and after running a bed mesh. See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_mesh_bed#define-the-mesh-size-and-spacing
To speed up probing even more, at the beginning of a print you could probe just in the area of the print, which will reduce the number of points you need to probe. See this thread: https://forum.duet3d.com/post/302519
Also, I believe the documentation is incorrect about M558. It says:
What?! I spat out my tea! And then checked... phew, sorry, you're wrong! M558 F parameter is the probing speed, T parameter is the travel speed between points. Both are limited by the maximum values set for the axis in config.g.
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@jay_s_uk Hmm, I see that!
Thanks for your clarification.
Cheers,
Derek
PS, How do I mark your reply as the solution? is there a button? -
undefined jay_s_uk marked this topic as a question
-
undefined jay_s_uk has marked this topic as solved
-
undefined jay_s_uk has marked this topic as solved
-
@Derek-F there you go
-
@droftarts Thanks for confirming and pointing me to the print area probe limit.
FYI, the code does already home before and after MBC.Glad I was wrong - sorry for tea tea mess.
Cheers,
Derek
-
@Derek-F Just to confirm, changing the T6000 to T18000 and the H10 to H5 has done exactly what I wanted and reduced the MBC to less than 1/3 of the original time. Thanks to all.
Cheers,
Derek
-
Hey Guys,
I'm struggling with the same issue, my maximum axis speed is set to 36000mm/min which equals 600mm/s, but no matter what I input as T value it's still traversing at 33.3 mm/s which is awfully slow for 90 points one a 1000*1000 build plate.
-
Share your current config.g and any meshes being called before your leveling routine. homing files, mesh.gm etc.
-
This post is deleted! -
Nevermind, stupid me found the issue while posting up the codes. I've adjusted the F value but not the T value. It now does indeed work
