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

    Lost connection to Duet 1LC?

    Scheduled Pinned Locked Moved
    General Discussion
    4
    6
    298
    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.
    • Argoundefined
      Argo
      last edited by Argo

      Hello forum...

      Board: Duet 3 Mini 5+
      Toolboard: Duet 1LC v1.1

      What happened: print stopped because of extruder heater thermistor fault.

      The LED on the Duet 1LC was not blinking anymore. The LED was on permanently.
      What can cause this? Bad wiring or even overheating? The 1LC is near the extruder which gets really hot. Does a temperature shutdown cause this? After restarting the printer everything seems to work again.

      M122 B121

      Error: M122: Response timeout: CAN addr 121, req type 6024, RID=1094
      

      M122

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (standalone mode)
      Board ID: W0DS5-R296U-D65J0-40KM6-LU03Z-Z3F72
      Used output buffers: 4 of 40 (40 max)
      === RTOS ===
      Static ram: 103684
      Dynamic ram: 111548 of which 40 recycled
      Never used RAM 22432, free system stack 112 words
      Tasks: NETWORK(ready,24.4%,178) HEAT(notifyWait,0.6%,338) Move(notifyWait,31.5%,263) CanReceiv(notifyWait,0.6%,772) CanSender(notifyWait,1.3%,345) CanClock(delaying,0.3%,337) TMC(delaying,32.0%,71) MAIN(running,324.4%,420) IDLE(ready,3.6%,29) AIN(delaying,21.5%,264), total 440.3%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 11:36:09 ago, cause: software
      Last software reset at 2022-04-26 21:48, reason: User, GCodes spinning, available RAM 22336, 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 41770032, completed 41770031, timed out 0, errs 0
      Step timer max interval 1479
      MCU temperature: min 47.8, current 67.6, max 74.2
      Supply voltage: min 24.5, current 24.7, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/8, heap memory allocated/used/recyclable 2048/1460/1204, gc cycles 30
      Events: 1912 queued, 1912 completed
      Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 49, reads 61524, writes 9, timeouts 0, DMA errors 0, CC errors 0
      Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 42, reads 61495, writes 38, timeouts 0, DMA errors 0, CC errors 0
      Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 41, reads 61494, writes 39, timeouts 0, DMA errors 0, CC errors 0
      Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 38, reads 61493, writes 40, timeouts 0, DMA errors 0, CC errors 0
      Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 61495, writes 38, timeouts 0, DMA errors 0, CC errors 0
      Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 20, reads 61494, writes 39, timeouts 0, DMA errors 0, CC errors 0
      Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 61493, writes 40, timeouts 0, DMA errors 0, CC errors 0
      Date/time: 2022-04-27 09:24:35
      Cache data hit count 4294967295
      Slowest loop: 2000.10ms; fastest: 0.07ms
      === Storage ===
      Free file entries: 9
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 4.7ms, write time 249.3ms, max retries 0
      === Move ===
      DMs created 83, segments created 48, maxWait 715499ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 939165, completed 939165, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 150, 18], 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
      Heater 0 is on, I-accum = 0.0
      === GCodes ===
      Segments left: 0
      Movement lock held by null
      HTTP is idle in state(s) 0
      Telnet is idle in state(s) 0
      File is idle in state(s) 0
      USB is idle in state(s) 0
      Aux is idle in state(s) 0
      Trigger is idle in state(s) 0
      Queue is idle in state(s) 0
      LCD is idle in state(s) 0
      SBC is idle in state(s) 0
      Daemon is idle in state(s) 0
      Aux2 is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty
      === Filament sensors ===
      Extruder 0: no data received
      === CAN ===
      Messages queued 1188025, received 529294, lost 0, boc 9462
      Longest wait 808ms for reply type 6029, peak Tx sync delay 49131, free buffers 18 (min 3), ts 208847/113772/0
      Tx timeouts 1458,0,93546,8,0,74762 last cancelled message type 30 dest 127
      === Network ===
      Slowest loop: 1483.75ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 1 of 8
      - WiFi -
      Network state is active
      WiFi module is connected to access point 
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.26
      WiFi MAC address f0:08:d1:02:e7:b3
      WiFi Vcc 3.32, reset reason Power up
      WiFi flash size 2097152, free heap 26448
      WiFi IP address 192.168.1.120
      WiFi signal strength -58dBm, mode 802.11n, reconnections 0, sleep mode modem
      Clock register 00002002
      Socket states: 0 0 0 0 0 0 0 0
      
      
      chrishammundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
      • chrishammundefined
        chrishamm administrators @Argo
        last edited by

        @argo Bad wiring sounds plausible. Can you make sure the firmware on the TOOL1LC is 3.4 as well? M122 B121 should work when the LEDs on both boards flash in sync.

        Duet software engineer

        Argoundefined 1 Reply Last reply Reply Quote 0
        • Argoundefined
          Argo @chrishamm
          last edited by

          @chrishamm

          Yes the Toolboard has 3.4 as well.
          Is there any way to measure the quality of the signal the toolboard receives?
          Maybe the data cable is not twisted enough? I don’t see any visible damage to the cable though.

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

            @argo said in Lost connection to Duet 1LC?:

            The 1LC is near the extruder which gets really hot.

            How hot?

            What kind of wiring? Do you have other wiring to test with?

            Z-Bot CoreXY Build | Thingiverse Profile

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

              @argo I don't think that lockup was caused by CAN signal quality. I think ESD is a more likely cause. Please ensure that the hot end metalwork is grounded, to avoid building up static charge. One option is to connect it to one of the ground pins on the tool board through a 100K resistor.

              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

              Argoundefined 1 Reply Last reply Reply Quote 1
              • Argoundefined
                Argo @dc42
                last edited by

                @dc42

                Once again I’m impressed.
                Thank you. Your suggestion was spot on. I have installed a frame thermistor because I’m observing thermal frame expansion on Z and that frame thermistor got loose and touched the frame which caused ESD which I can also reproduce.

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