Fixed! Thank you. Now I have a beautiful cylinder.

@phaedrux Thanks Phaedrux. The software versions are not entirely current (3.2.2 for the Duet, I think). Now that I've re-started the PanelDue and also stopped PrusaSlicer from overwriting my maximum rates it is all back under my control!

(I'm not keen to update the firmwares right now as I'm printing parts for a new printer. Updates once I am done!)

Worked for me on two printers with Duet 2 Wifi. One was update from 3.1.1 and the other from 3.2. Updated and restarted and both printers appeared on the net.

Your point about defining the centre relative to the ending points is probably exactly why I am getting the fluted cylinders! Thank you. I'll give it a burl with fixed up points.

(I am indeed using CCW coordinates for the G2 move, but that's just because I was unable to upload all of the examples I tried. They include CCW coordinates for G3 moves.)

@MJLew OK, I found the hidden interface element (see the rant below) that Phaedrux mentioned, but even though it promises when the command key is down to open the link "in a new tab behind the current one" is does no such thing. It just scrolls the current tab to put the selected command at the top.

When I hold the control key down I can get the popup that Infiniteloop showed (and it works), that is not how I have to use proper links in the browser.

• <rant> Hidden interface elements seem to be all the rage (even with Apple software) but they are terrible things for core elements of human computer interface. People should not have to hunt around for random hotspots that do surprising things, and people should not have to RTFM to work a web-page!

@jay_s_uk said in Y axis gains unasked for limits after homing:

M98 P"config.g"

Plus and minus 10 million seem to be acceptable and should suffice.

1. The coding language that I use most of the time (Livecode) uses "end repeat" to end a repeat loop, "end if" to end a conditional et cetera. It is very nice in that it does not depend on indents and it is entirely unambiguous. I commend it as a model to follow.

2. No. Do not allow mixtures. They will be confusing.

3. Ideally you would make the delimiting by keyword and do not support indentation. However, I'm guessing that indentation is already in use, and in that case your idea of something like 'noblockindent' would work rather like M82 and M83 (absolute and relative extruder). Perhaps it should have two keywords 'blockindent' and 'blockwords'.

@Phaedrux Thank you. Yes, that seems like it will be the problem. I wanted the extruder to have zero idle, not the others... I'll change it and my silence will indicate that the problem is fixed! Thank you.

@Norder I also recommend TitanX. It costs more than plain ABS but I need fewer attempts to get good prints. More than worth it to me.

@MJLew OK, I found the hidden interface element (see the rant below) that Phaedrux mentioned, but even though it promises when the command key is down to open the link "in a new tab behind the current one" is does no such thing. It just scrolls the current tab to put the selected command at the top.

When I hold the control key down I can get the popup that Infiniteloop showed (and it works), that is not how I have to use proper links in the browser.

• <rant> Hidden interface elements seem to be all the rage (even with Apple software) but they are terrible things for core elements of human computer interface. People should not have to hunt around for random hotspots that do surprising things, and people should not have to RTFM to work a web-page!

@infiniteloop I can't get that popup menu with any click on my Mac using Safari or with the Brave browser. Normally a command-click on a link will open the link in a new tab but it just scrolls rapidly (not fast enough and yet too fast!) to the entry in the existing tab. Opening in new tabs is expected behaviour and is very useful.

@kuon Oh my goodness, yes! I find the scrolling to be awful and have started using the RepRap gcode page (https://reprap.org/wiki/G-code) as a preliminary source because the new Duet docs are so slow to load...

@Norder I also recommend TitanX. It costs more than plain ABS but I need fewer attempts to get good prints. More than worth it to me.

@jay_s_uk said in Y axis gains unasked for limits after homing:

M98 P"config.g"

Plus and minus 10 million seem to be acceptable and should suffice.

@jay_s_uk Thanks. Will do.

@jay_s_uk OK, that's a shame. Is there an upper limit on the numbers I can put in?

I'm setting up a newly made printer with a rotating spindle in place of the Y-axis. I need to have no min or max limits on Y so it can spin without end. I have put no Y limits into the config.g file, and immediately after I start the board the Y-axis works as expected, but after homing all axes with homeall.g the y axis now will not go outside 0 and 200 (mm, I suppose, but really degrees of rotation). Re-starting removes the limits until I home again.
There is no command to put limits onto Y in the homeall.g file. What have I done wrong?

M115 result: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.4 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2022-10-20 16:18:28

Config file :

; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.14 on Thu Nov 03 2022 16:12:44 GMT+1100 (Australian Eastern Daylight Time)

; General preferences
M575 P1 S1 B57600                              ; enable support for PanelDue
G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"Spindle pen printer"                    ; set printer name

; Network
M552 S1                                        ; enable network
M586 P0 S1                                     ; enable HTTP
M586 P1 S0                                     ; disable FTP
M586 P2 S0                                     ; disable Telnet

; Drives
M569 P0 S0                                     ; physical drive 0 goes backwards
M569 P1 S1                                     ; physical drive 1 goes forwards
M569 P2 S0                                     ; physical drive 2 goes backwards
M569 P3 S1                                     ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3                               ; set drive mapping
M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
M92 X305.00 Y44.44 Z496.00 E420.00             ; set steps per mm
M566 X5400.00 Y900.00 Z600.00 E120.00           ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z1000 E1200.00        ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00            ; set accelerations (mm/s^2)
M906 X600 Y600 Z600 E600 I30                   ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout

; Axis Limits
M208 X0 Z0 S1                               ; set axis minima
M208 X85 Z100 S0                          ; set axis maxima

; Endstops
M574 X1 S1 P"io1.in"                         ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in
M574 Z2 S1 P"io2.in"                         ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin io1.in

;allow movement without homing
M564 H0 S1

; Z-Probe
M558 P0 H5 F120 T6000                          ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:20 Y15:195 S20                        ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138  ; configure sensor 0 as thermistor on pin ...
M950 H0 C"out1" T0                           ; create nozzle heater output on e0heat and map it to sensor 0
M307 H0 B0 S1.00                               ; disable bang-bang mode for heater  and set PWM limit
M143 H0 S280                                   ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out5" Q500                           ; create fan 0 on pin fan1 and set its frequency
M106 P0 S3 H0 T45                              ; set fan 0 value. Thermostatic control is turned on

; Tools
M563 P0 S"Extruder" D0 H0 F0                               ; define tool 0
G10 P0 X0 Y0 Z0                                ; set tool 0 axis offsets
G10 P0 R0 S0                                   ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
T0                                             ; select first tool


code_text

And the homeall file here:

; File homeall.g
G91 ; relative movement
G1 H2 Z4 F600 ; ensure head is clear of the bed
G1 H1 X-200 F3000 ; move radius towards min until the endstop switch is triggered
G1 H2 X5 ; move radius in by 5mm
G1 H1 X-20 F600 ; move radius slowly to the endstop switch again
; Home bed
;G1 H2 X-30 ; move to 30mm from centre of bed
G92 Y0 ; define current position as Y0
G90 ; absolute movement
; Home Z
G1 X5 Y0 ; put head near the centre of the bed, or wherever you want to probe
G91 ; relative movement
G1 H1 Z400 F900 ; raise head to the Z probe trigger height
G1 Z-4 F400; back off
G1 H1 Z400 F100 ;slow probe
G92 Z100  ;set this to the correct value!
G90 ; back to absolute mode
G1 Z5 F600; put head over the centre of the bed, or wherever you want to probe

@phaedrux Thanks Phaedrux. The software versions are not entirely current (3.2.2 for the Duet, I think). Now that I've re-started the PanelDue and also stopped PrusaSlicer from overwriting my maximum rates it is all back under my control!

(I'm not keen to update the firmwares right now as I'm printing parts for a new printer. Updates once I am done!)

@mjlew OK, I think I've solved my problem as it corrected itself when I cycled the power on the PanelDue. It seems to me that when I changed the z acceleration settings in the config.g file and restarted the board, the PanelDue was not updated. Restarting it updated its settings.

I'm not certain that my diagnosis is correct, as it seems strange to me that the command from the PanelDue would ignore the config settings, but what do I know?