@phaedrux well im not having an issue now for some reason, so likely you guys were right and it was a mechanical issue. Thank you for your help!

@phaedrux well im not having an issue now for some reason, so likely you guys were right and it was a mechanical issue. Thank you for your help!

@phaedrux Ok i tightened down the set screw on my stepper pulleys and made sure everything else in the housing looked good. Running again to see if that made any difference.

@phaedrux yes

@phaedrux
This is what it returned when I did M122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-956GU-DJ3SW-6JKDA-3S86L-KAMBG
Used output buffers: 3 of 24 (22 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 75024 of which 40 recycled
Never used RAM 13148, free system stack 188 words
Tasks: NETWORK(ready,11.4%,232) HEAT(notifyWait,0.0%,316) Move(notifyWait,0.0%,364) DUEX(notifyWait,0.0%,24) MAIN(running,85.3%,410) IDLE(ready,3.3%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:22 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 13148, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 22.9, current 26.6, max 26.8
Supply voltage: min 24.1, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min n/a
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 2022-05-11 19:18:39
Cache data hit count 803251729
Slowest loop: 2.51ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== DueX ===
Read count 1, 2.65 reads/min
=== Network ===
Slowest loop: 124.64ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.25
  WiFi MAC address cc:50:e3:66:6e:ff
  WiFi Vcc 3.35, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 26376
  WiFi IP address 192.168.40.123
  WiFi signal strength -33dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

@chrishamm also, is there a way to run it NOT from the SD and how does that work?

@chrishamm Will try that and report back. Thank you.

@chrishamm Latest firmware.

I'm printing via dragging and dropping into the web interface, does that just upload to the SD card and print from that? cause if so, i may need to change the card..

Hey all,

My printer was running fine and all of a sudden it starts jerking hard when making big arcs. The X and Y seem to be skipping steps and it wont trace the same arc twice correctly. I searched the forums and saw that for other people low jerk/acceleration parameters in the config file were to blame. I have accounted for this and I am still getting stuttering and skipping.

I have a HUNCH that it has something to do with how the slicer is breaking up large arcs into small line segments, but I thought that the processing capabilities of a duet2wifi would be plenty to mitigate this issue?

Seems like printing a large arc shouldnt be that big of a problem, but im at my wits end. Any help would be super appreciated!

BLV Cube 300 x 300
Duet2Wifi + Duex5
Triple independent Z
Latest firmware
Prusa slicer / Cura (same issue with both)

Thanks