Firmware for LulzBot 3D Printers. Source code is here.
Wed, Jun 21
Fri, Jun 16
May 4 2017
Mar 8 2017
Feb 1 2017
We've seen what I'm pretty sure is a manifestation of this bug on the mini line, they've seen 2 units that stopped sending the bed forward halfway through the final movement of a print. This is only happening when the right print stackup causes the x to tram upwards as it runs toward the x-max position while it's spitting the bed forward, and all movement stops when the z-max switch is hit. So far I haven't heard of any reports from customers on this.
Jan 31 2017
Jan 27 2017
Jan 17 2017
That makes good sense and a bit more helpful for the customer. I added the recommendation to steps 20C and 20D
Jan 16 2017
So just a bit of clarification because I was talking with Robert and I see this issue as well. For the Dual extruder:
Dec 29 2016
Dec 28 2016
Nov 22 2016
Jul 15 2016
We are not supporting installing TAZ 6 FW on older TAZ machines. The Palm firmware will likely have this issue resolved though.
This will actually need to be done in the profiles; simply home X first (G28 X), move X by the clearance distance (G0 X##), then home Y and Z (G28 Y Z).
The comment should say 2^16-1. The fans are actually being pwm'ed at a frequency of ~244Hz, this actually produced the best results from our testing. Take a look at planner.cpp L552 to see how we did the translation.
Jul 12 2016
Jul 11 2016
Jun 29 2016
After testing, Cura doesn't need any changes whatsoever.
The thermal runaway protection string will be "Thermal Error E1", "Thermal Error E2", "Thermal Error Bed".
The heating sanity check protection the string will be "Heating Failed E1", "Heating Failed E2", "Heating Failed Bed".
Jun 22 2016
What would Cura need to do when this happens?
Jun 5 2016
May 24 2016
This commit implements these changes: https://code.alephobjects.com/rMARLIN772d2498c572da02b8419495706f713bae85ede2