Duet Wifi Motors wont work after update to RRF3
-
Hi I am new to this community and after many hours of trying to fix my problem on my own I landed here to ask for your expertise:
I upgraded to RRF3 lately and cant get my Motors to work. Maybe its an obvious problem but i cant figure it out.
Here is my config file:
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 02 2021 20:27:45 GMT+0100 (Mitteleuropäische Normalzeit); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Angryprint V2" ; set printer name
M669 K1 ; select CoreXY mode; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; --- z-axis stepper leveling configuration ---
M671 X-50:-50:370:370 Y330:-65:-65:330 S20 ; Z belts at 4 corners; --- drive map ---
; _______
; | 6 | 7 |
; | ----- |
; | 5 | 8 |
; -------
; frontDrives
M569 P0 S1 ; X goes forwards
M569 P1 S1 ; Y goes forwards
M569 P2 R-1
M569 P3 S1 ; Extruder goes forwards
M569 P4 R-1
M569 P5 S1 ; Z1 goes forwards
M569 P6 S0 ; Z2 goes backwards
M569 P7 S1 ; Z3 goes forwards
M569 P8 S0
M569 P9 R-1M584 X0 Y1 E3 Z6:5:8:7 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80 Y80 Z400 E716 ; set steps per mm
M566 X900.00 Y900.00 Z20.00 E1000 ; set maximum instantaneous speed changes (mm/min)
M203 X20000.00 Y20000.00 Z1000.00 E3600.00 ; set maximum speeds (mm/min)
M201 X2500.00 Y2500.00 Z500.00 E1800.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E500 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X5 Y-5 Z0 S1 ; set axis minima
M208 X310 Y308 Z410 S0 ; set axis maxima; Endstops
M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop; Z-Probe
M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
M558 P9 C"^zprobe.in" H5 F600 T9000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y21 Z1.95 ; set Z probe trigger value, offset and trigger height
M557 X10:300 Y21:300 S55 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S130 ; set temperature limit for heater 0 to 130C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
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 S320 ; set temperature limit for heater 1 to 320C
M308 S2 P"e1temp" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2 ; create chamber heater output on e1heat and map it to sensor 2
M307 H2 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
M141 H2 ; map chamber to heater 2
M143 H2 S60 ; set temperature limit for heater 2 to 60C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1:2 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q0 ; create fan 2 on pin fan2 and set its frequency
M950 F3 C"duex.fan7" Q500
M950 F4 C"duex.fan8" Q500
M106 P1 S1 H1:2 T45; --LED--
M950 P5 C"duex.fan4" Q500
M42 P5 S255
M950 P6 C"duex.fan5" Q500
M42 P6 S255
M950 P7 C"duex.fan6" Q500
M42 P7 S255; Tools
M563 P0 S"Mosquito" D0 H1 F0 ; 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; Custom settings
; --- z-axis stepper leveling configuration ---
M671 X-50:-50:370:370 Y330:-65:-65:330 S20 ; Z belts at 4 corners; --- drive map ---
; _______
; | 6 | 7 |
; | ----- |
; | 5 | 8 |
; -------
; front; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first toolThe Error:
Warning: motor phase A may be disconnected reported by driver(s) 0 1
Warning: motor phase B may be disconnected reported by driver(s) 0 1Can someone help me?
-
Hi,
One thing you may find helpful is to execute from the DWC console M98 P"config.g".
This will display any status messages of interest including error messages that you won't see during power on.
Also what firmware version are you running?
Frederick
-
Hi Frederick,
thank you for this hint. I'm currently running RRF 3.2.2 but I upgraded to 3.0 first
Andi
-
@AndiG85 said in Duet Wifi Motors wont work after update to RRF3:
Warning: motor phase A may be disconnected reported by driver(s) 0 1
Warning: motor phase B may be disconnected reported by driver(s) 0 1Well that error would indicate that there may be a bad connection on drivers 0 and 1. So double check your wiring.
As a quick test you could connect the motors from another axis, like 2 of the Z motors to X and Y and see if it gives the same error. If it does, that may mean the problem is with the driver itself.
Can you also provide the results of sending M122?
Were you up and running before updating to RRF3?
-
Before the update it was running just fine on 2.05
I didn't touch anything of the wiring at all
I just tried to plug in 2 of the z-motos into X and Y but the problem remains the same.
M122.txt -
4.3.2021, 07:04:53 Warning: motor phase A may be disconnected reported by driver(s) 0 1
Warning: motor phase B may be disconnected reported by driver(s) 0 1
4.3.2021, 07:04:49 Warning: motor phase A may be disconnected reported by driver(s) 0 1
Warning: motor phase B may be disconnected reported by driver(s) 0 1
4.3.2021, 07:04:45 Warning: motor phase A may be disconnected reported by driver(s) 0 1
Warning: motor phase B may be disconnected reported by driver(s) 0 1
4.3.2021, 07:04:41 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DJM-9178L-L4MSN-6JKF4-3SJ6Q-1932R
Used output buffers: 1 of 24 (24 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 74488 of which 60 recycled
Never used RAM 14072, free system stack 119 words
Tasks: NETWORK(ready,180) HEAT(blocked,308) DUEX(blocked,31) MAIN(running,451) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:31 ago, cause: power up
Last software reset at 2021-03-03 21:49, reason: User, GCodes spinning, available RAM 13996, 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
MCU temperature: min 28.2, current 29.1, max 29.2
Supply voltage: min 24.0, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, open-load-A, open-load-B, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 2000, temperature-shutdown! short-to-ground, 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, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-03-04 07:04:41
Cache data hit count 22518687
Slowest loop: 13.92ms; fastest: 0.29ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 25368ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 2, completed moves 1, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = 2 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by HTTP
HTTP is idle in state(s) 1 8, running macro
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: 201.99ms; fastest: 0.09ms
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 1
WiFi firmware version 1.23
WiFi MAC address c8:2b:96:00:73:b7
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 4194304, free heap 25272
WiFi IP address 192.168.1.62
WiFi signal strength -51dBm, mode none, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 0, 0.00 reads/min
- WiFi -
-
@AndiG85 said in Duet Wifi Motors wont work after update to RRF3:
Driver 0: position 0, open-load-A, open-load-B, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 2000, temperature-shutdown! short-to-ground, 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, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not availableWell that's a pretty good range of errors in there. If you're really sure it has nothing to do with wiring and nothing other than the firmware update has happened you could simply try to revert back to the previous firmware version.
If you still have access to DWC. Upload the zip file for 2.05.1 in the system tab. Don't extract it first. Reboot after. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
If you still have your config.g from RRF2 you can upload that as well.
If the errors are now resolved that would be an interesting result. You could then try updating to 3.0 and then 3.2.2 again by uploading those zip files in the same way and see what happens.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
-
Ok..
I went back to 2.05 and everything was fine again.
I updated to 3.0 and now it works.
It is the same config file.Thank You very much for your help
Andi
-
Did you update to 3.2.2 as well?
-
Hello Everyone,
are there any news on this topic?
I have the exact same problem with my duet 2 with CustomDuex attached, and I'm getting the same errors regarding the steppermotors.
Everything works fine with 2.05. After editing the Config.g for the new conditions of RRF3 it works with 3.0 aswell. But everything after 3.0 doesn't work.
Best regards,
Basti -
@kaot93 please explain exactly what you mean by "same errors" and "doesn't work", and post your config.g file.
-
