Warning: Driver 0.3 warning: phase A/B may be disconnected
-
Unfortunately its still there.. And also after only the update - back up and format SD card i have some laying down first layer problems i need to address. And it looks like some extrusion problems with printing but not sure yet.
Connection interrupted it also a new one.Have to look in to it,
30-5-2024 22:52:37 Connection established 30-5-2024 22:52:37 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 30-5-2024 22:52:32 Warning: Driver 0.3 warning: phase A may be disconnected 30-5-2024 22:50:12 Warning: Driver 0.3 warning: phase B may be disconnected Warning: Driver 0.3 warning: phase A may be disconnected, phase B may be disconnected 30-5-2024 22:27:07 Connection established 30-5-2024 22:27:07 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 30-5-2024 22:27:04 Connection established 30-5-2024 22:27:04 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 30-5-2024 22:26:58 Warning: Driver 0.3 warning: phase B may be disconnected 30-5-2024 22:07:30 Warning: Driver 0.3 warning: phase B may be disconnected 30-5-2024 22:06:51 Connection established 30-5-2024 22:06:51 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 30-5-2024 22:06:46 Warning: Driver 0.3 warning: phase B may be disconnected Warning: Driver 0.3 warning: phase A may be disconnected, phase B may be disconnected 30-5-2024 22:03:42 Warning: Driver 0.3 warning: phase B may be disconnected 30-5-2024 21:14:47 Warning: Driver 0.3 warning: phase A may be disconnected -
The driver may be damaged. Have you tried a different driver assignment?
-
Well i switched 0.3 with 0.4. (extruder was 0.3 and now 0.4, one of the z motors is now on 0.3)
(can you double check old vs new if i did it correctly?)
So am i right to conclude there is something wrong with the steppenmotor of my E3D Hemera? @Phaedrux2-6-2024, 10:16:12 Warning: Driver 0.4 warning: phase B may be disconnected 2-6-2024, 09:59:06 Leadscrew adjustments made: -0.003 0.011, points used 2, (mean, deviation) before (0.004, 0.005) after (0.000, 0.000) 2-6-2024, 09:58:55 Leadscrew adjustments made: 0.115 0.070, points used 2, (mean, deviation) before (0.093, 0.016) after (0.000, 0.000) 2-6-2024, 09:58:08 File 0:/gcodes/corner_brace_3m_bolts_PETG_44m55s.gcode selected for printingNew
; Drives M569 P0.0 S0 ; physical drive 0.0 goes backwards M569 P0.1 S0 ; physical drive 0.1 goes backwards M569 P0.2 S0 ; physical drive 0.2 goes backwards (Z Axis Left) M569 P0.3 S0 ; physical drive 0.4 goes backwards (Z Axis Right) M569 P0.4 S0 ; physical drive 0.3 M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z800.00 E394.26 ; set steps per mm M566 X1200.00 Y1200.00 Z60.00 E3000.00 ; set maximum instantaneous speed changes (mm/min)(was X900.00 Y900.00 Z60.00(600) E120.00) M203 X5000.00 Y5000.00 Z180.00 E5000.00 ; set maximum speeds (mm/min)(was X6000.00 Y6000.00 Z180.00 E1200.00) M201 X1500.00 Y1500.00 Z20.00 E5000.00 ; set accelerations (mm/s^2)(was X500.00 Y500.00 Z20.00(80) E500.00) M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent(was X800 Y800 Z800 E800 I30) M84 S30 ; Set idle timeoutOld
; Drives M569 P0.0 S0 ; physical drive 0.0 goes backwards M569 P0.1 S0 ; physical drive 0.1 goes backwards M569 P0.2 S0 ; physical drive 0.2 goes backwards (Z Axis Left) M569 P0.3 S0 ; physical drive 0.3 goes backwards M569 P0.4 S0 ; physical drive 0.4 goes backwards (Z Axis Right) M584 X0.0 Y0.1 Z0.2:0.4 E0.3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z800.00 E394.26 ; set steps per mm M566 X1200.00 Y1200.00 Z60.00 E3000.00 ; set maximum instantaneous speed changes (mm/min)(was X900.00 Y900.00 Z60.00(600) E120.00) M203 X5000.00 Y5000.00 Z180.00 E5000.00 ; set maximum speeds (mm/min)(was X6000.00 Y6000.00 Z180.00 E1200.00) M201 X1500.00 Y1500.00 Z20.00 E5000.00 ; set accelerations (mm/s^2)(was X500.00 Y500.00 Z20.00(80) E500.00) M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent(was X800 Y800 Z800 E800 I30) M84 S30 ; Set idle timeoutextra information:
2-6-2024, 21:10:48 Finished printing file 0:/gcodes/blank_carriage_PETG_5h26m.gcode, print time was 6h 14m 2-6-2024, 20:51:29 Warning: Driver 0.4 warning: phase A may be disconnected, phase B may be disconnected 2-6-2024, 20:20:03 Warning: Driver 0.4 warning: phase A may be disconnected 2-6-2024, 19:48:10 Warning: Driver 0.4 warning: phase B may be disconnected 2-6-2024, 19:46:37 Warning: Driver 0.4 warning: phase B may be disconnected 2-6-2024, 19:44:45 Warning: Driver 0.4 warning: phase A may be disconnected 2-6-2024, 19:38:50 Warning: Driver 0.4 warning: phase A may be disconnected 2-6-2024, 19:29:59 m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus Ethernet (standalone mode) Board ID: 5QZRJ-6F6M2-G65J0-409FD-3Q81Z-72HAQ Used output buffers: 8 of 40 (40 max) === RTOS === Static ram: 103232 Dynamic ram: 116100 of which 12 recycled Never used RAM 18112, free system stack 122 words Tasks: NETWORK(1,ready,76.0%,180) ETHERNET(5,nWait 7,0.2%,567) HEAT(3,nWait 1,0.2%,326) Move(4,nWait 6,6.2%,237) CanReceiv(6,nWait 1,0.0%,940) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,2.6%,68) MAIN(1,running,12.2%,665) IDLE(0,ready,0.0%,30) AIN(4,delaying,2.7%,260), total 100.0% Owned mutexes: === Platform === Last reset 04:39:09 ago, cause: power up Last software reset at 2024-06-02 10:55, reason: User, Gcodes spinning, available RAM 18184, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,1,0 MCU revision 0, ADC conversions started 16749063, completed 16749063, timed out 0, errs 0 MCU temperature: min 24.8, current 47.6, max 47.9 Supply voltage: min 23.6, current 23.9, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/3, heap memory allocated/used/recyclable 2048/176/56, gc cycles 0 Events: 14 queued, 14 completed Driver 0: ok, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 29302, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 1: ok, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 29301, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 2: ok, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 29301, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 3: ok, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 29301, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 4: ok, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 29304, writes 12, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-06-02 15:47:29 Cache data hit count 4294967295 Slowest loop: 225.69ms; fastest: 0.13ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 4.9ms, write time 79.8ms, max retries 0 === Move === DMs created 83, segments created 46, maxWait 339966ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00 next step interrupt due in 174 ticks, enabled Moves shaped first try 36396, on retry 2560, too short 106922, wrong shape 35365, maybepossible 5431 === DDARing 0 === Scheduled moves 194886, completed 194876, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.4 Heater 1 is on, I-accum = 0.5 === GCodes === Movement locks held by null, null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is doing "G1 X108.786 Y129.904 E1.61464" 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 1, axes/extruders owned 0x0000807 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 150740, received 0, lost 0, errs 79636997, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 83746/0/0 Tx timeouts 0,0,83745,0,0,66993 last cancelled message type 30 dest 127 === Network === Slowest loop: 80.64ms; fastest: 0.03ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = Ethernet = Interface state: active Error counts: 0 0 0 0 0 0 Socket states: 5 2 2 2 2 0 0 0 -
@Jeronimo88 said in Warning: Driver 0.3 warning: phase A/B may be disconnected:
So am i right to conclude there is something wrong with the steppenmotor of my E3D Hemera?
So you switched the motor and wiring to driver 0.4 and the problem followed the motor? In that case it's either the wiring itself or the motors wiring internally.
-
@Phaedrux Indeed, and im on my second set of wiring and its still giving me errors on the extruder.
I will check if i can find a replacement motor for my E3D Hemera, perhaps ill mount the XS motor if its fits.What does seems "funny" that the errors don't screw up my prints.. So is there something i can "tweak" that its perhaps a bit less sensitive?
But i also get a lot of connection errors? Wondering if they are connected? I already did some searching and put my AJAX from 3 to 5. And when its done printing i will also update my Paneldue 7i to latest firmware.
See a small section of the errors now below, and thanks for coming back every time. Much appreciated.
3-6-2024 18:39:04 Connection established 3-6-2024 18:38:58 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 3-6-2024 18:38:55 Connection established 3-6-2024 18:38:55 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 3-6-2024 18:38:52 Connection established 3-6-2024 18:38:52 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 3-6-2024 18:38:49 Connection established 3-6-2024 18:38:49 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 3-6-2024 18:38:46 Connection established 3-6-2024 18:38:45 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 3-6-2024 18:38:42 Connection established 3-6-2024 18:38:42 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 3-6-2024 18:38:39 Connection established 3-6-2024 18:38:39 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 3-6-2024 18:38:36 Connection established 3-6-2024 18:38:36 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 3-6-2024 18:38:31 Warning: Driver 0.4 warning: phase A may be disconnected 3-6-2024 18:38:31 Warning: Driver 0.4 warning: phase A may be disconnected, phase B may be disconnected 3-6-2024 18:37:01 Warning: Driver 0.4 warning: phase A may be disconnected 3-6-2024 18:01:10 Warning: Driver 0.4 warning: phase A may be disconnected 3-6-2024 17:38:38 Warning: Driver 0.4 warning: phase A may be disconnected 3-6-2024 16:56:41 Leadscrew adjustments made: 0.003 0.019, points used 2, (mean, deviation) before (0.011, 0.006) after (-0.000, 0.000) 3-6-2024 16:56:29 Leadscrew adjustments made: 0.099 0.062, points used 2, (mean, deviation) before (0.081, 0.013) after (-0.000, 0.000) 3-6-2024 16:54:56 File 0:/gcodes/Rear_left_lower_PETG_6h10m.gcode selected for printing -
Do you have logging enabled? The increased activity can sometimes have unintended consequences.
Do you have a fresh SD card to test with? A failing SD card can cause seemingly random issues as well. -
@Phaedrux Ill will look for another SD, probably will find one.
~~I cant seem to find the log, or the option in the manual for DWC?Any pointers to find out/activate it?~~
I find something, ill look into it after my print is done with printing.
It was in the GCode dictionaryEDIT 2
Can i just add this to the end of my GCode? @Phaedrux
; Miscellaneous M501 ; load saved parameters from non-volatile memory M929 P"eventlog.txt" S1 ; start logging warnings to file eventlog.txt M929 P"eventlog.txt" S2 ; start logging Info to file eventlog.txt M929 P"eventlog.txt" S3 ; start logging DEBUG to file eventlog.txt -
I wasn't suggesting you enable logging, just asking if it was already in use. I don't think you're going to get anything useful out of it in this case.
-
Ah, i see/read what you ment. But then the answer is no, i have not enabled logging.
Do you know something about my question i asked earlier?"So is there something i can "tweak" so that it perhaps is a bit less sensitive?" and maybe doesn't give the errors? Because
its not affecting my prints. (As far i can tell). -
You can ignore it, but you can't prevent the warnings. Something is wrong with the connections to the motor coils, maybe intermittent.
Can you try with a temporary motor replacement just to determine if it's the motor itself or not? You don't need to run an actual print, just connect a motor and do a dry run.If the motor is failing and it's from E3D you may be able to get a replacement from them.
