Print stuttering around curves, LaErrors
-
M566 X480.00 Y480.00 Z30.00 E10000.00 ; Set maximum instantaneous speed changes (mm/min)166mm/s of jerk on extruder? Try lowering to 600 (10mm/s)
M906 X1400.00 Y1400.00 Z900.00 E1428.00 I30Why 1428 (that's useless) and not 1400 on extruder?
Are you on direct or bowden system? Can you try a print without PA?
Just comment this line:; Pressure Advance ; M572 D0 S0.05 ; Enable pressure advance and set it. Marlin setup used a K of 0.03-0.05. HatchBox Wood K=0.03. -
The LA errors should't be there. Please upgrade to firmware 2.05.1 and try again.
-
@dc42 Thank you very much for your reply. I updated to 2.05.1. Unfortunately the problem persists.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6J1DD-3S46R-1STHB
Used output buffers: 3 of 24 (8 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93224 of which 0 recycled
Exception stack ram used: 432
Never used ram: 11704
Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:13:52 ago, cause: power up
Last software reset at 2020-04-20 16:40, reason: User, spinning module GCodes, available RAM 6444 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: 9.7ms, max retries 0
MCU temperature: min 14.6, current 21.4, max 21.4
Supply voltage: min 23.9, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 16/317
Driver 1: ok, SG min/max 48/382
Driver 2: standstill, SG min/max 0/339
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Date/time: 2020-04-26 14:52:04
Cache data hit count 2367661333
Slowest loop: 24.37ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 157, MinFreeDm: 103, MaxWait: 193254ms
Bed compensation in use: mesh, comp offset 0.000
=== DDARing ===
Scheduled moves: 7078, completed moves: 7070, StepErrors: 0, LaErrors: 9, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.3
=== GCodes ===
Segments left: 1
Stack records: 1 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 doing "G1 F4200 X238.49 Y261.575 E1.08288" 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: 22.61ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.22
WiFi MAC address ec:fa:bc:2d:dd:0f
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 29640
WiFi IP address 192.168.1.44
WiFi signal strength -75dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
There are less LA Errors, but this was also only a few minutes into the print. Also, what specifically are LA Errors?
Also appears to be "MaxWait: 193254ms." Is this okay? What specifically does this mean?
- WiFi -
-
I have the same problem, the printhead stops randomly when extruding, producing blobs and a highly irregular surface.
The face shield perimeter in the middle is printed at 30mm/s, the right one is printed at 80mm/s. It gets much worse.
I then tried to replicate it with a 100mm circle printed with two perimeters at 80mm/s and one could easily see the printhead stopping mid line. How can that be? None of the blobs are a start/stop line.M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F23T0-6J9DJ-3S86S-TWBWD
Used output buffers: 3 of 24 (16 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 94004 of which 0 recycled
Exception stack ram used: 476
Never used ram: 10912
Tasks: NETWORK(ready,524) HEAT(blocked,812) MAIN(running,3744) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 08:05:39 ago, cause: power up
Last software reset at 2020-03-17 21:06, reason: User, spinning module GCodes, available RAM 10944 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 16
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 40.3, current 42.4, max 44.1
Supply voltage: min 24.3, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/458
Driver 1: standstill, SG min/max 0/467
Driver 2: standstill, SG min/max 0/275
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Date/time: 2020-04-26 21:28:53
Cache data hit count 4294967295
Slowest loop: 47.11ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 38319, FreeDm: 169, MinFreeDm: 133, MaxWait: 19487ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 5, completed moves: 5, 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.3
=== GCodes ===
Segments left: 0
Stack records: 1 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: 201.17ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 18580
WiFi firmware version 1.23
WiFi MAC address b4:e6:2d:52:f6:45
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24632
WiFi IP address 192.168.0.93
WiFi signal strength -61dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@brisma Thank you for your response! You bring up some really good points.
Regarding the overzealous extruder jerk, Ive been told that its too high ever since I found that I could mess with it! I was under the assumption that the print moves would be dictated by the speed, acceleration, and jerk of the least responsive axis (at least I thought that was correct in Marlin). Therefore, I wanted to make sure that the extruder was unlikely to be the least responsive axis. Is this incorrect? Or maybe I shouldn't be considering it in that way?
Regarding the M906, I was just making it 85% of the max motor current (which is 1680). I could change it to 1400, though Im not sure that it would change much (though I could be very mistaken!).
My setup is Direct Drive. E3D Titan Aqua to a Supervolcano running 24V. As represented by the very low pressure advance value, PA isnt doing too much, so I could remove it.
Thanks again for your time.
-
@NitroFreak First of all, thank you for printing items to fight COVID!
Looks like you have many "Hiccups." In my experience, this has to do with very high microstepping. In your config.g file, what does it show under "M350"? For instance, mine is "M350 X16 Y16 Z16 E16 I1".
-
Yup definitely a large number of hiccups. @NitroFreak usually a result of using too high microstepping. x16 with interpolation to x256 is recommended.
Regarding the halting movement behaviour I may have noticed something similar myself on curved surfaces lately but I was also testing a new slicer release and wrote it off as something I had changed there. I did not look at a M122 at the time. I'll keep that in mind on my next print.
-
@Phaedrux If the slicer matters, Im running cura 4.6.0 (newest release). Im still getting no hiccups, some LA Errors, and stuttering behavior.
-
I was using this version of Cura which is built on 4.6
https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0&lst=
-
@Phaedrux said in Print stuttering around curves, LaErrors:
Yup definitely a large number of hiccups. @NitroFreak usually a result of using too high microstepping. x16 with interpolation to x256 is recommended.
Regarding the halting movement behaviour I may have noticed something similar myself on curved surfaces lately but I was also testing a new slicer release and wrote it off as something I had changed there. I did not look at a M122 at the time. I'll keep that in mind on my next print.
I have nothing out of the ordinary, apart from an external Y servo that i run with no microstepping.
Also two X axis motors that i do indeed run with x16 and interpolation.M350 Y1 Z64 ;E16:16I0 ; Configure microstepping without interpolation
M350 X16:16 I1 E16:16 I1 ; Configure microstepping with interpolation
M92 X88.89 Y360.00 Z3200.00 E411:430 ; Set steps per mm, mk8 extruder 94.3Any idea what else it could be?
-
@NitroFreak said in Print stuttering around curves, LaErrors:
Z3200.00
Are you using z hop or something? I might try dropping the Z axis back to x16.
The external stepper could be something but I'm not familiar.
-
Are you sure that your M350 commands are all after your M584 commands?
-
As an update, decreasing extruder jerk did not improve or worsen the artifacts. The issue persists.
-
I'm about to try a print. The mesh isn't very high resolution though so the curves are pretty facetted.
-
=== DDARing === Scheduled moves: 11250, completed moves: 11225, StepErrors: 0, LaErrors: 1, Underruns: 34, 0Only a few minutes into the print and there is 1 La error and a few under runs.
-
Changing X, Y, and E instantaneous speed (jerk) settings dramatically (both high and low) did not affect the outcome.
Changing pressure advance mid print (through M572 command on the gcode console during the print) also did not change the fact that it still stopped while traveling around the large radius arcs.
Below is a link to the GCode for the affected print.
https://drive.google.com/file/d/17gsPftKUcRSPVDl176A_GBqD7sG8GH9i/view?usp=sharingPlease let me know if there is a better way to post gcode, as it exceeded the maximum file size for uploading.
-
From the end of the print:
=== DDARing === Scheduled moves: 18, completed moves: 18, StepErrors: 0, LaErrors: 14, Underruns: 698, 0m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later Board ID: 08DDM-9FAM2-LW4SD-6JKF0-3SN6N-T2ZBY Used output buffers: 1 of 24 (16 max) === RTOS === Static ram: 25712 Dynamic ram: 93328 of which 228 recycled Exception stack ram used: 544 Never used ram: 11260 Tasks: NETWORK(ready,628) HEAT(blocked,1176) MAIN(running,3728) IDLE(ready,160) Owned mutexes: === Platform === Last reset 03:48:36 ago, cause: power up Last software reset at 2020-03-30 17:04, reason: User, spinning module GCodes, available RAM 11148 bytes (slot 2) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 27.2, current 29.2, max 30.7 Supply voltage: min 23.7, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max 0/1023 Driver 1: standstill, SG min/max 0/1023 Driver 2: standstill, SG min/max 0/279 Driver 3: standstill, SG min/max 0/1023 Driver 4: standstill, SG min/max not available Date/time: 2020-04-26 19:43:09 Cache data hit count 4294967295 Slowest loop: 67.26ms; fastest: 0.07ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 160, MinFreeDm: 98, MaxWait: 60049ms Bed compensation in use: mesh, comp offset 0.000 === DDARing === Scheduled moves: 18, completed moves: 18, StepErrors: 0, LaErrors: 14, Underruns: 698, 0 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.2 Heater 1 is on, I-accum = 0.4 === 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: 200.47ms; fastest: 0.08ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 2 WiFi firmware version 1.23 WiFi MAC address 5c:cf:7f:ef:4a:74 WiFi Vcc 3.31, reset reason Turned on by main processor WiFi flash size 4194304, free heap 24512 WiFi IP address 10.10.0.95 WiFi signal strength -44dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0I did not have any of the pausing I saw previously on the more detailed mesh.
-
@Phaedrux Hmmm, seems like you still have LA Errors, though you didn't have any pausing. If you are using Cura, may I ask what your Maximum Resolution, Maximum Travel Resolution, and Maximum Deviation settings are? Mine are 0.833 mm, 0.7 mm, and 0.015 mm respectively. Do you think that this may be the cause of my issue? They may be too low.
-
No stutters this time, but the model was very low res by comparison. In the next couple days I'll be printing another bunch of high resolution curved models. I'll check again then.
Max res : 0.05
Max travel res 0.1094
Max deviation 0.05And this last print was with that custom cura build from just the other day. Maybe give that build a try.
-
@Charlie said in Print stuttering around curves, LaErrors:
@Phaedrux Hmmm, seems like you still have LA Errors, though you didn't have any pausing. If you are using Cura, may I ask what your Maximum Resolution, Maximum Travel Resolution, and Maximum Deviation settings are? Mine are 0.833 mm, 0.7 mm, and 0.015 mm respectively. Do you think that this may be the cause of my issue? They may be too low.
I also had this suspicion per this video
https://www.youtube.com/watch?v=Hvw3DrVAeTA
I changed my values to 1.133, 0,75 and 0.075 respectively. No change in the stuttering.
Also, it is weird because the duet being 32 bit should not really have this problem?
