Incorrect Z microstepping

[dc42]

I just spotted a big problem with your config.g. The M584 command must come before the M350 and M906 commands.

[Surgikill]

@dc42 It's a 4 start leadscrew so I needed to divide the microstepping by 4, so instead of 1600 it's 400. Did a test print last night and it came out fine, minus the z artifacts and lack of cooling. Why does the M584 need to come before M350 and M906? Looks like those are just microstepping and motor idle currents.

I was also reading in some other documentation that I need to configure microstepping and steps/mm for each z-motor. Is this true? It seems to work fine now but I can't find anything in the official documentation about it.

[dc42]

If you look up M584 in the GCode wiki, it says clearly that it must come before certain other GCode commands. That's so that the firmware knows which drivers to apply those settings to.

You don't need to set the steps/mm or microstepping separately for the multiple Z motors.

[Surgikill]

@dc42 Is there any way I or somebody else could add this to the documentation?

[nhof]

@surgikill You can register and modify the dokuzi wiki . Should not need any special permissions. I have done this several times.

[Surgikill]

@dc42 I just looked up M584 in the g-code wiki and didn't see anything about the order. Can you point me to where you found it? I want to read up on it.

[nhof]

@surgikill It's actually listed under the M350 and M92 commands rather than the M584

[aidar]

From https://duet3d.dozuki.com/Wiki/Gcode#Section_M584_Set_drive_mapping :
Order dependence

M584 must come earlier in config.g than any M350amd M906 commands. If it creates new axes, it must also be earlier than any M92, M201, M203, M208, M350, M566, M574 , M667 and M669 commands.

[Surgikill]

@aidar Is there anything I can't run M584 before? I'm just going to stick it at the top of the list.

[dc42]

Top is ok.