Duet 2 wifi Mesh compensation
-
Okay, thanks I try when I get home. Stupid question though, you say "save the height map in a file on the SD card" I do not use any SD card my heightmap.csv is in folder / sys. Is there a difference?
My Firmware 2,04
-
Ian means G29 saves the height map in file on SD card. And yes, you have SD card in Duet, the / sys folder is on it. Without SD card Duet will not work, assuming its Duet2 (wifi, ethernet or maestro, doesnt matter)
-
@aidar said in Duet 2 wifi Mesh compensation:
Ian means G29 saves the height map in file on SD card. And yes, you have SD card in Duet, the / sys folder is on it. Without SD card Duet will not work, assuming its Duet2 (wifi, ethernet or maestro, doesnt matter)
Thank you all, now I understand. I will check everything when I´m at home.
/Runar
-
@droftarts said in Duet 2 wifi Mesh compensation:
M408 S3
You can also see if compensation is active in the results of M122
-
Make sure your Z "jerk" (M566) isn't set too low, if it is, the motors may not move at all.
-
@gtj0 said in Duet 2 wifi Mesh compensation:
Make sure your Z "jerk" (M566) isn't set too low, if it is, the motors may not move at all.
If the Z zerk is too low the Z motors will still move, but the X and Y may pause to give the Z axis time to finish the move, resulting in jerky movement.
-
@Phaedrux said in Duet 2 wifi Mesh compensation:
@gtj0 said in Duet 2 wifi Mesh compensation:
Make sure your Z "jerk" (M566) isn't set too low, if it is, the motors may not move at all.
If the Z zerk is too low the Z motors will still move, but the X and Y may pause to give the Z axis time to finish the move, resulting in jerky movement.
You know, I thought I was speaking from experience...
https://forum.duet3d.com/topic/13423/can-anyone-else-confirm-these-z-behaviors-with-3-0rc1?_=1576942676499But I'll be damned if I can replicate my findings now.
-
@gtj0 I can't speak to any variation between 2.x behaviour and 3.x behaviour.
-
@Phaedrux said in Duet 2 wifi Mesh compensation:
@gtj0 I can't speak to any variation between 2.x behaviour and 3.x behaviour.
Thanks for confirming my worst nightmare... it's just me.
-
Used this to solve my issue with my Predator upgrade. Set Z jerk to 1500 and poof, problem solved.
