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

    short to ground issues

    Scheduled Pinned Locked Moved
    General Discussion
    2
    4
    143
    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.
    • motor5622undefined
      motor5622
      last edited by

      About 2 weeks ago the end stop in io4 quit working moved it to io3 and it worked again. Though that strange but it was working. Today about 5 layers into a print I get.

      4/6/2022, 4:22:17 PM Error: short-to-ground reported by driver(s) 0
      Error: over temperature shutdown reported by driver(s) 0
      Warning: high temperature reported by driver(s) 0
      4/6/2022, 4:22:12 PM Error: short-to-ground reported by driver(s) 0

      and the error just kept scrolling. My printer has been working just fine since it was put together. I only made one change since it was assembled and that was to change from an inductive probe to a euclid, but that was all done in the 1lc. here is the M122 and my config.g

      4/6/2022, 4:44:05 PM M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
      Board ID: Q4QR2-4196U-D65J0-40KMS-J703Z-RRM35
      Used output buffers: 3 of 40 (14 max)
      === RTOS ===
      Static ram: 102724
      Dynamic ram: 107004 of which 24 recycled
      Never used RAM 31096, free system stack 130 words
      Tasks: NETWORK(ready,15.6%,226) HEAT(delaying,0.0%,348) Move(notifyWait,0.1%,283) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,347) TMC(delaying,1.2%,115) MAIN(running,82.3%,412) IDLE(ready,0.0%,29) AIN(delaying,0.8%,264), total 100.0%
      Owned mutexes:
      === Platform ===
      Last reset 00:19:58 ago, cause: software
      Last software reset at 2022-04-06 16:24, reason: User, GCodes spinning, available RAM 30488, slot 0
      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 revision 3, ADC conversions started 1199105, completed 1199105, timed out 0, errs 0
      Step timer max interval 953
      MCU temperature: min 28.6, current 29.2, max 33.3
      Supply voltage: min 23.9, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/5, heap memory allocated/used/recyclable 2048/232/162, gc cycles 0
      Driver 0: position 26488, standstill, SG min/max 0/398, read errors 0, write errors 1, ifcnt 152, reads 43401, writes 19, timeouts 0, DMA errors 0
      Driver 1: position 2488, standstill, SG min/max 0/88, read errors 0, write errors 1, ifcnt 152, reads 43401, writes 19, timeouts 0, DMA errors 0
      Driver 2: position 340, standstill, SG min/max 0/84, read errors 0, write errors 1, ifcnt 152, reads 43401, writes 19, timeouts 0, DMA errors 0
      Driver 3: position 0, standstill, SG min/max 0/84, read errors 0, write errors 1, ifcnt 152, reads 43401, writes 19, timeouts 0, DMA errors 0
      Driver 4: position 0, standstill, SG min/max 0/10, read errors 0, write errors 1, ifcnt 149, reads 43402, writes 18, timeouts 0, DMA errors 0
      Driver 5: position 0, standstill, SG min/max 0/10, read errors 0, write errors 1, ifcnt 150, reads 43402, writes 18, timeouts 0, DMA errors 0
      Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 79, reads 43411, writes 9, timeouts 0, DMA errors 0
      Date/time: 2022-04-06 16:44:01
      Cache data hit count 2196188892
      Slowest loop: 12.26ms; fastest: 0.07ms
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 3.5ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 433726ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 66, completed moves 66, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 51], 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, chamberHeaters = -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
      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 10827, received 14393, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 368, free buffers 17 (min 15), ts 5994/5993/0
      Tx timeouts 0,0,0,0,0,0
      === Network ===
      Slowest loop: 22.78ms; 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:e5:af
        WiFi Vcc 3.33, reset reason Power up
        WiFi flash size 2097152, free heap 22528
        WiFi IP address 192.168.1.19
        WiFi signal strength -40dBm, mode 802.11n, reconnections 0, sleep mode modem
        Clock register 00002002
        Socket states: 0 0 0 0 0 0 0 0

      config.g

      I have not been able to get the error to show up by moving it manually.

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

        @motor5622 said in short to ground issues:

        I have not been able to get the error to show up by moving it manually.

        I think you're in stealthchop mode and moving too fast for it.

        I suggest you update to 3.4 which defaults to spreadcycle mode and see if it makes a difference.

        Since you're able to move the motor manually I don't think it's an actually failed driver.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • motor5622undefined
          motor5622
          last edited by

          Is there anything that needs to change right away in config.g moving to 3.4? I haven't looked to deep into the upgrade yet.

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

            Best to take a look https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-340

            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