Dual y motors but only one is hot
-
@Adamfilip What happens if you swap over the connections to the two motors? Does the "hot motor" switch or does it stay the same?
-
Can you share your config and firmware version as well?
-
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.5 (2022-11-30)
Duet WiFi Server Version: 1.27Config
;389.86; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.5 on Wed Jan 08 2020 19:38:55 GMT-0500 (Eastern Standard Time) ; General preferences ;M564 H0 ; allow movement without homing G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"TitanXY" ; set printer name M929 S3 ;Log console to SDCard M669 K0 ; Motion Kinematics for Cartesian mode ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet M586 P1 S1 C"*" ; allows Cross Origin Resource Sharing (CORS). ; --- drive map --- ; _______ 280,280 ; | V6 | W7 | ; | ----- | ; | U5 | Z8 | ; 0,0 ------- ; front ; Drives M569 P0 S0 ; X Motor physical drive 0 goes backwards previously P0 M569 P1 S1 ; Y Motor M569 P3 S1 ; E0 Extruder physical drive 3 goes Forwards M569 P5 S0 ; FRONT LEFT Z Drive 5 on Duex 5 0.10 M569 P6 S1 ; REAR LEFT Z Drive 6 on Duex 5 0.10 M569 P7 S1 ; REAR RIGHT Z Drive 7 on Duex 5 0.10 M569 P8 S0 ; FRONT RIGHHT Z Drive 8 on Duex 5 0.10 M584 X0 Y1:9 Z5:6:7:8 E3 ; MOTOR MAPPING WITH 4 Z STEPPERS dual y M350 X16 Y16 Z8 I1 ; configure microstepping without interpolation, previously 32 M350 E16 I1 ; configure microstepping with interpolation ;M92 X80.09 Y80.28 Z321.62 E397 ; set steps per mm. M92 X80 Y80.0 Z2400 E478.4 ; july 21 set steps per mm M566 X900 Y900 Z60 E800 ; Set maximum instantaneous speed changes (mm/min) JERK M203 X18000 Y18000 Z750 E2500 ; Set maximum speeds (mm/min) M201 X3000 Y3000 Z250 E1000 ; Set accelerations (mm/s^2) M906 X1200 Y1000 Z1200 E750 I30 ; Set motor currents (mA) and motor idle factor in per cent X1400 Y1400 Z1300 M204 P1500 T2000 ; Set printing acceleration and travel accelerations M84 S30 ; Set idle timeout M572 D0 S0.025 ; Pressure Advance ; Axis Limits M208 X0 Y0 Z-1 S1 ; set axis minima M208 X280 Y255 Z550 S0 ; set axis maxima. ;SKEW COMPENSATION . M556 S100 X1.47 Y0.924 Z-0.286 ;M556 S100 X-0.2 ;M556 S100 X-0.313 ;july 21 ;911 PRINT RECOVERY MODE M911 S19.8 R22.0 P"M913 X0 Y0 G91 M83 G1 Z1 E-5 F1000" ; Endstops M574 X2 S1 P"xstop" ; X max active high endstop switch M574 Y2 S1 P"ystop+duex.e6stop" ; Dual Y Optical endstops M591 D0 ; display filament sensor parameters for extruder drive 0 ;M574 Z0 P"nil" ; zstop is free ;M950 J1 C"!zstop" ; Use Z endstop as Emergency Stop if Triggers, due to head Plunge M581 P1 T0 S1 R0 ;Euclid Settings M574 E1 S2 ;configure Z-probe endstop for low end on Z ; M558 P8 C"!^zprobe.in" H5 F200 60 T5000 A1 S0.05 ; K0 for probe 0, P5 for NC switch, C for input pin, ; ^ for enabling the native pullup resistor on Duet 2 ; hardware running RRF3 ; H dive height of 8mm, F300 probing speed 6mm/sec, ; T9000 travel speed 150mm/sec, ; A3 number of probes 1, S0.01 max tolerance of 0.01 G31 K0 P500 X0 Y0 Z-2.3 ; CHECK for LOOSE things first! set Z probe trigger tap ;G31 K0 P500 X-21 Y0 Z7.55 ; CHECK for LOOSE things first! set Z probe trigger euclid ; value, offset and trigger height. Higher numbers ; makes nozzle closer to bed ; switch plunger is 16.4mm to the LEFT and 29.27mm in ; FRONT of the nozzle. Switch triggers 0.9mm BELOW nozzle ; https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Secti ; Bed leveling ; --- drive map --- ; _______ 280,270 ; | V6 | W7 | ; | ----- | ; | U5 | Z8 | ; 0,0 ------- ; front M671 x-65:-65:375:375 Y-105:435:435:-105 S40 ;tap ;M671 x-75:-75:367:367 Y-100:440:440:-100 S40 ; Define Z belts locations (Front_Left, Back_Left, Back_Right, Front_Right), S10 = MAX 10MM DIFFERENCE ALLOWED ;M671 x-76:-76:382:382 Y-37:421:421:-37 S40 ; Define Z belts locations (Front_Left, Back_Left, Back_Right, Front_Right), S10 = MAX 10MM DIFFERENCE ALLOWED ;M671 x15:15:298:298 Y15:298:298:15 S20 ; Define Z belts locations (Front_Left, Back_Left, Back_Right, Front_Right), S10 = MAX 20MM DIFFERENCE ALLOWED M557 X50:250 Y50:250 P5 ; define mesh grid S86 = Spacing 86mm P3 = 3 point spacing M376 H3 ; taper bed levelling off after 10mm height M581 ;Accelerometer M955 P0 C"spi.cs4+spi.cs3" I60 M593 P"zvd" F35.5 ; use ZVD input shaping to cancel ringing at 35.5Hz ;M593 P"none" ; disable input shaping ;M593 P"custom" H0.4:0.7 T0.0135:0.0135 ; use custom input shaping ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M140 H0 ; Map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C ;M307 H0 R0.668 K0.284:0.000 D5.21 E1.35 S1.00 B0 ; PID BED Tuning M307 H0 R0.671 K0.370:0.000 D6.13 E1.35 S1.00 B0 M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.060000e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M143 H1 S300 ; set temperature limit for heater 1 to 300C M307 H1 R4.107 K1.013:0.000 D1.94 E1.35 S1.00 B0 V24.0 ;REVO 24V M308 S2 P"e1temp" Y"thermistor" T100000 B3950 ; configure sensor 2 as thermistor on pin e1temp M950 H2 C"e1heat" T2 ; create chamber heater output on e1heat and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for the chamber heater and set PWM limit M141 H2 ; map chamber to heater 2 M143 H2 S100 ; set temperature limit for heater 2 to 100C ; Fans M950 F0 C"fan2" Q500 ;create fan 2 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0 ; define tool 0 ;M563 P1 D1 H2 F1 ; define tool 1 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M17 Z ;engage z stepper to prevent gantry falling -
@gloomyandy not that easy to test. as each homes individual. but will attempt and let you know
-
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.
-
@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
-
@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.
-
Is there a missing M569 P9?
-
@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?
-
Here is the results.
I will try swapping motor and or moving to Duex to see if it makes any difference and report backM98 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 portM122 === 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 -
@scumdead hmm good catch. not sure that will make a difference but will try
-
@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...? -
update: replaced the hot motor and new motor isnt getting hot, same setup otherwise. so I assume something was wrong with that motor.
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
