Internal stepper drivers form Duet WiFi are not responding
-
Hello everyone .
I was Trying to configure the board for CNC.
I went to configuration tool and made a clean setup . (trying to avoid manual cleaning of previous settings like BLtouch , Heaters, etc..)
Cleaned the old system files through DWC , loaded new ones on the board and did restart .
The Y and Z axis from the Expansion breakout board are working after I added them in config .g but ALL internal motor drivers stopped to work! I never had such a problem..
Only one X-Axis is connected to the DuetWifi driver .
All other drivers are free. They all (Except 4) worked before. Now I've tried them all and nothing...
What could happen?Already put exactly the same config.g as before..
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Mon Nov 16 2020 00:29:27 ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"M1" ; set printer name M669 ;K1 ; select Cartesian mode ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives ;M564 H0 S0 M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 M569 P4 R-1 ; physical drive 4 is dead .. M569 P5 R1 T2.5:2.5:5:5 S1 M569 P6 R1 T2.5:2.5:5:5 S1 M569 P7 R1 T2.5:2.5:5:5 S1 M584 X0 Y6:7 Z5 E3 ; set drive mapping M350 X16 Y16 Z16 E16 U16 I1 ; configure microstepping with interpolation M92 X80.00 Y170.00 Z5050 E820 ;U40.00 ; set steps per mm M566 X6000.00 Y1800.00 Z150.00 E800.00 ;U10500 ; set maximum instantaneous speed changes (mm/min) M203 X25000.00 Y20000.00 Z300.00 E1000.00 ;U15500 ; set maximum speeds (mm/min) M201 X13000.00 Y2000.00 Z500.00 E900 ;U3000 ; set accelerations (mm/s^2) M906 X1300 Y400 Z400 E260 ;U500 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X1010 Y790 Z500 S0 ; set axis maxima ; Endstops M574 X2 S1 P"!^xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"!^ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S1 P"!^zstop" ; configure active-high endstop for low end on Z via pin zstop ;M591 D0 P5 C"e0_stop" R70:100 L0.9 E15.0 S1 ; Z-Probe ;M307 H3 A-1 C-1 D-1 ;M558 P9 C"^zprobe.in" H5 F120 T6000 ;M950 S0 C"exp.heater3" ;Create a GPIO/Servo pin index using your chosen control pin ;G31 X-24 Y-1 Z0.85 P20 ;Set up the probe offsets, trigger height and trigger value in G31 ;M557 X40:440 Y65:470 S60 ; define mesh grid ; Heaters ;M308 S1 P"e0temp" Y"thermistor" T100000 B4415 C2.166385e-7 R4700 ; configure sensor 1 as thermistor on pin e0temp M308 S1 P"e0temp" Y"thermistor" T100000 B3950 ;M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ;M308 S2 P"e1temp" Y"thermistor" T100000 B3950 ; configure sensor 2 as PT1000 on pin e1temp ;M950 H2 C"e1heat" T2 ; create nozzle heater output on duex.e2heat and map it to sensor 2 ;M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Spindle ;M950 R0 C"exp.heater3" L12000 ; Create spindle index 0, with PWM pin on heater 3 and 12000 RPM achieved at full PWM ;M563 P1 S"Spindle 1" R0 ; Create tool 1 with spindle 0 and call it "Spindle 1" ; Fans M950 F0 C"fan0" Q100 ; create fan 0 on pin fan0 and set its frequency M106 P0 S1 R1 L15 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"Fan1" Q3300 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 L1 B0.1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P2 S1 R1 L255 H1 ; Tools M563 P0 S"Left" D0 H1 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 S"Right" D1:2 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue T0 ; select first tool M501The diagnostic doesn't show nothing special :
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later Used output buffers: 3 of 24 (11 max) === RTOS === Static ram: 23876 Dynamic ram: 74952 of which 0 recycled Never used RAM 15588, free system stack 184 words Tasks: NETWORK(ready,5.3%,237) HEAT(delaying,0.0%,238) Move(notifyWait,0.1%,340) MAIN(running,89.2%,445) IDLE(ready,5.5%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:16 ago, cause: software Last software reset at 2021-10-24 11:06, reason: User, GCodes spinning, available RAM 12556, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 34.9, current 35.4, max 35.7 Supply voltage: min 11.9, current 11.9, max 12.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-10-24 11:06:57 Cache data hit count 1172618336 Slowest loop: 5.09ms; fastest: 0.19ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 2.2ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 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 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 16.23ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address cc:50:e3:6a:87:1e WiFi Vcc 3.35, reset reason Turned on by main processor WiFi flash size 4194304, free heap 27168 WiFi IP address 192.168.43.48 WiFi signal strength -65dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0Driver 4 are removed long time ago. And day before machine was working .
I connected the board via Yat, because no panelDue and I couldn't connect through DWC after RRF Config loading. While connecting through USB for the WiFi setup the Expansion breakout board and external drivers was connected to duet.. -
There is nothing criminal in this.. It couldn't cause destroying the internal drivers..
I believe =\Should I try Factory Reset - Erase ..?
-
@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!
