Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] AUTO_BED_LEVELING_BILINEAR uses wrong area limits #16629

Closed
bill-orange opened this issue Jan 20, 2020 · 7 comments
Closed

[BUG] AUTO_BED_LEVELING_BILINEAR uses wrong area limits #16629

bill-orange opened this issue Jan 20, 2020 · 7 comments

Comments

@bill-orange
Copy link

Bug Description

Regarding Tronxy X3A with configuration only lightly modified from the sample files:

AUTO_BED_LEVELING_BILINEAR correctly probes a grid and probes it the correct number of times. The Grid, however, is only a small square roughly a quarter of the bed size.

My Configurations

Marlin.zip

Steps to Reproduce

  1. Enable AUTO_BED_LEVELING_BILINEAR and probe the bed
  2. observe the small pattern.

**Expected behavior:

Whole bed probed

*Actual behavior:

Only small area probed.

Additional Information

The 2.0.x bugfix version had around line 1055 in Configuration.h a section that allowed the probe limits to be defined. I do not see a similar section on 2.0.1 Without this section I can not fix the problem.

From bugfix:

#define LEFT_PROBE_BED_POSITION MIN_PROBE_EDGE
#define RIGHT_PROBE_BED_POSITION (X_BED_SIZE - MIN_PROBE_EDGE)
#define FRONT_PROBE_BED_POSITION MIN_PROBE_EDGE
#define BACK_PROBE_BED_POSITION (Y_BED_SIZE - MIN_PROBE_EDGE)

@sjasonsmith
Copy link
Contributor

What code are you running? This sounds like an issue that was already fixed. I believe it made it in to 2.0.1.

@bill-orange
Copy link
Author

bill-orange commented Jan 20, 2020 via email

@boelle boelle changed the title AUTO_BED_LEVELING_BILINEAR uses wrong area limits [BUG] AUTO_BED_LEVELING_BILINEAR uses wrong area limits Jan 20, 2020
@Vertabreak
Copy link
Contributor

image
the defines your looking for should be in configuration_adv.h they may have been moved.

@bill-orange
Copy link
Author

bill-orange commented Jan 20, 2020

I am not sure why they would be commented out as the default since they are in the if statement, In any case, uncommenting them makes no difference. The default value appears to be 30 which is a reasonable number if it worked.

@sjasonsmith
Copy link
Contributor

Oops. Left that out of my post. I am on 2.0.1

I think I was wrong thinking that was in 2.0.1. I lose track of the timelines for the labels since I'm in the bugfix branch all the time. You should try again with the latest bugfix-2.0.x branch.

You are most likely experience the issue fixed here:
#16367

The default value appears to be 30 which is a reasonable number if it worked.

30 is really high for most printers. Your NOZZLE_TO_PROBE_OFFSET is already factored in, MIN_PROBE_EDGE is just extra distance to stay away from the edge of the bed. It is useful if you have a probe which does't work close to the bed edge, or have something like clips that you need to avoid.

@bill-orange
Copy link
Author

Since this issue has been ( or is being) addressed at least two other places, I will close this issue. I will most likely wait for a release with this issue fixed. I can limp along for now.

@github-actions
Copy link

github-actions bot commented Jul 3, 2020

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants