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

    short to ground, over tempeature

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    5
    216
    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.
    • gabitundefined
      gabit
      last edited by gabit

      Hi
      i got some errors on drive 2
      All is clean, nothing is on board which could create short
      The Chip is getting hot
      Even if nothing is connected to the boad and powered by usb
      IMG_2696.jpg IMG_2693.jpg IMG_2694.jpg IMG_2695.jpg IMG_2697.jpg

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

        Can you send M122 and M98 P"config.g" in the Gcode console in DWC and post the results? Also your config.g?

        Is this a new Duet or an existing printer? Has it ever worked? Has anything recently changed?

        If you remove the SD card from the board and apply USB, does the chip still get hot?

        When and where did you purchase the Duet?

        Z-Bot CoreXY Build | Thingiverse Profile

        gabitundefined 2 Replies Last reply Reply Quote 0
        • gabitundefined
          gabit @Phaedrux
          last edited by gabit

          @phaedrux
          Hi,

          • with removed SD Card it gets also hot in a view seconds.
          • because of this, i think the config.g is not the problem
          • the Board is changed on 4.Jan see here
          • since it is changed it runs perfect, until a view days ago, nothing changed at this time
          • it it purchased at 19.04.2021 by filafarm (berlin/germany)
          • the z drive is never used, no stop no stepper
          • then new firmware i installed after i have get this problems, before it was workbee controll 1.0
          M122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet Ethernet 1.02 or later
          Board ID: 0JD0M-9P6B2-NJ4S8-6JKF0-3SD6Q-TU7UL
          Used output buffers: 1 of 24 (10 max)
          === RTOS ===
          Static ram: 23460
          Dynamic ram: 69040 of which 60 recycled
          Never used RAM 19520, free system stack 204 words
          Tasks: NETWORK(ready,206) HEAT(blocked,212) MAIN(running,471) IDLE(ready,20)
          Owned mutexes:
          === Platform ===
          Last reset 00:02:31 ago, cause: power up
          Last software reset at 2022-03-27 16:00, reason: User, GCodes spinning, available RAM 19520, slot 1
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
          Error status: 0x00
          Aux0 errors 0,0,0
          MCU temperature: min 31.1, current 35.6, max 116.7
          Supply voltage: min 1.3, current 1.7, max 2.1, under voltage events: 0, over voltage events: 0, power good: no
          Driver 0: position 0, ok, SG min/max not available
          Driver 1: position 0, ok, SG min/max not available
          Driver 2: position 0, ok, SG min/max not available
          Driver 3: position 0, ok, SG min/max not available
          Driver 4: position 0, ok, SG min/max not available
          Driver 5: position 0
          Driver 6: position 0
          Driver 7: position 0
          Driver 8: position 0
          Driver 9: position 0
          Driver 10: position 0
          Driver 11: position 0
          Date/time: 2022-03-31 19:05:18
          Cache data hit count 290514072
          Slowest loop: 7.05ms; fastest: 0.20ms
          I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
          === Storage ===
          Free file entries: 10
          SD card 0 detected, interface speed: 20.0MBytes/sec
          SD card longest read time 3.7ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === AuxDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === Heat ===
          Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
          === 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
          Daemon is idle in state(s) 0
          Autopause is idle in state(s) 0
          Code queue is empty.
          === Network ===
          Slowest loop: 7.03ms; fastest: 0.01ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
          HTTP sessions: 1 of 8
          Interface state active, link 100Mbps full duplex
          
          1 Reply Last reply Reply Quote 0
          • gabitundefined
            gabit @Phaedrux
            last edited by

            @phaedrux What are the next steps, i need my duet and wait for resulation.
            I think the board is damaged.

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

              Hello, sorry about that, I think I misplaced your reply.

              Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

              Z-Bot CoreXY Build | Thingiverse Profile

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