The matrix values and kinematics are as advised by Manuel who is part of the Duet team. I tend to believe what the Duet team tell me is the correct way to do things, rather than what a forum user who joined less that 3 months ago tells me.
relax . i did't say your matrix is wrong , i just stated that "I dont know whats going on here"
also i never suggested you to use different matrix or anything . just tried to help .
your matrix is correct .
documentation for M669 command is very poor and lacking.
i didn't realize at first that in axis matrix all extruder drives are ignored when counting the drivers .
i tested your matrix , this is the actual drive mapping :
Kinematics is modified CoreXYUV, matrix:
1.00 1.00 0 0 0 0 0
1.00 -1.00 0 0 0 0 0
0 0 1.00 0 0 0 0
0 0 0 1.00 1.00 0 0
0 0 0 1.00 -1.00 0 0
0 0 0 0 0 1.00 1.00
0 0 0 0 0 1.00 -1.00
i think drive assignment(m584) in RRF is pretty flawed also . it works , but it could be better .
for example when you assign drives for axis , you assign single drive for axis , while actually you move 2 motors (in case of corexy) so both X and Y should be assigned with same 2 motors .
@dc42 when i send M584 for corexyzuvab i get this
Driver assignments: X3.2 Y3.1 Z3.0 U0.0 V0.1 (r)A0.2 (r)B0.3 E1.0:1.1:1.2:2.0:2.1:2.2, 7 axes visible
what is the (r) on AB axis?
at first i thought its rotational axis indication , but i set R0 in m584 , so i set it to rotational axis intentionally and this is what i get :
Driver assignments: X3.2 Y3.1 Z3.0 U0.0 V0.1 (r)(c)A0.2 (r)(c)B0.3 E1.0:1.1:1.2:2.0:2.1:2.2, 7 axes visible
so now there is (r) and (c) , so (c) is indication for rotational axis?
is this a bug ?