Duex5 drivers dont appear to be applying full current...



  • build: 300x300x350 CoreXY, Duet + Duex 5 + PanelDUE

    duet and Duex connected by standard 30 pin, plus a 4" jumper main power wire to connect the + and - primary power blocks.

    So the other day i noticed something was just 'not right' with my z axis, which is a triple screw, and was driven by drivers 7 8 9 on duex5

    and the x y and E were driven by the stock drivers on the duet.

    x y and e were moving fine, no problems, for sure had no issues with torque, but i noticed that the z was missing steps, not holding torque, and i came to realize that just lightly pressing my finger on the screws, even when active was enough to halt movement, or cause movement when it was holding.

    moved the z axis motors to the DUET X Y Z drivers, and now my Z axis is primo, at 1.5A has enough force that i fear for the safety of my hot end, but, now my X Y axis are useless and struggle to even home when driven off drivers 8/9

    wondering if there was an issue getting power down that far i moved to driver

    but i am at a loss as to why there is no power on the duex drivers...
    config.g driver settings
    ; Drives
    M569 P0 S0 ; z1
    M569 P1 S0 ; z2
    M569 P2 S0 ; z3
    M569 P3 S1 ; E1
    M569 P5 S0 ; X
    M569 P6 S0 ; Y

    M584 X5 Y6 Z0:1:2 ; x, y and Z definitiions

    M350 X16 Y16 E16 Z16 I0 ; Configure microstepping with interpolation
    M92 X80.00 Y80.00 Z400.00 E415 ; Set steps per mm
    M566 X900.00 Y900.00 Z10.00 E1200.00 ; Set maximum instantaneous speed changes (mm/min)
    M203 X6000.00 Y6000.00 Z400.00 E6000.00 ; Set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z800.00 E1500.00 ; Set accelerations (mm/s^2)
    M906 X1000.00 Y1000.00 Z1700.00 E340.00 I60 ; Set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    M122 output:

    4/21/2019, 8:09:50 PM: M122: === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03beta2 running on Duet WiFi 1.02 or later + DueX5
    Board ID: 08DGM-917DA-G4MS4-6JTDA-3S06S-T8ZHA
    Used output buffers: 3 of 20 (16 max)
    === RTOS ===
    Static ram: 25532
    Dynamic ram: 91736 of which 440 recycled
    Exception stack ram used: 508
    Never used ram: 12856
    Tasks: NETWORK(ready,560) HEAT(blocked,1236) MAIN(running,3848) IDLE(ready,196)
    Owned mutexes:
    === Platform ===
    Last reset 07:18:13 ago, cause: software
    Last software reset at 2019-04-21 12:51, reason: User, spinning module GCodes, available RAM 12880 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 35.9, current 36.3, max 36.6
    Supply voltage: min 24.3, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Driver 5: standstill, SG min/max not available
    Driver 6: standstill, SG min/max not available
    Driver 7: standstill, SG min/max not available
    Driver 8: standstill, SG min/max not available
    Driver 9: standstill, SG min/max not available
    Date/time: 2019-04-21 20:09:47
    Cache data hit count 4294967295
    Slowest loop: 5.93ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 40, completed moves: 40
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 2 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 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
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 200.49ms; fastest: 0.08ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 1
      WiFi firmware version 1.23beta1

  • administrators

    Go to the GCodes wiki page, look up the entry for M584, and read the bit that starts with "Very important!". Acting on that will solve the problem.



  • @dc42 said in Duex5 drivers dont appear to be applying full current...:

    M584

    Roger! fixed! so my failure to explicitly define E in the M584 basically caused an incomplete build of the motor definitiions, for lack of a better description thus things were just not 'right'


  • administrators

    The reason was that your E motor current setting was being applied to those drivers, because they were configured as both extruder motor and axis motor drivers.


Log in to reply