I never had this problem with the original TAZ6 firmware, but see it pretty regularly on DO… I go through the menu to replace filament, the extruder heats up, retracts existing filament… I replace it, and then no amount of pressing on the screen does anything, it’s just stuck there not able to continue. I am starting to just manually increase temperature and move the extruder instead of using the wizard lol… it doesn’t happen every time but often enough to be annoying.
Known issue? Archim 2 + aerostruder version, not the latest release, and I have seen this since switching to DO a few months ago.
If there is a problem regarding the GLCD display, it is not anything specific to Drunken Octopus. Your best bet for getting this resolved is to bring the issue up in the Marlin forums in the hopes that you can get someone to look into this.
I’ll be honest, this is not a problem I will tackle. Now a days I no longer use any LulzBot printers (my “workhorse” now a days is a SynDaver Axi) and all my Marlin development efforts are going toward the color touch panels that is used in that printer.
While I will continue to make builds of Drunken Octopus for people who still need them, but I will not do work on fixing bugs in upstream Marlin that benefit LulzBot as a company. If they want their printers to remain relevant, they should be looking into problems like this and contributing fixes to upstream Marlin.
This is probably not the answer you were hoping to hear, but I rather just be upfront about how I feel about this.
So I compared the DO code and Marlin upstream and I did find one unintended difference with it as it regards to filament change behavior. I’ve pushed a fix to this to the DO repo, to make sure the behavior is identical to upstream.
I think it may be a far shot, but there is a small possibility that this could correct the issue you’ve been having. The fix will be in the next DO release.
Thanks for taking a look, especially despite saying you won’t!
Hey, so you mentioned GLCD, can the fact that I have SD_SPI_SPEED = SPI_FULL_SPEED be causing this? You did mentioned Lulzbot turned that way down due to problems, I figured that setting could only affect what’s displayed, not the spinner wheel input… I will experiment lowering it and see if the problem goes away.
@glebbb: Yeah, I wasn’t going to spend time troubleshooting this if it was an upstream Marlin issue, but I periodically review the DO code against upstream to make sure there are any changes I made which need to be pushed upstream. In doing so, I noticed some code differences in the filament change routine that ought to not have been there (they were probably remnants of earlier work related to the color LCD)
Give r36 a try and see if fixes the issue. It should behave exactly like upstream now. If there is still a problem, then it probably ought to be reported there.
I don’t think SD_SPI_SPEED would affect this at all.
I just posted about the same problem with my taz 5. And it only started doing it a day or two ago. But I have one old pla that works fine. Mine will extrude for a few minutes then stop extruding.