@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'
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
i tried to print this, and nothing came out...
i didnt cut any traces,. and works fine
is it possible this is the same issue the other guy had?
do you have a 10 pin connector hooked up to an LCD?
so glad you got it sorted, sounds like your super lucky you didnt take any thing out, sounds like a dead short caused by the wrong connection was your issue 
@aimrabbit something is seriously broken, unless your PSU is WAY underpowered. i can power my i7 from USB..... meaning it doesnt take that much power,
was it miswired?
M106 P0 S0 I0 F500 H-1
try this, this is what my part fan looks like.
your unrelated:
according to: https://duet3d.dozuki.com/Wiki/Gcode#Section_M106_Fan_On
the H1:2 sets thermostatic control for that fan, for heater 1 and 2
so, fan 2 (p2) S1 (100%) l0 (can go to zero speed) F500 (pwm frequency 500) H1:2 controled by heaters 1 and 2 t45 (when either heater over 45)
i just realized ... thats your name silk screened on this duex5 isnt it ....
thats freaking amazing customer service if the lead product engineer is trouble shooting things for customers.
What, you mean your not my dedicated servant??!!!
no worries, absolutely appreciate your help
now to get my Duex5 RMA'd
Not shocked at the suspicion of a failed duex, it was mine from the get go, supplier asked that i open a thread and get a response from you guys to validate the claim for RMA
thanks for reviewing and confirming.
i see you are rather knowledgeable on the duet / duex products, Have you got any input on this one? im a bit at a loss where to go.
Kind of starting to regret my decisions to go this route. -- expensive learning experience so far.
recap: hardware: duet wifi + duex 5 + paneldue 7i
currently i have all fans working as intended, 3 PWM fans on the Duet, one thermostatically controlled hotend cooler
one tool fan
one thermostatically controlled MCU fan
x and y are in original intended motor drivers and work fine
z i want on drivers 8 and 9, eventually will be 7 8 9 when i finish my coreXY with tripple z screws.
BL touch is using PWM 5 on the Duex and prob connector on duet, as described here: https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/
and surprizingly it actually works, while i cannot get the motor drivers on the duex to work
setting the motor drivers for z to 2:4 works fine.
also noticed last night, one of the endstop LEDs on the duex is permanantly on but super dim, i want to say it was stop 5?
under this chip
are these solder pads
wonder if there is just a bad solder job causing it?
don't hesitate, I'm not immune to mistakes 
in this instance though yes, i have them correct, reverse polarity as compared to the duet due to the design for back to back fitment , if there is any thing working IT and as a network engineer has taught me, check, recheck, check again, and recheck one more time before you plug that thing in, mistakes are bad
when i get home i can take a picture for more clarification if needed.
I will double check the endstop...
As to the guage of the wire, i do not recall the guage off hand, i can confirm when i get home
its thicker copper core than standard house wiring though, really beefy, probably 14, if not 12 ga.
output from settings -> general:
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.03beta2 (2019-02-16b1)
WiFi Server Version: 1.23beta1
Web Interface Version: 1.22.6
yes, i have a solid core wire, as short as humanly possible, with the duet / duex side by side for testing
I presume by the lack of input i either didnt post enough information, or no one has a clue?
help!
my Duex5 seems to not be working well
i have been able to use PWM5 for my bltouch, that part works, but the motors are not working
here is the config that does not drive the motors: 0_1551926112738_config -- Does not work.g
here is a config that drives the motors using driver 2 and 4 0_1551926117314_config -- works.g
the truly concerning part for me is the lack of seeing the duex in M115
7:36:21 PM M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03beta2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-02-16b1
output of m122 with every thing but the BL touch on the duet:
7:37:29 PM=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03beta2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS4-6JTDA-3S06S-T8ZHA
Used output buffers: 3 of 20 (15 max)
=== RTOS ===
Static ram: 25532
Dynamic ram: 91720 of which 0 recycled
Exception stack ram used: 360
Never used ram: 13460
Tasks: NETWORK(ready,544) HEAT(blocked,1236) MAIN(running,3784) IDLE(ready,196)
Owned mutexes:
=== Platform ===
Last reset 00:05:55 ago, cause: software
Last software reset at 2019-03-06 19:31, reason: User, spinning module GCodes, available RAM 13492 bytes (slot 3)
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 37.7, current 38.0, max 38.1
Supply voltage: min 12.0, current 12.0, max 12.1, 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
Date/time: 1970-01-01 00:00:00
Cache data hit count 1291325566
Slowest loop: 1.11ms; 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: 5, completed moves: 5
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: 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 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: 202.16ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
and with motor drivers 8 and 9
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03beta2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS4-6JTDA-3S06S-T8ZHA
Used output buffers: 3 of 20 (6 max)
=== RTOS ===
Static ram: 25532
Dynamic ram: 91720 of which 0 recycled
Exception stack ram used: 328
Never used ram: 13492
Tasks: NETWORK(ready,544) HEAT(blocked,1236) MAIN(running,3792) IDLE(ready,196)
Owned mutexes:
=== Platform ===
Last reset 00:00:15 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 13460 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 37.9, current 38.6, max 38.7
Supply voltage: min 12.0, current 12.0, max 12.1, 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
Date/time: 2019-03-06 19:38:52
Cache data hit count 44553741
Slowest loop: 3.67ms; fastest: 0.07ms
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: 0, completed moves: 0
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: 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 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: 15.54ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8