Drivers error short to ground - Multiple

ZakariahMT

Hi,

I have a Modix Big 60 V3 with the Duet2wifi and Duex board which has been working great for the last 8 months. I came into my workshop today and the clog detector had done its job and paused the printer because of a bump in the filament which had caused it to not feed. After clearing out the extruder and hitting resume i had a Event Notification appear "Driver 1 error: phase B short to ground". I've had this happen before and checked the wiring, connectors and motor but all looked good. I checked for continuity on the cable and it also passed.

I did a M122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S4-6J9D8-3S86P-TB1UL
Used output buffers: 1 of 26 (24 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 75440 of which 12 recycled
Never used RAM 9864, free system stack 120 words
Tasks: NETWORK(notifyWait,14.6%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,294) MAIN(running,85.4%,438) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:14:26 ago, cause: software
Last software reset at 2023-11-12 18:18, reason: User, GCodes spinning, available RAM 10008, slot 2
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
Step timer max interval 0
MCU temperature: min 38.7, current 40.4, max 40.9
Supply voltage: min 24.0, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/7, heap memory allocated/used/recyclable 2048/114/4, gc cycles 0
Events: 4 queued, 4 completed
Driver 0: ok, SG min 640
Driver 1: ok, SG min 640
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-11-12 18:32:45
Cache data hit count 4294967295
Slowest loop: 11.96ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 209747ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 9, completed 9, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no data received
=== Network ===
Slowest loop: 99.88ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 2
WiFi firmware version 1.27
WiFi MAC address c8:c9:a3:40:91:32
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 25712
WiFi IP address 192.168.0.224
WiFi signal strength -40dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

and there was also no faults for the drivers but whenever i tried to G28 i would continually get the same event notification. My next plan of attack was to remap that stepper to E1

; Drives_________________________________________________________________________
;Main board______________________________________________________________________
M569 P0 S0 ; Physical drive 0. X1
M569 P1 S1 ; Physical drive 1. X2
M569 P2 R-1 ; Physical drive 2. Disabled
M569 P3 S0 ; Physical drive 3. Primary Extruder
M569 P4 S0 ; Physical drive 4. Secondary Extruder
;Duex5 board_____________________________________________________________________
M569 P5 S0 ; Physical drive 5 . Y
M569 P6 S0 ; Physical drive 6 . Z1 (0,600)
M569 P7 S0 ; Physical drive 7 . Z2 (0,0)
M569 P8 S0 ; Physical drive 8 . Z3 (600,0)
M569 P9 S0 ; Physical drive 9 . Z4 (600,600)

;Motor to stepper motor driver mapping_________________________________________________________
M584 X0:1 Y5 Z6:7:8:9 E3:4 P3 ; Driver mapping
M671 X-185:-185:668:668 Y668:-46:-46:668 S30 ; Anticlockwise

So i went through and did the change and moved the wiring, at this stage i could now home the X axis but now i was getting "Driver 5 error: phase A short to ground". I then went through and checked all the same stuff for the driver and then moved it to driver 2. After then doing that i got Driver 3 error: phase A short to ground"

I've moved pretty much all the drivers around and it seems a new one seems to have a fault. I have also tried each driver (Excluding the Z Mapped) with a new cable and stepper driver as i have 3 Big60 printers and always have spares except for a motherboard...

Any help or guidance would appreciated.

dc42

@ZakariahMT check the ground connection between the Duet VIN ground terminal and the DueX VIN ground terminal (in particular, check that the terminal block screws are still tight), and check the 50-way ribbon cable between those two boards. It sounds to me that the SPI communication between the Duet and DueX is either intermittent or subject to interference. Failed communication can result in spurious short-to-ground and other error reports.

ZakariahMT

@dc42 Hey,

I've removed them and then reinserted both of them, the screws had a little give but weren't loose. After checking those and doing another home i still get the same event notification.

ZakariahMT

@dc42

Also maybe related but i just noticed that i get get these two Errors in the console on the printer.

Phaedrux

that looks like a comment that isn't commented out. You should be able to find that text using a text editor and make sure it's properly commented with a ;

ZakariahMT

@Phaedrux In the config.g?

Phaedrux

That depends. If you've got other macros called from config.g it could be in those too if that's right after power up.

ZakariahMT

@Phaedrux i've compared my config.g to a new one from modix using Notepad++ and noting looks out of the ordinary. I have no idea why it would be stating in the console on start up the error bad command. I have ; out the clog detector line on the config.g and physically removed it from the printer but it still comes up with the error.

Phaedrux

Are there any M98 P commands in your config.g that would be calling other macros?

ZakariahMT

@Phaedrux said in Drivers error short to ground - Multiple:

M98 P

M98 P"PID_tune_E1.g" R1 ; PID calibration
M98 P"config_networking.g" ; load networking settings
G4 P300 ; wait 300ms
"confM98 Pig_probe.g" ; Load the Z-offset from the config_probe.g file

Just those listed above

ZakariahMT

@Phaedrux @dc42

I ordered a new motherboard, Duet2 Wifi 1.05 and have installed that. I'm still getting the same event notifications

Phaedrux

Please share your files.

ZakariahMT

This post is deleted!

ZakariahMT

@Phaedrux

https://drive.google.com/drive/folders/1WLIpfyeUcX1bzfJ1XoEwUPUMuUCRHnSZ?usp=sharing

dc42

@ZakariahMT another possibility is that the VIN supply to the Duet is dropping. After power up, run M122 to clear the recorded minimum VIN voltage. Then after a driver error is reported, run M122 again and post the output here.

droftarts

@ZakariahMT said in Drivers error short to ground - Multiple:

"confM98 Pig_probe.g" ; Load the Z-offset from the config_probe.g file

Is that how it looks in config.g? It should be

M98 P"config_probe.g"

Ian

droftarts

@ZakariahMT said in Drivers error short to ground - Multiple:

https://drive.google.com/drive/folders/1WLIpfyeUcX1bzfJ1XoEwUPUMuUCRHnSZ?usp=sharing

There’s no config.g in that file set?

Ian

ZakariahMT

@dc42
M122 straight after power on and before home axis
14/11/2023, 17:59:09 m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 0JD2M-9F8TA-GJ4TD-6J9FA-3SN6T-K7QA4
Used output buffers: 7 of 26 (18 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 75368 of which 12 recycled
Never used RAM 10008, free system stack 184 words
Tasks: NETWORK(ready,11.9%,242) HEAT(notifyWait,0.0%,337) Move(notifyWait,0.0%,363) MAIN(running,84.1%,458) IDLE(ready,3.9%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:27 ago, cause: power up
Last software reset at 2023-11-14 17:11, reason: User, GCodes spinning, available RAM 10008, slot 2
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
Step timer max interval 0
MCU temperature: min 33.6, current 35.5, max 35.8
Supply voltage: min 23.7, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/7, heap memory allocated/used/recyclable 2048/114/4, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-11-14 17:59:08
Cache data hit count 1034103519
Slowest loop: 7.38ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 9.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no data received
=== Network ===
Slowest loop: 12.41ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address a4:e5:7c:03:b4:46
WiFi Vcc 3.41, reset reason Power up
WiFi flash size 2097152, free heap 23984
WiFi IP address 192.168.0.53
WiFi signal strength -47dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

M122 after home axis
14/11/2023, 18:02:29 m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 0JD2M-9F8TA-GJ4TD-6J9FA-3SN6T-K7QA4
Used output buffers: 8 of 26 (24 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 75440 of which 12 recycled
Never used RAM 9864, free system stack 120 words
Tasks: NETWORK(ready,14.1%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,304) MAIN(running,85.9%,458) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:47 ago, cause: power up
Last software reset at 2023-11-14 17:11, reason: User, GCodes spinning, available RAM 10008, slot 2
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
Step timer max interval 0
MCU temperature: min 35.1, current 36.0, max 36.1
Supply voltage: min 23.6, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/7, heap memory allocated/used/recyclable 2048/114/4, gc cycles 0
Events: 3 queued, 3 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-11-14 18:02:28
Cache data hit count 4294967295
Slowest loop: 11.99ms; fastest: 0.17ms
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 0.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 85625ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 11, completed 10, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by HTTP
HTTP is idle in state(s) 2 15, 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
=== Filament sensors ===
Extruder 0 sensor: no data received
=== Network ===
Slowest loop: 103.75ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 2
WiFi firmware version 1.27
WiFi MAC address a4:e5:7c:03:b4:46
WiFi Vcc 3.41, reset reason Power up
WiFi flash size 2097152, free heap 25448
WiFi IP address 192.168.0.53
WiFi signal strength -47dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

ZakariahMT

@droftarts

That's odd

It's coming up on my end,

; Modix Big-60, Duex Expansion, Dual Printhead
; Configuration file for Duet WiFi (firmware version 3.4.5)
; Generated by Modix - Version 3.4.5 Config B 
global config_version = "Version 3.4.5 Config B"
global generation = 3 ; Generation 3 printer
global printhead = 1 ; Griffin printhead
global expansion = 1 ; Duex expansion board is installed
global printheads = 1 ; Dual printhead, change this value to 1 to switch it to a single-printhead setup

; General preferences_________________________________________________________
G90															; send absolute coordinates...
M83															; ...but relative extruder moves
M555 P2														; Set output to look like Marlin
M575 P1 B57600 S1											; Set auxiliary serial port baud rate and require checksum (for PanelDue)

; Network_____________________________________________________________________
M550 P"Big 60"												; set printer name
;M551 P"MODIX3D"											; Set password (optional)
M98 P"config_networking.g"									; load networking settings
G4 P300														; wait 300ms
;M552 P0.0.0.0												; Uncomment this command for using Duet Ethernet board

; Drives_________________________________________________________________________
;Main board______________________________________________________________________
M569 P0 S0													; Physical drive 0. X1
M569 P1 S1													; Physical drive 1. X2
M569 P2 R-1												    ; Physical drive 2. Disabled
M569 P3 S0													; Physical drive 3. Primary Extruder
M569 P4 S0													; Physical drive 4. Secondary Extruder
;Duex5 board_____________________________________________________________________
M569 P5 S0													; Physical drive 5 . Y
M569 P6 S0													; Physical drive 6 . Z1 (0,600) 
M569 P7 S0													; Physical drive 7 . Z2 (0,0) 
M569 P8 S0													; Physical drive 8 . Z3 (600,0) 
M569 P9 S0													; Physical drive 9 . Z4 (600,600) 

;Motor to stepper motor driver mapping_________________________________________________________
M584 X0:1 Y5 Z6:7:8:9 E3:4 P3								; Driver mapping
M671 X-185:-185:668:668 Y668:-46:-46:668 S30    			; Anticlockwise 

;Motor settings and acceleration limits___________________________________________________________________
M350 X16 Y16 Z16 E16:16 I1									; Configure microstepping with interpolation
M92 X100 Y100 Z2000 E418.5:418.5							; Set steps per mm
M566 X360 Y360 Z30 E3600:3600 P1							; Set maximum instantaneous speed changes (mm/min)
M203 X9000 Y9000 Z200 E5000:5000							; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z200 E5000:5000							; Set accelerations (mm/s^2)
M204 P500													; Set print and travel accelerations  (mm/s^2)
M906 X1800 Y1800 E1000:1000 Z1800 I50						; Set motor currents (mA) and motor idle factor in per cent
M84 S100													; Set idle timeout - 100 seconds

; Axis Limits
M208 X0 Y0 Z-2 S1                               			; set axis minima
M208 X600 Y600 Z660 S0                          			; set axis maxima

; Endstops
M574 X1 S1 P"xstop + e0stop"                            	; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y2 S1 P"ystop"                            				; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop

; Z-Probe
M558 P9 C"zprobe.in" H3 F100 T9000 R0.5						; BLTouch probing settings
M950 S0 C"duex.pwm5"										; sets the BLTouch probe
M376 H100			                						; Height (mm) over which to taper off the bed compensation
G31 P500 X-25.5 Y26.9										; BLTouch X and Y offset
M557 X{move.axes[0].min + sensors.probes[0].offsets[0] + 1, move.axes[0].max + sensors.probes[0].offsets[0] - 1} Y{move.axes[1].min + sensors.probes[0].offsets[1] + 1, move.axes[1].max + sensors.probes[0].offsets[1] - 1} P10:10
; The M557 is used to define the mesh grid area. It uses the P parameter to set the amount of probing points. P10:10 would be a 10x10 grid. Supports up to a 21x21 grid. 
M98 P"config_probe.g"										; Load the Z-offset from the config_probe.g file
; The Z_offset value is now set in config_probe.g, not in config.g
; Adjust the values there, do not adjust anything here.

; Heaters___________________________________________________________
M140 H-1                                       				; disable heated bed (overrides default heater mapping)

;E0_________________________________________________________________
;M308 S0 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8   			; configure sensor 0 as thermistor on pin e0temp
;M308 S0 P"spi.cs1" Y"rtd-max31865"							; Configure sensor 0 as PT100 via the daughterboard
M308 S0 P"e0temp" Y"pt1000"									; Configure sensor 0 as PT1000 on pin e0temp
M950 H0 C"e0heat" T0                            			; create nozzle heater output on e0heat and map it to sensor 0
M98 P"PID_tune_E0.g" R1										; PID calibration
; M307 is not used in this config. The M307 files are stored and executed from the PID_tune_E0.g file. You can verify the values there.
M143 H0 S285                                    			; set temperature limit for heater 0 to 285C

if {global.printheads} = 2
	;E1_________________________________________________________________
	;M308 S1 P"e1temp" Y"thermistor" T100000 B4725 C7.06e-8   		; configure sensor 1 as thermistor on pin e1temp
	;M308 S1 P"spi.cs2" Y"rtd-max31865"						; Configure sensor 1 as PT100 via the daughterboard
	M308 S1 P"e1temp" Y"pt1000"								; Configure sensor 1 as PT1000 on pin e1temp
	M950 H1 C"e1heat" T1									; create nozzle heater output on e1heat and map it to sensor 1
	M98 P"PID_tune_E1.g" R1									; PID calibration
	; M307 is not used in this config. The M307 files are stored and executed from the PID_tune_E1.g file. You can verify the values there.
	M143 H1 S285											; set temperature limit for heater 1 to 285C

; Fans______________________________________________________________
M950 F0 C"fan0" Q500									; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 C"Primary blower fan"					; set fan 0 value. Thermostatic control is turned on
M950 F2 C"duex.fan7" Q500								; create LED on pin fan2 and set its frequency
M106 P2 S0 H-1 C"LED"									; Disable fan channel for LED
M106 P2 S255											; LED on by default
M950 F3 C"duex.fan5" Q500								; create fan 3 on pin fan1 and set its frequency
M106 P3 S255 H0 T45										; set fan 3 value. Thermostatic control is turned on

if {global.printheads} = 2
	M950 F1 C"fan1" Q500									; create fan 1 on pin fan1 and set its frequency
	M106 P1 S0 H-1 C"Secondary blower fan"					; set fan 1 value. Thermostatic control is turned on
	M950 F4 C"duex.fan6" Q500								; create fan 4 on pin fan1 and set its frequency
	M106 P4 S255 H1 T45										; set fan 4 value. Thermostatic control is turned on

; Tools______________________________________________________________
;T0_________________________________________________________________
M563 P0 S"E0 Primary" D0 H0 F0                  			; define tool 0
G10 P0 X0 Y0 Z0                                 			; set tool 0 axis offsets
G10 P0 R0 S210                                  			; set initial tool 0 active and standby temperatures to 0C

if {global.printheads} = 2
	;T1_________________________________________________________________
	M563 P1 S"E1 Secondary" D1 H1 F1						; define tool 1
	G10 P1 X0 Y74.3 Z0										; set tool 1 axis offsets
	G10 P1 R0 S210											; set initial tool 1 active and standby temperatures to 0C

; Automatic power saving____________________________________________
M911 S22.5 R29.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"     	; Set voltage thresholds and actions to run on power loss. Power Failure Pause

; Filament sensor settings__________________________________________________
;M591 D0 P1 C"duex.e2stop" S1								; Regular filament sensor for E0
;M591 D1 P1 C"duex.e3stop" S1								; Regular filament sensor for E1

; Add-on settings__________________________________________________

Primary hotend Clog detector__________________________________________________
M591 D0 P7 C"e1stop" S1 L3.2 E10 R10:300					 Clog Detector E0 [Add-On]

;Secondary hotend Clog detector__________________________________________________
;M591 D1 P7 C"zstop" S1 L3.2 E10 R10:300					; Clog Detector E1 [Add-On]

; Crash detector__________________________________________________
;M950 J2 C"duex.e4stop" 									; create Input Pin 2 on pin E4 to for M581 Command.
;M581 P2 T0 S0 R0											; Crash Detector   [Add-On]

; Emergency stop button__________________________________________________
;M950 J3 C"duex.e6stop" 									; create Input Pin 2 on pin E4 to for M581 Command.
;M581 P3 T0 S1 R0 											; Emergency stop [Add-On]
;M581 P3 T1 S1 R1											; Emergency stop, pause the print [Add-On]
;M581 P3 T1 S1 R0 											; Emergency stop, pause always [Add-On]

; Automatic Z Offset Calibration____________________________________
M574 Z1 S1 P"!duex.e5stop"									; configure switch-type for Automatic z-offset
;M501

droftarts

@ZakariahMT Sorry, I'm seeing config.g now, I was looking on my phone earlier, somehow I missed it.
The error in the console is triggered by the lines here that should be commented:

; Add-on settings__________________________________________________
 
Primary hotend Clog detector__________________________________________________
M591 D0 P7 C"e1stop" S1 L3.2 E10 R10:300					 Clog Detector E0 [Add-On]

It needs a ; in front of "Primary" and another between the end of the M591 command and "Clog Detector", ie

; Add-on settings__________________________________________________
 
; Primary hotend Clog detector__________________________________________________
M591 D0 P7 C"e1stop" S1 L3.2 E10 R10:300	;				 Clog Detector E0 [Add-On]

That should fix the errors when running config.g.

For the motor error, it almost sounds like you have one motor that has shorted internally, and by moving it around, you're killing the drivers on the Duet. Check the resistance of each phase (pair of wires) of the motor that first exhibited the problem, at the connector where it connects to the Duet, and test each wire to ground, ie between the connector and the body of the motor. See https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_connecting#identifying-the-stepper-motor-phases to check motor wiring.

Ian