"Error: short-to-ground reported by driver(s) 3"
-
Thanks for proving such complete troubleshooting.
Can you provide one last thing? The results of M122 and M98 P"config.g"
When and where did you purchase the Duet 3?
Do you see any visible damage to the driver chip itself?
-
@phaedrux said in "Error: short-to-ground reported by driver(s) 3":
M122
Thanks @Phaedrux
I purchased the duet 3 from https://aurarum.com.au/ the Australian reseller on the 26 March 2021.
I can't see any visible damage on the driver chip.
M122
11/04/2021, 11:41:10 Error: short-to-ground reported by driver(s) 3 11/04/2021, 11:41:06 Error: short-to-ground reported by driver(s) 3 11/04/2021, 11:41:03 m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-956L2-G43S8-6JKD0-3S46K-9U2YD Used output buffers: 3 of 40 (22 max) === RTOS === Static ram: 149788 Dynamic ram: 92972 of which 92 recycled Never used RAM 115980, free system stack 122 words Tasks: NETWORK(ready,169) ETHERNET(blocked,110) HEAT(blocked,297) CanReceiv(blocked,927) CanSender(blocked,352) CanClock(blocked,352) TMC(blocked,17) MAIN(running,1119) IDLE(ready,19) Owned mutexes: === Platform === Last reset 00:08:22 ago, cause: power up Last software reset at 2021-04-11 11:30, reason: User, GCodes spinning, available RAM 116064, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 36.2, current 38.3, max 38.3 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Driver 0: position 0, standstill, reads 42148, writes 8 timeouts 0, SG min/max not available Driver 1: position 0, standstill, reads 42149, writes 7 timeouts 0, SG min/max not available Driver 2: position 4096, standstill, reads 42150, writes 7 timeouts 0, SG min/max not available Driver 3: position 0, short-to-ground, standstill, reads 42146, writes 11 timeouts 0, SG min/max 0/70 Driver 4: position 0, standstill, reads 42156, writes 0 timeouts 0, SG min/max not available Driver 5: position 0, standstill, reads 42156, writes 0 timeouts 0, SG min/max not available Date/time: 2021-04-11 11:41:00 Slowest loop: 23.13ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 20.9ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 396543ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 17, completed moves 17, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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 = 0 -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 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 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. === Network === Slowest loop: 2.27ms; 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: 2 of 8 - Ethernet - State: active Error counts: 0 0 1 0 0 Socket states: 5 2 2 2 2 0 0 0 === CAN === Messages queued 1327, send timeouts 2986, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48M98 P"config.g"
11/04/2021, 11:40:14 M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset. Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 538CCheers
P
-
Please contact your vendor and initiate a warranty exchange. Include a link to this thread as authorization.
-
@phaedrux Thank you phaedrux
-
@phaedrux
Hi phaedrux,I contacted my reseller and they asked me to complete the following link https://docs.google.com/forms/d/e/1FAIpQLSdXpbRCNxUc2j_OePtuWdwyKPJ9VEg2Ohq_80f-VCZ4SCJJ9w/viewform (which I have now completed)
Is this something that needs to be processed on your end?
Cheers
P -
Nothing on my end personally no. Your reseller should take it from here.
-
@phaedrux
Hi Phaedrux, my reseller said they are awaiting your approval through that submitted google form. I provided them with this forum link, and they still said they needed duet3d’s approval. See below————
Hi Paul,yes - it should be ok. I think we still have them in stock.
just need to wait to hear from DuetKind regards,
Aurarum TeamIf you like our products/service and if you don't mind we would appreciate your feedback on Facebook and Google
https://g.page/Aurarum/review?rc——-
Create something “
Cheers
P
-
Thanks for bringing that to our attention. We'll get that tightened up. Thanks for your patience.
-
@phaedrux
Hi, I think I have a similar problem, but in my case all the wires are ok. When printing the model, the printer resets more or less on the 4th or 5th layer. I made 15 tries with the same effect. My aim is that the code contained in the line "software reset code" is the same as in the case of my colleague. Could you please help me, I am trying to find out what is causing the whole week but to no avail.
Sorry for screen shot but i can't download m122 comand from console.... when i click "download txt or csv" nothing do.
-
@kevvv Can I ask that you create a new thread for your issue?
You can also highlight, copy, and paste the text from the M122 report into the forum post.
-
undefined Kevvv referenced this topic
