3.5 B3 Toolboard stepper intermittently running backwards
-
It seems it only temporarily fixed the issue. I just startet my printer for the first time since I was able to successfully print a Voron test cube and when inserting filament via PanelDue the extruder runs backwards at 5mm/s and forward at 10 mm/s when commanding it to extrude. With other words the bug came back
-
-
and another 12h print completed without issue. Really weird.
-
@oliof
Yeah like i said in my thread, it seems totally sporadic. -
@Exerqtor well, I have one gcode file now that seems to stop at a certain point to just extrude, and another that runs for 12 hours. On monday I will have a couple hours to try and find a reproducer.
Out of interest, are you using slicer or firmware retract?
-
@oliof
I'm using FW✌ -
I am having the same issue withe B3: When trying to print a test for measuring pressure advance the filament gets retracted so far that it even leaves the extruder gears after printing some lines. It is always happening at the same position when trying to print the following gcode:pa_pattern.gcode
-
@mule Can you identify at which point it goes into reverse? Layer height or whatever? Having your config.g file would also be good if anyone needs to reproduce this.
-
@gloomyandy You don't need to be in a print for the problem to occur. You can just manually extrude from the DWC console or the extrude buttons on the DWC dashboard page. I thought the the threshold was F254 but now it seems to vary.
-
@gloomyandy
Some of my findings:
Nr. 1: The purge line is not being completed because the extruder runs backwards after printing about half of the line
Nr. 2: Line is not being printed because the extruder runs backwards
Nr. 3: The extruder motor stands still and neither moves forward nor backwards. Therefore no filament is being extruded until the end of the whole print job.Findings: There is not only an issue with retracting instead of extruding but also with a complete stop of the extruder motor. Looking at Nr. 1 and Nr.2 it seems to me that the extruder runs backwards whenever the y axis is moving from the front to the back (Y increases).
Hopefully this helps.
-
@mule That's very useful, but anyone trying to reproduce it really needs to see how you have things configured, so please post your config.g file (or whatever you use to setup things).
-
@gloomyandy Sorry, of course you're right. Please find attached the the config.g and the macro (PrintStart.txt) including the code for printing the purge line:
config.g
PrintStart.txt -
@mule
Is there any way you can try your extruder on a different driver?
I only say because I have had a driver fail that was randomly missing steps and only running in one direction
https://forum.duet3d.com/topic/28666/motor-travels-in-one-direction-regardless-of-command/4?_=1682994512366 -
@OwenD I like your thinking but its quite unlikely that we are seeing a mass death of drivers on various toolboards of different makes and models.
-
@OwenD It is not a defective driver, because if downgrading the firmware to v3.4 everything is working fine again.
-
@OwenD It's not a failure of a driver because rolling back to 3.4 fixes the issue
-
@gloomyandy I'm not trying to bug you but I'm just curious. Have you been able to reproduce the issue?
-
@ctilley79 Not exactly, I've been running a lot of general extrusion tests on my e3d toolchanger comparing two different toolboards (a 1LC and a prototype rp2040 based one) against a tool driven directly from the main board. I've seen some extrusion issues with both the toolboard based tools and with the directly driven tool, though they seem to be slightly different. In both cases I have only seen a problem when using both PA and IS at the same time. I've passed on my results to DC42 and hopefully he will be able to investigate further. I don't think I've seen the extruder running backwards in any of those tests.
-
@gloomyandy Not running backwards is one thing, but have you gotten it to just stop? The extruder i mean, Intermittently and then start again by itself?
-
We are aware of and looking into this issue. I'll create a github issue for it today hopefully.
And many thanks to those doing the excellent testing and reporting here.
