I have installed a Duet/Ethernet onto a Rostock Max V3 with an SE300 hotend and I'm trying to print a NASA Saturn V S-IC F-1 combustion chamber by faithfully printing the 356 lower tubes and 178 upper tubes using G2 circles over and over and over and over and over.

This part has 226,000 G2 commands in it.

I'm literally amazed that I can print a 1mm diameter circle using a 0.5mm diameter nozzle and it looks great.

I <almost> can't see the stepper motors turn as it's printing a circle.

And the extruder also seems to not be moving.

It's very impressive that the Duet can handle such teensy-tiny movements on a delta printer.

Thanks for all your work.

I've been using G2 for a while now, and have started using it to do X,Y,Z moves and it works perfectly.

Most of the online GCODE previewers don't render this correctly, neither does Simplify3D.
This previewer does render them correctly.
https://nraynaud.github.io/webgcode/

So, thank you for allowing my SeemeCNC Rostock Max V3.2/Duet to perform the proper motions to allow me to make things. (That seam has gone away since I started doing X,Y and Z moves for each semicircle.)

This object had a diameter of 2 inches and there are 178 G2 semicircles in each layer.

spiralG2.gcode

I write little programs in C that generate GCODE.

I'm adding lines with a layer number and a Z height in them similar to the output from Simplify3d:

; layer 5, Z = 1.2

But when I load and print, DWC does not show a layer time or the current layer number.

What is it looking for in the GCODE to figure out this information.

I've also added some other things I see in generated GCODE like:

;   layerHeight,0.3
; tool H0.300 W0.500
; layer 1, Z = 0.000000
; feature inner perimeter

But I can't get the right stuff in there.

I write little programs in C that generate GCODE.

I've been using G2 for a while now, and have started using it to do X,Y,Z moves and it works perfectly.

Most of the online GCODE previewers don't render this correctly, neither does Simplify3D.
This previewer does render them correctly.
https://nraynaud.github.io/webgcode/

So, thank you for allowing my SeemeCNC Rostock Max V3.2/Duet to perform the proper motions to allow me to make things. (That seam has gone away since I started doing X,Y and Z moves for each semicircle.)

This object had a diameter of 2 inches and there are 178 G2 semicircles in each layer.

spiralG2.gcode

I tried to get a simple failing example for HOURS yesterday and I could not get it to happen using a simpler set of GCode.

I'm thinking along the same lines you are that it might be peeling off.

I'll try more experiments again today and post again.
Also with my printer/firmware information. (Which is in my one other post if you're curious enough to look it up.)

I'm experimenting with some code like this:

G1 X0.000000 Y101.599998 Z1.386840 E 383.897919 F 3000.000000
G1 X0.000000 Y71.500595 Z1.386840 E 389.741913 F 3000.000000
G2 I0.000000 J-71.500595 X0.000000 Y71.500595 E409.353699
G60
G1 X0.000000 Y101.599998 Z1.386840 E 403.353699 F 3000.000000
G1 X0.000000 Y101.599998 Z1.386840 E 409.197693 F 3000.000000
G0 R0 F3000

and it seems like the G2 is not quite completing before the following G1 starts.

Maybe I'll put a pause and see if it changes things.

Anyway, if you could take a peek, I'd appreciate it.

I can't guarantee you'll be able to see it, but this image shows a G2 coming around clockwise, and the G1 moves coming towards the viewer.

See how the lower layers seem to start the G1 before the G2 finishes coming around?

Awesome.

I'll test it after the release.

Thank you.

I just switched to Inches (G20) and used a M579 to scale to 1/20 and my G2/G3 arcs are looking like they are ignoring the scale command.

Further testing looks like I and J ignore the scale factor, but X and Y honor the scale factor.

@oliof I guess I shouldn't call it a "slicer".

It just interpolates a spline curve every 0.2mm, calculates a radius, rotates the center and edge points and generates 356 G2 codes to make circles.

Another program generates tubes that turn into squashed tubes (two lines and two half-circles at the ends) as the combustion chamber moves through the throat of the engine.

So it's really a G1 and G2 creator program.

@oliof If you're interested in playing around with slicing, the model is in OnShape under S-IC F-1 Thrust Chamber

@oliof I tried Simplify and Cura and they all made a real mess, so I wrote a slicer in C to generate just the patterns I need for this combustion chamber.

I <think> Simplify could have been tamed, but I couldn't get it to generate every circle exactly the same for every layer so there were visual disturbances.

It's just at the resolution limit for slicers I think. (Hypothesis only)