Nit picked. Thanks.

@psgf2

The Duet 2 ethernet is actually aready modelled, see the documentation here for the link to it;
https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#h-3d-models

The Duex5 model is now uploaded to our github:
https://github.com/Duet3D/Duet-2-Hardware/tree/master/Duet_Expansion/Duex5v0.11

@örjane Thanks, finally updated!

Ian

I've added a bit extra to the M671 documentation in the GCode dictionary:

The X and Y coordinates in M671 are measured from the origin X0,Y0 set by M208. Measure to the pivot point of the bed where it connects to the Z axis. This is often each leadscrew, but may also be offset from the leadscrew if the bed rests on a carriage extending out from the leadscrew. The order of the X and Y coordinates is important; they relate to the order the motor drivers are defined in the M584 command. The first defined motor in M584 should be the first defined coordinates for X and Y in M671, and so on. For example, if you have M584 Z3:4:5 and M671 X[a]:[b]:[c] Y[a]:[b]:[c], the positions of X and Y for the motor on Z3 are defined by X[a],Y[a], Z4 by X[b],Y[b], and Z5 by X[c],Y[c].

Ian

@oliof Thanks, I've added a section on these (and the driver error/warnings) to the Macros page that links to the Events page: https://docs.duet3d.com/en/User_manual/Tuning/Macros#errors-and-events

Ian

@dc42 - I'm running in standalone mode. To demo my observation I made two files (fail_file_CRLF.g fail_file_LF.g attached) with a bad command on line 3. One file was saved with windows EOL (CR LF) and the other with Linux EOL (LF only).

I uploaded both to my macro directory and when I run them I get the following error messages:

LF only - calls out a problem on line 3 as expected.

21beb731-73b6-4f30-8a28-455f7c8f3b4f-image.png

CRLF file - calls out problem on line 5. It's counting one line for the CR and one line for the LF on each of lines 1 and 2, so it thinks the error on line 3 is really line 5.
5ef388ff-5639-4e35-9033-0cae1499c5cf-image.png

@mikeabuilder I think this is fixed now; the documentation (which I believe is automatically compiled from the source code):

move.axes[].jerk
Motor jerk (in mm/min)

move.axes[].speed
Maximum speed (in mm/min)

Ian

@achrn @mfs12 Thanks, I have updated the PanelDue firmware page.

Ian

@jens55 thanks fot reporting this. I have corrected it.

@droftarts No wonder I didn't find it. The search function needs to read your mind. 🙂

@fcwilt Ok confirmed yea this is exactly what I needed thanks!

Ahhh - M703. I did read this in the filaments section, then promptly forgot. I'll delete my macro (good practice, though) and put M703 into my tpost files.

And I'll put my macro practice to good use writing some macros for changing filaments.

@exerqtor I1 is no longer valid so is ignored

@owend thanks for pointing this out. I have updated the M957 documentation.

@marvineer thanks for pointing this out. I have corrected that page.

@mikeabuilder The documentation page is now updated.

@deckingman Thank you