Releases · th3dstudio/TH3D-Unified-U1.R2

06 Feb 03:15

houseofbugs

U1.R2.A3

995918e

U1.R2.A3 - Release

New Printer Support

AnyCubic Mega Zero
- EZABL Supported only with CUSTOM_PROBE option. OEM mount coming in the future

New Features/Improvements

All machines now have parity with Restore EEPROM menu for ease of use

Assets 2

23 Jan 00:49

houseofbugs

U1.R2.A2

9a4010a

U1.R2.A2 - Release

New Features and Tuning

Added MOUNTED_FILAMENT_SENSOR & DIRECT_DRIVE_PRINTER options
Updated load/unload speeds for quicker loading/unloading of filament
Set Ender 5 Plus to MOUNTED_FILAMENT_SENSOR by default to prevent filament from backing up in the sensor.
Set CR-10S Pro to MOUNTED_FILAMENT_SENSOR by default to prevent filament from backing up in the sensor.
Set CR-10 V2 to MOUNTED_FILAMENT_SENSOR by default to prevent filament from backing up in the sensor.
Updated EZABL sensor options for Ender 5 Plus and added Link for LCD conversion info
Made thermal protection more accurate and less aggressive
Updated Ender 5 Plus settings to be inline with U2.R1.X options

Assets 2

19 Jan 22:53

houseofbugs

U1.R2.A1

c4a98a9

U1.R2.A1 - Release

Update to new version numbering system

Version numbers ending with a upper case letter followed by a number (ex: U1.R2.A1) notes that the G28 Restore feature is disabled for easier validation of firmware version in use.

Any versions older containing only numbers and/or lowercase letters should not be used (example U1.R2.10, U1.R2.21a, etc) if you are using any type of ABL probe.

Why is this change occouring?

Versions before U1.R2.3 and before U1.R2.A1 have RESTORE_LEVELING_AFTER_G28 which has a bug that will not be patched due to Marlin development focusing on 2.x.
This U1.R2.XX branch is based on Marlin 1.1.9 with 1.1.x-bugfix patches along with our own patches
Disabling this extraneous feature fixes what users describe as their "Zoffset drifting" when using an ABL probe (BL Touch or EZABL).
Once time allows we will eventually retire the U1.R2.XX branch and move all configs/printer support to our U2.R1.XX branch for these 8 bit board based machines

What did the bug in the RESTORE_LEVELING_AFTER_G28 do?

Due to how this feature re-applies the mesh data to the machine after a G28 is run it will skew the Z height and cause what users referred to as "drifting" of their Z Offset. This amount would vary based on the accuracy of the probe being used and the machine condition.

Steps to reproduce the bug in the old firmware versions:

After starting the printer up send a G28. Note that Z shows 5
Start a print with G28 followed by G29 in the starting code OR by using a stored mesh/UBL
After the print starts cancel the print
Home all again (G28)
Notice that the Z now shows not 5 but a different number (example: 4.95)

This difference in the Z height will compound and eventually mess with the Z Offset requiring adjustment on every print. Disabling the RESTORE_LEVELING_AFTER_G28 fixes this issue and has been disabled in the U1.R2.A1 release.

Other Changes

Update Junction Deviation default Value (changed from 0.02 to 0.013 per Marlin 1.1.x/Marlin 2.x defaults

Assets 2