I have added this as an issue to the github tracker
https://github.com/dc42/RepRapFirmware/issues/345

HWW-GS created this issue in dc42/RepRapFirmware

closed M584 Multi Axis/Motor Mapping Error #345

@Danal A workaround solution until things get a proper fix!! Fantastic. I was just about to ask what your day to day config looks like since in the example from before it E got overwritten but you had a working readout from your day to day.

@Danal Triple motor Z also overwrote the E mapping

My best guess is that whatever values are getting used for multi motor mapping are not reset or filled or something between cycles of the code loop running

Yeah look at this one

M584 X0.0:0.1 Y0.2:0.3 Z0.4:0.5 E1.0:1.1

results in a reported drive map of
X0.0:0.1 Y0.0:0.1 Z0.0:0.1 E0.0:0.1

@droftarts Assigning them all individually like that they mapped correctly, the drive map report matched the mapping command.

I played around with it a bit more and I think whats happening has something to do with having multiple motors on two axis

I tried M584 X0.0 Y0.1:0.2 Z0.3 U0.4 V0.5 W1.0 A1.1 B1.2 P8 and that mapped correctly

However when I tried M584 X0.0 Y0.1:0.2 Z0.3:0.4 U0.5 V1.0 W1.1 A1.2 P7

the resulting map was X0.0 Y0.1:0.2 Z0.1:0.2 U0.5 V1.0 W1.1 A1.2

Also in all cases the extruders were mapped to 0:0 and 0:1 which I think is a default value since no E parameter was in the mapping

@droftarts No change in the result from removing the explicit board number, I also went ahead and threw in my other test of assigning all the Z motors to the Y axis to confirm that entering the mapping into the console was changing things and you can see the strange result from that as well. The Y axis is mapped correctly but both Z and E are incorrect.

Dont know why I didnt think of this before using the M584 command on its own spits out the drive mapping in the console. I never got around to actually testing the extruders but looks like those are mapped wrong as well. You can see in this photo I tried entering the M584 with the mapping command as well and the report after is also screwed up.

The first info from the M584 shows 0.0 and 0.1 mapped into the first two spots on the z axis followed by 0.5 and 0.4 this is using the last config line I was using which was "M584 X1.0 Y0.0:0.1 Z0.5:0.4:0.3:0.2 E1.1:1.2"

Then in the console I tried entering my original config of "M584 X1.0 Y0.0:0.1 Z0.2:0.3:0.4:0.5 E1.1:1.2" and it again results in 0.0 and 0.1 in the first two spots with 0.2 and 0.3 filling the last two.

And in both cases the extruders are mapped to 0.0 and 0.1 which I never noticed before as well

@droftarts Both the main board with M115 and the expansion with M115 B1 report back with Firmware 3.0RC1

@deckingman Using M564 H0 and omiting the H2 parameter from the G1 commands results in the same movements, so no difference there.

@deckingman Gave all your suggestions a shot and nothing changed in the way it operated.

Tried out a couple of different configurations as well just to see what kind of other behaviors would come out of it.

Same setup as in my images above but with a different drive mapping. I defined all of what should be the Z motors as the Y axis and the Y motors on the Z axis.

M584 X1.0 Y0.2:0.3:0.4:0.5 Z0.0:0.1 E1.1:1.2

With this mapping the four vertical motors spun as expected when given Y movement commands, when a Z movement was given only two motors would run but it was two of the vertical motors (the two that would run were the motors matching the 0.2 and 0.3 in the Y section of the mapping)

Trying a different test using the same mapping as in my original config but changing the order of the motors in the Z section of the drive map by reversing like so

M584 X1.0 Y0.0:0.1 Z0.5:0.4:0.3:0.2 E1.1:1.2

Behaves exactly how I suspected it might and results in the motors with the blue tape turning instead of the ones with the green tape, along with of course the two motors on their sides.

I suspect that it really is something going on with the firmware but I do not know how to confirm or fix it.

Wont be back at the workshop until after Christmas, but I just rebuilt the setup the printer in question is running using parts I had on hand at home. This way I can continue trying to figure out what is going on.

This is running the exact same config.g as the machine at the workshop (I just downloaded the one from my post above) and exhibits the same problem. Since both setups are showing the same problem using completely different hardware I think that likely rules out connections as the problem.

The motors on their sides represent the Y axis motors, the 4 vertical motors are the Z axis motors with green and blue tape marking left and right sides of the machine.

Sending G1 H2 Y50 F5000 twice with a pause between

Sending G1 H2 Z1 F100 twice with a pause between