Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Stuttering stepper motors and under voltage

    Duet Hardware and wiring
    2
    2
    607
    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.
    • JeroenZvZ
      JeroenZvZ last edited by

      Well,

      The stepper motors on my Kossel XL started stuttering and I did a M122. Could anyone point me to the culprit? I wonder if it are the drivers, a bad connection to the stepper motors or maybe the power supply connection (corsair sf450). Stepper motors are 2.4a and configured to 1.9a in the config.g. What steps can i follow to find out what the problem is? The board seems to be constantly powered as I don't see any leds flickering when the stuttering is there. Below my 122 results with the under voltage events that occurred:

      DuetWifi on 1.18, no paneldue attached, printing by uploading through the webinterface.

      Used output buffers: 1 of 32 (9 max)
      === Platform ===
      Static ram used: 20320
      Dynamic ram used: 72784
      Recycled dynamic ram: 1104
      Stack ram used: 968 current, 8104 maximum
      Never used ram: 28760
      Last reset 00:08:34 ago, cause: power up
      Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
      Spinning module during software reset: GCodes, available RAM 33336 bytes (slot 4)
      Error status: 0
      Free file entries: 8
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest block write time: 4.7ms
      MCU temperature: min 30.6, current 33.0, max 37.1
      Supply voltage: min 9.3, current 10.0, max 12.2, under voltage events: 11, over voltage events: 0
      Driver 0: stalled
      Driver 1: stalled
      Driver 2: stalled
      Driver 3: standstill
      Driver 4: standstill
      Date/time: 2017-08-10 00:36:04
      Slowest main loop (seconds): 0.082901; fastest: 0.000061
      === Move ===
      MaxReps: 3, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
      Scheduled moves: 1, 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 0 is on, I-accum = 0.8
      Heater 1 is on, I-accum = 0.4
      === GCodes ===
      Segments left: 0
      Stack records: 1 allocated, 1 in use
      Movement lock held by file
      http is idle in state(s) 0
      telnet is idle in state(s) 0
      file is idle in state(s) 1 0
      serial is idle 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
      Code queue is empty.
      === Network ===
      WiFiServer is running
      SPI underruns 0, overruns 0
      === Webserver ===
      HTTP sessions: 1 of 8

      1 Reply Last reply Reply Quote 0
      • dc42
        dc42 administrators last edited by

        The first thing to check is that the screws in the VIN terminal block are tight.

        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
        • First post
          Last post
        Unless otherwise noted, all forum content is licensed under CC-BY-SA