Closed mightystormy closed 3 years ago
zip file is actually a .rar, so unless you using rar for all compressed files this wont open on most machines.
version is 020007, this need to be tested on bug fix first.
version is 020007, this need to be tested on bug fix first.
The configuration files were teste on the latest bugfix with the same results.
zip file is actually a .rar, so unless you using rar for all compressed files this wont open on most machines.
I have updated the file with a proper zip archive.
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:
bugfix-2.0.x
to test with the latest code.DEBUG_LEVELING_FEATURE
and M114_DETAIL
and re-flash the firmware.M502
and M500
to ensure your Configurations are applied.M111 S247
to enable maximum logging.G28
to do your standard homing procedure.G29
to probe the bed. This will also enable bed leveling.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.
The same is happening to me, I've added some more details on the other BUG open which I assume is a duplicate of this or vice versa. - https://github.com/MarlinFirmware/Marlin/issues/20922
Sorry, I have seen the replies too late, I have already remove the BLTouch and disabled ABL in the firmware. The thought of restarting entire ABL saga is not appealing for the time being. I wanted ABL because from time to time I need to fine tune the level of the bed for small deviations and I wanted those small tunings to be handled automatically. But the time wasted trying to figure out why ABL is not working vs 4min tuning @ roughly 2 days .... yeah, I am just gonna enjoy my prints.
Below are the information I've added to the bug linked by @rechena, maybe will help someone somehow:
I have tried both bilinear and UBL with same results, meaning no visible improvement to the test pattern. I wanted to try firmware Marlin 2.0.5.3 as I've read reports that the ABL still works in those versions, but I was unable to configure it for Ender 3 Pro v4.2.7 board. If somebody can try this, it is worth a shot. Meanwhile I have just given up to bed leveling for the moment. I have decided to remove the BLTouch and do a manual bed leveling. It worked from the start and it provides consistent results. For me this means there is no mechanical issue at play concerning the printer or bed. Also the BLTouch self 10x probing test reports very small deviation which is well in the margin for ABL. In the end the fault lies within firmware somewhere.
PS. Maybe it's useful to add that I have also tried the last TH3D Unified firmware with same result -- no ABL working.
Also, a short feedback about what was my expectation when I opened the issue.
I thought that, if the firmware supports my configuration, than it means is was successfully tested on my configuration. So when I explained how to reproduce the results, my expectation was that those steps will be checked on the printer that validated the configuration and I would receive a status saying our validation system does not confirm the problem, let's gather more information to understand what is happening on your end. But if you start from scratch, based only on user data, when the issue is related to a major FW functionality... I wonder if the FW was validated on all system it claims it covers. I know it is a free service and I appreciate it, but if it was clarified that ABL does not work for Ender3-Pro with board v4.2.7, I would have not bought the BLTouch in the first place.
Having the same issue more or less, unlike with the OP though I can't just remove the BLTouch sensor and go back to manual. After so many prints with ABS and the bed temp at 80-90C the frame of the bed has warped like a potato chip. Definitely need a mesh leveling compensation for the discrepancy. I'm trying to dig around in the MARLIN config to see where the mesh data is saved to see if I can determine where the script is not properly picking the mesh back out of EEPROM. I don't have Octoprint and won't be able to set something like that up.
With the Creality print interface and MARLIN 2.1X bugfix running on an Ender 3 pro V4.2.7 board where do I find the Mesh text file output? G29 T doesn't seem to do anything in the Creality command UI. M111 S247 also doesn't seem to do anything. I have enabled the bug fix extra data logging in MARLIN config.h.
per Ellencp's post I enabled DEBUG_LEVELING_FEATURE, but M114_DETAIL doesn't exist anywhere in the MARLIN code, so not sure what to do about that if it is required.
I have Repetierhost as an option but haven't connected it to the printer yet, if that's required let me know and I'll give it a shot and post an update.
Bug Description
Autobed Leveling not working on Creality Ender 3 Pro with board 4.2.7 and BLTouch v3.1
Configuration Files
Marlin.zip
Steps to Reproduce
Expected behavior:
The print head is being adjusted in order to correct print bed irregularities.
Actual behavior:
There is no visible improvement when printing with G29 or printing without G29. When G29 is added in the code, the auto-level sequence is executed by probing 9 points. Yet when the printing starts the mesh information is just ignored.