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

Any thoughts on what might have caused this 6HC to go sideways?

Scheduled Pinned Locked Moved
Duet Hardware and wiring
3
4
254
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
    oozeBot
    last edited by oozeBot 15 Apr 2025, 16:01

    My personal dev system (photo below) has been sitting on my desk running happily for well over a year now completely sealed as shown. It has never had any motors connected to it (or anything else) nor had any known events that might have caused power spikes, etc. Last week, I found it doing this: Recording 2025-04-15 114733.mp4

    IMG_0019.jpg

    I guess I can't embed a video, so if you don't want to click the link, all six drivers are erroring with "over temperature shutdown, phase A short to ground, phase B short to ground." over and over..

    edit to answer the obvious - the board is cool to the touch. There is no signs of anything being "over temperature" and there is a cooling fan built in blowing directly on the board from behind.

    Perhaps something @dc42 can weigh in on? FYI - replacing the board immediately resolved the issue, so it's definitely the board.. Thanks

    undefined undefined 2 Replies Last reply 15 Apr 2025, 20:36 Reply Quote 0
    • undefined oozeBot marked this topic as a question 15 Apr 2025, 16:19
    • undefined
      elmoret @oozeBot
      last edited by 15 Apr 2025, 20:36

      That sounds like SPI failure, the microcontroller can't talk to the stepper drivers.

      1 Reply Last reply Reply Quote 0
      • undefined
        dc42 administrators @oozeBot
        last edited by dc42 17 Apr 2025, 08:46

        @oozeBot it's either an SPI failure or a failure of power to the drivers. The SPI data signal goes from pin 105 of the MCU to pin 15 of driver 0. Then from pin 16 of driver 0 to pin 15 of driver 1, then from pin 16 of driver 1 to pin 15 of driver 2 and so on until pin 16 of driver 5 is connected to the MCU pin 32.

        The SCLK signal goes from pin 46 of the MCU to pin 14 of every driver. The CS signal goes from pin 74 of the MCU to pin 13 of every driver.

        The drivers take 3.3V power on pin 20 and 12V power on pin 4. Caution: if you try to measure 12V power on pin 4 and in the process you short it to pin 5, you will destroy the driver. A safer way to check for 12V power to driver 5 is to measure it on capacitor C110. There should also be 5V on capacitor C116.

        I suggest you start by checking that driver 5 is receiving power, and that all three of its connections to the MCU are intact.

        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

        1 Reply Last reply Reply Quote 1
        • undefined
          oozeBot
          last edited by 17 Apr 2025, 15:18

          Thank you both! I'll have an engineer do some testing on it. We've never seen one have this kind of issue before and would like to understand if we (really, myself since it's been on my desk) caused it damage or if it was just a faulty board. I'll go ahead and remove the "Unsolved" tag.

          1 Reply Last reply Reply Quote 0
          • undefined oozeBot marked this topic as a regular topic 17 Apr 2025, 15:18
          1 out of 4
          • First post
            1/4
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA