Extruder motor not working correct.

eRick

Hello.
I have new Duet 2 WiFi, it is my second main board. Extruder motor is behaving strangely (You can see it on film ). This is E0 drive, rest working correctly (I check this on same motor). What could be causing this?

Duet_2_WiFi.mp4

Driver settings:

;--- Drives
M569 P0 S1												; physical drive 0 goes forwards
M569 P1 S0												; physical drive 1 goes forwards
M569 P2 S0												; physical drive 2 goes forwards
M569 P3 S1												; physical drive 3 goes forwards
M569 P4 S0												; physical drive 4 goes forwards
M584 X1 Y0 Z4:2 E3										; set drive mapping
M671 X285:285 Y-73:318 S3.0								; leadscrews at left (connected to Z) and right (connected to E1) of X axis
;M208 X0:0 Y10:259										; X carriage moves from -5 to 205, Y bed goes from 0 to 200
M350 X256 Y256 Z256 E256:256 I0							; configure microstepping without interpolation
M92 X2560.00 Y2560.00 Z12800.00 E2560.00:12800.00		; set steps per mm
M566 X900.00 Y900.00 Z600.00 E900.00:600.00				; set maximum instantaneous speed changes (mm/min)
M203 X21000.00 Y21000.00 Z6000.00 E21000.00:6000.00		; set maximum speeds (mm/min)
M201 X4000.00 Y4000.00 Z4000.00 E4000.00:4000.00		; set accelerations (mm/s^2)
M906 X1700 Y1700 Z1700 E1200:1700 I30					; set motor currents (mA) and motor idle factor in per cent
M84 S30													; Set idle timeout

M122 Diagnose:

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7JKF2-3SJ6Q-1A9VR
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93744 of which 44 recycled
Exception stack ram used: 256
Never used ram: 9048
Tasks: NETWORK(ready,388) HEAT(blocked,1224) MAIN(running,1824) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:14 ago, cause: power up
Last software reset at 2021-01-11 20:28, reason: User, spinning module GCodes, available RAM 9040 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 20.1, current 22.9, max 23.4
Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2021-01-11 21:09:15
Cache data hit count 23264431
Slowest loop: 6.74ms; fastest: 0.13ms
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 4.2ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.69ms; fastest: 0.00ms
Responder states: HTTP(2) 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.23
WiFi MAC address dc:4f:22:5d:fc:71
WiFi Vcc 3.35, reset reason Unknown
WiFi flash size 4194304, free heap 24152
WiFi IP address 192.168.1.87
WiFi signal strength -67dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

Phaedrux

@eRick said in Extruder motor not working correct.:

M350 X256 Y256 Z256 E256:256 I0 ; configure microstepping without interpolation M92 X2560.00 Y2560.00 Z12800.00 E2560.00:12800.00 ; set steps per mm

First, don't use x256 microstepping on all axis. Or any axis really. Switch back to x16 with interpolation enabled and set your steps per mm accordingly.

Second, you only have a single extruder defined in M584, but you are specifying parameters for two extruders in your other settings. So remove the second extruder values for M92, M566, M203, M201, M906

See if that improves your issue.

Third, RRF 3.2 is now available.
https://github.com/Duet3D/RepRapFirmware/releases/tag/3.2

Please update by uploading this zip file to the system tab in DWC.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2/Duet2and3Firmware-3.2.zip

If none of that helps, please include the commands you're using to cause the motion and double check your wiring phases are all properly connected as a loose connection on one of the wires can cause similar behaviour.

eRick

@Phaedrux said in Extruder motor not working correct.:

Second, you only have a single extruder defined in M584, but you are specifying parameters for two extruders in your other settings. So remove the second extruder values for M92, M566, M203, M201, M906

Second extruder is for auto bed leveling.

Updating doesn't help.

Phaedrux

I assume you mean you're using a second driver for dual Z leveling, which is fine, but not what I'm talking about.

I mean these bits.

E2560.00:12800.00
E900.00:600.00
E21000.00:6000.00
E4000.00:4000.00
E1200:1700

You only have a single extruder defined in M584 M584 X1 Y0 Z4:2 E3 So remove the second value from all of those commands.

Did you try any of the other things I mentioned?

eRick

@Phaedrux said in Extruder motor not working correct.:

Did you try any of the other things I mentioned?

Yes, I change motors on x16 stepping with interpolation.

Goooood damn, it's working, thank you, you my hero :3

@Phaedrux
I heve one question.
Why stepping with interpolation is beter?

Phaedrux

x16 with interpolation allows for a lower load on the CPU for step generation, but still allows for the drivers to interpolate and send a smooth x256 signal to the motors.

eRick

Ok thanks

eRick

@Phaedrux
Does the print quality change when you change the steping from x256 to x16 with interpolation?

Phaedrux

No it should be imperceptibly the same. the only time you'd want to increase the microstepping is if your steps per mm at x16 is incredibly low.