As described in the link I posted to the issue in Marlin upstream. If they run "M504" to verify the EEPROM, the runout distance will change to some random number.
Most probably won't, but to those that do, how does it manifest?
I already made a PR for a fix, BTW: https://github.com/MarlinFirmware/Marlin/pull/14661
Most probably won't.
How will end users see this issue?
Mon, Jul 15
The reason it says "TAZ Workhorse printing..." is because this is in the start GCODE.
Updated to .144
Fri, Jul 12
Please review .144
@marcio I think I like "TAZ Workhorse Ready" as long as it is all spelled correctly. =)
No preference. Whatever you think looks good.
@karrad: I will enable scrolling regardless (this was actually broken in Marlin upstream, so I fixed it), but still do we want to use the full "LulzBot TAZ Ready" to scroll? This is the first thing the user sees, so maybe it should be short enough not to scroll?
Scrolling sounds great! Didn't know it was an option.
@marcio I like the scrolling option myself to allow full names/M117 messages
@karrad: Also it looks like there is an option to scroll the status string. I will enable this. Would you prefer to see a non-scrolling "TAZ Ready" or a scrolling "LulzBot TAZ Ready"?
@karrad: "LulzBot TAZ ready" would still only show up as "LulzBot TAZ read" in the display, so I will have it read "TAZ Ready" instead.
Yes, I think it is the start gcode. Sorry, didn't notice this was a marlin related code ticket.
Thu, Jul 11
@eBeardslee We will need more information on what the printer is doing, but I suspect that is start gcode change not marlin. let us know where/when you are seeing it
@marcio Also, "TAZ Workhorse Printing" is cut off. Can we shorten this to "TAZ Printing"?
Wed, Jul 10
@marcio i am no longer seeing the issue with the continuous run button causing the freeze and thermal runaway on .141
As of fw 18.104.22.168, this appears to be fixed. Instead of restarting, it switches back to extruder 1 and returns to the home screen.
I suspect it this particular failure may be related to T5686. This is an old bug, where we were occasionally seeing printers failing during probing.
Were you printing from USB or Cura?
@marcio will do!
There are nozzle changes as the printer levels the bed.. so yes
@DaniAO: The filament change issue should be solved in .141. Let's make sure everyone is using that version to make sure we are all on the same page.
@DaniAO: Please have everyone upgrade to .141 to make sure we are on the same page.
By any chance did this happen after a nozzle change?
T8614 was created for that.
@DaniAO: Actually, if it happened at the start of the print, and not in the change filament screen, then it is possibly another issue and should be put in another ticket.
@DaniAO: I pushed .141 that should fix the issue. It should be done building in about 10 mins.
FYI- Just had the LCD freeze and printer keep heating while it was heating the bed to start a print.....
@marcio Flashing through Cura LE, I left the update EEPROM checked but did not manually restore failsafe.
Unable to reproduce this. Did you do a factory reset?
Testing the new firmware @marcio sent me, I have had 5 timeouts and 0 restarts or freezes. During my 139 and 135 testing I got 0 timeouts.
@marcio: My machine rebooted most of the times, but it froze once. I think I identified the issue however and sent a new FW to @samantha and @tutley to test out. If that initial test checks out, I'll push a new build to buildbot.
I just repeated the same steps as my last post, but on 135 instead of 139, and this time the machine reset itself instead of locking up.
i can confirm this is not happening on .135
I just froze on the change filament screen, extruder 2 heated, running continuous. 139, production unit. was holding steady at 220 prior to freeze, thermal runaway occurred after freeze.
I was able to get the machine to freeze and then over heat by heating both nozzles, being on E2 in the change filament page, and having it run continuous for about 2 minutes
Change filament > heat nozzle 1 up and then the LCD froze. Of course now that I am trying to recreate it I can't.. but we did have it happen on 2 separate machines- but both are betas.
can you explain how to repeat this?
Tue, Jul 9
This happened to me last night. I thought maybe there was just a timeout and it purposely had gone back the main screen, but I'm guessing it was rebooting. This has happened twice to me that I remember.
Tue, Jul 2
@karrad: I'll check. At the least, I could probably gray out the filament change option when the printer isn't paused.
@marcio Would we be able to send the pause command before using change filament via the LCD?
Mon, Jul 1
@alexei: Marlin .137 is built. Buildbot now needs to be updated to copy the files. And those files need to be added to Cura.
Due to the fact that these are all universal toolheads, I am now building all the following FW variants:
Fri, Jun 28
I'm reaching out to reseller user for more information on this. We've not been able to reproduce this on the betas in house that we've tested.
Tried the new nozzle offset calibration. Was almost spot on and getting amazing prints! I did have to make a minor 20 micron adjustment on the X to get it perfect but this was likely due to a dirty nozzle.
Tue, Jun 25
@marcio do you mean a dual v3? This is on redgum and does not have a standard dual.
@adam: I took the tool head to X293 Y-16 and it looks like it is 3mm too far forward and 2mm too far left. X295 Y-13 drops it right on on the bolt.
The prototype also ran auto-calibration fine. It was not perfectly centered on the block or the wiper pad, but good enough to clean the nozzle and complete the calibration.
@marcio I took the tool head to X293 Y-16 and it looks like it is 3mm too far forward and 2mm too far left. X295 Y-13 drops it right on on the bolt.
I ran auto-calibration and (besides landing on the cube too far to the back left) it completed with no issues. I will run with my prototype as well.
@nathan @Bobby4wd @Greggb please flash your redgums to 22.214.171.124 and run the auto-calibrate found under the LCD>movement>auto-calibrate. Please post any issues here.
Mon, Jun 24
@anolen I have not seen any other reports, we can go ahead and close this down. If another instance occurs, please open a new ticket.
Has anyone using a mini seen this recently? Hanna hasn't had any LCD freezes since she started working with 2 minis that have newer FW. (about 3/4 weeks of daily printing)
Fri, Jun 21
@adam: Check the whether the coordinate system is good. Take the toolhead to X293 Y-16 and lower it to the washer. It should be *exactly* on the center of the right front washer. If it does not fall in the exact center, then the coordinate system is off (either due to a mechanical problem, or something else)
We have this implemented in 126.96.36.199 FW and incorporated into cura 3.6.11. closing this one out.
Just an update here, this is with 188.8.131.52 FW
The location in the commit above worked well, closing this out.
Thu, Jun 20
On my beta Pro, I flashed .135, upgraded to Cura 3.6.11, used existing production fan shroud, ran the automatic nozzle offset and printed the following calibration print using standard PLA profiles (except .25mm layer) - without any tweaks. Black is left over burned residue from previous. Best print yet!
Wed, Jun 19
My thought process behind the not even allowing calibration to run if the filament sensors detect filament
For best results, remove filament
and clean hot-end prior to starting
@Greggb @nathan @DaniAO @adam Lets get a test on .135 as well, we had an update to the LCD screen message telling people to remove filament before running the offset calibration. It should be the only change, but we would like to verify.
@marcio Looks good to me, maybe "continue" instead of proceed, it seems a little more LCD
Hmm, maybe just one more line of text.
Well, we are currently limited to three lines of text. That's quite a lot more... I can try fudging it to support more lines, but I don't most people will even read that, to be honest. TL;DR.
Current wording is:
There is a dialog box that shows up before calibration starts. That text can be customized since it's not standard Marlin.
@marcio Do we have room on the LCD for a message, or perhaps a pop up stating "Offset calibration works best without filament loaded." or "Unload filament filament before starting offset calibraiton, proceed? Y/N"