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

    Odd Extruder Pausing - 1LC - Toolboard Duet 3 Mini

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    7
    14
    658
    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.
    • SputnikOC3dundefined
      SputnikOC3d
      last edited by

      Just started getting very odd extruder feed pauses. Seems very strange.

      If I ask DWC o extrude at temps [ ABS+ 255c ] 100 mm of material at 5mm/s - it will spew out about 30-40 mm / pause - send another 20mm then pause and so on - it extrudes in fits and starts - as if the can bus is confused or the motor is losing steps. Its not clicking. It s got good grip on material. Its coming off the roll with minimal friction. Totally at a loss ...

      1LC - Toolboard + Duet 3 Mini / SBC Mode

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus Ethernet (SBC mode)
      Board ID: 1JDTH-UA67A-G65J0-40TFU-22D0Z-R2KLQ
      Used output buffers: 1 of 40 (12 max)
      === RTOS ===
      Static ram: 103684
      Dynamic ram: 97612 of which 0 recycled
      Never used RAM 37320, free system stack 138 words
      Tasks: SBC(ready,2.9%,446) HEAT(notifyWait,0.0%,338) Move(notifyWait,0.1%,269) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,346) CanClock(delaying,0.0%,337) TMC(notifyWait,1.2%,71) MAIN(running,94.8%,498) IDLE(ready,0.2%,29) AIN(delaying,0.8%,264), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:31:22 ago, cause: software
      Last software reset at 2022-04-11 23:58, reason: User, GCodes spinning, available RAM 37992, slot 0
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
      Error status: 0x00
      MCU revision 3, ADC conversions started 1882694, completed 1882694, timed out 0, errs 0
      Step timer max interval 1481
      MCU temperature: min 32.0, current 39.4, max 44.2
      Supply voltage: min 23.8, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/11, heap memory allocated/used/recyclable 2048/918/780, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 36, reads 40018, writes 24, timeouts 0, DMA errors 0, CC errors 0
      Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 36, reads 40018, writes 24, timeouts 0, DMA errors 0, CC errors 0
      Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 36, reads 40017, writes 24, timeouts 0, DMA errors 0, CC errors 0
      Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 36, reads 40017, writes 24, timeouts 0, DMA errors 0, CC errors 0
      Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 40033, writes 9, timeouts 0, DMA errors 0, CC errors 0
      Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 59, reads 39994, writes 47, timeouts 0, DMA errors 0, CC errors 0
      Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 55, reads 39998, writes 43, timeouts 0, DMA errors 0, CC errors 0
      Date/time: 2022-04-12 00:30:18
      Cache data hit count 4011539488
      Slowest loop: 311.19ms; fastest: 0.07ms
      === Storage ===
      Free file entries: 10
      SD card 0 not detected, interface speed: 0.0MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, segments created 10, maxWait 459926ms, bed compensation in use: mesh, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 593, completed 593, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 30], CDDA state -1
      === AuxDDARing ===
      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
      === GCodes ===
      Segments left: 0
      Movement lock held by null
      HTTP* is doing "M122" 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 17597, received 37814, lost 0, boc 0
      Longest wait 3ms for reply type 6053, peak Tx sync delay 156, free buffers 18 (min 16), ts 9413/9412/0
      Tx timeouts 0,0,0,0,0,0
      === SBC interface ===
      Transfer state: 4, failed transfers: 0, checksum errors: 0
      RX/TX seq numbers: 9348/9348
      SPI underruns 0, overruns 0
      State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x0f6b8
      Buffer RX/TX: 0/0-0, open files: 0
      === Duet Control Server ===
      Duet Control Server v3.4.0
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
      Full transfers per second: 39.82, max time between full transfers: 168.1ms, max pin wait times: 91.1ms/24.8ms
      Codes per second: 0.87
      Maximum length of RX/TX data transfers: 3484/1232
      
      M122 B121
      Diagnostics for board 121:
      Duet TOOL1LC rev 1.1 or later firmware version 3.4.0 (2022-03-15 09:00:04)
      Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
      All averaging filters OK
      Never used RAM 2624, free system stack 45 words
      Tasks: Move(notifyWait,0.0%,99) HEAT(notifyWait,0.4%,95) CanAsync(notifyWait,0.0%,57) CanRecv(notifyWait,0.0%,74) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,3.0%,57) MAIN(running,91.6%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
      Last reset 00:36:35 ago, cause: software
      Last software reset data not available
      Driver 0: pos 358464, 415.0 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 33, reads 48788, writes 20, timeouts 0, DMA errors 0, CC errors 0, steps req 361028 done 361028
      Moves scheduled 545, completed 545, in progress 0, hiccups 0, step errors 0, maxPrep 477, maxOverdue 2, maxInc 1, mcErrs 0, gcmErrs 0
      Peak sync jitter -5/10, peak Rx sync delay 214, resyncs 0/0, no step interrupt scheduled
      VIN voltage: min 23.7, current 23.9, max 24.1
      MCU temperature: min 37.2C, current 49.8C, max 51.6C
      Last sensors broadcast 0x00000002 found 1 94 ticks ago, 0 ordering errs, loop time 1
      CAN messages queued 44082, send timeouts 0, received 20414, lost 0, free buffers 37, min 36, error reg 110000
      dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 361, adv 35831/74649
      Accelerometer: LIS3DH, status: 00
      I2C bus errors 0, naks 3, other errors 0
      
      ctilley79undefined Phaedruxundefined dc42undefined 3 Replies Last reply Reply Quote 0
      • ctilley79undefined
        ctilley79 @SputnikOC3d
        last edited by ctilley79

        @sputnikoc3d you know, I’m having some strange pauses as well. My purge strip for example. There’s now a brief pause between these two lines of code where there didn’t used to be. I’m using a 1LC 1.1

        G1 X60 E12 F1000
        G1 X100 E15.5 F1000
        
        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator @SputnikOC3d
          last edited by

          @sputnikoc3d Can you try gathering some logs on the SBC?

          https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#increasing-log-level

          @ctilley79 Are you using an SBC as well?

          Z-Bot CoreXY Build | Thingiverse Profile

          ctilley79undefined 1 Reply Last reply Reply Quote 0
          • ctilley79undefined
            ctilley79 @Phaedrux
            last edited by

            @phaedrux yes

            1 Reply Last reply Reply Quote 0
            • SputnikOC3dundefined
              SputnikOC3d
              last edited by SputnikOC3d

              @Phaedrux Ok so Im reviving this thread ...

              I took the whole toolboard off the machine - checked it over extensively for anything out of the ordinary. This is my 4th 1LC Ive owned, 2nd Ive used.

              I re-crimped all connectors - fans / motor / probe. Power and CAN-Bus I left as is. I re meshed the extruder gears to make sure filament and path was clear and the bondtech gears had good grip.

              Im at the point where m pretty sure its either the motor or the motor driver connector on the board. Everything on the toolboard functions flawlessly.

              PWM Fans, temp sensors, hot end, part cooling fan, probe, heater , onboard led's. Temps on hot end are rock solid. Only thing thats pear shaped is the extruder/extrusion. As above, when using dwc for 100mm @ 5mm/s - I get pauses and it feeds material in fits and starts. 50 mm lengths similar. 10-20 mm lengths at higher feed rates seem to go ok as theyre quick birsts hard to know if theyre flawed.

              I havent been able to do an update via the unstable server as I m wifi / interweb challenged and will have to take the machine up to the house from the garage shop to connect to stable wifi.

              Any other thoughts ?

              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                Do you have another toolboard handy to test with?
                Can you test with a different CAN cable?
                Were you able to test with 3.4.1 RC1 on the unstable branch?
                Are you able to test in standalone mode?

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • dhusoloundefined
                  dhusolo
                  last edited by

                  I'm having a similar issue. Duet 3 + RPI4 and tool board. randomly I will get under extrusion. If i restart the pi the issue seems to go away. Next time it happens I'll try gathering the DSF logs

                  1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators @SputnikOC3d
                    last edited by dc42

                    @sputnikoc3d said in Odd Extruder Pausing - 1LC - Toolboard Duet 3 Mini:

                    If I ask DWC o extrude at temps [ ABS+ 255c ] 100 mm of material at 5mm/s - it will spew out about 30-40 mm / pause - send another 20mm then pause and so on - it extrudes in fits and starts - as if the can bus is confused or the motor is losing steps. Its not clicking. It s got good grip on material. Its coming off the roll with minimal friction. Totally at a loss ...

                    What extruder motor current have you set? Does the tool board have any ventilation? Do you use a heated chamber?

                    I am wondering whether the stepper driver chip could be overheating. That would cause it to cut the motor current, then restore it when the chip has cooled down a little.

                    A command to extrude 50mm of filament with no other movement will be sent as a single CAN command, so it's not likely to be anything to do with CAN communications.

                    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

                    dhusoloundefined SputnikOC3dundefined 2 Replies Last reply Reply Quote 1
                    • dhusoloundefined
                      dhusolo @dc42
                      last edited by

                      @dc42 Personally I have a fully enclosed printer liquid cooled hotend and Mellow NF-Sunrise with current set to 900. I don't print ABS so at most my hotend temps are 230c and bed temps 75c. I've noticed it happens when the pi has been running for a day or more. After it happens I can let the hotend cool down, reboot the pi and it doesn't under-extrude anymore.

                      I have another printer with the same setup minus the liquid cooled hotend and it doesn't have this issue.

                      1 Reply Last reply Reply Quote 0
                      • SputnikOC3dundefined
                        SputnikOC3d @dc42
                        last edited by SputnikOC3d

                        @dc42 TY for your input and posting. Ive been away on business and travel so have just got back into the 3d shop to tinker here in the last week or so.

                        After spending approx $450 on "stuff" chasing down these gremlins [ toolboards / hotends / filaments / bondtech gears / thermistors / heaters et al ... Its come down to the Voron CW1 extruder IMHO.

                        I bolted up an LGX Lite and that with a some new heaters and therms - seemed to allow me to print ABS. Still no go with the eSUN ABS+ Im now thinking I got some mislabeled material from them. Atomic abs prints pretty well now.

                        I did have ot go to square one with this issue and essentially reset all things all over to day 1. It got that crazy. I nthe process I killed a 1LC, 2 thermistors and 1 cheapo heater. The heat actually may have been the impetus for most all mys initial issues from the onset. It wasn the problem but i think it kicked off a chain of events that threw sooo many things out of whack - its complicated.

                        Im now retuning the machine for the unique things about the new hotends and better heaters and therms as well as the LGX Lite.

                        wdenkerundefined 1 Reply Last reply Reply Quote 0
                        • wdenkerundefined
                          wdenker @SputnikOC3d
                          last edited by

                          @SputnikOC3d @dc42 did we get anywhere with this thread? I'm running into the same issues with a tool board in a heated chamber. Is there a way to check to see what the driver temperature is?

                          www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                          T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
                          • T3P3Tonyundefined
                            T3P3Tony administrators @wdenker
                            last edited by

                            @wdenker said in Odd Extruder Pausing - 1LC - Toolboard Duet 3 Mini:

                            Is there a way to check to see what the driver temperature is?

                            A proxy for this, if you are running it hot, is the MCU temperature reported by M122 Bnnn where nnn is the address of the toolboard. The TMC2209 drives do not report their temperature, they do report over temperature warning AFAIR. please send M122 Bnnn when the motor is pausing.

                            www.duet3d.com

                            wdenkerundefined 1 Reply Last reply Reply Quote 0
                            • wdenkerundefined
                              wdenker @T3P3Tony
                              last edited by

                              @T3P3Tony at what temperature do they shut down?

                              www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                              T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
                              • T3P3Tonyundefined
                                T3P3Tony administrators @wdenker
                                last edited by

                                @wdenker from the datasheet, 143C:

                                https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2209_datasheet_rev1.09.pdf

                                However that's internal temperature generated from the MOSFETs inside the TMC2209, not chamber temperature. The hotter the chamber, the less motor current can be used before the driver overtemp kicks in.

                                www.duet3d.com

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Unless otherwise noted, all forum content is licensed under CC-BY-SA