3.5 B3 Toolboard stepper intermittently running backwards
-
Ok. I think I've narrowed down the problem. Theres a speed threshold when the problem occurs. For Ex.
G1 E100 F180 the motor runs forwards
G1 E100 F300 the motor runs in reverse
I can now consistently reproduce the problem. Parts of my original question can be ignored because I hadn't realized it was speed based. Sometimes I was manually extruding at 5mm/s and sometimes I was extruding at 3mm/s.
-
@ctilley79 Can you post your config.g file so that we can see steps/mm acceleration PA/IS etc.
-
I've had some similar behaviour, mine just totally stops though.
-
@gloomyandy said in 3.5 B3 Toolboard stepper intermittently running backwards:
@ctilley79 Can you post your config.g file so that we can see steps/mm acceleration PA/IS etc.
Here ya go. I’m running in SBC mode btw
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.1 on Sat Jan 09 2021 15:21:32 GMT-0500 (Eastern Standard Time) ; General preferences G90 M83 M550 P"Voron2" M669 K1 G4 S2 M955 P121.0 I01 M593 P"zvddd" F50.0 S0.1 ; Drives M569 P0.0 S1 D2 M569 P0.1 S0 D2 M569 P0.2 S1 D2 M569 P0.3 S0 D2 M569 P0.4 S1 D2 M569 P0.5 S0 D2 M569 P121.0 S1 D2 M584 X0.1 Y0.0 Z0.2:0.3:0.4:0.5 E121.0 M671 X-50:-50:350:350 Y0:375:375:0 S5 M350 X16 Y16 Z16 E16 I1 M92 X160.00 Y160.00 Z400.00 E562.00 M566 X600.00 Y600.00 Z300.00 E4000.00 M203 X16800.00 Y16800.00 Z750.00 E5000.00 M201 X3000.00 Y3000.00 Z350.00 E5000.00 M906 X1000 Y1000 E900 I40 M906 Z1100 I80 M84 S60 ; Axis Limits M208 X0 Y-3 Z0 S1 M208 X300 Y300 Z250 S0 ; Endstops M574 X1 S3 M574 Y1 S3 M574 Z1 S2 M915 X Y S1 F0 R0 H400 ; Z-Probe M558 P8 C"121.^io_0.in" H1.8 F300 T16800 A5 S0.01 ; Euclit Probe G31 P500 X2 Y25 Z7.72 M557 X20:280 Y30:270 P5 ; Bed Heater M308 S0 P"0.temp1" Y"thermistor" T100000 B4725 C7.06e-8 M950 H0 C"0.out0" T0 Q10 M307 H0 B0 S1.0 M140 H0 M143 H0 S155 T2 ; Nozzle Heater M308 S1 P"121.temp0" Y"pt1000" M950 H1 C"121.out0" T1 M307 H1 B0 S1.0 M143 H1 S310 ; Heater Pad Thermistor M308 S2 P"0.temp0" Y"thermistor" T100000 B3950 A"Heater Pad" ; Fans M950 F0 C"121.out_1" Q10 M106 P0 C"Part Fan" S0 H-1 M950 F1 C"121.out_2" Q10 M106 P1 C"Heatsink Fan " S1.0 X0.5 H1 T45 ; Case Fans M950 F2 C"0.out7" Q10 M106 P2 S0.4 C"Case Fan 1" M950 F3 C"0.out8" Q10 M106 P3 S0.4 C"Case Fan 2" M950 F4 C"0.out9" Q10 M106 P4 S0 C"Exhaust Fan" M950 F5 C"0.out5" M106 P5 S0.0 C"Bed Fan" ; Tools M563 P0 S"Extruder" D0 H1 F0 G10 P0 X0 Y0 Z0 G10 P0 R0 S0 ; Neopixels M150 X3 Q3000000 M150 R255 U255 B128 W255 P128 S2 F1 M150 R100 U0 B120 W0 P100 S1 F0 ; Defining Global variables if !exists(global.hotend_temp) global diveHeight = sensors.probes[0].diveHeight if !exists(global.bed_temp) global bedtemp = heat.heaters[0].active if !exists(global.hotend_temp) global hotendtemp = heat.heaters[1].active if !exists(global.zprobestatus) global zprobestatus = "none" if !exists(global.job_completion) global jobcompletion = 0 ; Miscellaneous ;M575 P1 S1 B57600 M501 T0
I keep PA in my filament configs
;M307 H1 R2.683 K0.418:0.000 D5.84 E1.35 S1.00 B0 V23.8 ; This is for the RayPedo M307 H1 R2.695 K0.425:0.000 D6.05 E1.35 S1.00 B0 V23.7 ; This is for the Mosquito M307 H0 R0.179 K0.105:0.000 D6.97 E1.35 S1.00 B0 M207 S0.6 F2100 Z0 M572 D0 S0.035
-
-
@Exerqtor I just read through your issue and yours may still be speed based since it seems to print certain features and not the others.
-
@Exerqtor The problem persists even with input shaping and pressure advance disabled.
-
@ctilley79 Trying to understand what is happening. If you run at F180 the motor always goes one way (the correct way?), but if you try to go faster with F300 then does it always run the other way? If you then perform a slow move is it back to normal again?
-
correct. I don't know the precise threshold, but past a certain speed the motor direction changes.
G1 E100 F180 ;motor runs forwards G1 E100 F300 ;motor runs backwards G1 E-300 F300 ;motor runs forwards again
-
@ctilley79 Does the distance make any difference? So for instance if you move just 10mm at F300 does it move in the correct direction?
-
This post is deleted! -
@gloomyandy said in 3.5 B3 Toolboard stepper intermittently running backwards:
@ctilley79 Does the distance make any difference? So for instance if you move just 10mm at F300 does it move in the correct direction?
Ok. The threshold is F254 which makes sense because thats the last integer in an 8 bit number. Extrusion distance does not matter.
-
I cannot reproduce this on my Pico based toolboards. I am at 16x microstepping to and 631 microsteps.
-
@ctilley79 said in 3.5 B3 Toolboard stepper intermittently running backwards:
@Exerqtor The problem persists even with input shaping and pressure advance disabled.
It might be the case, since i'm short on time atm. I had to revert back to beta2 this time. Hope David has time to crunch this when he gets back to the UK.
-
@oliof is your pico toolboard running 3.5 beta 3? Does the pico even support RRF? I’m confused.
-
@ctilley79 Yes, 3.5-beta.3 on the Duet3 Mini 5+, and 3.5-beta.3 on the RP2040 toolboard, which has experimental support in 3.5b-eta.
-
@oliof SBC or Standalone?
-
@ctilley79 standalone
-
My test may have been invalid since I tested with F360; I sae a report that direction corrects itself again at F327 and higher. I am now traveling so wont be able to test before Sunday.
-
@argo I'm experiencing similar behavior here
-
Yes, I also had this issue and the extruder was overall extruding a bit too much filament whilst printing. My normally calibrated extrusion multiplier set in the slicer would not work anymore.
What helped:
- Duet 3 Mini5+ reset + Toolboard 1.2 reset (via button)
- formatted the SD card and copied just the config files
- flashed the Duet 3 Mini 5+ directly over the boot loader as a mounted drive to a PC and then flashed the Toolboard over the web interface
Now the reverse running extruder issue is gone and also my set extrusion multiplier works again.
I don't know what caused the issue tbh. Maybe the countless flashings over the web interface with all the beta versions (I also flashed Klipper to it fort testing purpose) causes issues over time but that's just a wild guess on my side.