[BUG] Auto-leveling is not working properly.

[shabgarde]

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

Yes, and the problem still exists.

Bug Description

I was previously using Marlin version 2.1.2.3 and had no problems printing the first layer. After updating to newer versions, such as 2.1.2.6, 2.1.2.7, and 2.1.28, I noticed that the first layer was not printing properly. The distance between the nozzle and the bad plate is always less on the left side of the bad , and the distance is greater on the right side. As a result, the left side prints tightly and the right side does not stick properly. We are the manufacturer of the 3d-printers and we had no problems on all devices in Marlin 2.1.2.3, but we have problem on the new version of Marlin. The problem cannot be hardware because with Marlin 2.1.2.3 the first layer prints correctly, but we have problem in the new versions of Marlin. Below I am attaching a picture of the result of printing the first layer in version 2.1.2.3 and version 2.1.2.8. Both tests were performed on the same device, only the Marlin version is different. Thank you.

Bug Timeline

No response

Expected behavior

I expect that the first layer will be printed correctly in the new version of Marlin, like Marlin 2.1.2.3

Actual behavior

The first layer does not print properly and the left side of the build plate is compressed, and conversely, on the right side, the distance between the nozzle and the build plate is too large.

Steps to Reproduce

No response

Version of Marlin Firmware

marlin bugfix2.1 and marlin2.1.2.3

Printer model

hypercube-corexy

Electronics

mks robin nano v3.1

LCD/Controller

mks ts35

Other add-ons

No response

Bed Leveling

ABL Bilinear mesh

Your Slicer

Other (explain below)

Host Software

None

Don't forget to include

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

Additional information & file uploads

Marlin.zip

[ellensp]

From the look of the provided config files, you are not running a recent bugfix

Please test with the current bugfix code.

Your configs are updated Configuration current bugfix 2.1.x.zip

I do, however, recommend you enable EEPROM_INIT_NOW This ensures the EEPROM doesn't contain outdated data

[shabgarde]

From the look of the provided config files, you are not running a recent bugfix

Please test with the current bugfix code.

Your configs are updated Configuration current bugfix 2.1.x.zip

I do, however, recommend you enable EEPROM_INIT_NOW This ensures the EEPROM doesn't contain outdated data

Thank you. I also tested with the latest version and unfortunately the problem still exists.

[Nuck-TH]

Leveling issues like this seem ti be highly dependent on configuration and intermittent. There is always trouble in reproducing them by other people. Since you have the way to reliably reproduce it, would you be so kind to run bisect between closest working and broken version to narrow down where issue started?

[shabgarde]

Leveling issues like this seem ti be highly dependent on configuration and intermittent. There is always trouble in reproducing them by other people. Since you have the way to reliably reproduce it, would you be so kind to run bisect between closest working and broken version to narrow down where issue started?

Thanks for your reply. Okay, I'll try to find the latest version that works properly.

[ellensp]

Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information so that we're not just taking stabs in the dark. Here is the boilerplate:

• Download Marlin bugfix-2.1.x to test with the latest code.
• Enable DEBUG_LEVELING_FEATURE and M114_DETAIL and re-flash the firmware.
• Connect to your printer from host software such as Cura, Printrun or Repetier Host.
• 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.