MarlinFirmware / MarlinFirmware/Configurations
[BUG] (Bedleveling fails with Z_AFTER_PROBING < 100)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2.3k
- Forks
- 3.4k
- Avg merge
- 19h 32m
- Merged PRs (30d)
- 1
Description
### Bug Description
I use the settings for my Creality CR-10 V3 provided by marlin: https://github.com/MarlinFirmware/Configurations/blob/release-2.1.2.1/config/examples/Creality/CR-10%20V3/Configuration.h
After probing, the print head always raises 100mm what is unnecessary and for a different feature I'm using unpractical as well. Thats why I'd like to reduce that value. But reducing the value Z_AFTER_PROBING from 100 to 50 the probing suddenly fails. And I have no idea why and it makes no sense at all for me. The value seems also quiet high for me as well, as in other configurations its just around 10.
### Configuration Files
**Required:** Include a ZIP file containing `Configuration.h` and `Configuration_adv.h`.
[Configuration.zip](https://github.com/MarlinFirmware/Configurations/files/14585850/Configuration.zip)
If you've made any other modifications describe them in detail here.
### Steps to Reproduce
1. Compile firmware
2. Flash to printer
3. Try Autobedleveling (G29)
4. Fails with error message: Probe failed. Rewiping.
**Expected behavior:**
ABL working normally
**Actual behavior:**
#### Additional Information
* Provide pictures or links to videos that clearly demonstrate the issue.
* See [Contributing to Marlin](https://github.com/MarlinFirmware/Marlin/blob/2.0.x/.github/contributing.md) for additional guidelines.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached Configuration.h and Configuration_adv.h for the Creality CR-10 V3 settings, then reproduce the behavior by changing Z_AFTER_PROBING and running G29 on the specified branches. Compare the 100 and 50 values and the resulting “Probe failed. Rewiping.” message; done means identifying the cause or documenting the correct configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100