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

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'.

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.)

@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.

@falkia Most (non-3D) broken or superseded printers have at least a couple of optical endstops, so scavenging is a good option.

@stout I wonder if the 4mm banding is a result of out of phase inaccuracies in the 8mm lead screws.

I bought four lead screws last year and found that two of them (A and B) meshed together well, but two others (C and D) did not mesh with A or B, but would mesh with each other, but only when I rotated one or the other until I found a particular meshing alignment. I decided that rods C and D had matching irregularities in pitch and have not used them.

If your lead screws have a similar irregularity then z movement might exhibit an error with a 4mm period.

@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.

My printer (Duet 2 Wifi firmware 3.2.2) has developed a recent habit of 'forgetting' that it has been homed.

I home by clicking the home x, home y and home z buttons in the web control and they home correctly but a short time later the buttons revert from their homed state to the un-homed state. (The X, Y and Z homing buttons on the PanelDue show the same status as the web controls.)

I recently changed extruder and had to change a few bits on the config file, but have made no changes to homex.g, homey.g and homez.g.

config.g

M122 does not seem to report any error.

console 1.txt

@dc42 Does the firmware use a finer G2/G3 arc segment for Duet boards with better calculation capacity?

I'm working with G2/G3 segments on my Duet 2 Wifi and I can occasionally see fine facets in cylinders (occasionally as in when everything else worked well!).

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.

@Sindarius Works fine for gcode from S3D, but not my return-delimited files come up blank. (The Minecraft style is really cool!)

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'.

Ah, I would never hav worked that out. It seems like I should simply make three segments in the circles. I'll give that a go tomorrow.

Thanks for fixing it.

@MJLew Sorry, I uploaded two files that fail (the second is a misnamed copy of the first, I think). Here is a two layer circle that works: test12 8.8001.gcode