Independent Y and Z Motors not working

Jim46

Hi Phaedrux,
I forgot to report m the M584 command, I just did it and here are the result in the Console. The field is blue and the text reads:
5/12/2020, 11:59:17 AM M584
Driver assignments: X0.1 Y0.2:0.3 Z0.2:0.3 E0.0, 3 axes visible.
That looks a little strange to me. Would it be X0.1 Y0.2:0.3 Z0.4:0.5 E0.0 ??? If this is so, how do you edit that?
Also Side question. Can I use 53.3333 on Line 29 M92 Steps per mm?
Thank you so much,
Jim

Phaedrux

Alright, that confirms my suspicion. At least that explains why Y is moving. I think we need to modify how your M584 is written. The way you have it currently works in RRF2, but in RRF3 we need to specify the board location of the drivers so that it knows if it's on the main board or on a tool board, etc.

Try this

M584 X0.1 Y0.2:0.3 Z0.4:0.5 E0.0

The leading 0 identifies the main board. The number after the period is the driver number on that board.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M584_Set_drive_mapping

In RRF_3, M584 works the same way as in RRF_2, with exception that on Duet 3 the driver on expansion boards are assigned with <board address>.<driver number>. Example:
M584 X0 Y1 Z2 E3:4:1.0:1.1
The "0" index for the main board is implicit, this is equivalent to the previous example:

M584 X0.0 Y0.1 Z0.2 E0.3:0.4:1.0:1.1

I should have clued into that sooner.

@Jim46 said in Independent Y and Z Motors not working:

Also Side question. Can I use 53.3333 on Line 29 M92 Steps per mm?

Yes, decimal values are supported in Reprap firmware.

@Phaedrux said in Independent Y and Z Motors not working:

The leading 0 identifies the main board. The number after the period is the driver number on that board.

he had it like that initially and no drivers worked, removing the 0. resulted in some success. could be changed since RRF3.0 though.

Phaedrux

@bearer Hmmm. I also thought it was implied for the main board with no leading board identifier, but the result of M584 in the console indicates that either the M584 in config.g is either not being applied or there is another M584 hiding out somewhere else.

Jim46

Greetings,

Up dated M584
M584 X0.1 Y0.2:0.3 Z0.4:0.5 E0.0 ; set drive mapping, dual on Y drives 2&3 and Z drives on 4&5
Ran M584 and came back in console with:
5/12/2020, 3:18:04 PM M584
Driver assignments: X0.1 Y0.2:0.3 Z0.2:0.3 E0.0, 3 axes visible.
To your point, it looks like M584 is not updating the Z drives. How does one find a ghost version of M584? Or, could this be an issue in the firmware?
It seems like we might be near an answer?
jim

deckingman

@Jim46 I don't see an M501 in your config.g so that rules out the possibility of it being config_overide.g. Try sending M98 P"config.g". This will run the config.g file again. Then send M584 again and report the result.

droftarts

@Jim46 what version of RRF3 are you using? Send M115 and post reply. Earlier versions had an issue with defining more than one multiple motor axis in one M584 command. Try:

M584 X1 Y2:3
M584 Z4:5 E0

Ian

@droftarts said in Independent Y and Z Motors not working:

Earlier versions

it should be 3.0 (possibly 3.0beta-somethin) so you're probably onto something there.

dc42

To add to Ian's reply, I recommend you upgrade to RRF 3.01-RC12 if you are running an earlier version.

Jim46

Hello All,
Just ran M98 P"config.g" and then M584 yielding...

5/12/2020, 4:19:04 PM 	M584
Driver assignments: X0.1 Y0.2:0.3 Z0.2:0.3 E0.0, 3 axes visible

5/12/2020, 4:22:10 PM 	M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 v0.6 FIRMWARE_VERSION: 3.0beta11 ELECTRONICS: Duet 3 version v0.6 FIRMWARE_DATE: 2019-10-21b1

Loaded and ran commands from the Dashboard,

M584 X1 Y2:3
M584 Z4:5 E0

Hallelujah! It worked!
X1 X-50 and X+50 ran smoothly!
Y2&3 Y-50 and Y+50 ran smoothly
Z4&5 Z-25 and Z+25 ran the Z motors smoothly, NO effect on the Y motors now!
Gentlemen, please take a big bow and applause from me!
Jim
PS. I imagine that there are a lot of updates coming that I may ask for your help again.