XY Movement pauses mid movement.

BlueDust

It happened again.

	m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet Ethernet 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3S0-7JTDL-3SN6N-TS6VG
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93836 of which 0 recycled
Exception stack ram used: 632
Never used ram: 10892
Tasks: NETWORK(ready,676) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,1300) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 10:07:57 ago, cause: power up
Last software reset at 2021-06-27 14:32, reason: User, spinning module GCodes, available RAM 11064 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 15.0ms, max retries 0
MCU temperature: min 19.5, current 35.7, max 39.3
Supply voltage: min 23.6, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/272
Driver 1: standstill, SG min/max 0/260
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max 0/192
Driver 8: standstill, SG min/max 0/153
Driver 9: standstill, SG min/max 0/177
Date/time: 2021-06-28 22:53:48
Cache data hit count 4294967295
Slowest loop: 479.98ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 770128, FreeDm: 160, MinFreeDm: 148, MaxWait: 5990516ms
Bed compensation in use: mesh, comp offset 0.000
=== DDARing ===
Scheduled moves: 32, completed moves: 32, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.7
=== GCodes ===
Segments left: 0
Stack records: 3 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 804.98ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex
=== Filament sensors ===
Extruder 0: no data received

BlueDust

Submitting M98 P"config.g" to the console didn't fix it, but M999 did resolve the issue.

M98 P"config.g"
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is disabled
Driver 0: stall threshold 3, filter off, steps/sec 400, coolstep 0, action: none
Driver 1: stall threshold 3, filter off, steps/sec 400, coolstep 0, action: none
Driver 2: stall threshold 1, filter off, steps/sec 200, coolstep 0, action: none
Driver 3: stall threshold 1, filter off, steps/sec 200, coolstep 0, action: none
Driver 4: stall threshold 1, filter off, steps/sec 200, coolstep 0, action: none
Driver 5: stall threshold 1, filter off, steps/sec 200, coolstep 0, action: none
Driver 6: stall threshold 1, filter off, steps/sec 200, coolstep 0, action: none
Driver 7: stall threshold 1, filter off, steps/sec 200, coolstep 0, action: none
Driver 8: stall threshold 1, filter off, steps/sec 200, coolstep 0, action: none
Driver 9: stall threshold 1, filter off, steps/sec 200, coolstep 0, action: noneDuet3D magnetic filament monitor on input 3, disabled, sensitivity 25.01mm/rev, allow 85% to 125%, check every 6.0mm, no data received
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 226C.
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 226C.
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 574C.

Phaedrux

@bluedust said in XY Movement pauses mid movement.:

Hiccups: 770128

That's a lot of hiccups.

Are you using x256 microstepping on all axis?

BlueDust

@phaedrux

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Fri Aug 31 2018 18:58:38 GMT-0400 (Eastern Daylight Time)

; General preferences
M929 S1				; Logging Enabled
G90                              ; Send absolute coordinates...
M83                              ; ...but relative extruder moves
;M555 P1                          ; Set firmware compatibility to look like RepRapFirmare
M555 P2                          ; Set firmware to work like Marlin, with responses after every command and needed for OctoPrint/Palette2 setup

M667 S1                          ; Select CoreXY mode


; Network
M550 P"v-Core"                    ; Set machine name
M552 S1                          ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1                       ; Enable HTTP
M586 P1 S1                       ; Disable FTP ENABLED
M586 P2 S0                       ; Disable Telnet

; Drives
M569 P0 S0                       ; Drive 0 goes forwards
M569 P1 S0                       ; Drive 1 goes forwards
M569 P3 S1                       ; Drive 3 goes forwords
M569 P7 S1
M569 P8 S1
M569 P9 S1


M584 X0 Y1 E3 Z9:7:8 ; three Z motors connected to driver outputs 9, 7 and 8

M671 X6:163:315 Y-7:300:-7 S10



M350 X16 Y16 I1
M350 Z256 I0
M350 E16 I1                              ; Configure microstepping with interpolation


M915


M92 X160 Y160 Z12800 E813.768		;w/o Interpolation Z = pitch of 2mm w Gear 4:1 ratio


M591 D0 P3 C3 R85:125 E6.0 L25.01 S0 	; Magnetic Filament Sensor - currently off
M591 D0                       		; display filament sensor parameters for extruder drive 0


M566 X300 Y300 Z4 E1000		; Have ghosting, and testing lower Jerk.  Also testing lower Z jerk because of issues on Z.
 
M203 X8000 Y8000 Z1000 E1000 	

M201 X800 Y800 Z100 E3000	; Lowered this for testing because.... Have ghosting, and testing lower Jerk.  Also testing lower Z jerk because of issues on Z.


M906 X1200 Y1200 Z1200 E1200 I30
M84 S30                          ; Set idle timeout

M572 D0 S0.06			 ; Pressure Advance this was M572 D0 S0.08 but testing with 4

; Axis Limits
M208 X0 Y0 Z0 S1                 ; Set axis minima
M208 X305 Y296 Z245 S0           ; Set axis maxima


; Endstops
M574 X1 Y1 S3			; for stall guard


; Z-Probe
M574 Z1 S2                       ; Set endstops controlled by probe - Works for IR and BLTouch Probes

M558 P9 F100 H5 R0.2 T6000 A5 B0 

G31 P25 X-34.5 Y-14.5 Z4.0 			

M557 X15:300 Y0:230 P10	

; Heaters
M307 H0 B0 S1.00                 ; Disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 C0 R4700   ; Set thermistor + ADC parameters for heater 0
M143 H0 S140                     ; Set temperature limit for heater 0 to 120C BED
M305 P1 B4725 C7.060000e-8
M143 H1 S280                     ; Set temperature limit for heater 1 to 280C HOTEND

; BLTouch - Heaters
M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.
;M307 H6 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.

; Fans
M106 P0 S0.3 I0 F500 H-1         ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45        ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
;M106 P1 T40 H1
M106 P2 H100:101:102 T39:40 L0.0 ; Motherboard FAN Turns on at 38C, MAX @ 40C, L0.0 = always run @ low 0% fan

; Tools
M563 P0 D0 H1                    ; Define tool 0
G10 P0 X0 Y0 Z0                  ; Set tool 0 axis offsets
G10 P0 R0 S0                     ; Set initial tool 0 active and standby temperatures to 0C

; Automatic power saving
M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

M501 ; Enables auto save of config to config-override.g

BlueDust

@phaedrux

Nope. I enabled on Z a few months ago to try and fix a quality problem I have been having and haven't put it back because I didn't notice any changes (and just forgot about it).
But that is a good catch. I completely forgot about that being something to look at.

M350 X16 Y16 I1
M350 Z256 I0
M350 E16 I1

Phaedrux

@bluedust said in XY Movement pauses mid movement.:

Z12800

Yeah that's a lot of steps. Do you also have mesh compensation active to make it move up and down quickly during XY movement?

@bluedust said in XY Movement pauses mid movement.:

M929 S1 ; Logging Enabled

Also do you normally run with logging enabled? Might wanna turn that off to test.

Phaedrux

@bluedust said in XY Movement pauses mid movement.:

M566 X300 Y300 Z4

Lower Z jerk could be part of the problem, as mentioned earlier.

M566 Z60
M201 Z200

Should be pretty safe.

BlueDust

@phaedrux
Yes I log. I don't do it as often as I used to, but generally use it to compare print times when testing changes to prints when testing/calibrating.

BlueDust

@phaedrux
I changed the settings. Will follow up next time I see the problem.

Thanks!

BlueDust

I have only been running small prints... mostly less than an hour or two and so far haven't noticed any problems, or seen anything more then 1 hiccup after a print. When I mentioned this as an issue I was completing longer prints. Saying that, I am still currently under the impression that the excessive hiccups were the problem. (or just very hopeful)

Thanks!

BlueDust

@Phaedrux
Made the suggested changes and I haven't seen any more problems with random pausing.

That includes changing the extruder back to x16 microstepping.

Thanks!