Hi… Sorry this may be a newb question… I’ve had such good luck with my Lulzbots but I’m running into a bit of a quirk at the moment on two printers that have barely any use on them.
I have 2 Lulzbot TAZ 5’s they are like straight new out of the box, I’ve never updated the firmware, they are running 1.0.0.1…
Both worked fine for months and then both now have ERR: MINTEMP
(ERROR)Specifically:
(Shows the logs are seeing 0 temp although on the LCD screen shows around 8c for both bed and print head.)
* Recv: ok T:0.0 /0.0 B:0.0 /0.0 T0:0.0 /0.0 @:0 B@:0
* Recv: Error:0
* Recv: : Extruder switched off. MINTEMP triggered !
* Changing monitoring state from ‘Operational’ to ‘Error: 0: Extruder switched off. MINTEMP t…’
What I’ve done on Both printers:
* I’ve swapped the print beds,
* I’ve swapped out Print Heads
* I’ve swapped out Cabling bundles from the control box to the print head…
* I even tossed on a Moarstruder on one that is new brand new no issues and ERR:MINTEMP
* Warmed up the existing print head with my head to see if it would flip, but nada
I’m sure I’m missing something but I’m too warpped up into this to see. Just at a loss on what to do next and looking for a few tips… Really would like to get one or both of these back up and running.
Thank you for any help.
Justin
What is the temperature showing at idle when you turn it on? 0? 19?
Does the reported temperature on the LCD raise when you tell it to heat up?
Hi… Thank you for your reply as I’m a bit at a loss on next steps. Both printers register a temp for the nozzle and the bed via the LCD screen. But if you say tell it to heat up to any degree, the value shown on the LCD for target temp is always “0” like it won’t process the command because of the MIN-TEMP error.
Printer 1 shows: Nozzle (7) Bed (7)
Printer 2 shows: Nozzle (20) Bed (19)
If you put your hand over the nozzle for a few minutes it will cause the temp reading to raise a few degrees.
Thanks, Justin
Printer 1 might have the wrong thermistor installed, which would definitely cause issues with properly tracking heating. Unless you’re running it in a very cold room and the other in a normal-temp room.
But first thing I’d do is to get the firmware up to date, and see if they register temps properly.
After that, you can start looking into failed thermistor/heater or faulty wiring.
So updated one of the two printers to the latest firmware for the Taz 5 v1.1.9.34 … Stinks because when on v1.0.0.1 you can still access the menu system, but now can’t. And now I can’t connect to the console to view times out. Still the same error: E1 Err: MinTemp - Printer Halted. I have swapped out the print head assembly and the nozzle wiring from the black side box to the print head nozzle to no avail. still same error.
sad but since updating to v1.1.9.34 I no longer can see temps since it gets stuck on the error on the main display.
Thoughts? or just start replacing more parts?
Can you do a video of the attempt, showing the screen? Terminal output as well if you’re connected to a computer.
here is a quick video of the issue - I connected via USB tried pronterface and won’t connect… When I try and connect with CURA 3.6.3 or any version of Cura below that, it will try to connect but never send anything to the console when I have that screen up.
I spoke with Lulzbot support / sales they obviously don’t do anything with TAZ5’s but want to upsell… But the one rep mentioned using the TAZ5/6 adapter and adapting a new print head to the printer. Which I thought heck I have all that and never used it so I unboxed all of it and connected but same E1 ERR: MINTEMP issue which is random. I also found i had a brand new cable bundle to go from the Main box to the extruder and swapped that out as well, but again no luck.
image attached of console output from Pronterface
Are you certain that it’s COM7?
I haven’t run the RAMBO board for a while but IIRC, it’s 250000 baud.
ok yeah the default for some reason on Pronterface came at the 115k baud and I switched down to 56k, once I went up to 250k I was able to connect and see the printer halted error but then it didn’t seem to take any commands after that. When I’d try to issue a temp status command or reset printer command etc it would just sit at sending.
I kind of feel its something that maybe got tripped I used these two printers in the same spot and they worked great until some random unknown sequence and I came down and the printers have the same issue and I can’t seem to get past it to get them back up and running…
Thank you in advance for all your assistance so far really trying to bring these two back up as they really don’t have many hours of printing on them maybe 100-200hrs max.
