G28 X took too long to respond
-
I have got the X axis moving now via the other drivers which is strange, haven't done anything different than when I did this last time and got nothing!? No luck so far with anything on driver 0
-
@eegroeg said in G28 X took too long to respond:
Was going through the very basics and tried re configuring drivers again and looks like I'm getting nothing now from driver 0 now...
Well at least that makes more sense.
With the board being under warranty would this be able to be replaced?
I have no idea - you would have to ask @dc42 or @Phaedrux.
Frederick
-
-
@eegroeg said in G28 X took too long to respond:
@fcwilt Thank you for all your help. Yes thankfully thinks start to make a bit more sense I will get in touch with @dc42 to ask about the warranty.
Many thanks.
Sorry we couldn't actually fix the problem.
Frederick
-
I'll take a closer look through your thread later today.
-
Hi, please post the results of sending M122 and M98 P"config.g" in the gcode console.
When and where did you purchase your Duet?
Can you confirm what happens if you swap the X and Y steppers and drivers?
It sounds like now you get no errors or movement from driver 0?
Can you tell if the driver 0 chip is getting hot?
Can you get a photo of the board, particularly around driver 0? Do you notice any damage to the chip? Like a pock mark?
-
Please see M122 and M98 below. I purchased Duet a month or so ago, only just in the past week actually unpacked it and started to use it for my project. It was purchased from E3D.
When swapping the drivers now nothing happens and I get a G28 X too long to respond message with the warning that repeats several times until I reset the board or get the "Error: Homing failed" message:
Warning: motor phase A may be disconnected reported by driver(s) 0
Warning: motor phase B may be disconnected reported by driver(s) 0The chip doesn't seem to get hot and there are no marks
as far as I can see. (Please see photo attached.)
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-956L2-G43S8-6J9DG-3S46K-KV2LD Used output buffers: 1 of 40 (11 max) === RTOS === Static ram: 150904 Dynamic ram: 91852 of which 40 recycled Never used RAM 111396, free system stack 206 words Tasks: NETWORK(ready,29.9%,254) ETHERNET(notifyWait,0.1%,117) HEAT(delaying,0.0%,331) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.5%,93) MAIN(running,62.2%,1096) IDLE(ready,0.2%,29), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:01:08 ago, cause: power up Last software reset at 2021-07-10 18:45, reason: User, GCodes spinning, available RAM 108364, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 131 MCU temperature: min 27.7, current 39.3, max 39.4 Supply voltage: min 23.7, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, standstill, reads 52797, writes 14 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 52797, writes 14 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 52798, writes 14 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 52798, writes 14 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 52798, writes 14 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 52801, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2021-07-16 21:46:16 Slowest loop: 4.57ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 2.3ms, write time 0.0ms, max retries 0 === Move === DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP is ready with "M122 " 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages queued 615, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 343/0/0 Tx timeouts 0,0,342,0,0,271 last cancelled message type 4514 dest 127 === Network === Slowest loop: 4.37ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 1 of 8 - Ethernet - State: active Error counts: 0 0 0 0 0 Socket states: 5 2 2 2 2 0 0 0M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled
-
@eegroeg said in G28 X took too long to respond:
When swapping the drivers now nothing happens and I get a G28 X too long to respond message with the warning that repeats several times until I reset the board or get the "Error: Homing failed" message:
Warning: motor phase A may be disconnected reported by driver(s) 0
Warning: motor phase B may be disconnected reported by driver(s) 0Can you swap the X and Y motor plugs with each other and then send these commands to test movement. If you have the motors connected to belts it would be best to free them first.
G92 X100 Y100
G91
G1 X10
G1 Y10Do either motors move? Do you get any errors?
Trying to determine if the phase disconnected error is correct, which could just mean that a cable isn't making good contact. perhaps a bad crimp. We want to see if it will follow the motor or if it stays with the driver.
-
@phaedrux said in G28 X took too long to respond:
sorry for the delay, thanks for your response.
I tested all the above, no errors all commands are green.
The only command which had any movement was G1 Y10 so it seems nothing is happening from driver 0.
I’m happy to try anything else, please let me know what the next options are
-
It would seem that a driver has failed prematurely. Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
