Stutters during arcs & circles

Jarery

Recent upgrades to my printer, but same board and firmware as previous.

Slicer is Superslicer Version: 2.4.58.5, which I used prior also with no issues.

Doing parts now I get blobs and zits on my part, even in vase mode
I can watch it in vase mode with no layer changes or retractions and it pauses/stutters whenever it's doing arcs or circles.

Issue is very similar to https://youtu.be/Hvw3DrVAeTA

edit :
https://youtu.be/ZM1MYbsC5Aw
this is the same problem, and zits on parts, except I have power recovery off so his solution does not work.
I also reduced resolution to 0.5mm in slicer, so that round egg shape is now low poly looking, but same problem,

Is there a setting with RRF that helps this situation or is this purely slicer based ?

System:
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.3+ (2022-10-06)
Duet WiFi Server Version: 1.27

Edit 2: Turns out to be related to daemon.g
When I did my upgrades I added neopixels to printhead which change based on different input status.
Have not figured out just what in the macros was causing the pauses.
Daemon was only 2 lines G4 1 , and a P98 to run the led macro.

jay_s_uk

@Jarery probably the G4 S1 causing a 1 second pause

deckingman

@Jarery It's probably as @jay_s_uk says, but there may be other issues which could only be guessed at unless you provide more information such as your configuration files and slicer settings.

Jarery

@jay_s_uk

Probably, so I just removed the daemon.g completely and its running fine.
When I get time I'll try to find why the G4 S1 is causing a pause instead of just reloading macro, its also recommended in the documentation to have such a command.

Phaedrux

@Jarery said in Stutters during arcs & circles:

Daemon was only 2 lines G4 1 , and a P98 to run the led macro.

The documentation is more specific.

https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands#daemong

It is recommended to use a while loop inside the daemon.g file if you are using it to prevent the firmware having to open it every 10 seconds. E.g if you want a shorter update time then put a while loop inside the daemon.g with G4 S1 in it for 1 second repeats.

If you have just 2 lines to pause and turn on the LEDs that will be executed every 10 seconds. You're missing the while loop.

Is daemon.g the best place for your LED macro?

dc42

@Jarery driving Neopixels from Duet 2 requires motion to be paused while the data is sent to the Neopixels, because their timing requirements are strict, so step pulses cannot be generated at the same time.

Duet 3 main boards have a dedicated output for LED strips so that motion does not need to be interrupted.