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_mesh: behavior fixes #6473

Merged
merged 2 commits into from
Jan 28, 2024

Conversation

Arksine
Copy link
Collaborator

@Arksine Arksine commented Jan 27, 2024

This includes two minor fixes to the behavior of bed_mesh.

  1. Avoid probing additional points for the zero_reference_position and faulty_regions when the user chooses the "manual" method. Those options aren't useful when probing manually.

  2. Fix a reporting regression introduced by the adaptive mesh change. Since we avoid saving the mesh, the value reported in the profile_name field will be whatever was previously stored in ProfileManger.current_profile. This is often an empty string, which is leading some frontends to believe that no mesh is loaded. This patch moves profile name tracking to the ZMesh class and generates a placeholder name for adaptive meshes.

Kevin, this is likely going to cause a merge conflict with #6459, so if you would like we can hold this PR until its merged and I will resolve the conflicts.

Do not generate points for the zero_reference_position or faulty_regions
when manual probing is requested.

Signed-off-by: Eric Callahan <[email protected]>
Adaptive meshing avoids saving the mesh after calibration to prevent
users from inadvertently overwriting an existing profile with an
adaptive mesh.  This introduced a change in behavior of how
get_status() reports the profile_name, as it can now be an empty
string when a mesh is active.

This patch assigns adaptive meshes a name with a unique postfix.
In addition, it moves profile name tracking from the profile manager
to the ZMesh class.

Signed-off-by:  Eric Callahan <[email protected]>
@KevinOConnor
Copy link
Collaborator

Thanks. I don't think we should wait for #6459 - I'll rebase that PR as needed. Let me know when you'd like me to commit this PR.

-Kevin

@kyleisah
Copy link

Wow awesome work @Arksine with the quick fix!

@Arksine
Copy link
Collaborator Author

Arksine commented Jan 28, 2024

Sounds good. I have tested the changes here and everything works as expected. You can commit when ready.

@KevinOConnor KevinOConnor merged commit 9f41f53 into Klipper3d:master Jan 28, 2024
1 check passed
@KevinOConnor
Copy link
Collaborator

Thanks.

-Kevin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants