@shirnschall the kraken motors have thermistors embedded in them so I doubt there's any issues. The ones they use are nothing special

Also, searching around the forum, it seems like this post might be the same issue, just with a delta printer instead of a simple z axis.

https://forum.duet3d.com/topic/36572/v2-0-consistently-increasing-probe-heights

@CaiJonas said in Bug on 3.6.0? Layershifts & stuttering on arc travel moves:

I changed one other setting in the slicer --> resolution down to 0,025. This should result in shorter segments? I don't know.

Yes, I'd think that creates smaller segments. If you can get it to create arc moves for the travel moves, that would probably help.

The M122 reports still say max steps late 1, but that might be a limit rather than the number of late steps. I'll check with @dc42.

For the M595 P parameter, it takes up extra memory as you increase it. If you increase it too much, you'll get a memory warning. You can check how much free RAM you have in the M122 report. Adding more to your config will increase the memory usage, too.

Ian

Oh yeah and yes I did learn a long time ago to use L.
I assume 1 is the highest value but it doesn't exactly clarify in the documentation. I have tried higher values like 10 and it seems to accept them but I never noticed any difference with values higher than 1.

@luc said in Very slight systematic waves every about 2mm on the prints:

What object could I print?

A pyramid/cone.

@perfetto

Good evening, since at the beginning you told me that the best solution was to switch to firmware 3.5.4
I took courage I ran by installing first 2.05.1 then 3.3 and finally 3.5.4 it tells me that the firmware is not compatible with the configurator I ran configuration and launched I also did the bl touch procedure it works, but the extruder did not work or I redid the configuration but there was nothing strange (I think) now it does not even want to reset the x and y axis with microswitches, I do not know what to do anymore. if you eventually want me to send the jonson file to take a look at it or if you kindly give me some advice.

I have asked you a number of times to post your config.g, and the response to M122. That way I know what firmware you are using, and how it is configured. Please post these as text, not as pictures.

In your last post, you said you had installed firmware 2.05.1 again. You need to use your OLD configuration, not the one produced by the Configuration Tool. Then we can fix that to work with the BLTouch.

If you want my help to get the configuration correct for 3.5.4, please post your old 2.05.1 config.g, and the new config.g for 3.x that the configuration tool created.

Ian

@900turbo Interested if you completed this? We have a Extreme 2000 Pro and a Duet conversion would be something I'm considering. I'd like to replace the extruder and add some modern quality of life functions. Thanks.

Success! After restarting the printer, I was also getting errors "G90: Probe was not triggered during probing move" after it finished its homing moves. I looked in homeall.z and it ended in a G90. That really shouldn't have impacted it so I commented it out and ran it again. This time, no errors. To test it again, I removed the ; to comment it out and it still ran fine. No errors. Go figure. I am now able to get it to home properly, do a 4 motor gantry level and run mesh compensation. Mesh compensation takes forever now because it probes the bed twice at each point and, over a 400mm square bed, that takes a lot of time. I'll tweak its settings.

Thanks all for the help. This forum is one of the best out there for solving issues.

@droftarts Result of motor drive mapping with M584- X=0 Y=1 Z=2 E=3. Extruder does not move along with X and Z when attempting to extrude. Physically looking at the board everything looks perfect. No damage. I see nothing amiss under the board. It sits on a 3D printed mount. I will say that when attempting to test motor movement following the Duet 3D guide, I get no movement at all when sending , G1 H2 X10 F3000, but I do get movement out of X,Y when sending G1 H2 Y10 F3000 and it moves how the guide describes it should in the +x and -Y directions. Here are the things you asked me to share. Homeall.g1000008461.jpg 1000008463.jpg ![1000008464.jpg](/assets/uploads/files/1745450157161-1000008464-resized.jpg Thankful for your help.

EDIT 4/25/25:
AHA! The move X command, G1 H2 X10 F3000 is turning the extruder motor upon further testing, but why does moving X in DWC work normal as expected? Why doesn't the extruder motor turn instead of X in DWC?Now, my question to you and myself is,.....Did I plug X and E into the board swapped when changing out boards? I don't think so. That means the problem lies within config.g or motor mapping doesn't it? But motor mapping seems proper and so does config.g.

I just uploaded my current .json file to the RRF config tool and notice the motor mapping it displays is different from what I'm seeing in my config.g Here it is from the RRFC. Only P3 is changed from S0 in my config.g to S1 that I'm seeing in RRFC tool. I've tried changing it to that in my config.g,, but end up with a bad result.

M569 P0 S0 D2 ; driver 0 goes backwards (X axis)
M569 P1 S0 D2 ; driver 1 goes backwards (Y axis)
M569 P2 S0 D2 ; driver 2 goes backwards (Z axis)
M569 P3 S1 D2 ; driver 3 goes forwards (extruder 0)

EDIT 4/25/24: Solved
I did have the X and E swapped into wrong positions on the board.

@airking7

Please test the latest release to confirm its fixed?

@tcamguil
Thank you I will give it a try

@droftarts Much appreciated! Sounds like just the info I was in need of

@justGuner said in G32 causes printhead to go beyond limits:

However, I keep on getting the following error:

Error: Some computed corrections exceed configured limit of 1.00mm: 2.404 -2.621

That's coming from your M671 command in config.g, which defines the leadscrew positions:

... M671 X-22:287 Y163:163 ...

See https://docs.duet3d.com/User_manual/Reference/Gcodes#m671-define-positions-of-z-pivot-points-or-bed-levelling-screws
You have omitted the S parameter, so it is defaulting to 1mm. If the levelling is likely to move, it's worth making the first probe have a wider limit eg M671 ... S5, with more probe lift (M558 H parameter).

Ian