Dual y motors but only one is hot

Adamfilip

@gloomyandy not that easy to test. as each homes individual. but will attempt and let you know

RogerPodacter

i have the same behavior on my 3 Z motors with my Duet 3 Mini 5+. the printer uses 3 identical independent Z motors to level the bed etc. one of the 3 motors is always hot while the other 2 are cool. its been this way for months but i never really tried to solve it.

Adamfilip

@RogerPodacter hmm maybe one motor has a winding error or a wiring issue. I am going swap it out for another to see if problem persists

Phaedrux

@RogerPodacter said in Dual y motors but only one is hot:

i have the same behavior on my 3 Z motors with my Duet 3 Mini 5+. the printer uses 3 identical independent Z motors to level the bed etc. one of the 3 motors is always hot while the other 2 are cool. its been this way for months but i never really tried to solve it.

All 3 motors are directly connected to the mini5? It kind of sounds like the 1 hot motor has an internal short.

scumdead

Is there a missing M569 P9?

Phaedrux

@Adamfilip Can you send M122 and M98 P"config.g" and share the results here?

Are you able to change your motor wiring around to have both Y motors on either the Duex or Duet itself?

Do you have another same motor to test with?

Adamfilip

@Phaedrux

Here is the results.
I will try swapping motor and or moving to Duex to see if it makes any difference and report back

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
FTP is enabled on port 21
Extruder 0 has no filament sensor
Endstop configuration:
X: high end switch connected to pin xstop
Y: high end switches connected to pins ystop duex.e6stop
Z: noneError: in file macro line 109: M581: missing parameter 'T'
Error: Accelerometer not found on specified port

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 + DueX5
Board ID: 08DLM-996RU-N85T0-6JKF2-3SJ6Q-1AVVR
Used output buffers: 1 of 26 (13 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 75748 of which 40 recycled
Never used RAM 12408, free system stack 174 words
Tasks: NETWORK(ready,18.2%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,304) DUEX(notifyWait,0.0%,24) MAIN(running,80.9%,438) IDLE(ready,0.9%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:54 ago, cause: power up
Last software reset at 2023-01-29 13:50, reason: User, GCodes spinning, available RAM 8248, 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
Step timer max interval 0
MCU temperature: min 29.3, current 32.8, max 33.0
Supply voltage: min 24.0, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min n/a
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min 0
Driver 10: 
Driver 11: 
Date/time: 2023-01-31 00:07:29
Cache data hit count 4080099192
Slowest loop: 25.78ms; fastest: 0.18ms
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 29.8ms, write time 4.7ms, max retries 0
=== Move ===
DMs created 83, segments created 2, maxWait 52089ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 1, completed 1, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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 0 -1 -1 -1, chamber heaters 2 -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
=== DueX ===
Read count 1, 0.52 reads/min
=== Network ===
Slowest loop: 31.18ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 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 84:0d:8e:b2:f8:6f
WiFi Vcc 3.31, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24088
WiFi IP address 192.168.0.184
WiFi signal strength -32dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Adamfilip

@scumdead hmm good catch. not sure that will make a difference but will try

o_lampe

@Adamfilip You didn't mention which motor gets hotter, so:
Is there a reason, why you don't use driver 2 for anything? Maybe, because it's burnt?
The former incident could have damaged more than just the one driver and it's time for a new Duet2...?

Adamfilip

update: replaced the hot motor and new motor isnt getting hot, same setup otherwise. so I assume something was wrong with that motor.