I've been trying to get ABL working on the Cheetah for the past week. I own an Ender 3 and a BL Touch, I had this working on the Creality 1.1.4 board running Marlin 1.1.9 perfectly before installing the Cheetah. My startup GCODE was successfully enabling ABL and initiating bed levelling during a print on my Creality board.
After I installed the board I used the BLTouch config folder from GitHub, I followed the BL Touch With Cheetah on Ender 3 post to make sure my wiring was correct, and that there was nothing unusual I had to adjust for.
I found that I had to enable a method of bed levelling in Marlin as 'G29' was not recognised when sending commands via Octoprint. So I enabled Bilinear bed levelling in 'Configuration.h':
#define AUTO_BED_LEVELING_BILINEAR
This was better as now it would recognise G29, probe the bed successfully and store the value. I was able to read the mesh with an M503 just fine but when printing however there is no movement from the Z motor.
Bed levelling is turned on, M503 reveals ‘M420 S1 Z20.00’ and my GCODE was unchanged so I knew it at leats worked under Marlin 1.1.9.
I followed Teaching Tech's tutorial on setting up the BL Touch under Marlin 1.1.9 as this was the tutorial I had successfully used to get ABL working on the Creality 1.1.4.
I added everything except #define SERVO0_PIN 27
as we have a dedicated connection on the Cheetah.
The machine will level the bed but it still will not adjust during printing.
I've also tried different GCODEs in case Marlin 2.0 prefers a different startup code with no luck.
If anyone has ABL adjusting the Z axis during print how have you gotten this to work?
No matter what configuration file I use it does not seem to adjust during printing. I have also used the latest configuration files form GitHub, as of today, with no luck. I'm not sure where to go now.
Here's a link to my config files on GitHub if it helps.
--
This issue may seem similar to that posted here but I've not had a repose and need some further help on a specific issue related to ABL which is why I've created a new discussion.