Internal stepper drivers form Duet WiFi are not responding
-
@allsirius said in Internal stepper drivers form Duet WiFi are not responding:
M350 X16 Y16 Z16 E16 U16 I1
I don't know whether this causes your problem, but you still use an undefined U in M350, and M669 without parameters.
You can call M98 P"config.g" to test for syntax errors. -
@joergs5
Thanks' for pointing out, i'll check it,
but I pasted the MicroSd card to another Duet and it was working.. -
@allsirius maybe some problem with the external drivers then (sharing ground or not sharing ground signal and power? => depends on whether they are optocoupled). Anyway, I would disconnect everything from the Duet and test every driver isolated to see whether they are damaged. (I always make an image before pulling all wires...)
-
@joergs5
Already ! Naked duet connected to 12v and only few steppers, m564 s0 h0, movements on DWC , and quiet motors.. =/ -
@allsirius you can use G1 H2 also, it also ignores any homing and limits, and addresses the individual axes.
G1 H2 X100 uses only the first axis/actuator, even if coupled by kinematics like CoreXY.
Sorry to hear quiet, if you mean they don't move at all.Are you sure the steppers are ok, which you connect? (Duet would probably report an error, but as last idea...)
-
@allsirius do you have some measuring equipment, like a voltmeter? Maybe some fuse is defect. Another thing to check is whether there are burned elements on the board.
One more thing I saw was, in your M122 report were no movements, so there will be no stepper data also. Please try some movements first (like G1 H2 X, Y, Z ones), with drives connected and mapped with M584, then make a M122. The M122 may include some better report data in the Driver lines then.
-
@AllSirius what firmware version were you running before? There was an issue where if a driver had been damaged/ removed from the board then in 3.3 all the drivers wont startup.
This was fixed in 3.4b5:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta-&-RC#reprapfirmware-340beta5
[Duet 2 WiFi/Ethernet] If a TMC2660 driver was removed from the Duet or Duex then none of the TMC2660 drivers would start up
you may want to upgrade to 3.4b5 to see if that resolved the driver issue.
-
@allsirius said in Internal stepper drivers form Duet WiFi are not responding:
M669 ;K1 ; select Cartesian mode
I bet my money on the FW version, like Tony mentioned. But this line above has a semikolon (at the wrong place)
-
-
@allsirius that are good news!!!
You are the King Man!
