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

    Sudden Issue with Driver 1, but Can't move any Axis

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    2
    100
    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.
    • CCS86undefined
      CCS86
      last edited by

      Yesterday I got my new Maestro board online and driving my printer around. Everything worked beautifully. All axes driven correctly, endstops, heater and fans all running smoothly.

      When I powered it up today, everything seemed fine, but when I tried to home all axes, it just sat there. Eventually, I got a "homing failed" error, which seems to just be a timeout.

      I did some more digging and found a string of "Error: over temperature shutdown reported by driver(s) 1" in the console.

      When I give an M122 command, the following section seems to confirm an issue with driver 1:

      MCU temperature: min 27.8, current 38.6, max 39.2
      Supply voltage: min 0.0, current 23.0, max 23.1, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 9799
      Driver 1: standstill, read errors 0, write errors 0, ifcount 6, reads 9793, timeouts 0
      Driver 2: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 9798
      Driver 3: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 9798
      Driver 4: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 9798
      Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 9798
      Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 9798
      

      I am trying to disable driver 1, which I believe is Y axis by default, with the following config edit:

      ; Drives
      M569 P0 S1                   ; physical drive 0 goes forwards
      M569 P1 R-1  ;S0         ; physical drive 1 goes backwards
      M569 P2 S0                  ; physical drive 2 goes backwards
      M569 P3 S1                  ; physical drive 3 goes forwards
      M584 X0 Y4 Z2 E3         ; set drive mapping
      

      But I still can't move any axis, and the M122 report looks the same. It seems like a replacement board is in my future, but I'd love to find a configuration workaround that lets me get some more testing done.

      Thanks!

      droftartsundefined 1 Reply Last reply Reply Quote 0
      • droftartsundefined
        droftarts administrators @CCS86
        last edited by

        @CCS86 I'd guess this is an SPI issue, judging by all the driver timeouts, but I'm not sure. One for @dc42 ?
        Can you post your full config.g, and a full M122? And your homeall.g.

        Ian

        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

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