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

Steppers Disabled

Scheduled Pinned Locked Moved
Firmware installation
2
3
893
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
    Zest
    last edited by 7 Nov 2017, 05:30 11 Jul 2017, 05:05

    I made a thread a couple days ago regarding the spotty WIFI on my new Duet WIFI… The good news is the WIFI on my replacement works great. The bad news is the steppers don't work at all. With the previous board I was able to jog the printer using Pronterface, but with this board the steppers are completely disabled.

    In an attempt to troubleshoot, I upgraded to 1.19 Beta9 and I'm getting an immediate "short to ground" and "over temp" errors with nothing connected to the board. I did not touch any wiring while the board was powered up and the board has been sitting on the box it came in throughout the setup process. Starting to lose hope here. Reading the forums it seems like failures are extremely rare so I can't believe my luck.

    I have a multimeter and basic electronics experience so I can try to identify the fault if you tell me where to probe. The output below is with absolutely nothing connected except USB. When I had it wired up I had all lights and temps were working. Additionally, the lights for the x,y,z stops worked on trigger. It's just the steppers that don't do anything. The output with 1.18 said the steppers were in standstill.

    EDIT: I have verified that all 6 stepper headers have no continuity on any pin to power ground. I can't see any solder bridges or physical damage to the board. ???

    >>> m122
    SENDING:M122
    === Diagnostics ===
    Used output buffers: 1 of 32 (9 max)
    === Platform ===
    RepRapFirmware for Duet WiFi version 1.19beta9 running on Duet WiFi 1.0
    Board ID: 08DDM-9FAM2-LW4SD-6JKF0-3SJ6Q-TLZMY
    Static ram used: 20904
    Dynamic ram used: 96392
    Recycled dynamic ram: 1488
    Stack ram used: 4000 current, 5212 maximum
    Never used ram: 7076
    Last reset 00:01:36 ago, cause: power up
    Last software reset reason: User, spinning module GCodes, available RAM 33024 bytes (slot 1)
    Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    [ERROR] Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 30.7, current 31.3, max 31.5
    Supply voltage: min 12.6, current 12.7, max 12.8, under voltage events: 0, over voltage events: 0
    Driver 0: stalled temperature-shutdown! short-to-ground standstill
    Driver 1: stalled temperature-shutdown! short-to-ground standstill
    Driver 2: stalled temperature-shutdown! short-to-ground standstill
    Driver 3: stalled temperature-shutdown! short-to-ground standstill
    Driver 4: stalled temperature-shutdown! short-to-ground standstill
    Date/time: 1970-01-01 00:00:00
    Slowest main loop (seconds): 0.003207; fastest: 0.000031
    === Move ===
    MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    Probe change coordinates:
    === Heat ===
    Bed heater = 0, chamber heater = -1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    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
    serial is ready with "M122" in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    Network state is disabled
    WiFi module is disabled
    HTTP sessions: 0 of 8
    Socket states: 0 0 0 0 0 0 0 0
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    Error: Short-to-ground on drivers 0 1 2 3 4
    [ERROR] Error: Short-to-ground on drivers 0 1 2 3 4
    Error: Over temperature shutdown on drivers 0 1 2 3 4
    [ERROR] Error: Over temperature shutdown on drivers 0 1 2 3 4
    Disconnected.
    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 11 Jul 2017, 06:48

      Are you using the same config.g file? Send M906 to check that motor currents have been set.

      If you get over temperature or short to ground errors on all the drivers with nothing connected, and the back of the board is not shorting against a metallic surface, ask for the Duet to be replaced. It sounds like something has gone wrong with the SPI bus used to communicate with the drivers. That's the first time I've heard of that happening. I expect you will find that the drivers are actually cool. I'm sorry that you seem to have received a bad board.

      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 0
      • undefined
        Zest
        last edited by 11 Jul 2017, 07:05

        Boy that's super discouraging. That's two bad boards in a row. I used both the default config.g and a config provided by another wanhao user that was linked here. I get sane output from M906 so I guess I won the Duet lottery again.

        Your diagnosis seems spot on. The drivers are indeed cold. All steppers are completely idle as if they're not even plugged in.

        >>> M906
        SENDING:M906
        Motor current (mA) - X:855, Y:855, Z:670, E:855:855:855:855:855:855:855, idle factor 30%
        Error: Short-to-ground on drivers 0 1 2 3 4
        [ERROR] Error: Short-to-ground on drivers 0 1 2 3 4
        Error: Over temperature shutdown on drivers 0 1 2 3 4
        [ERROR] Error: Over temperature shutdown on drivers 0 1 2 3 4
        1 Reply Last reply Reply Quote 0
        1 out of 3
        • First post
          1/3
          Last post
        Unless otherwise noted, all forum content is licensed under CC-BY-SA