Missing Steps - Cant Print SpreadCycle StealthChop tuning help
-
@carcamerarig, it seems to me that you can reproduce this issue at will. Please can you try the following (still in spreadCycle mode):
-
Install the firmware at https://www.dropbox.com/sh/qlucwfda9257p7u/AABoJogMNT-9P0kefE2W_0bxa?dl=0. After the problem occurs, get a M122 report. This firmware includes an additional diagnostic line.
-
Test whether a gcode file containing a simple repeated loop such as the following provokes the problem:
while true G1 X300 Y400 F24000 G1 X0 Y0
Adjust the G1 movement limits and speed according to the capabilities of your machine.
- Test whether increasing XY microstepping from the default x16 to x64 makes the issue happen more or less often.
Thanks in advance!
-
-
@dc42
so I ran the gcode loop to replicate my travel speed 180mm/swhile true
G1 X150 Y150 F10800
G1 X50 Y50Homed in stealthchop, M122 and M569 P0.0 + M569 P0.1 to verify, sent M569 P0.1 D2. M569 P0.0 D2 to set spreadcycle, M569 P0.0 + M569 P0.1 to verify. Ran the loop but could not get the bangs to replicate.
M569 P0.0 Drive 0 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 0 (inf mm/sec), pwmScaleSum 11, pwmScaleAuto 4, pwmOfsAuto 255, pwmGradAuto 44, pos 636 M569 P0.1 Drive 1 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 0 (inf mm/sec), pwmScaleSum 13, pwmScaleAuto 6, pwmOfsAuto 255, pwmGradAuto 50, pos 644 m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2+2 (2021-04-14 10:44:57) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: Z9NZN-A296U-D65J0-40KM4-LY03Z-ZPQPD Used output buffers: 3 of 40 (19 max) === RTOS === Static ram: 100040 Dynamic ram: 106372 of which 0 recycled Never used RAM 34436, free system stack 134 words Tasks: NETWORK(ready,204) HEAT(delaying,316) CanReceiv(notifyWait,944) CanSender(notifyWait,357) CanClock(delaying,334) TMC(notifyWait,101) MAIN(running,410) IDLE(ready,20) AIN(notifyWait,266) Owned mutexes: === Platform === Last reset 00:09:58 ago, cause: power up Last software reset at 2021-04-13 22:30, reason: User, GCodes spinning, available RAM 34100, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU revision 3, ADC conversions started 711706, completed 711705, timed out 0, errs 0 Step timer max interval 3776 Supply voltage: min 23.8, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/2042/2042, gc cycles 6 Driver 0: position 2000, standstill, SG min/max 0/508, read errors 0, write errors 0, ifcnt 18, reads 31475, writes 18, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, SG min/max 0/496, read errors 0, write errors 0, ifcnt 18, reads 31475, writes 18, timeouts 0, DMA errors 0 Driver 2: position 39164, standstill, SG min/max 0/290, read errors 0, write errors 0, ifcnt 17, reads 31476, writes 17, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 31482, writes 10, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/284, read errors 0, write errors 0, ifcnt 17, reads 31476, writes 17, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-04-14 17:49:29 Cache data hit count 1055446963 Slowest loop: 19.63ms; fastest: 0.07ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 0.9ms, write time 5.2ms, max retries 0 === Move === DMs created 83, maxWait 179045ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 28, completed moves 28, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], CDDA state -1 === 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, chamberHeaters = -1 -1 Heater 0 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 5393, send timeouts 5389, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 16) Last cancelled message type 30 dest 127 === Network === Slowest loop: 25.06ms; 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.25beta0 WiFi MAC address f4:cf:a2:6f:e9:78 WiFi Vcc 3.36, reset reason Power up WiFi flash size 2097152, free heap 25256 WiFi IP address 192.168.1.226 WiFi signal strength -44dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 M569 P0.1 D2 M569 P0.0 D2 M569 P0.0 Drive 0 runs in reverse, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 636 M569 P0.1 Drive 1 runs in reverse, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 644 m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2+2 (2021-04-14 10:44:57) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: Z9NZN-A296U-D65J0-40KM4-LY03Z-ZPQPD Used output buffers: 3 of 40 (26 max) === RTOS === Static ram: 100040 Dynamic ram: 106372 of which 0 recycled Never used RAM 34436, free system stack 134 words Tasks: NETWORK(ready,204) HEAT(delaying,316) CanReceiv(notifyWait,944) CanSender(notifyWait,357) CanClock(delaying,334) TMC(notifyWait,67) MAIN(running,410) IDLE(ready,20) AIN(notifyWait,266) Owned mutexes: === Platform === Last reset 00:13:04 ago, cause: power up Last software reset at 2021-04-13 22:30, reason: User, GCodes spinning, available RAM 34100, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU revision 3, ADC conversions started 933641, completed 933640, timed out 0, errs 0 Step timer max interval 2263 Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/384/384, gc cycles 9 Driver 0: position 10000, ok, SG min/max 0/352, read errors 0, write errors 0, ifcnt 21, reads 9805, writes 3, timeouts 0, DMA errors 0 Driver 1: position 10000, ok, SG min/max 0/344, read errors 0, write errors 0, ifcnt 21, reads 9805, writes 3, timeouts 0, DMA errors 0 Driver 2: position 39164, standstill, SG min/max 158/158, read errors 0, write errors 0, ifcnt 18, reads 9807, writes 1, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 9808, writes 0, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 164/164, read errors 0, write errors 0, ifcnt 18, reads 9807, writes 1, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-04-14 17:52:35 Cache data hit count 1385967058 Slowest loop: 7.46ms; fastest: 0.10ms === Storage === Free file entries: 9 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 0.7ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 170982ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 36, completed moves 32, 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, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.0 === 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 X50 Y50" 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 1676, send timeouts 1676, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17) Last cancelled message type 30 dest 127 === Network === Slowest loop: 201.01ms; fastest: 0.08ms 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 1 WiFi firmware version 1.25beta0 WiFi MAC address f4:cf:a2:6f:e9:78 WiFi Vcc 3.36, reset reason Power up WiFi flash size 2097152, free heap 25256 WiFi IP address 192.168.1.226 WiFi signal strength -42dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0
-
@carcamerarig. thanks. Please try your original print file with this firmware. Post a M122 report after any occurrences of this issue.
-
@dc42 What mode?
-
@carcamerarig thanks for your efforts. If i may add one bit ...in my case it was mesh enable to create major issues (axis shifts) .
Did you run with or without mesh ? -
@carcamerarig said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:
@dc42 What mode?
Please use spreadCycle mode until there are no problems when using this mode.
-
@dc42 I can't actually get it to home now in this fw...
-
Homing does work for me with this compiled version and the timeout issues seems solved though it did not lead to any issues with my printer.
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2+2 (2021-04-13 22:55:13) running on Duet 3 Mini5plus Ethernet (standalone mode) Board ID: ZDWF8-8296U-D65J0-40KMU-J603Z-77MM8 Used output buffers: 1 of 40 (22 max) === RTOS === Static ram: 100040 Dynamic ram: 102832 of which 176 recycled Never used RAM 37800, free system stack 112 words Tasks: NETWORK(ready,208) ETHERNET(notifyWait,566) ACCEL(notifyWait,345) HEAT(delaying,300) CanReceiv(notifyWait,944) CanSender(notifyWait,353) CanClock(delaying,332) TMC(notifyWait,99) MAIN(running,310) IDLE(ready,20) AIN(notifyWait,265) Owned mutexes: === Platform === Last reset 00:52:47 ago, cause: software Last software reset at 2021-04-14 23:24, reason: User, GCodes spinning, available RAM 37976, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00489000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 112,112,112 Aux1 errors 0,0,0 MCU revision 3, ADC conversions started 3769704, completed 3769703, timed out 0, errs 0 Supply voltage: min 22.6, current 22.7, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/12, heap memory allocated/used/recyclable 2048/528/120, gc cycles 41 Driver 0: position 18183, ok, SG min/max 0/488, read errors 0, write errors 1, ifcnt 96, reads 55172, writes 15, timeouts 0, DMA errors 0 Driver 1: position 17525, standstill, SG min/max 0/462, read errors 0, write errors 1, ifcnt 90, reads 55172, writes 15, timeouts 0, DMA errors 0 Driver 2: position 796, ok, SG min/max 0/338, read errors 0, write errors 1, ifcnt 95, reads 55169, writes 17, timeouts 0, DMA errors 0 Driver 3: position 0, ok, SG min/max 0/464, read errors 0, write errors 1, ifcnt 96, reads 55169, writes 17, timeouts 0, DMA errors 0 Driver 4: position 0, ok, SG min/max 0/342, read errors 0, write errors 1, ifcnt 95, reads 55170, writes 17, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-04-15 00:17:46 Cache data hit count 4294967295 Slowest loop: 197.42ms; fastest: 0.07ms === Storage === Free file entries: 9 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 10.6ms, write time 56.4ms, max retries 0 === Move === DMs created 83, maxWait 1500779ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 34138, completed moves 34098, 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, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.4 Heater 1 is on, I-accum = 0.7 === 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 X96.057 Y82.736 E0.13106" 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is not empty: Queued 'M106 S204' for move 34130 1 of 16 codes have been queued. === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 28678, send timeouts 28675, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17) Last cancelled message type 4514 dest 127 === Network === Slowest loop: 145.39ms; fastest: 0.03ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - Ethernet - State: active Error counts: 0 0 0 0 0
-
@argo - No Bang Bang ?
-
Nope, never had issues with bangs or skipped steps.
But also had many timeouts in the M122 report which are gone now. -
@oc_geek said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:
@carcamerarig thanks for your efforts. If i may add one bit ...in my case it was mesh enable to create major issues (axis shifts) .
Did you run with or without mesh ?@oc_geek, do you still have problems with bangs or layer shifts, using more recent firmware such as the one I posted at https://www.dropbox.com/sh/qlucwfda9257p7u/AABoJogMNT-9P0kefE2W_0bxa?dl=0 ?
More generally: is anyone else apart from @carcamerarig still having this issue, using this firmware?
-
@dc42 hi i have not tried that version yet
IF i disable mesh i can print with spreadcycle forcedAre you suggesting to try the fw AND enable mesh to see how it goes (it scares me a bit...tbh as i already had two noozle hits on bed...)
Shall i disable the forcing of SpreadCycle too ?thanks
-
@oc_geek said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:
@dc42 hi i have not tried that version yet
IF i disable mesh i can print with spreadcycle forcedAre you suggesting to try the fw AND enable mesh to see how it goes (it scares me a bit...tbh as i already had two noozle hits on bed...)
Yes. Would you be able to tell if there was a problem if you air-printed a few cm above the bed, to avoid the risk of nozzle hits?
Shall i disable the forcing of SpreadCycle too ?
No, I'd rather resolve any issues running in spreadCycle mode before we look at other modes.
-
@dc42 said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:
More generally: is anyone else apart from @carcamerarig still having this issue, using this firmware?
Initially I could also reproduce the issue at will. I won't be able to confirm for a couple of weeks as I no longer have a working Mini5+ to test with (amazingly my replacement was dead on arrival, this is being handled separately by @T3P3Tony I believe).
This will of course be one of my first tests once I get a working board in my hands again.
-
@dc42 said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:
Would you be able to tell if there was a problem if you air-printed a few cm above the bed, to avoid the risk of nozzle hits?
Loaded the Beta 3.3 beta 2+2 as per your indication
- spreadcycle forced (D2)
- mesh active
it apperas to be working fine
i made two prints: one 1st layer and 4 corners prints, no issues of sortthanks
-
@fulg said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:
This will of course be one of my first tests once I get a working board in my hands again.
We all hope it will be history by then
-
@oc_geek said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:
@dc42 said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:
Would you be able to tell if there was a problem if you air-printed a few cm above the bed, to avoid the risk of nozzle hits?
Loaded the Beta 3.32+2 as per your indication
- spreadcycle forced (D2)
- mesh active
it apperas to be working fine
i made two prints: one 1st layer and 4 corners prints, no issues of sortThanks for the report! It may be that fixing the stepper driver comms timeout errors has fixed this issue.
I have just added a new M569.2 command to RRF so that if this issue still occurs, we can read the actual values of the stepper driver registers.
-
@dc42 Fairly productive day with Ian using the new fw as you know, we couldn't replicate the bangs (large travel bangs causing layer shifts) and Ian explained the mini bangs during infill are the switchovers (these never caused layer shifts, mini bangs was just how described them) Had some fun and games with homing but I think we've got something like with maybe just a bit of fine tuning.
Need to check through the config later / tomorrow and see if I can rattle off a couple of prints, fingers crossed no bangs I did mention yesterday under the 2+2 fw I couldn't get it to bang air printing. Only just back home so ill update later / tomorrow.Ian and Dave thanks for the support both.
-
@carcamerarig Yes, good day! Can you share a copy of your config.g and homeall.g? I forgot to get a copy, and I think it contains a good example of stealthchop tuning.
Ian
-
@droftarts - any chance of elaborating on the mods and changes and focus of how to sort this ?
What did we discover was happening that was corrected ?