X Axis stops working after moving Y

DC

@fcwilt Correct.
That was my first assumption as well. I checked and redid all connections but the issue is still there.
Also as mentioned - If I switch X and Z around, the problem moves to the Z axis and now the X axis works just fine.

DC

Another thing I noticed today: After moving the Y axis the motors will emit a certain high frequency sound while idling.
After a while that sound stops and then I'm yet again able to move the X axis.

fcwilt

@dc said in X Axis stops working after moving Y:

Another thing I noticed today: After moving the Y axis the motors will emit a certain high frequency sound while idling.
After a while that sound stops and then I'm yet again able to move the X axis.

I notice that in one of the M584 commands you have Y1:3.

Below that you have M584 P3.

That's two axes Y and P referencing the same stepper. Also I have no idea what the period after the P would mean.

Is that intentional?

Frederick

DC

@fcwilt I have no idea what that is supposed to to. I can't remember adding it but I might have copy pasted a bit too much when I was setting up the dual Y axis.

I'll try to remove it as soon as I have a few minutes, thanks!

jay_s_uk

@fcwilt P allows you to hide axis so they aren't visible in DWC https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m584-set-drive-mapping
In this instance it isn't required.

@DC can you post your full config?
I don't see why M669 K0 etc is required on a standard workbee setup

droftarts

@dc said in X Axis stops working after moving Y:

Remove this line (unnecessary):

M584 P3.

Remove U16 from this line (potentially confusing firmware):

M350 X16 Y16 Z16 U16 I1 ; Configure microstepping

Remove this line (unnecessary, potentially confusing firmware):

M669 K0 X1:0:0:0 Y0:1:0:1 Z0:0:1:0

If that doesn't help, post your full config.g and any macros run from it. Also send M98 P"config.g" and post response.

Ian

fcwilt

@jay_s_uk said in X Axis stops working after moving Y:

@fcwilt P allows you to hide axis so they aren't visible in DWC https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m584-set-drive-mapping

Thanks - I had forgotten about that.

Frederick

DC

Remove U16 from this line (potentially confusing firmware):

M350 X16 Y16 Z16 U16 I1 ; Configure microstepping

Remove this line (unnecessary, potentially confusing firmware):

M669 K0 X1:0:0:0 Y0:1:0:1 Z0:0:1:0

Woohoo! That seems to have been it - I'm now able to move all 3 axis again and again and again... Thanks a lot for the suggestions everyone!

Can anybody explain to me what the proper setting for M350 should be or how I figure it out?
And what is the purpose of M669? Why shouldn't kinematics be set to cartesian on my Workbee?

And last but not least; Does anyone happen to have a link to a full 3.4 config for a setup matching mine?

Sincerely,
Daniel

fcwilt

@dc said in X Axis stops working after moving Y:

Can anybody explain to me what the proper setting for M350 should be or how I figure it out?

Well generally you need the letters for each axis, in your case X, Y, Z, and the letters for your extruders (usually E0 and/or E1).

Some folks put one M350 for the axes and another for the extruders.

I've never used anything but 16x on the axes and extruders and I1 to enable interpolation. The reason for always using 16x was the the boards I started with, Duet 2 WiFi, only supported interpolation for 16x.

If there is some really good reason for using other than 16x I have not read about it. Others may have a better understanding and will chime in.

And what is the purpose of M669? Why shouldn't kinematics be set to cartesian on my Workbee?

M669 K0 is a quick way of setting the X, Y, Z parameters for a Cartesian. You can use X, Y, Z if you know what they should be for a given kinematics. But having K0 and the X, Y, Z parameters is redundant and possible troublesome if the K value specifies one set of X, Y, Z values and you specify another set with the X, Y, Z parameters.

Frederick

DC

@fcwilt said in X Axis stops working after moving Y:

I've never used anything but 16x on the axes and extruders and I1 to enable interpolation. The reason for always using 16x was the the boards I started with, Duet 2 WiFi, only supported interpolation for 16x.

16x it is

M669 K0 is a quick way of setting the X, Y, Z parameters for a Cartesian. You can use X, Y, Z if you know what they should be for a given kinematics. But having K0 and the X, Y, Z parameters is redundant and possible troublesome if the K value specifies one set of X, Y, Z values and you specify another set with the X, Y, Z parameters.

That makes sense, thanks for the explanation!

droftarts

@dc cartesian is also the default kinematics, no M669 needed.

Ian