Motors suddenly sound Horrible
-
The stepper motors and or drivers (X,Y,Z,E,Z2) do not sound as they did only moments ago. Same firmware, DWC, same everything. Funny, every driver on the Duet2 WiFi produce this. Tried amp adjustment via config.g, G90, G91. Relative mode slightly lessened the horrifying sound, slightly. Plenty of internet research. WTF. New board too!
-
Please post the results of M122 and M98 P"config.g" and post your full config.g file. You haven't given us much to go on.
-
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NW4SJ-6J9DD-3SJ6M-KASVK
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 78800 of which 0 recycled
Never used RAM 9340, free system stack 134 words
Tasks: NETWORK(ready,13.3%,232) HEAT(notifyWait,0.0%,332) Move(notifyWait,0.0%,305) MAIN(running,85.9%,442) IDLE(ready,0.7%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:10 ago, cause: software
Last software reset at 2022-04-11 22:39, reason: User, GCodes spinning, available RAM 9340, slot 0
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 31.2, current 33.6, max 34.2
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 0
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: 2022-04-11 22:41:30
Cache data hit count 4294967295
Slowest loop: 5.56ms; 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 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 42582ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 5, completed 5, 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 0 -1 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.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
=== Network ===
Slowest loop: 15.57ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
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.26
WiFi MAC address f4:cf:a2:e2:20:91
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 23384
WiFi IP address 192.168.137.26
WiFi signal strength -66dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Apr 04 2022 02:23:47 GMT-0600 (Mountain Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender 3 Pro" ; set printer name
M918 P1 E4 F2000000 ; configure direct-connect display; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M569 P4 S1 ; physical drive 4 goes forwards
M584 X0 Y1 Z2:4 E3 ; set drive mapping
M671 X-27:263 Y115:115 S0.5 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E93.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E1200 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X235 Y235 Z260 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop; Z-Probe
M558 P5 C"!zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X-53 Y-9 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S150 ; set temperature limit for heater 0 to 150C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; 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
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S275 ; set temperature limit for heater 1 to 275C
M308 S2 P"e1temp" Y"thermistor" T100000 B4092 ; 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 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
M141 H2 ; map chamber to heater 2
M143 H2 S275 ; set temperature limit for heater 2 to 275C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"Part Cooling" S1 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"HE Sink" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H2 T45 ; set fan 2 value. Thermostatic control is turned on; Tools
M563 P0 S"Hot End" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
; Miscellaneous
T0 ; select first tool - WiFi -
-
Is this at idle? During movement? Homing?
Can you make a video?
Did you recently update firmware? something must have changed recently? What was the last time it didn't make more noise?
-
@phaedrux Yes the firmware updated recently. From March 28, the first ever software and firmware setup, to April 4th 2022. In April, I updated from 3.2.x to 3.4.0. However the update, the printer was homing fine at the beginning of using the current RepRapFirmware. Also, recently I added a Z-Probe. Initially it was an inductive probe using a voltage divider to bring the Zstop.in to 0 from around 3. It was G92 Z0, G30 S-1 making sure the trigger height was consistent. Well, was not. So I setup an old endstop switch as a viable replacement. Unfortunately this has not yet been tested because of this fundamental issue of kinematics (STEPPER PROBLEM).
The endstop I now have as the Z-Probe is from the Ender 3's factory package, just without the metal lever. The switch has no electronic influence on the signal in that it simply goes from NO to closed, IF I'm correct.This is a video of homing the x axis from the most recent update of DWC:
https://drive.google.com/file/d/1gQD5vdYzfHeV8nGMgnYxXpspTOY6eONl/view?usp=sharing
Note; the motor does continue to make a slight ticking noise after the loud vibration that sounds until DWC finally reports:
G28 X
Error: Failed to home axes X
After z raises the x-gantry; the loud vibrating sounds for 5sec, the 2nd slight quickly ticking lasts for 1min. These recorded measurements are real-time, the video is edited for time and file size. -
Are you getting any phase disconnected errors in the console? That type of shaking and noise is usually seen when one wire of the motor is disconnected/broken. So check your wiring carefully.
Another test you can do is disconnect the belt from the motor shaft and see if it will spin freely that way. In this case it may be friction or binding preventing the movement. If the printer off are you able to slowly move the print head by hand?
-
@phaedrux Removed one wire from X connection at board. Home X in DWC. Received this: G28 X
Warning: Driver 0 warning: phase A may be disconnected. The carriage (X stepper, this is an original Ender 3 setup I'm working to get inside an enclosure minded) does try to go down to the endstop but only vibrates fairly rapidly and quite noisily.I did move the X stepper termination from the X stepper to an identical stepper motor and attempt to home. Just to generate some movement, ID the motor or the board... the swapped motor did the same thing, vibration without turning.
When the printer is without power to the drivers (the 24vdc IN) I can move any component freely, gently always. When 24v is flowing through the motors hold their positions.
Did the link to the video work? I had edited it for time however I could produce the long, drawn out, data hog version of whatever. Let me know. This thing may be at the warrantied time frames limitation very soon. Struggling poor person, 200 buck is a TON of money to me.
-
Update: So, with limited knowledge of driver chips and some confirming knowledge from FPV chips (ESC's) I have deduced that the two phases are in contact of one another on the drivers side. Yes, continuity has been detected and confirmed within drivers 0, 1 & 4. Axis ZA and E0, extruder, seem to be holding their own between their respective phases. I find any sort of explanation a high overstatement. This is something I fail to understand the how, whys, or just about any thing about.
-
@crookid said in Motors suddenly sound Horrible:
Also, recently I added a Z-Probe. Initially it was an inductive probe using a voltage divider to bring the Zstop.in to 0 from around 3. It was G92 Z0, G30 S-1 making sure the trigger height was consistent.
I'm not exactly sure what you mean here. You installed a zprobe and then started having problems?
@crookid said in Motors suddenly sound Horrible:
Removed one wire from X connection at board. Home X in DWC. Received this: G28 X
Warning: Driver 0 warning: phase A may be disconnected. The carriage (X stepper, this is an original Ender 3 setup I'm working to get inside an enclosure minded) does try to go down to the endstop but only vibrates fairly rapidly and quite noisily.I did not suggest that you SHOULD do that. Be very careful with how you wire and mis-wire the drivers as you're likely to damage them.
@crookid said in Motors suddenly sound Horrible:
I did move the X stepper termination from the X stepper to an identical stepper motor and attempt to home. Just to generate some movement, ID the motor or the board... the swapped motor did the same thing, vibration without turning.
Have you tried with new wiring? Do any of the motors and drivers produce proper motion?
@crookid said in Motors suddenly sound Horrible:
Update: So, with limited knowledge of driver chips and some confirming knowledge from FPV chips (ESC's) I have deduced that the two phases are in contact of one another on the drivers side. Yes, continuity has been detected and confirmed within drivers 0, 1 & 4. Axis ZA and E0, extruder, seem to be holding their own between their respective phases. I find any sort of explanation a high overstatement. This is something I fail to understand the how, whys, or just about any thing about.
I do not recommend you do that. It's like you're trying to short them out or something.
-
Is it possible you just switched to the latest version of PrusaSlicer? Starting in version 2.4.1 (I think -- I might have been 2.4), by default they send the commands to set the feed rates, accelerations, and jerk. This had me completely confused for a while, as I had just fixed a hardware issue on my printer, so naturally I figured I must have messed something up.
If you have switched recently, go to the printer settings tab, and select Machine Limits in the list on the left. Set "How to apply limits" to "Use for time estimate". That will revert you to the former behavior.
-
@bergy said in Motors suddenly sound Horrible:
Is it possible you just switched to the latest version of PrusaSlicer? Starting in version 2.4.1 (I think -- I might have been 2.4), by default they send the commands to set the feed rates, accelerations, and jerk. This had me completely confused for a while, as I had just fixed a hardware issue on my printer, so naturally I figured I must have messed something up.
If you have switched recently, go to the printer settings tab, and select Machine Limits in the list on the left. Set "How to apply limits" to "Use for time estimate". That will revert you to the former behavior.
I think this is happening during homing, so before the slicer is involved.
-
@bergy
Haven't used PrusaSlicer with this machine yet, have in the past and liked it. However this is happening with a spanky shiny new build; firmware, drivers, board. All is fresh from scratch and RepRap config is at the top execution. Everything is handled though DWC including firmware upgrades and transfers. I do appreciate your thoughts.As for the wiring. the Looms are correct. They are stayed the same as was working before, same motors, setup, all is correct. Man, should the phases hold continuity across the two? Phase 1 (A or B) is in continuity with phase 2 (A or B). So really, any one of the four wires contacts any other three. This is not normal. I think I need to file for an RMA, request requested. Right? Thanks.
-
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
Take extra care on wiring the replacement. Shorting the pins of the drivers are a good way to damage them.
