Random overshoots and stutters in X and Y axis on Duet 3 mini?
-
After having had a very long week of figuring out a lot of other issues after basically remaking a printer, I've finally been able to start printing actual parts again but just ran into an odd issue.
This happened in 3 separate instances that I have seen so far, and potentially more when I am not nearby.
Issue 1: An X or Y move will overshoot a turn it was supposed to make by about a cm or two while extruding, then go back to where it should have turned and will continue on as if nothing had happened, but will leave this random plastic tab sticking out wherever it occurred. I have only noticed it in corners so far, or what appears to be a corner to my eye. Sometimes it happens in the same layer side by side in the walls, or sometimes in the same spot also in the next layer or two.
Example: X axis should move 100mm while extruding, then the Y axis should move 100mm at the end of that move. What happens is the X axis will go 110, then back 10, then do the Y axis move.
Issue 2: When an axis is moving (again in a straight line) it will stutter the whole way down, or stay in place until it should have finished, then travel to the next point and continue as if nothing happened. On one occasion it bounced back and forth a few mm while extruding, then stopped extruding and traveled to the end of the line before continuing as usual, but with a blob in one corner and no filament in the wall path after it until it got back on track.
Examples: X axis should move 100mm then Y axis 100mm while consistently extruding. What happens is it will do one of two things, seemingly randomly (but repeatable with the same .gcode, or even same stl):
-A. X axis moves forward 3mm, back 1mm, forward 3mm, back 1... until about 75mm, then will stop extruding and move to the end of the X move and start the Y as if nothing happened, leaving an over extruded pattern the first 75mm, then nothing the last 25.
-B. X axis moves forward 1mm, back 1mm, forward 1mm, back 1mm, until I assume it thinks it went 100mm, leave a blob, and then move to the end of the move before starting the next line on the Y axis.With all of these, there haven't been any layer shifts, or really anything that significantly affects the finished print, except the extra tabs that need to be pulled off, or a blob/missing line somewhere. However, it is incredibly annoying and I would rather not have to worry about this kind of thing if possible.
I put the .gcode files into a few online analyzers to see if those moves show up as an error in the slicer (Cura 4.10.0, MacOS) but aside from everything looking funny in those viewers, nothing looked like my issue. Reading the files didn't show that as "intentional" either, so that leads me to think that I either missed something in the .gcode file, or the Duet board sees a particular move or variables and interprets it the wrong way.
My setup is more or less a stripped Ender-3 Max frame and steppers, a belt driven Z mod, and a Bondtech LGX Flexibles direct drive all tied into a Duet 3 Mini, which so far has worked very well. I am on the most recent stable firmware and DWC 3.3, if it helps. If any of this seems familiar, I would be very glad to get some help as I haven't found anything like this online yet. If requested I can try to get some decent pictures of this soon.
Thanks!
-
@praisetheesun Very odd. Can you post your config.g, and a gcode file that exhibits the problems?
Ian
-
The results of M122 after it's done these things might be helpful as well.
Also a video or photo of the problems you're describing.
I can't think of any reason why it would over shoot by 10mm and then return to where it was supposed to unless that's exactly what the gcode commanded it to do.
-
@droftarts Sure, I'll put images and videos along with the gcode files and config in a separate response. I also noticed that for some reason I had the ArcWelder plugin setting "G90 influences extruder" set to true (I used to be on Marlin and must have loaded an older slicer profile) in the first print I had with the blob; I am not sure if that is the cause or not, but unchecking that and changing the orientation and removing the raft didn't have a blob in the second print.
-
The images with a raft are from the first print, which had the overshoot and a blob (circled in red), and the rotated one without a raft is the second print after unchecking "G90 influences extruder." I also noticed now after having looked at these, the blue line exhibits a potentially related issue of not moving at a consistent speed before getting near the end, shown with the red line. Also a little bit of overshoot after the red line.
Apologies for not the image quality, my phone is not great at focusing up close.
These are the gcode files and config. I made the config with the tool online with 3.2.3 a few days before 3.3 was released, but I upgraded and kept the same config, which didn't seem to have any issues but I am sure there's something in there that should be changed.
The FanHolder gcode file is the first one with the blob and overshoot, the FanMountV2 is the second one with seemingly just the overshoot issue. It had a much better overall print quality as well, but will still need to be tweaked for correct hole dimensions and such anyway.
FanMountV2.gcode FanHolder.gcode config.g
And here are two videos showing the issues happen on a print of the first gcode a second time (Before I noticed the G90 issue).
https://youtu.be/eFk9ngwve5c, https://youtu.be/eFk9ngwve5c -
@phaedrux I will attempt to get an M122 there next time I notice it, but I haven't had the chance to reprint it yet.
I am unable to upload the video files because they are too large so I will upload unlisted to YouTube and then post the link in an edit to my other post with the images as soon as I can.
-
I'm not sure familiar with Arc welder, but have you tried without it yet?
-
@phaedrux That's the next thing I am going to try once I get home, I haven't had a problem with it in the past, but it might not be as compatible with RR as it is with Marlin. Theoretically it shouldn't have an issue, but I suppose thats when most issues and bugs occur. I also haven't gotten Pressure Advance dialed in correctly yet, perhaps that may be affecting something as well. So I have it set to 0 in the config. Is that any different than having it not set at all?
I also have the two videos linked in the other post now
Thanks for the help so far!
-
So After having ran a print with Arc Welder off entirely, it seems to not have either of the issues, but it didn't always have it with it on before, so it might just be a coincidence. Unless it happens again, I will tentatively say that the plugin I was using was the cause of those issues. Only downside now is the file sizes having doubled and not utilizing the G2/3 commands. Time will tell if I will miss this or not!
Thanks all, hopefully this is solved!
-
There are others here that use ArcWelder successfully (I think), so maybe there is something there that we are both missing.
-
@praisetheesun said in Random overshoots and stutters in X and Y axis on Duet 3 mini?:
@droftarts Sure, I'll put images and videos along with the gcode files and config in a separate response. I also noticed that for some reason I had the ArcWelder plugin setting "G90 influences extruder" set to true (I used to be on Marlin and must have loaded an older slicer profile) in the first print I had with the blob; I am not sure if that is the cause or not, but unchecking that and changing the orientation and removing the raft didn't have a blob in the second print.
You should definitely uncheck "G90 influences extruder" for RRF. Leaving to checked might well cause excess extrusion.
-
@dc42 Thanks for that confirmation, I initially turned it off when I switched but never noticed it back on when switching profiles, so I just assumed it wasn't helping things.
I ended up just disabling it overall for several prints and haven't noticed a drop in quality for those so far yet so I am pretty happy with that. Once I get everything else dialed in I will likely attempt to start using it again after more research.
-
what's the idea behind Z-axis without microstepping, but then only have 25 steps/mm?
M350 X16 Y16 Z1 E32 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z25.00 E842.00 ; set steps per mm
It's probably not related to the issue, but might not be the best solution...
I was wondering, if your slicer shows any errors related to the .stl file?
Or do you have a small wipe tower enabled that would cause the overshoot thing?