Thanky @chrishamm!
It works great now!!!
Best posts made by TypQxQ
-
RE: 3.2b3: XY stalls when bed compensation activated
-
3.3b1CAN timeout resets itself?
I'm running 3.3b1 on 6HC+SBC+3HC. Testing 2 motors on X and 2 on Y, each on a board:
M584 X0.1:1.1 Y0.0:1.0 Z0.4:0.3:0.5 E1.2 U0.2
Wile printing I got a skipped step on XY that I belive is from CAN communication.
Paused the print and took out the diagnostics.
Then Homed X, Y and canceled the print.
When issuing M122 again, the ticker of CAN messages was reset.CAN messages queued 93948, send timeouts 11, received 149541, lost 0, free buffers 36, min 36, error reg 110000 CAN messages queued 12504, send timeouts 0, received 9388, lost 0, free buffers 36, min 36, error reg 0 Messages queued 149589, send timeouts 749, received 94000, lost 0, longest wait 20ms for reply type 6024, peak Tx sync delay 493, free buffers 49 (min 37) Messages queued 9270, send timeouts 0, received 12324, lost 0, longest wait 1ms for reply type 6037, peak Tx sync delay 493, free buffers 49 (min 48)
Do I have even higher timeouts throughout a print that do not show up?
What can I do to make communications more stable to be able to use all steppers?Printing paused at X264.7 Y302.5 Z3.2 U102.1 2021-02-21 14:40:52 Diagnostics for board 1: Duet EXP3HC firmware version 3.3beta1 (2021-02-14 16:32:08) Bootloader ID: SAME5x bootloader version 2.2 (2021-01-16b1) Never used RAM 154840, free system stack 0 words Tasks: Move(notifyWait,80) HEAT(delaying,69) CanAsync(notifyWait,72) CanRecv(notifyWait,82) CanClock(notifyWait,74) TMC(notifyWait,30) MAIN(running,219) AIN(delaying,260) Last reset 02:09:54 ago, cause: software Last software reset at 2020-11-10 18:16, reason: StackOverflow, available RAM 154112, slot 0 Software reset code 0x0100 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080e BFAR 0xe000ed38 SP 0x2002ffb4 Task � Freestk 4294967295 ok Stack: 2000137c 200013b0 0002525d 00000000 0003e418 20001598 20003b28 00000000 00024885 200014b4 20003ab0 00000000 00f00000 e000ef34 c0000000 20003b30 000249c5 0002472c 61000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff Driver 0: position 45987, 160.0 steps/mm, ok, reads 18656, writes 69 timeouts 0, SG min/max 0/1023, steps req 23168985 done 22785568 Driver 1: position -476781, 160.0 steps/mm, ok, reads 18659, writes 69 timeouts 0, SG min/max 0/1023, steps req 26754621 done 26371205 Driver 2: position 2877052, 830.0 steps/mm, standstill, reads 18687, writes 45 timeouts 0, SG min/max 0/1023, steps req 3456130 done 3456130 Moves scheduled 78967, completed 78966, in progress 1, hiccups 0, step errors 0, maxPrep 176, maxOverdue 2, maxInc 1, mcErrs 0, gcmErrs 0 Peak sync jitter 11, peak Rx sync delay 196, resyncs 0, next step interrupt due in 636 ticks, enabled VIN: 24.1V, V12: 12.1V MCU temperature: min 39.8C, current 40.0C, max 40.2C Ticks since heat task active 221, ADC conversions started 7794962, completed 7794962, timed out 0 Last sensors broadcast 0x00000002 found 1 226 ticks ago, loop time 0 CAN messages queued 93948, send timeouts 11, received 149541, lost 0, free buffers 36, min 36, error reg 110000 dup 0, oos 3, bm 13, wbm 15976800 2021-02-21 14:40:56 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3beta1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6JKDD-3SJ6L-TB62G Used output buffers: 5 of 40 (17 max) === RTOS === Static ram: 148196 Dynamic ram: 62972 of which 128 recycled Never used RAM 139376, free system stack 118 words Tasks: Linux(ready,113) HEAT(delaying,283) CanReceiv(notifyWait,774) CanSender(notifyWait,357) CanClock(delaying,349) TMC(notifyWait,18) MAIN(running,664) IDLE(ready,20) Owned mutexes: HTTP(MAIN) === Platform === Last reset 02:09:45 ago, cause: software Last software reset at 2021-02-21 12:31, reason: User, GCodes spinning, available RAM 139476, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 42.2, current 45.6, max 45.7 Supply voltage: min 27.9, current 31.9, max 32.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0 Driver 0: position 49080, standstill, reads 61701, writes 69 timeouts 0, SG min/max 0/1023 Driver 1: position -47940, standstill, reads 61701, writes 69 timeouts 0, SG min/max 0/1023 Driver 2: position 25620, standstill, reads 61601, writes 169 timeouts 0, SG min/max 0/163 Driver 3: position 294, standstill, reads 61697, writes 73 timeouts 0, SG min/max 0/1023 Driver 4: position 0, standstill, reads 61697, writes 73 timeouts 0, SG min/max 0/1023 Driver 5: position 0, standstill, reads 61697, writes 73 timeouts 0, SG min/max 0/1023 Date/time: 2021-02-21 14:40:56 Slowest loop: 1840.97ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 2543486ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 78676, completed moves 78676, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 46], 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 0 is on, I-accum = 0.1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122 B0" 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. === CAN === Messages queued 149589, send timeouts 749, received 94000, lost 0, longest wait 20ms for reply type 6024, peak Tx sync delay 493, free buffers 49 (min 37) === SBC interface === State: 4, failed transfers: 0 Last transfer: 3ms ago RX/TX seq numbers: 42758/42758 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x2d3e0 Buffer RX/TX: 0/0-0 2021-02-21 14:42:59 Done printing file 2021-02-21 14:42:59 Done printing file 2021-02-21 14:42:59 Cancelled printing file 0:/gcodes/RearLeft v6.1.gcode, print time was 0h 30m 2021-02-21 14:43:05 G10 P0 S0 R0 2021-02-21 14:43:05 Error: G10: Attempt to set/report offsets and temperatures for non-existent tool: 1 2021-02-21 14:58:02 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3beta1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6JKDD-3SJ6L-TB62G Used output buffers: 3 of 40 (22 max) === RTOS === Static ram: 148196 Dynamic ram: 62972 of which 128 recycled Never used RAM 139376, free system stack 118 words Tasks: Linux(ready,113) HEAT(delaying,283) CanReceiv(notifyWait,774) CanSender(notifyWait,357) CanClock(delaying,349) TMC(notifyWait,18) MAIN(running,664) IDLE(ready,20) Owned mutexes: HTTP(MAIN) === Platform === Last reset 02:26:51 ago, cause: software Last software reset at 2021-02-21 12:31, reason: User, GCodes spinning, available RAM 139476, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 44.3, current 44.5, max 45.9 Supply voltage: min 31.8, current 31.9, max 32.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0 Driver 0: position 80800, standstill, reads 35023, writes 2 timeouts 0, SG min/max 0/154 Driver 1: position 79200, standstill, reads 35023, writes 2 timeouts 0, SG min/max 0/227 Driver 2: position 42946, standstill, reads 35023, writes 2 timeouts 0, SG min/max 0/158 Driver 3: position 0, standstill, reads 35025, writes 2 timeouts 0, SG min/max 0/132 Driver 4: position 0, standstill, reads 35025, writes 2 timeouts 0, SG min/max 0/182 Driver 5: position 0, standstill, reads 35025, writes 2 timeouts 0, SG min/max 0/97 Date/time: 2021-02-21 14:58:02 Slowest loop: 121.18ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 303ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 78701, completed moves 78701, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 0 is on, I-accum = 0.1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122 B0" 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. === CAN === Messages queued 9270, send timeouts 0, received 12324, lost 0, longest wait 1ms for reply type 6037, peak Tx sync delay 493, free buffers 49 (min 48) === SBC interface === State: 4, failed transfers: 0 Last transfer: 3ms ago RX/TX seq numbers: 14016/14016 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x2d3e0 Buffer RX/TX: 0/0-0 2021-02-21 14:58:09 Diagnostics for board 1: Duet EXP3HC firmware version 3.3beta1 (2021-02-14 16:32:08) Bootloader ID: SAME5x bootloader version 2.2 (2021-01-16b1) Never used RAM 154840, free system stack 0 words Tasks: Move(notifyWait,80) HEAT(delaying,69) CanAsync(notifyWait,72) CanRecv(notifyWait,82) CanClock(notifyWait,74) TMC(notifyWait,30) MAIN(running,219) AIN(delaying,260) Last reset 02:27:12 ago, cause: software Last software reset at 2020-11-10 18:16, reason: StackOverflow, available RAM 154112, slot 0 Software reset code 0x0100 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080e BFAR 0xe000ed38 SP 0x2002ffb4 Task � Freestk 4294967295 ok Stack: 2000137c 200013b0 0002525d 00000000 0003e418 20001598 20003b28 00000000 00024885 200014b4 20003ab0 00000000 00f00000 e000ef34 c0000000 20003b30 000249c5 0002472c 61000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff Driver 0: position 229507, 160.0 steps/mm, standstill, reads 57431, writes 2 timeouts 0, SG min/max 0/171, steps req 219914 done 165700 Driver 1: position -499341, 160.0 steps/mm, standstill, reads 57431, writes 2 timeouts 0, SG min/max 0/259, steps req 219914 done 165699 Driver 2: position 2876222, 830.0 steps/mm, standstill, reads 57430, writes 2 timeouts 0, SG min/max 29/169, steps req 830 done 830 Moves scheduled 78988, completed 78988, in progress 0, hiccups 0, step errors 0, maxPrep 103, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 9, peak Rx sync delay 183, resyncs 0, no step interrupt scheduled VIN: 24.1V, V12: 12.1V MCU temperature: min 39.8C, current 40.0C, max 40.2C Ticks since heat task active 106, ADC conversions started 8832848, completed 8832848, timed out 0 Last sensors broadcast 0x00000002 found 1 111 ticks ago, loop time 0 CAN messages queued 12504, send timeouts 0, received 9388, lost 0, free buffers 36, min 36, error reg 0 dup 0, oos 0, bm 3, wbm 8341058
-
3.3b1: Can’t pause or cancel file in progress
I run 3.3b1 on 6HC+3HC+SBC with DWC3.2.2. While printing, i loose the ability to pause or cancel the current job.
2021-02-27 17:14:56 M1 Error: M1: Pause the print before attempting to cancel it 2021-02-27 17:14:52 M0 Error: M0: Pause the print before attempting to cancel it 2021-02-27 17:14:48 M25 Error: M25: Cannot pause print, because no file is being printed! 2021-02-27 16:57:08 M122 B1 Diagnostics for board 1: Duet EXP3HC firmware version 3.3beta1 (2021-02-14 16:32:08) Bootloader ID: SAME5x bootloader version 2.2 (2021-01-16b1) Never used RAM 154784, free system stack 0 words Tasks: Move(notifyWait,80) HEAT(delaying,69) CanAsync(notifyWait,72) CanRecv(notifyWait,82) CanClock(notifyWait,74) TMC(notifyWait,30) MAIN(running,207) AIN(delaying,260) Last reset 08:56:06 ago, cause: power up Last software reset at 2020-11-10 18:16, reason: StackOverflow, available RAM 154112, slot 0 Software reset code 0x0100 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080e BFAR 0xe000ed38 SP 0x2002ffb4 Task � Freestk 4294967295 ok Stack: 2000137c 200013b0 0002525d 00000000 0003e418 20001598 20003b28 00000000 00024885 200014b4 20003ab0 00000000 00f00000 e000ef34 c0000000 20003b30 000249c5 0002472c 61000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff Driver 0: position 78019, 160.0 steps/mm, ok, reads 60727, writes 0 timeouts 0, SG min/max 0/1023, steps req 51010289 done 51010128 Driver 1: position -441066, 160.0 steps/mm, ok, reads 60726, writes 0 timeouts 0, SG min/max 0/1023, steps req 53426002 done 53425629 Driver 2: position 35383024, 830.0 steps/mm, ok, reads 60727, writes 0 timeouts 0, SG min/max 0/1023, steps req 9814045 done 9814008 Moves scheduled 1552785, completed 1552782, in progress 1, hiccups 0, step errors 0, maxPrep 151, maxOverdue 3, maxInc 1, mcErrs 0, gcmErrs 0 Peak sync jitter 11, peak Rx sync delay 191, resyncs 0, next step interrupt due in 20 ticks, enabled VIN: 24.1V, V12: 12.1V MCU temperature: min 39.8C, current 40.0C, max 40.2C Ticks since heat task active 14, ADC conversions started 32166756, completed 32166754, timed out 0 Last sensors broadcast 0x00000002 found 1 19 ticks ago, loop time 0 CAN messages queued 82129, send timeouts 0, received 428755, lost 0, free buffers 36, min 36, error reg 0 dup 0, oos 9, bm 0, wbm 0 2021-02-27 16:57:03 M122 B0 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3beta1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6JKDD-3SJ6L-TB62G Used output buffers: 1 of 40 (18 max) === RTOS === Static ram: 148196 Dynamic ram: 62796 of which 304 recycled Never used RAM 139376, free system stack 118 words Tasks: Linux(ready,105) HEAT(delaying,283) CanReceiv(notifyWait,774) CanSender(notifyWait,357) CanClock(delaying,342) TMC(notifyWait,18) MAIN(running,667) IDLE(ready,20) Owned mutexes: HTTP(MAIN) === Platform === Last reset 08:55:08 ago, cause: software Last software reset at 2021-02-27 08:01, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 140492, slot 2 Software reset code 0x0163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x0444a804 BFAR 0x00000008 SP 0x204327b0 Task Linu Freestk 316 ok Stack: 2042efd0 00000063 00000003 00000000 0048ff96 00406dab 00406eb8 61030000 00406d7f 004865b4 20000000 403e0000 204327e8 20432a14 00000106 41f00001 20426e68 00486954 00000001 00000000 20432a14 20432950 00486960 00000000 20432950 00406eeb 2042da88 Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 45.1, current 45.6, max 46.3 Supply voltage: min 31.8, current 31.9, max 32.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0 Driver 0: position 71013, ok, reads 65003, writes 0 timeouts 0, SG min/max 0/1023 Driver 1: position -608, ok, reads 65003, writes 0 timeouts 0, SG min/max 0/1023 Driver 2: position 111952, standstill, reads 65004, writes 0 timeouts 0, SG min/max not available Driver 3: position 298, ok, reads 65002, writes 0 timeouts 0, SG min/max 0/1023 Driver 4: position 0, ok, reads 65002, writes 0 timeouts 0, SG min/max 0/1023 Driver 5: position 0, ok, reads 65002, writes 0 timeouts 0, SG min/max 0/1023 Date/time: 2021-02-27 16:57:02 Slowest loop: 47.36ms; fastest: 0.06ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 1425778, completed moves 1425718, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 0 is on, I-accum = 0.1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 1 Movement lock held by null HTTP* is doing "M122 B0" in state(s) 0 Telnet is idle in state(s) 0 File* is doing "G1 X197.882004 Y238.949997 E0.019730" 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. === CAN === Messages queued 430408, send timeouts 3051, received 82507, lost 0, longest wait 22ms for reply type 6024, peak Tx sync delay 557, free buffers 49 (min 33) === SBC interface === State: 4, failed transfers: 2 Last transfer: 1ms ago RX/TX seq numbers: 51371/38827 SPI underruns 1, overruns 1 Number of disconnects: 1, IAP RAM available 0x2d410 Buffer RX/TX: 2688/128-4080 === Duet Control Server === Duet Control Server v3.2.2 File: Buffered code: G1 X197.814 Y238.249 E0.01973 Buffered code: G1 X197.780 Y237.545 E0.01973 Buffered code: G1 X197.780 Y236.841 E0.01973 Buffered code: G1 X197.814 Y236.137 E0.01973 Buffered code: G1 X197.882 Y235.436 E0.01973 Buffered code: G1 X197.984 Y234.739 E0.01973 Buffered code: G1 X198.119 Y234.048 E0.01972 Buffered code: G1 X198.288 Y233.364 E0.01973 Buffered code: G1 X198.489 Y232.689 E0.01973 Buffered code: G1 X198.723 Y232.025 E0.01973 Buffered code: G1 X198.989 Y231.373 E0.01973 Buffered code: G1 X199.285 Y230.734 E0.01973 Buffered code: G1 X199.613 Y230.110 E0.01973 Buffered code: G1 X199.970 Y229.503 E0.01973 Buffered code: G1 X200.356 Y228.914 E0.01973 Buffered code: G1 X200.770 Y228.344 E0.01973 Buffered code: G1 X201.211 Y227.795 E0.01973 Buffered code: G1 X201.678 Y227.268 E0.01973 Buffered code: G1 X202.170 Y226.764 E0.01973 Buffered code: G1 X202.686 Y226.284 E0.01973 Buffered code: G1 X203.224 Y225.830 E0.01972 Buffered code: G1 X203.784 Y225.402 E0.01973 Buffered code: G1 X204.363 Y225.002 E0.01973 Buffered code: G1 X204.962 Y224.631 E0.01973 Buffered code: G1 X205.577 Y224.288 E0.01973 Buffered code: G1 X206.208 Y223.976 E0.01973 Buffered code: G1 X206.854 Y223.695 E0.01972 Buffered code: G1 X207.513 Y223.445 E0.01973 Buffered code: G1 X208.183 Y223.227 E0.01973 Buffered code: G1 X208.862 Y223.042 E0.01972 Buffered code: G1 X209.550 Y222.890 E0.01973 ==> 1460 bytes Code buffer space: 2560 Configured SPI speed: 8000000 Hz Full transfers per second: 57.94 Maximum length of RX/TX data transfers: 4932/1688 File /opt/dsf/sd/gcodes/RearLeft v6.2.gcode is selected, processing
-
M915 E returns same as empty
I'm running on duet wifi 1.03 and 2.02RC2(RTOS) (2018-09-07b2).
Typing 'M915 E' returns truncated response, same as 'M915'. Is that normal? -
RE: Markforged Kinematics Troubleshooting
@Red-Sand-Robot
Beautiful build! A lot like how I want to do it.
I was thinking of calibrating the steps per unit of the X axis in regards to Y to get it completely square.
Because when moving Y axis you need X axis to be stationary but X stepper has to move with it, needing belts and such to be perfectly equal.
I use this calibration cross to check on my CoreXY:
https://www.thingiverse.com/thing:2484766 -
RE: Limited service from me during 3D Meetup Sweden
@deckingman I really do love the idea and the results! (That's my printer)
-
RE: 3.2b3: XY stalls when bed compensation activated
@chrishamm Upgraded to ” RepRapFirmware for Duet 3 MB6HC version 3.2-beta3+3-ch running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)” and looks like it fixed both the missed stepps and the stuttering.
Ran the macro above and runs well even at 500mm/s.
Doing a multitool testprint now.
-
RE: stop.g using conditional G code
@dc42 said in stop.g using conditional G code:
if state.currentTool >= 0 if #tools[state.currentTool].heaters > 0 & heat.heaters[tools[state.currentTool].heaters[0]].current > heat.coldRetractTemperature G1 E-2 F300
Just for information if anyone else pulls his/hers hair out wondering why it doesn't work.
This will not work if the tool has 0 heaters because the whole second statemet is evaluated and an error is thrown.
This works instead:if state.currentTool >= 0 if #tools[state.currentTool].heaters > 0 if heat.heaters[tools[state.currentTool].heaters[0]].current > heat.coldRetractTemperature G1 E-2 F300
Tested with RRF 3.4b6 on Duet3 6HC whithout SBC.
-
RE: Eventlog not recording
@chrishamm Thank you!
Please also note that the log level of S1 and S2 are reversed to what is stated in Gcode documentation.
Latest posts made by TypQxQ
-
Failed to get file list - Service Unavailable
Hi!
Upgraded my Duet 2 WiFi from a older 3.4 beta to latest and greatest today.
After uploading a file, be it in DWC or trough PrusaSlicer, it doesn't show up in the job list and when refreshing I get the error:
Not sure if it's DWC or where this comes from. After waiting a while, refreshing works again.
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.2 (2024-06-11 17:13:43) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-956GU-DJMSN-6J1FJ-3SN6T-KTNHD Used output buffers: 16 of 26 (26 max) === RTOS === Static ram: 23384 Dynamic ram: 74276 of which 0 recycled Never used RAM 12364, free system stack 120 words Tasks: NETWORK(2,nWait 6,14.3%,195) HEAT(3,nWait 5,0.1%,319) Move(4,nWait 5,0.3%,298) DUEX(5,nWait 5,0.0%,23) MAIN(1,running,85.2%,717) IDLE(0,ready,0.1%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 02:11:20 ago, cause: software Last software reset at 2024-08-26 16:49, reason: User, Gcodes spinning, available RAM 11684, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x14 MCU temperature: min 38.3, current 39.1, max 42.4 Supply voltage: min 23.9, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/96/96, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 153 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min n/a Driver 4: standstill, SG min 0 Driver 5: standstill, SG min 0 Driver 6: standstill, SG min 185 Driver 7: standstill, SG min n/a Driver 8: standstill, SG min 0 Driver 9: standstill, SG min 0 Driver 10: Driver 11: Date/time: 2024-08-26 19:00:51 Cache data hit count 4294967295 Slowest loop: 267.71ms; fastest: 0.17ms 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 12.2ms, write time 228.7ms, max retries 0 === Move === DMs created 83, segments created 11, maxWait 842538ms, bed compensation in use: mesh, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 9696, completed 9696, 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.2 Heater 1 is on, I-accum = 0.3 === GCodes === Movement locks 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 Q0 segments left 0 Code queue 0 is empty === Filament sensors === check 2921242 clear 26867682 Extruder 0 sensor: no filament === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 247.23ms; fastest: 0.07ms Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1.0 MAC address 5c:cf:7f:76:66:58 Module reset reason: Turned on by main processor, Vcc 3.40, flash size 4194304, free heap 39528 WiFi IP address 192.168.1.205 Signal strength -55dBm, channel 8, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0
Regards, Andrei
-
Old Duet 2 WiFi 3v regulator problem
Hi!
I have a genuine but old Duet 2 Wi-Fi v1.03 that is not booting anymore.
I haven't used this printer in a while but decided to start using it again today.
When homing Z with the Precision Piezo Orion probe, the printer died. Before starting the print I tested the Z-probe, by taping on it and tested the heaters and steppers.It restarted and I checked the logs but could not see anything more than that it had booted today and no errors, last boot before today was 9 months ago according to the log.
I tried to print again, and it died once more but doesn't boot up anymore.
The 3v led is not powering on. So, after some searching here, I disconnected all connectors, the DueX board and the SD card and tried powering by USB.
The u2 3v regulator gets hot but nothing else, not the SD, Wi-Fi or processor.
My electronics knowledge is close to none so my question is if it would be enough to change the regulator (have to find and pay someone) or if I should just "recycle" the board.
-
RE: What is the sensors.probes[0].offsets[2]?
@dc42 Thank you! That did it!
-
What is the sensors.probes[0].offsets[2]?
In the object model there is a sensors.probes[n].offsets[2] that is set to -0.7 for both my P8 probes.
This is not the trigger height, that is 0.
I do setup my probe with G31 Z0.
Where does this offset come from and what is it? -
Delay standby temperature at toolchange?
Hello!
I run a toolchanger with only different colors of PLA right now.
For a small object the tool can be in action for just a couple of seconds for maybe a couple of layers and then change back to the other one and in between maybe not used for a 10 minutes.Is there a way to delay putting the tool in Standby temperature for like 15 seconds from it being deactivated?
Using e3d Revo betas and heat up times are fast but so are the cooldown times.
I was thinking of using global variables and daemon.g but it might be overcomplicating things.
-
RE: Please Help me interpret accelerometer
@t3p3tony Thank you! This looks much better!
-
RE: Please Help me interpret accelerometer
@t3p3tony Forgot about it, have it in a macro:
M955 P0 C"0.spi.cs2+0.spi.cs3" I41
-
Please Help me interpret accelerometer
Hi!
I’m building a printer, CoreXY toolchanger, 500x500x600 build area.
When Irun the accelerometer on the carriage I get very hight response at very low frequency. Around 0.7 and 2Hz regardless of M201 setting, regardless of whether I tighten or loosen my belts.Now using 3.4b6 but same problem since I got the accelerometer when this was first introduced.
My speed settings for XY:
M556 50
M203 33900 (reaching 500mm/s when collecting accelerometer data)
M201 5000
M204 5000Collecting after 4s wait with:
M955 P0 C"0.spi.cs2+0.spi.cs3" I41
M956 P0 S1000 A0 G4 P10 G1 X100 F30000!
I’ve been having this issue since the beginning and I now thaught that I’d ask for help.
This are some imaages of the printer if it helps:
Also, my config files are at: https://github.com/TypQxQ/DuetBackup/tree/main/qTC-backup
Thank you for looking at this.
-
RE: [my bad] Can't see the new toolchange behaviour
@t3p3tony Thankyou, I missed that when checking the code for it....
-
[my bad] Can't see the new toolchange behaviour
[My fault, see below.]
I read that the b6 has a new toolchange behaviour: Important! After changing tool, RRF no longer moves the new tool head to the coordinates at which the old tool head was at when the Tn command was actioned.But my toolchanges have not changed, the new tool still goes back to where the old one was.
Am I missing something?All my config files and logs are updated at: https://github.com/TypQxQ/DuetBackup