only one silent stepper driver
-
Hi everyone. I have a problem with my Duet3 6HC. Only the stepper motors connected to driver 1 are quiet. Motors connected to the other five stepper motor drivers are very loud and vibrate a lot. If I connect a motor that is very loud on driver 0, for example, to driver 1 with the same cable, the motor suddenly becomes quiet and the other way round. All drivers are configured the same in the Config. I use QSH4218-51-049 stepper motors from Trinamics.
I have tried the following things without noticing any change:
-Varying the motor current between 200mA and 1500mA.
-Stealthchop mode
-changing the microstepping
-Using different stepper motors from different manufacturersSince all motors on driver 1 work without problems and only vibrate strongly when connected to the other drivers, even though all drivers are configured the same, I assume that something is wrong with the circuit board. Can anyone think of another cause?
Here are my driver settings in config.g
M569 P0.0 S0 M569 P0.1 S0 M569 P0.2 S0 M569 P0.3 S0 M569 P0.4 S0 M584 X0.1 Y0.0 Z0.4 E0.3:0.2 M350 X256 Y256 Z256 E256:256 I0 M92 X1285.00 Y1285.00 Z34133.33 E6640.00:6640.00 M566 X720.00 Y720.00 Z60.00 E300.00:300.00 M203 X18000.00 Y18000.00 Z400.00 E1200.00:1200.00 M201 X1000.00 Y1000.00 Z50.00 E250.00:250.00 M906 X600 Y600 Z600 E600:600 I50 M84 S30 -
Firmware version?
Can you post the results of M122 and M98 P"config.g" along with your full config.g?
-
@utsnaderabob said in only one silent stepper driver:
M350 X256 Y256 Z256 E256:256 I0
Do you have a particular reason for using x265 microstepping?
-
@phaedrux thanks for your quick reply. There is no particular reason für using 265 microstepping but lower microstepping with or without interpolation does not improve motor behaviour.
Here is the Result of M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
Board ID: 08DJM-956L2-G43S4-6JKDA-3SD6Q-1V52F
Used output buffers: 3 of 40 (14 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 92392 of which 432 recycled
Never used RAM 110464, free system stack 208 words
Tasks: NETWORK(ready,28.7%,254) ETHERNET(notifyWait,0.1%,124) HEAT(delaying,0.0%,331) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.5%,93) MAIN(running,63.3%,924) IDLE(ready,0.3%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:39 ago, cause: power up
Last software reset at 2021-09-12 23:43, reason: User, GCodes spinning, available RAM 107608, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 137
MCU temperature: min 21.8, current 31.5, max 31.6
Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 20512, writes 17 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 20512, writes 17 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 20513, writes 16 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 20513, writes 16 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 20513, writes 16 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 20519, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-09-14 21:02:19
Slowest loop: 9.58ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 1.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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 352, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 197/0/0
Tx timeouts 0,0,196,0,0,154 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 11.92ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0Here ist the result of M98 P"config.g"
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 513C
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 236CAnd here is my full config.g:
M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M669 K1 ; select CoreXY mode ; Network M552 P192.168.1.1 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.3 D3 H45 S0 M569 P0.1 D3 H45 S0 M569 P0.0 D3 H45 S0 M569 P0.4 D3 H45 S0 M569 P0.2 D3 H45 S0 M584 X0.1 Y0.0 Z0.4 E0.3:0.2 M350 X256 Y256 Z256 E256:256 I0 M92 X1285.00 Y1285.00 Z34133.33 E6640.00:6640.00 M566 X720.00 Y720.00 Z60.00 E300.00:300.00 M203 X18000.00 Y18000.00 Z400.00 E1200.00:1200.00 M201 X1000.00 Y1000.00 Z50.00 E250.00:250.00 M906 X600 Y600 Z600 E600:600 I50 M84 S30 ; Axis Limits M208 X-5.5 Y-19.3 Z0 S1 ; set axis minima M208 X310 Y310 Z415 S0 ; set axis maxima ; Endstops M574 X1 S3 ; configure sensorless endstop for low end on X M574 Y1 S3 ; configure sensorless endstop for low end on Y M574 Z1 S2 ; configure Z-probe endstop for low end on Z M915 X1 R0 F0 M915 Y1 R0 F0 ; Z-Probe M950 S0 C"io4.out" ; create servo pin 0 for BLTouch M558 P9 C"io4.in" H5 F200 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P25 X0 Y45 Z2.8 ; set Z probe trigger value, offset and trigger height 2.8 größer=düse niedriger M557 X15:295 Y35:295 S50 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"out2" Q250 ; create fan 0 on pin out4 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"!out4+out4.tach" Q250 ; create fan 0 on pin out4 and set its frequency M106 P1 I1 S0.75 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F2 C"!out5+out5.tach" Q250 ; create fan 1 on pin out5 and set its frequency M106 P2 I1 S0.75 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F3 C"out7" Q250 ; create fan 1 on pin out5 and set its frequency M106 P3 S1 H-1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 S"left" 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 M563 P1 S"right" D1 H1 F0 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M307 H1 B0 R1.962 C248.9 D4.60 S1.00 V23.8 M307 H0 B0 R0.580 C364.6 D1.70 S1.00 V24.0 -
@utsnaderabob said in only one silent stepper driver:
M569 P0.3 D3 H45 S0 M569 P0.1 D3 H45 S0
Those two lines have double spaces between the H45 and S0. Not sure how it's going to handle that.
You can send M569 by itself to see the currently applied settings.
-
@phaedrux the double spaces make no difference, according to m569 the drivers apply the settings:
M569 P0.0
Drive 0 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, thigh 45 (207.5 mm/sec), tpwmthrs 2000 (4.7 mm/sec), pwmScaleSum 15, pwmScaleAuto 0, pwmOfsAuto 29, pwmGradAuto 0, pos 0I have now completely rebuilt the config.g with the configurationtool and tested the motors again without connecting anything else to the board and still get the same result: the motors are still only quiet when i connect them to driver 1, no matter what motors or cables i use, what microstepping with or without interpolation i use and no matter if stealthchop or spreadcycle is used. The last possibility I see is that I got a broken board. To test this I would need a new board from my reseller, but he will only exchange my board if I get a warranty authorization code from Duet3D.
-
@utsnaderabob said in only one silent stepper driver:
M569 P0.0
Drive 0 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, thigh 45 (207.5 mm/sec), tpwmthrs 2000 (4.7 mm/sec), pwmScaleSum 15, pwmScaleAuto 0, pwmOfsAuto 29, pwmGradAuto 0, pos 0Can you send that command for each one of the drivers? P0 P1, etc?
If we can't determine the cause and or it points to hardware defect and the board is under warranty, then yes we would authorize an exchange. We will see what @dc42 thinks.
Have you tried removing the D3 and H45 entirely?
-
@phaedrux here are the results of M569 for all drivers:
M569 P0.0
Drive 0 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, thigh 45 (207.5 mm/sec), tpwmthrs 2000 (4.7 mm/sec), pwmScaleSum 15, pwmScaleAuto 0, pwmOfsAuto 29, pwmGradAuto 0, pos 0
M569 P0.1
Drive 1 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, thigh 45 (207.5 mm/sec), tpwmthrs 2000 (4.7 mm/sec), pwmScaleSum 15, pwmScaleAuto 0, pwmOfsAuto 29, pwmGradAuto 0, pos 0
M569 P0.2
Drive 2 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, thigh 45 (40.2 mm/sec), tpwmthrs 2000 (0.9 mm/sec), pwmScaleSum 15, pwmScaleAuto 0, pwmOfsAuto 29, pwmGradAuto 0, pos 0
M569 P0.3
Drive 3 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, thigh 45 (40.2 mm/sec), tpwmthrs 2000 (0.9 mm/sec), pwmScaleSum 15, pwmScaleAuto 0, pwmOfsAuto 29, pwmGradAuto 0, pos 0
M569 P0.4
Drive 4 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, thigh 45 (7.8 mm/sec), tpwmthrs 2000 (0.2 mm/sec), pwmScaleSum 15, pwmScaleAuto 0, pwmOfsAuto 29, pwmGradAuto 0, pos 0
M569 P0.5
Drive 5 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x08053, toff 3, tblank 1, thigh 200 (46.9 mm/sec), hstart/hend/hdec 5/0/0, pos 8Yes, I tried removing th D3 and H45 entirely for all drivers (M569 P0.0 S0 ) and the drivers also takes over the settings according to M569:
M569 P0.0
Drive 0 runs in reverse, active low enable, timing fast, mode spreadCycle, ccr 0x08053, toff 3, tblank 1, thigh 200 (46.7 mm/sec), hstart/hend/hdec 5/0/0, pos 0But as already said, it makes no difference whether I use stealthchop or spreadcycle. The motor on driver P0.1 remains very quiet and the motors on the other drivers are still very loud.
-
@utsnaderabob there are two other things you need to be aware of:
-
For stealthChop to work effectively, you need to execute tuning move when you first use the motor. See https://duet3d.dozuki.com/Wiki/Tuning_Stepper_Motor_Drivers#Section_stealthChop_tuning.
-
There is an automatic changeover from stealthChop to spreadCycle above a certain speed, which is defined be the tpwmthrs parameter (the V parameter in the M569 command). The corresponding speed is reported in the M569 response. As you can see from the responses, the defaults are quite low, and typical movement speeds will exceed them. So your motors are working in spreadCycle mode except at low speeds.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
-
Hi @dc42. My problem is not that stealthchop is not working properly, I was just testing stealthchop to see if it would improve the actual problem. I will try to describe the problem again in more detail:
Stepper motors connected to the P0.1 driver run quieter than the printer's fans, even in spread cycle mode, as would be expected with high quality motors with a microstep of x256. Motors I connect to any of the other five drivers are so loud with the same settings that my neighbor asked me yesterday what that noise was. It is possible to print this way, but the vibration from the motors is so strong that it has a negative effect on print quality. Attempts to run the motors in Stealthchop have the effect that the motors are now almost silent on the P0.1 driver, but there is no improvement at all on the other drivers.
Since I have already tested other cables and motors, completely rebuilt the config.g and even reloaded the firmware without noticing any change, I see only a broken board as a possibility.
-
@utsnaderabob as you appear to have exhausted other possibilities, I will approve a replacement board - although it's hard to think of a hardware fault that would cause this problem. Please send an email to warranty@duet3d.com and include in it a link to this thread.
