Firmware for LulzBot 3D Printers.
Tue, Aug 20
Wed, Aug 7
@hanna: Do you mind re-testing with .149?
Tue, Aug 6
Mon, Aug 5
Thu, Aug 1
Wed, Jul 31
@marcio Tested under m.148, auto-calibration completes successfully and data is saved.
@oliver What version of the firmware are you currently flashing?
Tue, Jul 30
@Steven We have removed the "update EEPROM" checkbox by default for redgum and quiver. This should help prevent customers from clearing calibration data, and would not make this as pressing of a release as current changes.
@Steven: You may want to review this document with the draft FW release process https://code.alephobjects.com/diffusion/MARLIN/browse/devel/docs/lulzbot_marlin_development_process.odt
@Steven: The latest version, .148, will have the fix. However, if we do not want upstream changes in the next release, then we will need a new release-candidate branch for the .144 release.
Mon, Jul 29
@marcio Thanks for the info, we appreciate it.
Absolutely, as soon as my workhorse is done with the print it is running.
Only in the GLCD products, not TAZ Pro or the Bioprinter as the color touch panel does not have localization capabilities.
Fixed in .146 and above.
@logan: Could you retest this under .148?
@marcio yes, this request is specific to quiver. For now, I recommend leaving all other machines' default values as-is.
This is for Quiver, correct? Do we wish to leave all other printers with a default of zero?
X and Y offsets:
Here are the averages for all the printers on .135 fw
Sat, Jul 27
Fri, Jul 26
Thu, Jul 25
Okay. My fault entirely. I tested a fix and confirmed it worked. But that fix introduced a problem when I tried compiling for Quiver, which is a 32-bit boards, so I tweaked my fix for Quiver prior to pushing .147, but never actually tested it again on Workhorse. It turned out the tweak actually rendered the original fix ineffective.
@marcio do you mean a dual v3? This is on redgum and does not have a standard dual.