Crying stepper motors

Rushmere3D

@jason0607 Yeah better, you will need to maybe adjust some of your settings but that should work.

You have commented out you Tool settings.

jason0607

@Rushmere3D
Now the motor is just as loud but moves slower

Rushmere3D

@jason0607 Are the phases of the stepper motors connected correctly?

Is this a new build? ~~Your config has multiple M584 commands make sure you have the correct one in use.~~

jason0607

@jason0607 Yes they are connected correctly

Rushmere3D

@jason0607 I would say these settings need, tweaking.

M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X1000.00 Y1000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X200.00 Y200.00 Z20.00 E250.00 ; set accelerations (mm/s^2)

Something like this maybe? BUT you need to adjust based on your machine, these are based on one of my printers.

M566 X300.00 Y300.00 Z60.00 E420.00           	; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z360.00 E1500.00   	; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z300.00 E10000.00     	; set accelerations (mm/s^2)

Rushmere3D

Would also be a good idea to share the results of m122 and M98 P"config.g" please?

jason0607

@rushmere3d
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.1 (2022-06-01 21:06:56) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: 0KSJD-0296U-D65J0-40KMS-K803Z-H4BUF
Used output buffers: 3 of 40 (14 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 104352 of which 100 recycled
Never used RAM 33504, free system stack 182 words
Tasks: NETWORK(ready,25.6%,244) ETHERNET(notifyWait,0.2%,576) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,290) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.7%,81) MAIN(running,71.8%,510) IDLE(ready,1.0%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:56 ago, cause: software
Last software reset at 2022-08-16 09:30, reason: User, GCodes spinning, available RAM 33520, slot 1
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 56285, completed 56285, timed out 0, errs 0
Step timer max interval 1487
MCU temperature: min 23.9, current 24.8, max 24.8
Supply voltage: min 24.0, current 24.0, max 24.0, 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: 2 queued, 2 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 2937, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 2935, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 2934, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 2936, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 2939, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2022-08-16 09:31:34
Cache data hit count 97077235
Slowest loop: 299.88ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.4ms, write time 11.7ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 40644ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 6, completed 6, 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 -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 282, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 282/0/0
Tx timeouts 0,0,281,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 101.62ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0

jason0607

@rushmere3d Error: M98: control character in string

Rushmere3D

@jason0607

M98 P"config.g"

Didn't work?

I'm out of ideas if your still having issues I'm sorry to say.

jason0607

@Rushmere3D What would be the settings for my motor?

jason0607

@rushmere3d M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Failed to initialise thermocouple: bad response from sensor
Warning: Sensor number 0 has not been defined

Rushmere3D

@jason0607 You mean in relation to the settings I posted? It's totally dependent on your setup, what printer is it?

jason0607

@rushmere3d I only have a Duet3Mini5+ Ethernet Board and the steppermotor 103-H5210-4240 / NEMA17 / Flansch 42mm / 1A / 51 Ncm

Rushmere3D

@jason0607 So are you saying this is just setup on a bench? It's not an actual printer?

jason0607

@rushmere3d Yes

Rushmere3D

@jason0607 I can't really help then, I'm not sure I understand what issue you are having.

What are you trying to achieve? What command are you sending to make the motor move?

droftarts

@jason0607 Your motors are quite high resistance at 4.8ohms and high inductance at 9.5mH. It may not be possible to drive them very fast, though they should have a good amount of torque. See https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_choosing#inductance

The high resistance/inductance may be contributing to 'coil whine', which is what I expect you mean by your motor 'crying'. Do they do this all the time, when moving and when stationary, once powered up? Does the movement seem smooth when it moves? Are you just testing one axis, if so which, or are they all doing it?

The drivers on the Mini 5+ can run in stealthChop mode, as opposed to spreadCycle. stealthChop is a quiet mode of operation for stepper motors at standstill and at low velocities, while spreadCycle will give better performance in medium to high velocity range for motors. Send M569 P0.0 to show how the X axis is set. To run in stealthchop all the time, change the M569 commands in config.g to:

M569 P0.0 S1 D3 V0 ; physical drive 0.0 goes forwards
M569 P0.1 S1 D3 V0 ; physical drive 0.1 goes forwards
M569 P0.2 S1 D3 V0 ; physical drive 0.2 goes forwards
M569 P0.3 S1 D3 V0 ; physical drive 0.3 goes forwards

Ian

jason0607

@droftarts
What are normal values? I can only move my stepper motor up to about 15mm/s.

droftarts

@jason0607 In the config.g you posted earlier, you have:

M203 X1000.00 Y1000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)

1000mm/min = 16.666mm/s. Try increasing the M203 values of X and Y. 6000mm/min = 100mm/s, 12000mm/min = 200mm/s etc.

Did you manage to resolve the stepper motor whine/crying?

Ian