Duet Wifi Motors wont work after update to RRF3
-
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.
-
