M564... again?

soare0

Working on 6XD, updated to 3.5.0 rc2 from 3.4.6, all the boards and dwc. On 3.4.6, M564 worked fine.
However, today, I made some macro for unlocking/locking xyz, and they did not worked.

M564 S0 H0
M564 S1 H1

each in one macro, of course. They did not work, neither in DWC or on Panel Due, I mean they do nothing.
If the printer is after power on, the xyz motors are free, but I cant lock them.
If the printer is homed, and xyz motors are locked, I cant free them.

They work well otherwise, I just cant lock/unlock them with M564. I can move the axes from PanelDue, for example, after homing.
Using M564 without parameters, after homing (so it should be default, S0 H0), I get a message in PanelDue that I can move motors, etc, but ... nada, the motors are still locked. If I add any parameter, I got no message in PanelDue

It is an useful command. When it works.

For now, I replaced with M17/M18, both for XYZ and for E0, in separate macros (as this is the way I need), and I am ok with this.

T3P3Tony

@soare0 I have tested this on a machine running in SBC mode (what i had to hand for a quick test) and M564 is working as expected:

M564 S0 allowed axes to move outside of boundaries defined by M208
M564 H0 allowed axes to move when flagged as unhomed
M564 S0 H0 allowed both of those to happen
With the S1 H1 set they prevented out of bounds or unhomed movement.

From your description I am not sure M564 is the issue. When you say you can't lock/unlock them with M564, what behaviour do you expect? what do you mean by lock them?

Also the default for M564 is S1 H1
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m564-limit-axes

The default behaviour is S1 H1.

soare0

@T3P3Tony Indeed, my mistake, after homing is S1 H1 and this is right.

What I am expecting, is this (and this is what I used on 3.4.6): after homing, if I send a M564 S0 H0, to be able to move freely the axes, with my hand (at least x/y). This way I can put the head in an adequate position to work at it.
Also, I am expecting that after moving freely to that point, if I am using M564 S1 H1 to lock the steppers, so the head will stay there, whatever I am doing to it.
It worked like that previously, with 3.4.6.
Also, missing the answer in Console to either command (S1H1 or S0H0), seems to be strange.
My board it is standalone for now, as my PI5 waits for the much needed software, but I think they should work the same.
Maybe I am missing something, I will check later again, but I am not waiting for many improvements meanwhile...

T3P3Tony

@soare0 Oh right I understand.

If that did work in 3.4.6 then its a bug with 3.4.6

M564 should not de power the motors.

The commands that you need for that are indeed M18 and M17 as you are currently using.

soare0

@T3P3Tony
Indeed, right now I realised this, and hurried to my post to correct my mistake. However, you were much more faster

It was not a bug in 3.4.6, where I only could move the motors by commands issued from Panel or DWC, when (or not) homed. Being some time, I forgot that I have not done this manually, but by command.

I hope at least that this will help somebody else, as normally this kind of support should be paid, even with a beer. Have my blessings, then...