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

Bed Tramming and Create Mesh tools do not use Physical Bed Settings #163

Closed
enderextender opened this issue May 20, 2022 · 5 comments
Closed
Labels
bug: False alarm? It is not a firmware bug or the bug cannot be confirmed.

Comments

@enderextender
Copy link

Describe the bug
When adjusting the Physical Printer Settings (max X, max Y, max Z) and setting bed size, these settings are not utilized when performing Bed Tramming Wizard or Mesh Bed Levelling, instead, the hard coded Ender 3 size (220x220) is used.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Advanced, Physical Settings, set X size, Y Size (I am using 400x400 on an Ender Extender). Set Max X and Max Y to 410/410
  2. Store Settings
  3. Go to Bed Tramming Wizard
  4. Observe Bed Tramming Wizard only using 220x200

Expected behavior
Bed Tramming Wizard and Mesh Levelling should respect adjusted physical settings.

Version (please complete the following information):
20220419

@mriscoc
Copy link
Owner

mriscoc commented May 20, 2022

Please complete the version of your firmware, ABL or UBL. Did you set up your mesh inset?
Use Advanced / Mesh leveling / Mesh Inset / Maximize area (and optionally center area)

@enderextender
Copy link
Author

I used UBL. I will check the values you specified.

@mriscoc mriscoc added bug: False alarm? It is not a firmware bug or the bug cannot be confirmed. and removed bug: Potential? labels May 23, 2022
@mriscoc
Copy link
Owner

mriscoc commented May 28, 2022

No more feedback?

@mriscoc mriscoc closed this as completed May 28, 2022
@enderextender
Copy link
Author

enderextender commented May 31, 2022 via email

@github-actions
Copy link

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 Apr 24, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug: False alarm? It is not a firmware bug or the bug cannot be confirmed.
Projects
None yet
Development

No branches or pull requests

2 participants