I had previously modded my Ender 3 to use the FreeABL for auto bed-leveling.
This requires compiling and uploading a custom version of Marlin firmware with AUTO_BED_LEVELING_BILINEAR enabled. Since this takes quite a quite of extra storage, it requires SLIM_LCD_MENUS to be enabled. This removes the function to configure E-steps from the control panel.
So the other day, I started poking around to see if there is a way to fit both AUTO_BED_LEVELING_BILINEAR and SLIM_LCD_MENUS in the limited storage on the plain-vanilla Ender 3. After much research and tinkering, I am glad to report this is indeed possible. Here are 2 links I found most useful in helping me achieve this objective:
- Reducing Marlin firmware binary size to fit in your 3D printer board memory
- Table of Marlin 1.1.9 configuration options memory sizes
I use PlatformIO to compile the Marlin firmware (2.0.6.1) using the melzi_optimized profile:
which essentially uses the build parameters mentioned here:
build_unflags = -g -ggdb build_flags = ${common.build_flags} -fno-tree-scev-cprop -fno-split-wide-types -Wl, --relax -mcall-prologues
The following features were modified from the default Ender 3 Configuration.h file:
//#define STRING_CONFIG_H_AUTHOR //#define SHOW_BOOTSCREEN //#define SHOW_CUSTOM_BOOTSCREEN //#define CUSTOM_STATUS_SCREEN_IMAGE //#define SPEAKER
#define S_CURVE_ACCELERATION
#define MANUAL_PROBE_START_Z 0.2 #define FIX_MOUNTED_PROBE #define NOZZLE_TO_PROBE_OFFSET { -45, -5, -5 } #define AUTO_BED_LEVELING_BILINEAR #define RESTORE_LEVELING_AFTER_G28 #define GRID_MAX_POINTS_X 4 #define EXTRAPOLATE_BEYOND_GRID #define Z_SAFE_HOMING #define DISABLE_M503
//#define LCD_INFO_MENU //#define ARC_SUPPORT
RAM: [=== ] 30.6% (used 5007 bytes from 16384 bytes) Flash: [==========] 98.1% (used 127580 bytes from 130048 bytes)
The new firmware didn't like the old config values, so the settings had to be initialized. There were basically 2 operations that needs to be performed from a fresh setup like this:
- Probe Z-offset
- Auto bed leveling
Probe Z-offset
Z-offset is the distance between the print bed and the nozzle when the ABL probe is engaged. Another way to look at it is that when the ABL probe is disengaged, the Z-offset is the distance that the nozzle needs to travel down so that it just touches the print bed. Therefore if the Z-offset is set too high, the nozzle will dig into the print bed and leave scratch marks on it as it moves, as I had the privilege of finding out! So set the Z-offset to as low as possible to get the first layer to stick, and not any higher.
Finding the Z-offset requires some work on the user's part. First, select Menu > Motion > Auto Home. This will move to print head to the center of the print bed and lowers the print head until the ABL probe engages.
Now disengage the ABL probe and move the nozzle to touch the print bed using Menu > Motion > Move Axis > Z Axis. Move using the 1mm interval initially until the nozzle is almost touching the print bed, then insert a piece of paper between the nozzle and the print bed. Switch to using 0.1mm interval and continue moving the nozzle downwards until you can just feel drag when you move the paper.
Remember the current Z-axis value (eg. 0.2mm). Now select Menu > Configuration > Probe Z-offset, which will show you the current Z-offset value (default -5mm i.e. last value of NOZZLE_TO_PROBE_OFFSET). To get the new Z offset, simply add the 2 values toegther (eg. -5mm + 0.2mm = -4.8mm). Adjust and set the Z-offset value, and remember to store it using Menu > Configuration > Store settings.
Select Menu > Motion > Auto Home again with the ABL probe engaged, then disengage the probe and test again by moving the Z-axis. Now when the Z-axis is at 0.0mm, it should just touch the print bed and introduce the same drag on the piece of paper.
Auto Bed Leveling
The auto bed leveling option is found under Menu > Motion > Bed leveling. Since I have defined GRID_MAX_POINT_X to be 4, the firmware will automatically perform bed leveling by probing 16 points (4x4) on the print bed. This part is pretty straightforward.
Comments
Post a Comment