[BUG]G29 don't work for Ender3 v4.2.7 board

[kinlougha]

Did you test the latest bugfix-2.1.x code?

Yes, and the problem still exists.

Bug Description

The G29 command for bed leveling won't work in release 2.1.2.2, 2.1.2.3 and 2.1.2.4.
My setup was Ender3 with Creality v4.2.7 board with a BLToutch sensor and config BILINEARLEVELING.
When I issue a G29 gcode, the probe go to the first position (ie: 25,25) , go down slowly, toutch the bed and stop.
We have no error message on the Ender3 display but on serial terminal (pronterface connect on com port) I have this message:

"Error:Probing Failed"

Everything work fine in 2.1.1.1. but I have the same behavier in 2.1.2.2 true 2.1.2.4

Bug Timeline

New

Expected behavior

A working g29 gcode

Actual behavior

Print stop on G29 gcode

Steps to Reproduce

Issue a G29 gcode in gcode file ou on serial terminal ou on the command pannel.
Configuration_File_2.1.1.1.zip
Configuration_File_2.1.2.2.zip
Configuration_File_2.1.2.3.zip
Configuration_File_2.1.2.4.zip

Version of Marlin Firmware

2.1.2.2 - 2.1.2.3 - 2.1.2.4

Printer model

Creality Ender-3

Electronics

Creality v4.2.7

LCD/Controller

Stock 12864 Ender LCD

Other add-ons

BLTouch

Bed Leveling

ABL Bilinear mesh

Your Slicer

Cura

Host Software

None

Don't forget to include

• A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

No response

[thisiskeithb]

Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information:

• Download Marlin bugfix-2.1.x to test with the latest code. You will need to port your config/settings to this version.
• Enable DEBUG_LEVELING_FEATURE and M114_DETAIL and re-flash the firmware.
• Connect to your printer from host software such as Pronterface, Repetier Host, or OctoPrint.
• Send M502 and M500 to ensure your Configurations are applied.
• Issue the command M111 S247 to enable maximum logging.
• Perform a G28 to do your standard homing procedure.
• Do a G29 to probe the bed. This will also enable bed leveling.
• Do some of the moves that revealed problems before. Take notes.
• Copy the log output into a .TXT file and attach it to your next reply.

Repeat this procedure, if needed, to demonstrate inconsistencies. From these logs we should hopefully get a better idea of what's going on with your machine.

[kinlougha]

Hello, I have a problem with bugfix-2.1.x , I can't config my probe offset, it was at -45,-10,-4.65 but at compilation I have this message:
In file included from Marlin\src\HAL\STM32../../inc/MarlinConfigPre.h:37,
from Marlin\src\HAL\STM32../../inc/MarlinConfig.h:28,
from Marlin\src\HAL\STM32\HAL.cpp:26:
Marlin\src\HAL\STM32../../inc/../core/macros.h:243:41: error: static assertion failed: NOZZLE_TO_PROBE_OFFSET.x must be within -20 and 235

If I put my offset at -20, -10, -4.65, on the g92 the probe is outside of the bed.

[thisiskeithb]

NOZZLE_TO_PROBE_OFFSET.x must be within -20 and 235

What is PROBE_OFFSET_XMIN set to?

[kinlougha]

OK I set to -20 by error. Sorry.

[kinlougha]

Hello Keith,
LOG_bugfix2.1.x.txt
OK, change PROBE_OFFSET_XMIN to -50 and run Bugfix-2.1.x successfuly many times. See attach log file.

What next?

Thanks.

[kinlougha]

Hello Keith,

I found the error. Il was a misunderstood of a config parm:

#define Z_PROBE_LOW_POINT -4
but my offset was -4.65 so the #define Z_PROBE_LOW_POINT was to short for my offset. I put it at -5 and everything is OK.

Thanks for your help.

Alain K.

[mriscoc]

Your Z offset is very large, check the recommended position of the BLTouch in the image:

So, a Z offset should be approximately in the range of -1 to -3

[kinlougha]

I know that.