• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

1LC - extruder randomly stopping/reversing - ≤3.5.0-rc1

Scheduled Pinned Locked Moved Solved
Beta Firmware
9
147
8.7k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    Exerqtor @Exerqtor
    last edited by 11 Dec 2023, 16:54

    @Exerqtor said in 1LC stepper intermittently running backwards - 3.5.0-r1+:

    @dc42 Ok let's see, I've installed those last binaries and the "normal" 3.5.0rc1+ release on the 1LC.

    After that I tried one of the jobs that failed earlier, and it completed without reversing the extruder (or crashing).

    I'll try some of the other jobs that has failed too now and see of they also complete.

    Should i still leave the "stuff" we put in daemon.g be there for a while btw?

    (Copying this response to the other thread too, since it's refering to the same binaries)

    Well that didn't last long, the next print started reversing after the second layer completed, it's still going as i type this reply.

    So here is a few reports from when it's currently reversing:

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1++wdb (2023-12-11 09:30:48) running on Duet 3 Mini5plus WiFi (standalone mode)
    Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
    Used output buffers: 12 of 40 (40 max)
    === RTOS ===
    Static ram: 102844
    Dynamic ram: 126732 of which 0 recycled
    Never used RAM 7128, free system stack 128 words
    Tasks: NETWORK(1,ready,143.3%,173) HEAT(3,nWait,0.2%,327) Move(4,nWait,6.2%,242) CanReceiv(6,nWait,0.4%,774) CanSender(5,nWait,0.2%,327) CanClock(7,delaying,0.1%,350) TMC(4,nWait,5.7%,74) MAIN(1,running,583.5%,584) IDLE(0,ready,0.9%,29) AIN(4,delaying,6.4%,264), total 746.8%
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 01:50:12 ago, cause: software
    Last software reset at 2023-12-11 16:03, reason: User, Gcodes spinning, available RAM 13548, slot 1
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00446000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x04
    Aux0 errors 0,0,0
    MCU revision 3, ADC conversions started 6612142, completed 6612142, timed out 0, errs 0
    MCU temperature: min 34.7, current 46.4, max 46.8
    Supply voltage: min 7.5, current 24.1, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
    Heap OK, handles allocated/used 198/23, heap memory allocated/used/recyclable 2048/788/444, gc cycles 18
    Events: 0 queued, 0 completed
    Driver 0: ok, SG min 0, read errors 0, write errors 1, ifcnt 166, reads 20196, writes 50, timeouts 0, DMA errors 0, CC errors 0
    Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 164, reads 20196, writes 50, timeouts 0, DMA errors 0, CC errors 0
    Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 70, reads 20217, writes 28, timeouts 0, DMA errors 0, CC errors 0
    Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 72, reads 20217, writes 28, timeouts 0, DMA errors 0, CC errors 0
    Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 68, reads 20219, writes 27, timeouts 0, DMA errors 0, CC errors 0
    Driver 5: not present
    Driver 6: not present
    Date/time: 2023-12-11 17:54:00
    Cache data hit count 4294967295
    Slowest loop: 306.84ms; fastest: 0.09ms
    === Storage ===
    Free file entries: 16
    SD card 0 detected, interface speed: 22.5MBytes/sec
    SD card longest read time 9.2ms, write time 6.2ms, max retries 0
    === Move ===
    DMs created 83, segments created 44, maxWait 2843003ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, ebfmin 0.00, ebfmax 0.00
    next step interrupt due in 63 ticks, enabled
    Moves shaped first try 2684, on retry 3142, too short 7967, wrong shape 32970, maybepossible 1754
    === DDARing 0 ===
    Scheduled moves 7910, completed 7871, hiccups 0, stepErrors 0, LaErrors 31, Underruns [0, 0, 0], CDDA state 3
    === DDARing 1 ===
    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.4
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Movement locks held by null, null
    HTTP is idle in state(s) 0
    Telnet is idle in state(s) 0
    File is doing "G1 X170.601 Y152.656 E.00239" 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 doing "G4 S10000" in state(s) 0 0, running macro
    Aux2 is idle in state(s) 0
    Autopause is idle in state(s) 0
    File2 is idle in state(s) 0, sync state 1
    Queue2 is idle in state(s) 0
    Q0 segments left 0, axes/extruders owned 0x0000807
    Code queue 0 is empty
    Q1 segments left 0, axes/extruders owned 0x0000000
    Code queue 1 is empty
    === Filament sensors ===
    in 0 notIn 0
    Extruder 0 sensor: no filament
    === CAN ===
    Messages queued 111977, received 136294, lost 0, errs 1, boc 0
    Longest wait 6ms for reply type 6029, peak Tx sync delay 340, free buffers 26 (min 24), ts 33061/33060/0
    Tx timeouts 0,0,0,0,0,0
    === Network ===
    Slowest loop: 210.23ms; fastest: 0.00ms
    Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    HTTP sessions: 3 of 8
    === WiFi ===
    Interface state: active
    Module is connected to access point
    Failed messages: pending 0, notrdy 0, noresp 0
    Firmware version 2.1beta4
    MAC address c4:5b:be:ce:91:93
    Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42948
    WiFi IP address 192.168.10.x
    Signal strength -49dBm, channel 6, mode 802.11n, reconnections 0
    Clock register 00002001
    Socket states: 0 0 0 0 0 0 0 0
    M122 B121
    Diagnostics for board 121:
    Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.1+ (2023-11-21 09:48:16)
    Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
    All averaging filters OK
    Never used RAM 2556, free system stack 89 words
    Tasks: Move(3,nWait,1.4%,71) HEAT(2,nWait,2.5%,91) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.4%,77) CanClock(5,nWait,0.1%,67) ACCEL(3,nWait,0.0%,53) TMC(2,nWait,22.2%,57) MAIN(1,running,38.2%,316) IDLE(0,ready,0.0%,27) AIN(2,delaying,35.0%,114), total 100.0%
    Last reset 01:50:46 ago, cause: software
    Last software reset data not available
    Driver 0: pos 0, 568.8 steps/mm, standstill, SG min 0, read errors 0, write errors 3, ifcnt 140, reads 40832, writes 24, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 4320865
    Moves scheduled 47946, completed 47946, in progress 0, hiccups 77, segs 43, step errors 0, maxPrep 887, maxOverdue 7251, maxInc 2966, mcErrs 0, gcmErrs 0, ebfmin -1.00 max inf
    Peak sync jitter -2/11, peak Rx sync delay 279, resyncs 0/0, no timer interrupt scheduled
    VIN voltage: min 7.7, current 24.1, max 24.5
    MCU temperature: min 38.8C, current 66.5C, max 74.8C
    Last sensors broadcast 0x00000012 found 2 34 ticks ago, 0 ordering errs, loop time 0
    CAN messages queued 137004, send timeouts 0, received 112920, lost 0, errs 1213, boc 0, free buffers 18, min 18, error reg 110000
    dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 369, adv 35625/74652
    Accelerometer: LIS3DH, status: 00
    Inductive sensor: not found
    I2C bus errors 0, naks 6, contentions 0, other errors 0
    === Filament sensors ===
    Interrupt 5726621 to 0us, poll 2 to 1966us
    Driver 0: ok
    undefined 1 Reply Last reply 11 Dec 2023, 17:55 Reply Quote 0
    • undefined
      dc42 administrators @Exerqtor
      last edited by dc42 12 Nov 2023, 17:59 11 Dec 2023, 17:55

      @Exerqtor please use the 3.5.0-rc.1++ tool board/expansion board firmware from https://www.dropbox.com/scl/fo/gaxzegafmnmagaefo9mgc/h?rlkey=hk4wpttdje76oews8zkuh86q3&dl=0.

      Duet WiFi hardware designer and firmware engineer
      Please do not ask me for Duet support via PM or email, use the forum
      http://www.escher3d.com, https://miscsolutions.wordpress.com

      undefined 1 Reply Last reply 11 Dec 2023, 18:22 Reply Quote 0
      • undefined
        Exerqtor @dc42
        last edited by Exerqtor 12 Nov 2023, 19:11 11 Dec 2023, 18:22

        @dc42 said in 1LC stepper intermittently running backwards - 3.5.0-r1+:

        @Exerqtor please use the 3.5.0-rc.1++ tool board/expansion board firmware from https://www.dropbox.com/scl/fo/gaxzegafmnmagaefo9mgc/h?rlkey=hk4wpttdje76oews8zkuh86q3&dl=0.

        Aha, ok just moved over to it. I'll try the same job file again before hitting the bunk and report back✌️


        Just tried the same print with 3.5.0-c.1++ on the 1LC and it's the exact same behaviour:

        M122
        === Diagnostics ===
        RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1++wdb (2023-12-11 09:30:48) running on Duet 3 Mini5plus WiFi (standalone mode)
        Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
        Used output buffers: 4 of 40 (40 max)
        === RTOS ===
        Static ram: 102844
        Dynamic ram: 125540 of which 0 recycled
        Never used RAM 9168, free system stack 138 words
        Tasks: NETWORK(1,ready,16.8%,179) HEAT(3,nWait,0.0%,352) Move(4,nWait,0.5%,244) CanReceiv(6,nWait,0.1%,774) CanSender(5,nWait,0.0%,327) CanClock(7,delaying,0.0%,350) TMC(4,delaying,0.7%,74) MAIN(1,running,80.9%,584) IDLE(0,ready,0.2%,29) AIN(4,delaying,0.8%,264), total 100.0%
        Owned mutexes: WiFi(NETWORK)
        === Platform ===
        Last reset 00:25:33 ago, cause: software
        Last software reset at 2023-12-11 19:17, reason: User, Gcodes spinning, available RAM 7056, slot 2
        Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00446000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
        Error status: 0x04
        Aux0 errors 0,0,0
        MCU revision 3, ADC conversions started 1533781, completed 1533780, timed out 0, errs 0
        MCU temperature: min 37.0, current 46.4, max 46.6
        Supply voltage: min 7.8, current 24.0, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
        Heap OK, handles allocated/used 99/23, heap memory allocated/used/recyclable 2048/1912/1572, gc cycles 7
        Events: 0 queued, 0 completed
        Driver 0: ok, SG min 0, read errors 0, write errors 1, ifcnt 201, reads 15125, writes 32, timeouts 0, DMA errors 0, CC errors 0
        Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 199, reads 15124, writes 32, timeouts 0, DMA errors 0, CC errors 0
        Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 93, reads 15136, writes 20, timeouts 0, DMA errors 0, CC errors 0
        Driver 3: ok, SG min 0, read errors 0, write errors 1, ifcnt 96, reads 15135, writes 21, timeouts 0, DMA errors 0, CC errors 0
        Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 91, reads 15137, writes 20, timeouts 0, DMA errors 0, CC errors 0
        Driver 5: not present
        Driver 6: not present
        Date/time: 2023-12-11 19:43:28
        Cache data hit count 2492399296
        Slowest loop: 226.89ms; fastest: 0.09ms
        === Storage ===
        Free file entries: 16
        SD card 0 detected, interface speed: 22.5MBytes/sec
        SD card longest read time 5.4ms, write time 5.1ms, max retries 0
        === Move ===
        DMs created 83, segments created 42, maxWait 1083591ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, ebfmin 0.00, ebfmax 0.00
        next step interrupt due in 30 ticks, enabled
        Moves shaped first try 265, on retry 158, too short 102, wrong shape 2987, maybepossible 63
        === DDARing 0 ===
        Scheduled moves 4562, completed 4522, hiccups 0, stepErrors 0, LaErrors 5, Underruns [0, 0, 0], CDDA state 3
        === DDARing 1 ===
        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.4
        Heater 1 is on, I-accum = 0.0
        === GCodes ===
        Movement locks held by null, null
        HTTP is idle in state(s) 0
        Telnet is idle in state(s) 0
        File is doing "G1 X187.692 Y162.442 Z1.35" 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 doing "G4 S10000" in state(s) 0 0, running macro
        Aux2 is idle in state(s) 0
        Autopause is idle in state(s) 0
        File2 is idle in state(s) 0, sync state 1
        Queue2 is idle in state(s) 0
        Q0 segments left 0, axes/extruders owned 0x0000807
        Code queue 0 is empty
        Q1 segments left 0, axes/extruders owned 0x0000000
        Code queue 1 is empty
        === Filament sensors ===
        in 0 notIn 0
        Extruder 0 sensor: no filament
        === CAN ===
        Messages queued 17932, received 31633, lost 0, errs 0, boc 0
        Longest wait 3ms for reply type 6013, peak Tx sync delay 327, free buffers 26 (min 25), ts 7669/7668/0
        Tx timeouts 0,0,0,0,0,0
        === Network ===
        Slowest loop: 208.78ms; fastest: 0.00ms
        Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
        HTTP sessions: 2 of 8
        === WiFi ===
        Interface state: active
        Module is connected to access point
        Failed messages: pending 0, notrdy 0, noresp 0
        Firmware version 2.1beta4
        MAC address c4:5b:be:ce:91:93
        Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 43112
        WiFi IP address 192.168.10.x
        Signal strength -48dBm, channel 6, mode 802.11n, reconnections 0
        Clock register 00002001
        Socket states: 0 0 0 0 0 0 0 0
        M122 B121
        Diagnostics for board 121:
        Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.1++ (2023-12-07 12:52:31)
        Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
        All averaging filters OK
        Never used RAM 2628, free system stack 89 words
        Tasks: Move(3,nWait,0.1%,71) HEAT(2,nWait,0.3%,91) CanAsync(5,nWait,0.0%,55) CanRecv(3,nWait,0.0%,77) CanClock(5,nWait,0.0%,67) ACCEL(3,nWait,0.0%,53) TMC(2,nWait,3.0%,57) MAIN(1,running,91.7%,316) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.8%,114), total 100.0%
        Last reset 00:26:29 ago, cause: software
        Last software reset data not available
        Driver 0: pos 0, 568.8 steps/mm, standstill, SG min 0, read errors 0, write errors 1, ifcnt 174, reads 7708, writes 22, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6c, steps req 0 done 401933
        Moves scheduled 2847, completed 2847, in progress 0, hiccups 1, segs 40, step errors 0, maxLate 1 maxPrep 900, maxOverdue 40, maxInc 40, mcErrs 0, gcmErrs 0, ebfmin -1.00 max inf
        Peak sync jitter -2/9, peak Rx sync delay 219, resyncs 0/0, no timer interrupt scheduled
        VIN voltage: min 8.1, current 24.1, max 24.7
        MCU temperature: min 45.6C, current 61.2C, max 61.2C
        Last sensors broadcast 0x00000012 found 2 228 ticks ago, 0 ordering errs, loop time 0
        CAN messages queued 32789, send timeouts 0, received 19593, lost 0, errs 1210, boc 0, free buffers 18, min 18, error reg 100000
        dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 354, adv 35712/74647
        Accelerometer: LIS3DH, status: 00
        Inductive sensor: not found
        I2C bus errors 0, naks 6, contentions 0, other errors 0
        === Filament sensors ===
        Interrupt 5726621 to 0us, poll 2 to 1314us
        Driver 0: ok
        undefined 1 Reply Last reply 13 Dec 2023, 18:39 Reply Quote 0
        • undefined
          dc42 administrators @Exerqtor
          last edited by 13 Dec 2023, 18:39

          @Exerqtor is the reversal random, or at the same point each time in a given print?

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          undefined 3 Replies Last reply 13 Dec 2023, 18:46 Reply Quote 0
          • undefined
            Exerqtor @dc42
            last edited by Exerqtor 13 Dec 2023, 18:46

            @dc42 Seemingly random, definetly not on the same point/layer each time.

            The first time it happened (where i thought it was a clog or something) it happened between layer 59-61 (based on messsuring the height of the failed print), so after making sure there was no clog etc. and restarting the print it began reversing at layer 4-5. And on the third try it started reversing on layer 2.

            1 Reply Last reply Reply Quote 0
            • undefined
              Exerqtor @dc42
              last edited by Exerqtor 14 Dec 2023, 09:54

              @dc42 said in 1LC stepper intermittently running backwards - 3.5.0-r1+:

              @Exerqtor is the reversal random, or at the same point each time in a given print?

              I just saw this thread and your reply to it. And it got me to remember that i did some IS tuning and changes between it working and these issues came back. May these be connected to each other?

              The only changes i did was to alter the frequency and try a couple different shapers to see what changes it did to the readings.

              1 Reply Last reply Reply Quote 0
              • undefined
                Exerqtor @dc42
                last edited by Exerqtor 15 Dec 2023, 17:01

                @dc42 So I just grabbed the 3.5.0rc2 binaries and tried them on the machine, and it's still reversing the the print.

                This time I kept a finger on the filament where it enters the reversed bowden while looking at the Z-height and it stopped extruding somewhere along Z 0.65.

                Here is a couple fresh reports grabbed while it's acting up during a print:

                M122
                === Diagnostics ===
                RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.2 (2023-12-15 13:33:26) running on Duet 3 Mini5plus WiFi (standalone mode)
                Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
                Used output buffers: 3 of 40 (40 max)
                === RTOS ===
                Static ram: 102812
                Dynamic ram: 128208 of which 0 recycled
                Never used RAM 5756, free system stack 120 words
                Tasks: NETWORK(2,nWait,21.9%,181) HEAT(3,nWait,0.0%,328) Move(4,nWait,0.5%,243) CanReceiv(6,nWait,0.1%,776) CanSender(5,nWait,0.0%,329) CanClock(7,delaying,0.0%,350) TMC(4,nWait,0.7%,80) MAIN(1,running,71.5%,603) IDLE(0,ready,4.5%,29) AIN(4,delaying,0.8%,264), total 100.0%
                Owned mutexes:
                === Platform ===
                Last reset 00:36:34 ago, cause: software
                Last software reset at 2023-12-15 17:21, reason: User, Gcodes spinning, available RAM 12348, slot 2
                Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                Error status: 0x04
                Aux0 errors 0,0,0
                MCU revision 3, ADC conversions started 2195019, completed 2195017, timed out 0, errs 0
                MCU temperature: min 35.9, current 46.2, max 46.7
                Supply voltage: min 7.5, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
                Heap OK, handles allocated/used 198/28, heap memory allocated/used/recyclable 2048/1524/1120, gc cycles 4001
                Events: 0 queued, 0 completed
                Driver 0: ok, SG min 0, read errors 0, write errors 1, ifcnt 149, reads 49926, writes 32, timeouts 0, DMA errors 0, CC errors 0
                Driver 1: ok, SG min 0, read errors 0, write errors 1, ifcnt 149, reads 49926, writes 32, timeouts 0, DMA errors 0, CC errors 0
                Driver 2: ok, SG min 0, read errors 0, write errors 1, ifcnt 115, reads 49937, writes 21, timeouts 0, DMA errors 0, CC errors 0
                Driver 3: ok, SG min 0, read errors 0, write errors 1, ifcnt 116, reads 49936, writes 21, timeouts 0, DMA errors 0, CC errors 0
                Driver 4: ok, SG min 0, read errors 0, write errors 1, ifcnt 115, reads 49937, writes 21, timeouts 0, DMA errors 0, CC errors 0
                Driver 5: not present
                Driver 6: not present
                Date/time: 2023-12-15 17:57:46
                Cache data hit count 3773989065
                Slowest loop: 224.53ms; fastest: 0.09ms
                === Storage ===
                Free file entries: 16
                SD card 0 detected, interface speed: 22.5MBytes/sec
                SD card longest read time 11.1ms, write time 4.5ms, max retries 0
                === Move ===
                DMs created 83, segments created 41, maxWait 1602827ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, ebfmin 0.00, ebfmax 0.00
                next step interrupt due in 795 ticks, enabled
                Moves shaped first try 499, on retry 404, too short 194, wrong shape 4852, maybepossible 141
                === DDARing 0 ===
                Scheduled moves 8101, completed 8061, hiccups 0, stepErrors 0, LaErrors 10, Underruns [0, 0, 0], CDDA state 3
                === DDARing 1 ===
                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.4
                Heater 1 is on, I-accum = 0.0
                === GCodes ===
                Movement locks held by null, null
                HTTP is idle in state(s) 0
                Telnet is idle in state(s) 0
                File is doing "G1 X170.827 Y153.319 E.00731" 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 0, running macro
                Aux2 is idle in state(s) 0
                Autopause is idle in state(s) 0
                File2 is idle in state(s) 0, sync state 1
                Queue2 is idle in state(s) 0
                Q0 segments left 0, axes/extruders owned 0x0000807
                Code queue 0 is empty
                Q1 segments left 0, axes/extruders owned 0x0000000
                Code queue 1 is empty
                === Filament sensors ===
                check 0 clear 0
                Extruder 0 sensor: no filament
                === CAN ===
                Messages queued 26867, received 45197, lost 0, errs 1, boc 0
                Longest wait 2ms for reply type 6031, peak Tx sync delay 403, free buffers 26 (min 25), ts 10975/10974/0
                Tx timeouts 0,0,0,0,0,0
                === Network ===
                Slowest loop: 89.37ms; fastest: 0.00ms
                Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
                HTTP sessions: 3 of 8
                === WiFi ===
                Interface state: active
                Module is connected to access point
                Failed messages: pending 0, notrdy 0, noresp 0
                Firmware version 2.1beta6
                MAC address c4:5b:be:ce:91:93
                Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 41512
                WiFi IP address 192.168.10.x
                Signal strength -50dBm, channel 6, mode 802.11n, reconnections 0
                Clock register 00002001
                Socket states: 0 0 0 0 0 0 0 0
                M122 B121
                Diagnostics for board 121:
                Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.2 (2023-12-15 13:41:02)
                Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
                All averaging filters OK
                Never used RAM 2708, free system stack 91 words
                Tasks: Move(3,nWait,0.1%,73) HEAT(2,nWait,0.4%,97) CanAsync(5,nWait,0.0%,55) CanRecv(3,nWait,0.0%,77) CanClock(5,nWait,0.0%,69) ACCEL(3,nWait,0.0%,53) TMC(2,delaying,3.0%,57) MAIN(1,running,91.8%,318) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.7%,114), total 100.0%
                Last reset 00:36:54 ago, cause: software
                Last software reset data not available
                Driver 0: pos 0, 568.8 steps/mm, standstill, SG min 0, read errors 0, write errors 1, ifcnt 97, reads 57835, writes 22, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 440142
                Moves scheduled 3003, completed 3003, in progress 0, hiccups 4, segs 40, step errors 0, maxLate 1 maxPrep 887, maxOverdue 322, maxInc 322, mcErrs 0, gcmErrs 0, ebfmin -1.00 max inf
                Peak sync jitter -2/10, peak Rx sync delay 217, resyncs 0/0, no timer interrupt scheduled
                VIN voltage: min 7.7, current 24.1, max 24.5
                MCU temperature: min 39.1C, current 68.7C, max 68.7C
                Last sensors broadcast 0x00000012 found 2 11 ticks ago, 0 ordering errs, loop time 0
                CAN messages queued 45614, send timeouts 0, received 27424, lost 0, errs 1173, boc 0, free buffers 18, min 18, error reg 110000
                dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 346, adv 35766/74655
                Accelerometer: LIS3DH, status: 00
                Inductive sensor: not found
                I2C bus errors 0, naks 6, contentions 0, other errors 0
                === Filament sensors ===
                Interrupt 5726621 to 0us, poll 4 to 1409us

                And the sliced file for good measure.

                undefined 1 Reply Last reply 16 Dec 2023, 09:40 Reply Quote 0
                • undefined
                  Exerqtor @Exerqtor
                  last edited by 16 Dec 2023, 09:40

                  I just adjusted my belt tention and retuned input shaping after moving to 3.5.0-rc2, to see if applying new shaper settings would remedy anything.

                  Started a print, and now it stops extruding earlier than ever, now it only does a tiny bit of my purge line before it stops.

                  So i thought fuck it and removed the extrusion reset commands from my layer change g-code, sliced the model again and did another try. The exact same behaviour.

                  Here is another set of M122 reports from while the problem is happening:

                  M122
                  === Diagnostics ===
                  RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.2 (2023-12-15 13:33:26) running on Duet 3 Mini5plus WiFi (standalone mode)
                  Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
                  Used output buffers: 13 of 40 (40 max)
                  === RTOS ===
                  Static ram: 102812
                  Dynamic ram: 128544 of which 0 recycled
                  Never used RAM 5420, free system stack 120 words
                  Tasks: NETWORK(1,ready,83.7%,181) HEAT(3,nWait,1.0%,328) Move(4,nWait,0.3%,243) CanReceiv(6,nWait,1.7%,776) CanSender(5,nWait,0.0%,328) CanClock(7,delaying,0.3%,350) TMC(4,delaying,24.0%,74) MAIN(1,running,106.6%,584) IDLE(0,ready,179.1%,29) AIN(4,delaying,27.9%,264), total 424.7%
                  Owned mutexes: WiFi(NETWORK)
                  === Platform ===
                  Last reset 17:00:25 ago, cause: software
                  Last software reset at 2023-12-15 17:21, reason: User, Gcodes spinning, available RAM 12348, slot 2
                  Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                  Error status: 0x04
                  Aux0 errors 0,0,0
                  MCU revision 3, ADC conversions started 61224767, completed 61224767, timed out 0, errs 0
                  MCU temperature: min 34.8, current 46.4, max 46.4
                  Supply voltage: min 23.4, current 23.9, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
                  Heap OK, handles allocated/used 198/28, heap memory allocated/used/recyclable 2048/612/192, gc cycles 119204
                  Events: 0 queued, 0 completed
                  Driver 0: ok, SG min 0, read errors 0, write errors 0, ifcnt 247, reads 26512, writes 98, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x71
                  Driver 1: ok, SG min 0, read errors 0, write errors 0, ifcnt 247, reads 26513, writes 98, timeouts 0, DMA errors 0, CC errors 0
                  Driver 2: ok, SG min 0, read errors 0, write errors 0, ifcnt 152, reads 26571, writes 37, timeouts 2, DMA errors 0, CC errors 0, failedOp 0x41
                  Driver 3: ok, SG min 0, read errors 0, write errors 0, ifcnt 154, reads 26572, writes 38, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6c
                  Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 152, reads 26572, writes 37, timeouts 2, DMA errors 0, CC errors 0, failedOp 0x6f
                  Driver 5: not present
                  Driver 6: not present
                  Date/time: 2023-12-16 10:21:36
                  Cache data hit count 4294967295
                  Slowest loop: 408.12ms; fastest: 0.09ms
                  === Storage ===
                  Free file entries: 16
                  SD card 0 detected, interface speed: 22.5MBytes/sec
                  SD card longest read time 8.7ms, write time 8.1ms, max retries 0
                  === Move ===
                  DMs created 83, segments created 41, maxWait 53449812ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, ebfmin 0.00, ebfmax 0.00
                  next step interrupt due in 55 ticks, enabled
                  Moves shaped first try 196, on retry 110, too short 86, wrong shape 1517, maybepossible 32
                  === DDARing 0 ===
                  Scheduled moves 432, completed 422, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 49], CDDA state 3
                  === DDARing 1 ===
                  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.4
                  Heater 1 is on, I-accum = 0.0
                  === GCodes ===
                  Movement locks held by null, null
                  HTTP is idle in state(s) 0
                  Telnet is idle in state(s) 0
                  File is idle in state(s) 3
                  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 0, running macro
                  Aux2 is idle in state(s) 0
                  Autopause is idle in state(s) 0
                  File2 is idle in state(s) 0
                  Queue2 is idle in state(s) 0
                  Q0 segments left 1, axes/extruders owned 0x0000807
                  Code queue 0 is empty
                  Q1 segments left 0, axes/extruders owned 0x0000000
                  Code queue 1 is empty
                  === Filament sensors ===
                  check 0 clear 0
                  Extruder 0 sensor: no filament
                  === CAN ===
                  Messages queued 533567, received 1211128, lost 0, errs 0, boc 0
                  Longest wait 6ms for reply type 6024, peak Tx sync delay 277, free buffers 26 (min 24), ts 295151/295151/0
                  Tx timeouts 0,0,0,0,0,0
                  === Network ===
                  Slowest loop: 211.17ms; fastest: 0.00ms
                  Responder states: MQTT(0) HTTP(0) 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.1beta6
                  MAC address c4:5b:be:ce:91:93
                  Module reset reason: Power up, Vcc 3.37, flash size 2097152, free heap 41168
                  WiFi IP address 192.168.10.x
                  Signal strength -49dBm, channel 6, mode 802.11n, reconnections 0
                  Clock register 00002001
                  Socket states: 0 0 0 0 0 0 0 0
                  M122 B121
                  Diagnostics for board 121:
                  Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.2 (2023-12-15 13:41:02)
                  Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
                  All averaging filters OK
                  Never used RAM 2708, free system stack 91 words
                  Tasks: Move(3,nWait,0.1%,73) HEAT(2,nWait,11.4%,97) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.4%,77) CanClock(5,nWait,0.6%,69) ACCEL(3,nWait,0.0%,17) TMC(2,delaying,101.1%,57) MAIN(1,running,154.7%,318) IDLE(0,ready,0.0%,27) AIN(2,delaying,159.0%,114), total 427.3%
                  Last reset 17:00:30 ago, cause: software
                  Last software reset data not available
                  Driver 0: pos 0, 568.8 steps/mm, standstill, SG min 0, read errors 0, write errors 0, ifcnt 101, reads 16617, writes 4, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x71, steps req 0 done 91906
                  Moves scheduled 3087, completed 3087, in progress 0, hiccups 3, segs 40, step errors 0, maxLate 0 maxPrep 853, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max inf
                  Peak sync jitter -3/10, peak Rx sync delay 219, resyncs 0/0, no timer interrupt scheduled
                  VIN voltage: min 23.3, current 24.1, max 24.6
                  MCU temperature: min 38.6C, current 63.8C, max 69.2C
                  Last sensors broadcast 0x00000012 found 2 24 ticks ago, 0 ordering errs, loop time 0
                  CAN messages queued 1210805, send timeouts 0, received 533070, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
                  dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 334, adv 35725/74654
                  Accelerometer: LIS3DH, status: 00
                  Inductive sensor: not found
                  I2C bus errors 0, naks 0, contentions 0, other errors 0
                  === Filament sensors ===
                  Interrupt 5726621 to 0us, poll 5 to 1436us
                  Driver 0: ok

                  And here is the relevant config files & sliced job.
                  (All these files are grabbed from the printer, so it's 100% the config I'm currently running)

                  undefined 1 Reply Last reply 16 Dec 2023, 10:02 Reply Quote 0
                  • undefined
                    droftarts administrators @Exerqtor
                    last edited by 16 Dec 2023, 10:02

                    @Exerqtor have we already ascertained if the problem goes away when input shaping and/or pressure advance are disabled? What size nozzle are you using?

                    Ian

                    Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                    undefined 1 Reply Last reply 16 Dec 2023, 10:16 Reply Quote 1
                    • undefined
                      Exerqtor @droftarts
                      last edited by Exerqtor 16 Dec 2023, 10:16

                      @droftarts said in 1LC - stepper randomly reversing - ≤3.5.0-r1+:

                      @Exerqtor have we already ascertained if the problem goes away when input shaping and/or pressure advance are disabled? What size nozzle are you using?

                      Ian

                      No I haven't tried that out yet, been waiting on feedback as to where/what to start with to be honest.

                      I can try disabling Input Shaping first and see if that yield different results on the same job that I supplied in my last post.


                      I can confirm that it still happens with IS disabled:

                      M593
                      Input shaping is disabled
                      M122
                      === Diagnostics ===
                      RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.2 (2023-12-15 13:33:26) running on Duet 3 Mini5plus WiFi (standalone mode)
                      Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
                      Used output buffers: 25 of 40 (40 max)
                      === RTOS ===
                      Static ram: 102812
                      Dynamic ram: 128544 of which 0 recycled
                      Never used RAM 5420, free system stack 120 words
                      Tasks: NETWORK(2,nWait,23.7%,179) HEAT(3,nWait,0.0%,328) Move(4,nWait,2.4%,243) CanReceiv(6,nWait,0.1%,776) CanSender(5,nWait,0.0%,328) CanClock(7,delaying,0.0%,350) TMC(4,nWait,0.8%,74) MAIN(1,running,66.8%,584) IDLE(0,ready,5.3%,29) AIN(4,delaying,0.9%,264), total 100.0%
                      Owned mutexes: WiFi(NETWORK)
                      === Platform ===
                      Last reset 18:04:31 ago, cause: software
                      Last software reset at 2023-12-15 17:21, reason: User, Gcodes spinning, available RAM 12348, slot 2
                      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                      Error status: 0x04
                      Aux0 errors 0,0,0
                      MCU revision 3, ADC conversions started 65070749, completed 65070749, timed out 0, errs 0
                      MCU temperature: min 46.0, current 46.4, max 46.7
                      Supply voltage: min 23.8, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
                      Heap OK, handles allocated/used 198/28, heap memory allocated/used/recyclable 2048/1836/1416, gc cycles 126614
                      Events: 0 queued, 0 completed
                      Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 1329, writes 0, timeouts 0, DMA errors 0, CC errors 0
                      Driver 1: ok, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 1329, writes 0, timeouts 0, DMA errors 0, CC errors 0
                      Driver 2: ok, SG min 0, read errors 0, write errors 0, ifcnt 160, reads 1329, writes 0, timeouts 0, DMA errors 0, CC errors 0
                      Driver 3: ok, SG min 0, read errors 0, write errors 0, ifcnt 162, reads 1329, writes 0, timeouts 0, DMA errors 0, CC errors 0
                      Driver 4: ok, SG min 0, read errors 0, write errors 0, ifcnt 159, reads 1329, writes 0, timeouts 0, DMA errors 0, CC errors 0
                      Driver 5: not present
                      Driver 6: not present
                      Date/time: 2023-12-16 11:25:42
                      Cache data hit count 4294967295
                      Slowest loop: 9.56ms; fastest: 0.11ms
                      === Storage ===
                      Free file entries: 16
                      SD card 0 detected, interface speed: 22.5MBytes/sec
                      SD card longest read time 6.0ms, write time 1.0ms, max retries 0
                      === Move ===
                      DMs created 83, segments created 41, maxWait 842ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, ebfmin 0.00, ebfmax 0.00
                      next step interrupt due in 107 ticks, enabled
                      Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
                      === DDARing 0 ===
                      Scheduled moves 1066, completed 1044, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
                      === DDARing 1 ===
                      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.4
                      Heater 1 is on, I-accum = 0.0
                      === GCodes ===
                      Movement locks held by null, null
                      HTTP is idle in state(s) 0
                      Telnet is idle in state(s) 0
                      File is doing "G1 X226.271 Y197.626 E.02799" 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 doing "G4 P10" in state(s) 0 0, running macro
                      Aux2 is idle in state(s) 0
                      Autopause is idle in state(s) 0
                      File2 is idle in state(s) 0
                      Queue2 is idle in state(s) 0
                      Q0 segments left 1, axes/extruders owned 0x0000807
                      Code queue 0 is empty
                      Q1 segments left 0, axes/extruders owned 0x0000000
                      Code queue 1 is empty
                      === Filament sensors ===
                      check 0 clear 0
                      Extruder 0 sensor: no filament
                      === CAN ===
                      Messages queued 509, received 517, lost 0, errs 0, boc 0
                      Longest wait 0ms for reply type 0, peak Tx sync delay 9, free buffers 26 (min 25), ts 126/126/0
                      Tx timeouts 0,0,0,0,0,0
                      === Network ===
                      Slowest loop: 20.63ms; fastest: 0.06ms
                      Responder states: MQTT(0) HTTP(0) 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.1beta6
                      MAC address c4:5b:be:ce:91:93
                      Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42988
                      WiFi IP address 192.168.10.x
                      Signal strength -50dBm, channel 6, mode 802.11n, reconnections 0
                      Clock register 00002001
                      Socket states: 0 0 0 0 0 0 0 0
                      M122 B121
                      Diagnostics for board 121:
                      Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.2 (2023-12-15 13:41:02)
                      Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
                      All averaging filters OK
                      Never used RAM 2708, free system stack 91 words
                      Tasks: Move(3,nWait,0.0%,73) HEAT(2,nWait,0.3%,97) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.0%,77) CanClock(5,nWait,0.0%,69) ACCEL(3,nWait,0.0%,17) TMC(2,delaying,3.0%,57) MAIN(1,running,91.9%,318) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.7%,114), total 100.0%
                      Last reset 18:04:47 ago, cause: software
                      Last software reset data not available
                      Driver 0: pos 0, 568.8 steps/mm, standstill, SG min 0, read errors 0, write errors 0, ifcnt 103, reads 28066, writes 2, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 38048
                      Moves scheduled 3098, completed 3098, in progress 0, hiccups 1, segs 40, step errors 0, maxLate 0 maxPrep 334, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max inf
                      Peak sync jitter -2/11, peak Rx sync delay 215, resyncs 0/0, no timer interrupt scheduled
                      VIN voltage: min 23.3, current 24.1, max 24.5
                      MCU temperature: min 38.6C, current 57.8C, max 69.2C
                      Last sensors broadcast 0x00000012 found 2 103 ticks ago, 0 ordering errs, loop time 0
                      CAN messages queued 79268, send timeouts 0, received 35985, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
                      dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 323, adv 35708/74652
                      Accelerometer: LIS3DH, status: 00
                      Inductive sensor: not found
                      I2C bus errors 0, naks 0, contentions 0, other errors 0
                      === Filament sensors ===
                      Interrupt 5726621 to 0us, poll 5 to 1432us
                      Driver 0: ok
                      undefined 1 Reply Last reply 16 Dec 2023, 10:36 Reply Quote 0
                      • undefined
                        Exerqtor @Exerqtor
                        last edited by 16 Dec 2023, 10:36

                        @droftarts And the exact same with both Input Shaping and Pressure Advance disabled:

                        M593
                        Input shaping is disabled
                        M572 D0
                        Extruder pressure advance: 0.000
                        M122
                        === Diagnostics ===
                        RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.2 (2023-12-15 13:33:26) running on Duet 3 Mini5plus WiFi (standalone mode)
                        Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
                        Used output buffers: 3 of 40 (40 max)
                        === RTOS ===
                        Static ram: 102812
                        Dynamic ram: 128544 of which 0 recycled
                        Never used RAM 5420, free system stack 120 words
                        Tasks: NETWORK(2,nWait,22.2%,179) HEAT(3,nWait,0.0%,328) Move(4,nWait,0.5%,243) CanReceiv(6,nWait,0.1%,776) CanSender(5,nWait,0.0%,328) CanClock(7,delaying,0.0%,350) TMC(4,nWait,0.7%,74) MAIN(1,running,70.6%,584) IDLE(0,ready,5.0%,29) AIN(4,delaying,0.9%,264), total 100.0%
                        Owned mutexes: WiFi(NETWORK)
                        === Platform ===
                        Last reset 18:14:11 ago, cause: software
                        Last software reset at 2023-12-15 17:21, reason: User, Gcodes spinning, available RAM 12348, slot 2
                        Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                        Error status: 0x04
                        Aux0 errors 0,0,0
                        MCU revision 3, ADC conversions started 65650769, completed 65650768, timed out 0, errs 0
                        MCU temperature: min 42.2, current 46.2, max 46.8
                        Supply voltage: min 23.4, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
                        Heap OK, handles allocated/used 198/28, heap memory allocated/used/recyclable 2048/716/296, gc cycles 127712
                        Events: 0 queued, 0 completed
                        Driver 0: ok, SG min 0, read errors 0, write errors 0, ifcnt 29, reads 30499, writes 19, timeouts 0, DMA errors 0, CC errors 0
                        Driver 1: ok, SG min 0, read errors 0, write errors 0, ifcnt 29, reads 30499, writes 19, timeouts 0, DMA errors 0, CC errors 0
                        Driver 2: ok, SG min 0, read errors 0, write errors 0, ifcnt 168, reads 30510, writes 8, timeouts 0, DMA errors 0, CC errors 0
                        Driver 3: ok, SG min 0, read errors 0, write errors 0, ifcnt 169, reads 30512, writes 7, timeouts 0, DMA errors 0, CC errors 0
                        Driver 4: ok, SG min 0, read errors 0, write errors 0, ifcnt 167, reads 30510, writes 8, timeouts 0, DMA errors 0, CC errors 0
                        Driver 5: not present
                        Driver 6: not present
                        Date/time: 2023-12-16 11:35:22
                        Cache data hit count 4294967295
                        Slowest loop: 216.18ms; fastest: 0.09ms
                        === Storage ===
                        Free file entries: 16
                        SD card 0 detected, interface speed: 22.5MBytes/sec
                        SD card longest read time 6.6ms, write time 5.2ms, max retries 0
                        === Move ===
                        DMs created 83, segments created 41, maxWait 322812ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, ebfmin 0.00, ebfmax 0.00
                        next step interrupt due in 50 ticks, enabled
                        Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
                        === DDARing 0 ===
                        Scheduled moves 842, completed 836, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state 3
                        === DDARing 1 ===
                        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.5
                        Heater 1 is on, I-accum = 0.0
                        === GCodes ===
                        Movement locks held by null, null
                        HTTP is idle in state(s) 0
                        Telnet is idle in state(s) 0
                        File is idle in state(s) 3
                        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 doing "G4 P10" in state(s) 0 0, running macro
                        Aux2 is idle in state(s) 0
                        Autopause is idle in state(s) 0
                        File2 is idle in state(s) 0
                        Queue2 is idle in state(s) 0
                        Q0 segments left 1, axes/extruders owned 0x0000807
                        Code queue 0 is empty
                        Q1 segments left 0, axes/extruders owned 0x0000000
                        Code queue 1 is empty
                        === Filament sensors ===
                        check 0 clear 0
                        Extruder 0 sensor: no filament
                        === CAN ===
                        Messages queued 6599, received 12089, lost 0, errs 0, boc 0
                        Longest wait 6ms for reply type 6013, peak Tx sync delay 262, free buffers 26 (min 25), ts 2900/2900/0
                        Tx timeouts 0,0,0,0,0,0
                        === Network ===
                        Slowest loop: 209.17ms; fastest: 0.06ms
                        Responder states: MQTT(0) HTTP(0) 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.1beta6
                        MAC address c4:5b:be:ce:91:93
                        Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 39732
                        WiFi IP address 192.168.10.x
                        Signal strength -48dBm, channel 6, mode 802.11n, reconnections 0
                        Clock register 00002001
                        Socket states: 0 0 0 0 0 0 0 0
                        M122 B121
                        Diagnostics for board 121:
                        Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.2 (2023-12-15 13:41:02)
                        Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
                        All averaging filters OK
                        Never used RAM 2708, free system stack 91 words
                        Tasks: Move(3,nWait,0.0%,73) HEAT(2,nWait,0.4%,97) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.0%,77) CanClock(5,nWait,0.0%,69) ACCEL(3,nWait,0.0%,17) TMC(2,delaying,3.0%,57) MAIN(1,running,91.8%,318) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.7%,114), total 100.0%
                        Last reset 18:14:15 ago, cause: software
                        Last software reset data not available
                        Driver 0: pos 0, 568.8 steps/mm, standstill, SG min 0, read errors 0, write errors 0, ifcnt 105, reads 21809, writes 2, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 38048
                        Moves scheduled 3109, completed 3109, in progress 0, hiccups 2, segs 40, step errors 0, maxLate 0 maxPrep 261, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max inf
                        Peak sync jitter -1/10, peak Rx sync delay 213, resyncs 0/0, no timer interrupt scheduled
                        VIN voltage: min 23.4, current 24.1, max 24.5
                        MCU temperature: min 38.6C, current 61.1C, max 69.2C
                        Last sensors broadcast 0x00000012 found 2 168 ticks ago, 0 ordering errs, loop time 0
                        CAN messages queued 11838, send timeouts 0, received 6345, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
                        dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 324, adv 35827/74649
                        Accelerometer: LIS3DH, status: 00
                        Inductive sensor: not found
                        I2C bus errors 0, naks 0, contentions 0, other errors 0
                        === Filament sensors ===
                        Interrupt 5726621 to 0us, poll 5 to 1488us
                        Driver 0: ok
                        undefined 1 Reply Last reply 17 Dec 2023, 13:19 Reply Quote 0
                        • undefined
                          Exerqtor @Exerqtor
                          last edited by Exerqtor 17 Dec 2023, 13:19

                          @dc42
                          I just removed all the "extra stuff "that was put in daemon.g to see if that mad a difference but it still starts reversing. Same if i "disable" daemon.g or run it completely empty.

                          Now it's on the first line of my 3-line purge/prime code each time "no matter" what i do.

                          Is it any apparent issue from the M122 reports i've been posting, or is that just a complete waste of time to post those?


                          Feel like i'm pulling straws out of my ass at this point, but could formating the sd-card and reinstalling all the firmware be worth a try?

                          I mean, i've been installing so many different builds the last 3-4months maybe something got messed up?

                          Or is that just nonsense?

                          A Former User? 1 Reply Last reply 17 Dec 2023, 14:24 Reply Quote 0
                          • A Former User?
                            A Former User @Exerqtor
                            last edited by 17 Dec 2023, 14:24

                            @Exerqtor If it makes you feel better I figured out the problem I have been having for the last week is the extruder occasionally stopping. Using a Duet 3 mini 5+ with a RRF-36 toolboard. 3.5.0-R1 on the board and 3.5.0.r1+101 on the toolboard.

                            I thought it was cooling related since it is a new Dragonfly BMO hotend and EVA34 setup thanks to a fan failure earlier. But nothing is wrong, the heatbreak is clear, the nozzle is not clogged Went through the wiring too to make sure no momentaries were happening.

                            Not seeing an error and no desire to try it again and waste more expensive carbon fiber PC filament. Plus I am going to be tied up for the next couple weeks, So I'll park that printer and revisit it early next year.

                            I did kill daemon.g to see if it was related since that and the new hotend assembly were the changes recently done and it did not help. Not seeing any crashes but I am running a different setup than you. Win 10 with Cura slicing the files and firefox running DWC. And the 2 reprints also failed. They sure mess up a print when they happen.

                            undefined 1 Reply Last reply 17 Dec 2023, 14:47 Reply Quote 1
                            • undefined
                              Exerqtor @A Former User
                              last edited by 17 Dec 2023, 14:47

                              @KenW
                              Sucks to hear you also have problems, but it really does make me feel better to hear that it's not another "one off" issue, and it's something happening to others as well 😮‍💨

                              I've got alot of projects I hoped to get done by/in the comming holidays, but it's looking increasingly less and less likely 💩

                              It's luckily some bog standard ABS i've had to throw in the fuckit-bucket, but it's still annoying af.

                              A Former User? 1 Reply Last reply 17 Dec 2023, 16:48 Reply Quote 0
                              • A Former User?
                                A Former User @Exerqtor
                                last edited by 17 Dec 2023, 16:48

                                @Exerqtor That is the only printer running the beta firmware. It has to run it to use the RRF-36 toolboard. I had noticed your post but was ignoring them since I thought it was filament getting stuck in the heatbreak or possibly carbon fiber jamming the nozzle. I can take down and reassemble the EVA in minutes now with all the practice I have been getting.

                                Since mine is not acting up exactly like yours unless your extruder just stops for a bit then restarts with no error maybe it's another issue.
                                After I get back home in a few weeks I'll play around more with it,. Gave up today on the print I was trying to take with me.

                                undefined 1 Reply Last reply 17 Dec 2023, 19:16 Reply Quote 0
                                • undefined
                                  Exerqtor @A Former User
                                  last edited by Exerqtor 17 Dec 2023, 19:16

                                  @KenW I also thought i had gotten a clog or something when it started happening again so i get your logic lol. It will be interesting seeing how it plays out when you get some time to look at it again.


                                  I just reverted to 3.5.0b4 on the mobo & toolboard to see what happens at least, too be continued.

                                  EDIT:
                                  After reverting too 3.5.0b4 I was finally able to complete the print without issues.

                                  I'm gonna try doing some more prints after work tomorrow to see if the "solution" holds, but it sure looks like the problem lies in 3.5.0-rc1/2.

                                  undefined 1 Reply Last reply 20 Dec 2023, 20:09 Reply Quote 0
                                  • undefined Exerqtor referenced this topic 18 Dec 2023, 10:59
                                  • undefined
                                    Exerqtor @Exerqtor
                                    last edited by 20 Dec 2023, 20:09

                                    @dc42 I've ran over ballpark 24hr of prints on 2.5.0b4 now without any issues.

                                    Weird that noone else reports about this.

                                    A Former User? 1 Reply Last reply 20 Dec 2023, 23:17 Reply Quote 0
                                    • A Former User?
                                      A Former User @Exerqtor
                                      last edited by A Former User 20 Dec 2023, 23:17

                                      @Exerqtor Not home to look at anything but it might depend on the setup. I had another printer earlier that I also had a duet 3 mini 5+ with 3.5.0 r.1 and a RRF-36 mounted with 3.5.0 r1 firmware. That was an ender 3 pro, a simple bed slinger. I did multiple test prints on it before it was wrapped up as a gift and hauled up here. In 5 days it gets to live again and hopefully will still be problem free.

                                      The printer giving me problems is a CoreXY with 3 Z steppers and a klicky so a bit more complex and different motion system. Also a Duet 3 mini 5_ with the other RRF-36 and the same firmware as the ender.

                                      undefined 1 Reply Last reply 22 Dec 2023, 16:44 Reply Quote 0
                                      • undefined Exerqtor referenced this topic 21 Dec 2023, 15:29
                                      • undefined
                                        Exerqtor @A Former User
                                        last edited by 22 Dec 2023, 16:44

                                        @dc42 I tried installing 3.5.0-rc2 again, with a freshly formated SD card etc. to see if that might help (downloaded the binaries again also just in case) and it still shits the bed:

                                        M122
                                        === Diagnostics ===
                                        RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.2 (2023-12-14 10:30:57) running on Duet 3 Mini5plus WiFi (standalone mode)
                                        Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
                                        Used output buffers: 4 of 40 (40 max)
                                        === RTOS ===
                                        Static ram: 102812
                                        Dynamic ram: 128720 of which 0 recycled
                                        Never used RAM 5196, free system stack 118 words
                                        Tasks: NETWORK(1,ready,119.4%,195) HEAT(3,nWait,0.7%,328) Move(4,nWait,14.5%,239) CanReceiv(6,nWait,1.2%,774) CanSender(5,nWait,0.3%,327) CanClock(7,delaying,0.2%,350) TMC(4,nWait,17.4%,74) MAIN(1,running,53.1%,580) IDLE(0,ready,19.8%,29) AIN(4,delaying,20.2%,264), total 246.8%
                                        Owned mutexes: WiFi(NETWORK)
                                        === Platform ===
                                        Last reset 24:56:40 ago, cause: software
                                        Last software reset at 2023-12-21 16:42, reason: User, Gcodes spinning, available RAM 12348, slot 0
                                        Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00446000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                                        Error status: 0x04
                                        Aux0 errors 0,0,0
                                        MCU revision 3, ADC conversions started 89801376, completed 89801376, timed out 0, errs 0
                                        MCU temperature: min 34.4, current 46.8, max 47.3
                                        Supply voltage: min 8.0, current 23.9, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
                                        Heap OK, handles allocated/used 198/28, heap memory allocated/used/recyclable 2048/532/136, gc cycles 15646
                                        Events: 1 queued, 1 completed
                                        Driver 0: ok, SG min 0, read errors 0, write errors 1, ifcnt 33, reads 7119, writes 123, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x72
                                        Driver 1: ok, SG min 0, read errors 0, write errors 1, ifcnt 33, reads 7120, writes 123, timeouts 0, DMA errors 0, CC errors 0
                                        Driver 2: ok, SG min 0, read errors 0, write errors 1, ifcnt 149, reads 7187, writes 56, timeouts 0, DMA errors 0, CC errors 0
                                        Driver 3: ok, SG min 0, read errors 0, write errors 1, ifcnt 145, reads 7185, writes 57, timeouts 0, DMA errors 0, CC errors 0
                                        Driver 4: ok, SG min 0, read errors 0, write errors 1, ifcnt 144, reads 7187, writes 55, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x01
                                        Driver 5: not present
                                        Driver 6: not present
                                        Date/time: 2023-12-22 17:38:55
                                        Cache data hit count 4294967295
                                        Slowest loop: 226.03ms; fastest: 0.09ms
                                        === Storage ===
                                        Free file entries: 16
                                        SD card 0 detected, interface speed: 22.5MBytes/sec
                                        SD card longest read time 11.0ms, write time 62.9ms, max retries 0
                                        === Move ===
                                        DMs created 83, segments created 43, maxWait 59621605ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, ebfmin 0.00, ebfmax 0.00
                                        next step interrupt due in 37 ticks, enabled
                                        Moves shaped first try 52954, on retry 20590, too short 71476, wrong shape 255081, maybepossible 11645
                                        === DDARing 0 ===
                                        Scheduled moves 2684, completed 2644, hiccups 1184, stepErrors 0, LaErrors 1095, Underruns [0, 0, 4], CDDA state 3
                                        === DDARing 1 ===
                                        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.0
                                        === GCodes ===
                                        Movement locks held by null, null
                                        HTTP is idle in state(s) 0
                                        Telnet is idle in state(s) 0
                                        File is doing "G1 X131.338 Y134.213 E.09057" 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 doing "G4 P250" in state(s) 0 0, running macro
                                        Aux2 is idle in state(s) 0
                                        Autopause is idle in state(s) 0
                                        File2 is idle in state(s) 0, sync state 1
                                        Queue2 is idle in state(s) 0
                                        Q0 segments left 1, axes/extruders owned 0x0000807
                                        Code queue 0 is empty
                                        Q1 segments left 0, axes/extruders owned 0x0000000
                                        Code queue 1 is empty
                                        === Filament sensors ===
                                        check 0 clear 0
                                        Extruder 0 sensor: no filament
                                        === CAN ===
                                        Messages queued 1264763, received 1844452, lost 0, errs 1, boc 0
                                        Longest wait 6ms for reply type 6013, peak Tx sync delay 276, free buffers 26 (min 24), ts 449002/449001/0
                                        Tx timeouts 0,0,0,0,0,0
                                        === Network ===
                                        Slowest loop: 211.13ms; fastest: 0.00ms
                                        Responder states: MQTT(0) HTTP(0) 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.1beta6
                                        MAC address c4:5b:be:ce:91:93
                                        Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 36292
                                        WiFi IP address 192.168.10.x
                                        Signal strength -52dBm, channel 6, mode 802.11n, reconnections 0
                                        Clock register 00002001
                                        Socket states: 0 0 0 0 0 0 0 0
                                        M122 B121
                                        Diagnostics for board 121:
                                        Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.2 (2023-12-14 08:58:51)
                                        Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
                                        All averaging filters OK
                                        Never used RAM 2580, free system stack 89 words
                                        Tasks: Move(3,nWait,2.9%,71) HEAT(2,nWait,7.9%,91) CanAsync(5,nWait,0.0%,55) CanRecv(3,nWait,1.0%,77) CanClock(5,nWait,0.4%,67) ACCEL(3,nWait,0.0%,53) TMC(2,nWait,70.2%,57) MAIN(1,running,53.1%,316) IDLE(0,ready,0.0%,27) AIN(2,delaying,111.1%,114), total 246.6%
                                        Last reset 24:56:46 ago, cause: software
                                        Last software reset data not available
                                        Driver 0: pos 0, 568.8 steps/mm, ok, SG min 0, read errors 5, write errors 1, ifcnt 112, reads 29381, writes 30, timeouts 10, DMA errors 0, CC errors 0, failedOp 0x01, steps req 0 done 54758132
                                        Moves scheduled 451072, completed 451072, in progress 0, hiccups 6856, segs 42, step errors 0, maxLate 2 maxPrep 759, maxOverdue 7315, maxInc 2784, mcErrs 0, gcmErrs 0, ebfmin -1.00 max inf
                                        Peak sync jitter -2/12, peak Rx sync delay 280, resyncs 0/0, no timer interrupt scheduled
                                        VIN voltage: min 8.3, current 24.1, max 24.6
                                        MCU temperature: min 39.4C, current 73.3C, max 79.5C
                                        Last sensors broadcast 0x00000012 found 2 138 ticks ago, 0 ordering errs, loop time 0
                                        CAN messages queued 1844535, send timeouts 0, received 1264877, lost 0, errs 1230, boc 0, free buffers 18, min 17, error reg 110000
                                        dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 390, adv 34547/74657
                                        Accelerometer: LIS3DH, status: 00
                                        Inductive sensor: not found
                                        I2C bus errors 0, naks 6, contentions 0, other errors 0
                                        === Filament sensors ===
                                        Interrupt 5726621 to 0us, poll 4 to 2681us

                                        And it's still happening at random points.

                                        undefined undefined 2 Replies Last reply 22 Dec 2023, 18:05 Reply Quote 0
                                        • undefined
                                          droftarts administrators @Exerqtor
                                          last edited by 22 Dec 2023, 18:05

                                          @Exerqtor I can’t remember if you have posted your config.g recently, but if not, could you post it again, please? If it calls macros, maybe a zip of you sys folder might be easier, to include them all. It’s just the Mini 5+ and a 1LC? What revision of each board? And what extruder type and motor? Does it still do it if you run a ‘dry’ job with no filament? Finally, can you post a Gcode file that provokes the retractions? Though I suspect it isn’t related to the Gcode itself.

                                          Ian

                                          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                                          undefined 1 Reply Last reply 22 Dec 2023, 19:01 Reply Quote 0
                                          27 out of 147
                                          • First post
                                            27/147
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA