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

Support for Unlocking after ERCF error #386

Open
4 tasks
Doogle03 opened this issue Jul 13, 2024 · 0 comments
Open
4 tasks

Support for Unlocking after ERCF error #386

Doogle03 opened this issue Jul 13, 2024 · 0 comments
Labels
feature-request New feature or request

Comments

@Doogle03
Copy link

Feature Request

Requesting ability for app to be notified the print has been locked by Happy Hare software when a tool change error occurs, with a button to unlock and click on various macros, then click resume.

Problem Description

When an error occurs with ERCFv2 and Happy Hare software, print gets locked. Must unlock via web portal or KlipperScreen, cannot unlock with app

Proposed Solution

Detect when lock has been applied, pop up window with error message and option to unlock or cancel print

Alternatives Considered

If you've thought of any alternative solutions or features, please briefly describe them here.

Additional Context

image


Checklist
To help us understand your feature request, please ensure you've covered the following points:

  • Provided a clear description of the problem you're facing.
  • Clearly outlined the proposed solution or feature.
  • Mentioned any alternative solutions or ideas you've considered.
  • Included any relevant context or supporting materials.

Your input is valuable in shaping the development of our project. Thank you for taking the time to submit your feature request!

@Doogle03 Doogle03 added the feature-request New feature or request label Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant