Duet 3 mini 5+ screeching noise when moving stepper motors
-
Hi, im new to 3d printing and even newer to using RepRap firmware. I googled solutions for the problem that I was having and the only thing I found close to my issues was a forum topic called "controlling a cetus 3d with a duet3d 0.8.5". I tried applying their configuration files to my current system but for whatever reason, the board still sounds like tea pot kettle when I move any of the stepper motors. When i first turn on the machine in idle, the machine is quite but, as soon as i move any of the stepper motors, the machine begins to make a high pitch screeching and continues to do so until I turn off the machine. It sounds like the screeching is coming from the board itself but,I could he mistaken and the it could be the stepper motors making the noise. I am currently using my Cetus Mk3 with the duet mini. The board is being directly powered by a 350w 24v psu. Is there anything that I am missing here or should be looking out for?
-
@ray-r what stepper motors are you using? make/model please
and can you post your config.gOwns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
M350 X256 Y256 Z256 E16 I1 ; configure microstepping with interpolation M92 X1280.00 Y1280.00 Z1280.00 E690.00 ; set steps per mmMicrostepping is uncommon high....
-
Stick to x16 microstepping with interpolation enabled. Experiment later if you want.
What is your firmware version? Can you please send M122 and copy paste the results here?
-
I'm working on that kind of sound on a machine myself and I'm sure it's because the motor is "skipping steps" = not moving when commanded to move. In my case, I believe I've got a bad motor (because I think I've eliminated all other options).
Also agree with @Phaedrux that 256 interpolation is way too much. As interpolation step quantity increases, the holding torque for each microstep decreases and you might be in a place where you just don't have the power to turn the motors. Also be sure to adjust your your steps per mm when you change your M350 number.
-
@mikeabuilder said in Duet 3 mini 5+ screeching noise when moving stepper motors:
Also be sure to adjust your your steps per mm when you change your M350 number.
If the M92 is setup for 16x micro-stepping and the M350 occurs after it in the config.g file there is no need to change M92 regardless of what values you try in M350.
The firmware does the necessary calculations and adjusts M92 "internally", so to speak.
Frederick
-
@jay_s_uk Im using moons motors type:17HT4003-02N(I believe the stepper motors are made special for the Cetus because I already looked for the model number online). I have the version 1.01 of duet mini 5+ Wifi. The config file is in the top line. Im not sure how to show the whole config on the page.
-
@phaedrux The only reason I put such a high microstepping is because as I mentioned above, I found a post on this forum with the config files for the cetus and I copy and pasted most of the config. I originally started at 32 but it still gave the loud noise. I will try lowering ever further. Here is the results of the M122 command.
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.1 (2022-06-01 21:06:56) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 4J3NN-Q396U-D65J0-40KMS-3413Z-760H1
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 109888 of which 12 recycled
Never used RAM 28128, free system stack 206 words
Tasks: NETWORK(ready,10.7%,267) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.7%,114) MAIN(running,85.7%,412) IDLE(ready,2.0%,29) AIN(delaying,0.9%,274), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:11 ago, cause: software
Last software reset at 2022-06-28 17:45, reason: User, GCodes spinning, available RAM 28128, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 11579, completed 11579, timed out 0, errs 0
Step timer max interval 752
MCU temperature: min 31.7, current 32.6, max 32.6
Supply voltage: min 24.1, current 24.2, max 24.2, 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, read errors 0, write errors 1, ifcnt 19, reads 567, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 567, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 567, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 566, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 567, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2022-06-28 17:45:24
Cache data hit count 22382075
Slowest loop: 11.27ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.3ms, 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
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
Code queue is empty
=== CAN ===
Messages queued 99, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 56/0/0
Tx timeouts 0,0,55,0,0,42 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 17.05ms; 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 d8:bf:c0:15:09:ca
WiFi Vcc 3.35, reset reason Power up
WiFi flash size 2097152, free heap 25224
WiFi IP address 192.168.1.162
WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@mikeabuilder Just lowered the interpolation to 16 and I would move the motors at all or at least it struggled to move them. I originally had it set to 32 and it worked moving the motors but the mainboard is making a loud noise, or at least it sounds like its the mainboard.
-
Please post your full config.g as well. If you're using an ancient config you found online it's unlikely to be updated for 3.4.1.
-
@phaedrux That makes sense. 20220628_180132.mp4 here is a quick video of the noise generated by the board (only when the stepper motors are active). My current configuration
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sun Jun 26 2022 16:52:21 GMT-0700 (Pacific Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CETUS MK3" ; set printer name; Network
M551 P"" ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
M350 X32 Y32 Z32 E32 I1 ; configure microstepping with interpolation
M92 X180.00 Y180.00 Z180.00 E690.00 ; set steps per mm
M566 X900.00 Y900.00 Z600.00 E600.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z12000.00 E7200.00 ; set maximum speeds (mm/min)
M201 X150.00 Y150.00 Z150.00 E800.00 ; set accelerations (mm/s^2)
M906 X400 Y400 Z450 E1200 I10 ; 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 X180 Y180 Z175 S0 ; set axis maxima; Endstops
M574 X2 S1 P"io5.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin io5.in
M574 Y2 S1 P"io6.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin io6.in
M574 Z2 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin io2.in; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:165 Y15:165 S50 ; define mesh grid; Heaters
M140 H-1 ; disable heated bed (overrides default heater mapping)
M308 S0 P"temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out1" T0 ; create nozzle heater output on out1 and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H0 S300 ; set temperature limit for heater 0 to 300C; Fans
M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency
M106 P1 S0 H1:0 T45 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 D0 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
-
Does the sound stop when you de-energize the motors with M84?
They are starting up in Spreadcycle mode, you can try switching them over to stealthchop mode. That will likely drop the idle noise, but you'll have to configure the speed to switch over to spread cycle again.
I think it's likely just the way those motors are going to work with these drivers.
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_tuning
Take a look there, specifically the M569 portion where you'd set spreadcycle and stealthchop.
-
@phaedrux yes it does. I will try to implement that into my printer thank you very much for the help. Just out of curiosity, why does the noise happen from this board? I've ran the machine with its original mainboard, as well as a Mellow Fly E3, and they both sounded alot better in this situation. Is it the stepper motors or something?
-
They may be using stealthchop by default.
-
@phaedrux I enabled stealth chop and its still making the noise, albeit more quite but, it is still significantly louder than expected.
-
@ray-r Why are the motor currents for XY and Z only one third of the current for the extruder? We could really do with knowing the specification of the motors.
-
@ray-r Also, having only 10% holding current on 400 mA means it'll be 40mA which will do next to nothing in terms of holding position. Set it to 50% and see if that makes any difference to the sound you hear.
-
@deckingman I would to provide information on the stepper motors but, unfortunately there is no information on these stepper motors. I already looked online for the model number/manufacturer but there is no info. Ill add a picture of the stepper motor for reference.
-
@phaedrux So what are my options here? Do i need to replace the stepper motors or is this going to happen with any system that I plug into the Duet 3?
-
@ray-r Are the model numbers the same on the axes motors as the extruder? If they are, then it would reasonably safe to assume that you could make the motor current the same for all of them - i.e. increase it to 1200mA. I'm not saying it will cure your problem, but it might.
