3.4.0-b6 – Delta – print leaning/moving on Y+ and Z+

jay_s_uk

@fred-y nothing out of the ordinary in your config that I can see that would explain those hiccups

Fred-Y

@jay_s_uk Thanks for checking it!

I'm finding odd that the issue only start to happen when the long walls are getting printed, the skirt and round walls looks to be properly printed at the correct height.

Everything before the red arrows are ok - I forgot to post this screenshot on my initial post.

T3P3Tony

@fred-y you had a high hiccup count in both M122s you posted so which could be an indication of a cause of the problem. I assume you are printing the skirt at a different speed than the perimeter of the first layer where you see the issue? as a test can you set the first layer to the same speed as the skirt, or vice versa?

Fred-Y

@t3p3tony By looking at the gcode and also the gcode preview, the skirt and perimeters appear to be at the same speed 20mm/s (F1200).

Only the solid infill is at 30mm/s.

Is there a way to log when (line #) the hiccups happen?

Fred-Y

Just wanted to check if there is any updates here, I did get another file had the same issue but this time immediately when the print start.
On the first gcode file it was after having printed the skirt and a few small features but still on the first layer.

SR - Effector Spring-2-fail.gcode

M122 from beta6

11/29/2021, 9:29:25 PM	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta6 (2021-11-06 11:37:41) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6JKDA-3S46N-1VWZD
Used output buffers: 4 of 24 (21 max)
=== RTOS ===
Static ram: 23772
Dynamic ram: 76760 of which 16 recycled
Never used RAM 10956, free system stack 122 words
Tasks: NETWORK(ready,14.8%,220) ACCEL(notifyWait,0.0%,350) HEAT(notifyWait,0.0%,310) Move(notifyWait,0.3%,283) MAIN(running,84.4%,127) IDLE(ready,0.5%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:15 ago, cause: software
Last software reset at 2021-11-27 18:55, reason: User, GCodes spinning, available RAM 11120, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 29.6, current 31.4, max 31.6
Supply voltage: min 23.7, current 23.9, 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
Driver 0: pos 65151, ok, SG min 0
Driver 1: pos 51461, ok, SG min 0
Driver 2: pos 55683, ok, SG min 0
Driver 3: pos 0, ok, SG min 0
Driver 4: pos 0, standstill, SG min n/a
Driver 5: pos 0
Driver 6: pos 0
Driver 7: pos 0
Driver 8: pos 0
Driver 9: pos 0
Driver 10: pos 0
Driver 11: pos 0
Date/time: 2021-11-29 21:29:24
Cache data hit count 4294967295
Slowest loop: 216.29ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.6ms, write time 3.0ms, max retries 0
=== Move ===
DMs created 83, segments created 24, maxWait 122805ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 201, completed 195, hiccups 72, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== 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 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X107.193 Y-7.073 E66.50864" 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
=== Network ===
Slowest loop: 213.13ms; 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.26
WiFi MAC address 60:01:94:2e:1b:d6
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26736
WiFi IP address 192.168.50.254
WiFi signal strength -54dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

The fill prints well after rolling back to RRF3.3
M122

11/29/2021, 9:39:21 PM	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6JKDA-3S46N-1VWZD
Used output buffers: 3 of 24 (19 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 76488 of which 12 recycled
Never used RAM 11184, free system stack 112 words
Tasks: NETWORK(ready,13.4%,252) ACCEL(notifyWait,0.0%,334) HEAT(delaying,0.0%,314) Move(notifyWait,0.2%,311) MAIN(running,85.9%,128) IDLE(ready,0.5%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:48 ago, cause: software
Last software reset at 2021-11-27 18:55, reason: User, GCodes spinning, available RAM 11120, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 32.0, current 33.2, max 33.6
Supply voltage: min 23.7, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/36/0, gc cycles 0
Driver 0: position 51925, ok, SG min/max 0/196
Driver 1: position 63275, ok, SG min/max 0/191
Driver 2: position 58898, ok, SG min/max 0/906
Driver 3: position 0, ok, SG min/max 0/66
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-11-29 21:39:20
Cache data hit count 4294967295
Slowest loop: 212.15ms; fastest: 0.11ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 35546ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 1076, completed moves 1037, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X43.263 Y-8.009 E29.37223" 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.
=== Network ===
Slowest loop: 187.35ms; 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.26
WiFi MAC address 60:01:94:2e:1b:d6
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25520
WiFi IP address 192.168.50.254
WiFi signal strength -63dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Please, let me know if I can do anything to help.

o_lampe

@fred-y
What if you reduce microstepping? (from 16 to 8). Isn't the hiccup count an indication of too many step pulses?

Fred-Y

@o_lampe Unfortunately, the same issue happen.

I changed
M350 X16 Y16 Z16 E16 I1
M92 X160.00 Y160.00 Z160.00 U400 E726
to
M350 X8 Y8 Z8 E16 I1
M92 X80.00 Y80.00 Z80.00 U400 E726

11/30/2021, 8:11:36 AM	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta6 (2021-11-06 11:37:41) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6JKDA-3S46N-1VWZD
Used output buffers: 10 of 24 (21 max)
=== RTOS ===
Static ram: 23772
Dynamic ram: 76760 of which 16 recycled
Never used RAM 8100, free system stack 110 words
Tasks: NETWORK(ready,12.6%,232) ACCEL(notifyWait,0.0%,350) HEAT(notifyWait,0.0%,307) Move(notifyWait,0.6%,283) MAIN(running,86.5%,127) IDLE(ready,0.3%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:07:36 ago, cause: software
Last software reset at 2021-11-30 08:03, reason: User, GCodes spinning, available RAM 11004, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00417000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 31.2, current 32.5, max 32.8
Supply voltage: min 23.7, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/36/0, gc cycles 0
Driver 0: pos 30667, ok, SG min 0
Driver 1: pos 27794, ok, SG min 0
Driver 2: pos 29655, ok, SG min 0
Driver 3: pos 0, ok, SG min 0
Driver 4: pos 0, standstill, SG min n/a
Driver 5: pos 0
Driver 6: pos 0
Driver 7: pos 0
Driver 8: pos 0
Driver 9: pos 0
Driver 10: pos 0
Driver 11: pos 0
Date/time: 2021-11-30 08:11:35
Cache data hit count 4294967295
Slowest loop: 218.08ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 24, maxWait 264309ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 1305, completed 1265, hiccups 37, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== 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 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X-49.368 Y9.851 E40.15928" 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
=== Network ===
Slowest loop: 174.42ms; 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.26
WiFi MAC address 60:01:94:2e:1b:d6
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26904
WiFi IP address 192.168.50.254
WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

dc42

@fred-y thanks for the additional example. ~~Can you post a photo or video of what happens when you print that one?~~ EDIT: looks like I may not need that.

dc42

@fred-y I have found and fixed the bug that was causing this. The fix will be in 3.4.0beta7. The hiccups were the clue.

Fred-Y

@dc42 Thank you for the update, I started to be concerned that my board might be defective as I was the only one reporting this issue - I was close to test one from another printer or just buy another one.

Let me know if you have a pre-beta version you want to be validated, I can do it fairly quickly.