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

k1max shutdown upon accessing via app on IOS #415

Open
6 tasks
bodydropped72 opened this issue Sep 20, 2024 · 2 comments
Open
6 tasks

k1max shutdown upon accessing via app on IOS #415

bodydropped72 opened this issue Sep 20, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@bodydropped72
Copy link

Bug Report

Description

anytime i access machine remotely after starting a print i notice it takes a while to populate, then machine errors and shuts down and can no longer access ive attached my klippy.log
klippy (3).log

Steps to Reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See the error.

Expected Behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain the problem.

Version Information

  • Device-OS (Android/iOS): [OS]
  • Mobileraker: [version]
  • Klipper: [version]
  • Moonraker: [version]

Debug Logs

Please attach the log files generated by Mobileraker. You can find them by navigating to the app's settings page, scrolling to the bottom, and pressing the Debug Logs button.

Additional Context

Add any other relevant context about the problem here.


Checklist

To help us diagnose the issue, please ensure you've completed the following steps:

  • Provided a clear bug description.
  • Listed detailed steps to reproduce the issue.
  • Described the expected behavior.
  • Included the Mobileraker version you are using.
  • Attached Mobileraker's debug log files.
  • Specified the version numbers of Klipper and Moonraker if applicable.
@bodydropped72 bodydropped72 added the bug Something isn't working label Sep 20, 2024
@Clon1998
Copy link
Owner

Hey,

I'm sorry to hear about the issue. I took a quick look at the klippy file you provided, and it seems to me like the host is overloaded and missing some events from the connected MCUs. I've only seen this on very low-spec hosts, which is unfortunately the case for many Creality Klipper machines.

[ERROR] 2024-09-20 23:02:41,107 [root] [klippy:invoke_shutdown:300] Transition to shutdown state: {"code": "", "msg":"MCU 'nozzle_mcu' shutdown: Missed scheduling of next digital out event
This is generally indicative of an intermittent
communication failure between micro-controller and host.", "values": []}

@bodydropped72
Copy link
Author

bodydropped72 commented Sep 20, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants