RRF v3.3/Mini 5+ Wifi - Major problems with layer shifting

fcwilt

I got four printers running RRF v3.3 and two of them are using Mini 5+ boards.

Layer shift is not a problem.

So its not a fundamental RRF or Duet problem.

Which leaves us with something about your hardware, your configuration or some of each.

If you post your files using the </> tag it makes it easy for anyone to take a look, as opposed to having to download and open in some editor.

Frederick

Gixxerfast

@fcwilt Hi, yes I don't think there's a general problem with the mini5+

~~BUT, reading from and talking with quite a few, there's seem to be a problem with 0.9 steppers and the mini5+(TMC2209) / rrf.~~

Do you run 0.9 degrees stepper motors+

fcwilt

@gixxerfast said in RRF v3.3/Mini 5+ Wifi - Major problems with layer shifting:

@fcwilt Hi, yes I don't think there's a general problem with the mini5+

BUT, reading from and talking with quite a few, there's seem to be a problem with 0.9 steppers and the mini5+(TMC2209) / rrf.

Do you run 0.9 degrees stepper motors+

No except for one extruder.

Does it appear to be a hardware or firmware compatibility problem with the Mini 5+ and 0.9 steppers?

Frederick

Gixxerfast

@fcwilt I should actually amend my comment. It could be old topics. So I really don't know and shouldn't make such statements.

It's getting late I might have to edit this a bit tomorrow

Cheers

T3P3Tony

@gixxerfast I get your frustration! especially with those long prints. What we need to work out is what is the root cause of the layer shifts, is it:
a) the print head knocking on the print so there is in issue with Z motion of some sort or
b) the XY motion.

Initially I went down the rabbit hole of Z motion due to the mentions of mesh bed levelling being in question, you mentioned the nozzle grinding on the prints, and at least one image looked like squashed layers. I now am not sure about that because of:

@gixxerfast said in RRF v3.3/Mini 5+ Wifi - Major problems with layer shifting:

all layer shifts, shifts to the down(-y)/left(-x)

As you have already pointed out that indicates something with the XY motion, not Z. You have also checked the connector, are confident about the wiring and tried a different driver which eliminates quite a few possibilities also the fact you only see it on the more complex prints makes some causes less likely.

From the look of your new pictures the layer shifts are cumulative, always in the one direction?

I know you have already swapped X from D0 to D2 without resolving the problem. Can you try the following:

Swap the X and Y drivers and motor cables and see if the issue stays the same place or changes to layer shifts in the opposite direction

M584 X0.1 Y0.0 Z0.3:0.4:0.5:0.6 E121.0

I have used the driver 0 for the swap here but you can use driver 2 as you currently have it configured if you prefer. The idea is that you change Y and X, not just X.

When/if the layer shifts are happening please do the following:

Send M906 and M913 with no parameters and confirm that the currents are as expected and at 100%.
Send M569 P1 and M569 P0 (or P2 if you are using driver 2) and posts the results here.
Send M122 and post the results here.

Gixxerfast

@t3p3tony said in RRF v3.3/Mini 5+ Wifi - Major problems with layer shifting:

Send M906 and M913 with no parameters and confirm that the currents are as expected and at 100%.
Send M569 P1 and M569 P0 (or P2 if you are using driver 2) and posts the results here.
Send M122

Hi, thanks for the reply even on a saturday

I'm in the middle of testing again, but I haven't switched the cables as you suggested just yet as it requires a bit of printer disassembly (quite a bit). I will do it later.

However, I'm starting to wonder if I have beed barking up the wrong tree. With a corexy, if it shifts to -x/-y couldn't that suggest that it's the A-motor (y-motor right one) that is skipping steps when trying to do a non-diagonal move?

Is this something to worry about, btw?

T3P3Tony

@gixxerfast I will have to get @dc42 's opinion on the failedOp 0x01 error.

mrehorstdmd

@gixxerfast Z axis jerk (1 mm/sec) and acceleration (250 mm/sec^2) seem awfully low to me. Maybe the nozzle is dragging on the print when the layer changes or when you use lift on retract...

Gixxerfast

@t3p3tony

Latest shift after z 5mm. Going to check y-motor, crimps and switch driver for that.

Need to get myself an easier testprint.

Cable switching is after that. (The y-motor cable is shorter than the x-motor cable)

021-10-09 14:24:38	M98 P"0:/macros/test/motorcheck.g"
Motor current (mA) - X:1200, Y:1200, Z:1200, E:500, idle factor 70%
Motor current % of normal - X:100, Y:100, Z:100, E:100
Drive 1 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 920
Drive 2 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 56
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: H1668-Y296U-D65J0-40KMA-KR03Z-RK6ZH
Used output buffers: 3 of 40 (30 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 115376 of which 0 recycled
Never used RAM 22748, free system stack 120 words
Tasks: NETWORK(ready,17.0%,226) HEAT(delaying,0.0%,344) Move(notifyWait,2.5%,272) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.1%,357) CanClock(delaying,0.0%,338) TMC(notifyWait,1.4%,72) MAIN(running,77.6%,400) IDLE(ready,0.4%,29) AIN(delaying,0.9%,264), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:53:49 ago, cause: software
Last software reset at 2021-10-09 12:30, reason: User, GCodes spinning, available RAM 24252, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 6827511, completed 6827511, timed out 0, errs 0
Step timer max interval 751
MCU temperature: min 31.1, current 31.5, max 31.5
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/31, heap memory allocated/used/recyclable 2048/680/220, gc cycles 2
Driver 0: position 43187, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 19, reads 18270, writes 0, timeouts 0, DMA errors 0
Driver 1: position 3882, standstill, SG min/max 0/138, read errors 0, write errors 0, ifcnt 59, reads 18270, writes 0, timeouts 0, DMA errors 0
Driver 2: position 1972, ok, SG min/max 0/140, read errors 0, write errors 0, ifcnt 59, reads 18271, writes 0, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/6, read errors 0, write errors 0, ifcnt 53, reads 18270, writes 0, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/6, read errors 0, write errors 0, ifcnt 53, reads 18270, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, standstill, SG min/max 0/16, read errors 0, write errors 0, ifcnt 53, reads 18270, writes 0, timeouts 0, DMA errors 0
Driver 6: position 0, standstill, SG min/max 0/4, read errors 0, write errors 0, ifcnt 53, reads 18270, writes 0, timeouts 0, DMA errors 0
Date/time: 2021-10-09 14:24:35
Cache data hit count 4294967295
Slowest loop: 7.46ms; fastest: 0.07ms
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 380245, completed moves 380205, hiccups 0, stepErrors 0, LaErrors 0, Underruns [403, 4, 0], CDDA state 3
=== 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, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is ready with "M122" in state(s) 0 0, running macro
Telnet is idle in state(s) 0
File is doing "G1 X135.826 Y123.358 E0.02813" 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 22392, received 2415, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 278, free buffers 17 (min 3), ts 1006/1006/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 201.41ms; fastest: 0.06ms
Responder states: HTTP(1) 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 8
WiFi firmware version 1.26
WiFi MAC address f0:08:d1:02:eb:c9
WiFi Vcc 3.36, reset reason Power up
WiFi flash size 2097152, free heap 25616
WiFi IP address 192.168.1.70
WiFi signal strength -50dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 2 0 0 0 0 0 0 0

Gixxerfast

@mrehorstdmd
Hmm, it's all stolen from allegedly working setups:-)

; Sets normal speeds and acceleration for printing operation

M566 X600 Y600 Z60 E8000        ; Set maximum instantaneous speed changes (mm/min) aka Jerk
M203 X12000 Y12000 Z3000 E15000 ; Set maximum speeds (mm/min)
M201 X4000 Y4000 Z250 E2000     ; Set maximum accelerations (mm/s^2) 
M204 P3000 T4000                ; Set printing acceleration and travel accelerations

I'll recheck those. I have a belted z and four z-motors so fast z-movements shouldn't be a problem. DO you have a suggestion?

I could up the z-acc to my old Klipper-value which was 350 mm/s2. I have no idea what a good jerk value would be.

Gixxerfast

@t3p3tony

Well, shifted A cables to B-motor and vice versa. And reconfigured th emotor assignment as described.

But no, same thing. It shifted in the same direction.

So I made a descision to change motors to 1.8 degr OMC motors. It seems like I just can't get it to work with the LDO 0.9 degr steppers.

Anyway, I'm posting the output so that anyone that wants can maybe find out what's not working.
Here's the output from before the shifted print

BEFORE
2021-10-09 18:51:44	M98 P"0:/macros/test/motorcheck.g"
Register 0x06 value 0x21000048
Register 0x06 value 0x21000040
Register 0x06 value 0x2100004c
Register 0x06 value 0x21000040
Register 0x06 value 0x21000044
Register 0x06 value 0x21000048
Motor current (mA) - X:1200, Y:1200, Z:1200, E:400, idle factor 70%
Motor current % of normal - X:100, Y:100, Z:100, E:100
Drive 0 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 936
Drive 2 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 392
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: H1668-Y296U-D65J0-40KMA-KR03Z-RK6ZH
Used output buffers: 3 of 40 (12 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 113440 of which 0 recycled
Never used RAM 24684, free system stack 200 words
Tasks: NETWORK(ready,10.2%,238) HEAT(delaying,0.0%,380) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,352) TMC(delaying,1.1%,115) MAIN(running,85.9%,426) IDLE(ready,1.8%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes: WiFi(NETWORK) HTTP(MAIN)
=== Platform ===
Last reset 00:00:17 ago, cause: software
Last software reset at 2021-10-09 18:51, reason: User, GCodes spinning, available RAM 24252, 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 17941, completed 17941, timed out 0, errs 0
Step timer max interval 752
MCU temperature: min 28.6, current 29.5, max 29.8
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/5, heap memory allocated/used/recyclable 2048/232/162, gc cycles 0
Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 116, reads 1577, writes 12, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 49, reads 1579, writes 9, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 116, reads 1576, writes 12, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 110, reads 1576, writes 12, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 112, reads 1576, writes 12, timeouts 0, DMA errors 0
Driver 5: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 110, reads 1576, writes 12, timeouts 0, DMA errors 0
Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 110, reads 1576, writes 12, timeouts 0, DMA errors 0
Date/time: 2021-10-09 18:51:40
Cache data hit count 32653113
Slowest loop: 4.75ms; fastest: 0.12ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, 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, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is ready with "M122" in state(s) 0 0, running macro
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 169, received 202, lost 0, longest wait 2ms for reply type 6031, peak Tx sync delay 240, free buffers 17 (min 16), ts 89/88/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 20.47ms; 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 f0:08:d1:02:eb:c9
WiFi Vcc 3.36, reset reason Power up
WiFi flash size 2097152, free heap 25880
WiFi IP address 192.168.1.70
WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

After:

After:
2021-10-09 20:23:58	M98 P"0:/macros/test/motorcheck.g"
Register 0x06 value 0x21000248
Register 0x06 value 0x21000240
Register 0x06 value 0x2100004c
Register 0x06 value 0x21000240
Register 0x06 value 0x21000044
Register 0x06 value 0x21000248
2021-10-09 20:23:59	Motor current (mA) - X:1200, Y:1200, Z:1200, E:400, idle factor 70%
Motor current % of normal - X:100, Y:100, Z:100, E:100
Drive 0 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 56
Drive 2 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 824
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: H1668-Y296U-D65J0-40KMA-KR03Z-RK6ZH
Used output buffers: 3 of 40 (30 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 115376 of which 0 recycled
Never used RAM 22748, free system stack 114 words
Tasks: NETWORK(ready,15.9%,226) HEAT(delaying,0.0%,344) Move(notifyWait,1.4%,272) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.1%,357) CanClock(delaying,0.0%,338) TMC(notifyWait,1.3%,72) MAIN(running,80.1%,415) IDLE(ready,0.2%,29) AIN(delaying,0.9%,264), total 100.0%
Owned mutexes: WiFi(NETWORK) HTTP(MAIN)
=== Platform ===
Last reset 01:32:33 ago, cause: software
Last software reset at 2021-10-09 18:51, reason: User, GCodes spinning, available RAM 24252, 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 5551983, completed 5551983, timed out 0, errs 0
Step timer max interval 954
MCU temperature: min 28.6, current 32.2, max 32.4
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/29, heap memory allocated/used/recyclable 2048/1616/1178, gc cycles 1
Driver 0: position 47774, ok, SG min/max 0/478, read errors 0, write errors 0, ifcnt 130, reads 44394, writes 14, timeouts 0, DMA errors 0
Driver 1: position 3742, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 49, reads 44409, writes 0, timeouts 0, DMA errors 0
Driver 2: position 1985, ok, SG min/max 0/490, read errors 0, write errors 0, ifcnt 130, reads 44395, writes 14, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/62, read errors 0, write errors 0, ifcnt 125, reads 44393, writes 15, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/52, read errors 0, write errors 0, ifcnt 127, reads 44394, writes 15, timeouts 0, DMA errors 0
Driver 5: position 0, standstill, SG min/max 0/54, read errors 0, write errors 0, ifcnt 125, reads 44394, writes 15, timeouts 0, DMA errors 0
Driver 6: position 0, standstill, SG min/max 0/66, read errors 0, write errors 0, ifcnt 127, reads 44392, writes 17, timeouts 0, DMA errors 0
Date/time: 2021-10-09 20:23:56
Cache data hit count 4294967295
Slowest loop: 211.33ms; fastest: 0.07ms
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 262933ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 378342, completed moves 378302, hiccups 0, stepErrors 0, LaErrors 0, Underruns [3832, 33, 1], CDDA state 3
=== 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, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is ready with "M122" in state(s) 0 0, running macro
Telnet is idle in state(s) 0
File is doing "G1 X159.839 Y151.486 E0.00557" 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 386228, received 66906, lost 0, longest wait 1ms for reply type 6013, peak Tx sync delay 291, free buffers 17 (min 3), ts 27680/27680/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 201.61ms; fastest: 0.06ms
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 1
WiFi firmware version 1.26
WiFi MAC address f0:08:d1:02:eb:c9
WiFi Vcc 3.36, reset reason Power up
WiFi flash size 2097152, free heap 22224
WiFi IP address 192.168.1.70
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

Gixxerfast

EDIT: I almost forgot. I'm an ungrateful git. Big thanks to everyone that has helped trying to pinpoint the problem.

Finally! Swapped out the Voron branded 0.9 LDO 42STH40-2004MAC with the OMC 17HS19-2004S1 1.8 degr motors and YES it comes out as it should. Btw, all grub screws and pullies were rock solid. The belts ran super smooth and was even and the gantry wasn't racked but super square

I removed all drive mod config (D2 etc..) and just ran it vanilla.

Much more silent as well

Conclusion (I hope), must be after 20 something failed prints that either this setup just doesn't work with these 0.9 degr stepper motors unless you configure it some way unknown to me or I have faulty motors. Then again I came from a fast working setup where I regulary printed with 5000+ acceleration with these.

I just don't know. I just hope this is history for me now

JADoglio

I had this problem a few months ago. To fix it I had to replace the Y stepper motor. It was apparently missing steps many steps then starting up again. I suppose it could have been a connector but I used the same connector on the new motor and had no issues after that.

aprz

@gixxerfast I wonder if replacing the PSU with a higher Voltage (36v-48v) would help? I have this problem on my corexy and can only print at 60mm/s which is slow compared to what other printers can do. I'm also using 0.9 degree motors. I'm thinking of doing what you did and changing the motors to 1.8 deg motors. this post was helpful.

Gixxerfast

@aprz I don't know if you can even do that. Guess it depends on which board you have.

However I can't say if it would help but I think it's a hard way to go to fix something that might be fixed with other motors.

I should have changed a long time ago but I was convinced it was an "upgrade" even though I see now that those motors do not belong on a 2.4 IMHO. The OMC BOM motors are quite affordable.

I hope you can make it work better.

60 mm/sec on a Voron, or really any good corexy, is painfully slow

Cheers