@owend - thanks! this is very helpful. I'm going to test today this all today, including parking the head.

@phaedrux @OwenD

So, I did set in config.g:

M84 S0

Am I misunderstanding what M84 does? I thought setting the seconds(S) to zero would hold infinitely.

But the motors still lost power at the end of the print and dropped... Alternatively, is there a way to run a script or macro at the end of every print that will park the print head in a designated place? I could just type up the gcode and add it to the footer but that is not optimal for my purposes.

I need the Z axis stepper of my machine to stay engaged at the end of a print; otherwise the print head drops. I would like the idle timeout of my other axis to be 30 seconds. Can I separate these? In Config.g, would the syntax be:

M84 X Y S30 Z S0

Are tool mix ratios limited to a single decimal place?

e.g. M567 P2 E0.1:0.2:0.1:0.6

or can it be:

M567 P2 E0.15:0.25:0.15:0.45

or even:

M567 P2 E0.155:0.255:0.155:0.435

providing that the the values total to 1

@fcwilt

The N0 etc is line numbers - I find it helpful for troubleshooting.

I’ll have to report back with specifics, but - my m203 X and Y values are 6000, for Z and E they are lower.

@oliof and @fcwilt

I did read that on the Duet supported Gcode page, but I should still be able to use both G1 and G0 in my gcode if for no other reason that human readability, and with the following, I would assume that I can expect the first command to travel at twice the speed of the second and third.

N0 G0 F1000 X89.491664 Y138.276349 Z3.000
N1 G1 F500 X89.491664 Y138.276349 Z0
N2 G1 F500 X94.440476 Y138.573733 Z0 E0.310

But for some reason, all travel is about the same speed...

m203 max is defined at 6000 so I should be able to use any feedrate under that.

I'm used to working with a different flavor of gcode and I'm a little confused about controlling the speed for Duet Wifi.

background: I am generating gcode for a custom machine using Rhino to model and Grasshopper to create code. I'm switching from a tinyg control board by synthetos to the DuetWifi. I'm used to using G1 and G0 separately with different speed assignments so that the tool will move fast when not extruding (G0 for traveling between extrusion, G1 for travel associated with extrusion). In response to the following gcode, my G0 movements are not any faster than my G1 movements. What am I missing?

;PRINTING_2018_SORTING_1.0.4

;Friday, June 5th 2020 (13:51:03)

G90 ;ABSOLUTE DISTANCE MODE
M82 ; EXTRUDER ABSOLUTE DISTANCE MODE
G0 F1000 ;feedrate
G1 F500 ;feedrate

G92 A0 ;VERIFY AND SET A POSITION TO 0

M567 P0 E1:0:0:0:0
N0 G0 F1000 X89.491664 Y138.276349 Z3.000
N1 G1 F500 X89.491664 Y138.276349 Z0
N2 G1 F500 X94.440476 Y138.573733 Z0 E0.310
N3 G1 F500 X99.333629 Y139.371951 Z0 E0.620
N4 G1 F500 X104.124716 Y140.647376 Z0 E0.930
N5 G1 F500 X108.7726 Y142.373478 Z0 E1.239
N6 G1 F500 X113.239765 Y144.524609 Z0 E1.549
N7 G1 F500 X117.489313 Y147.078892 Z0 E1.859

Thanks, It helped me find a typo in M208 as declared in config.g

Issue closed.

I have a cartesian setup and I want my 0,0,0 home to be in the center for X and Y. For instance, my X settings range from -243 to 243 but when I home it is still setting the X min as 0 rather than -243.

I've tried adding "G92 x -243" to the end of homex.g and attempted entering it into the console. It does not seem to acknowledge negative values.

I guess that does work - I was looking feedback on the screen - like maybe 'ok' if it ran the command.