search

knutwurst / Marlin-2-0-x-Anycubic-i3-MEGA-S

Marlin 2.0.x Version for Anycubic i3 MEGA M/S/P/X/CHIRON and 4MAX with Anycubic TFT or the "new" DGUS Clone TFT - Now also with BLTouch!
GNU General Public License v3.0
787 stars 187 forks source link

[BUG] Using the Touch Screen Resets the printer #113

Closed rianweaver closed 3 years ago

rianweaver commented 3 years ago

Bug Description

I've found that using the touch screen on my Mega X after being flashed with Knutwurst often resets the printer. This will mess up running prints when trying to do a filament change, etc.

My Configurations

Required: used downloaded compiled firmware

Steps to Reproduce

  1. Using the touch screen, hit buttons (like filament change), more than once, in quick succession This happens intermittently, both during a print, and during "idle"

Expected behavior: On screen buttons work as expected

Actual behavior: Intermittently, it sends a reset to the printer. Any expected temperatures are reset to zero, printer beeps, and resets. Reset detected in Octoprint.

Additional Information

rianweaver commented 3 years ago

Here are my octoprint logs if that's helpful. It seems maybe the M110 is what's being sent by the button presses?

2021-03-29 21:39:09,046 - octoprint.util.comm - WARNING - Printer sent 'start' while printing. External reset? Aborting job since printer lost state. 2021-03-29 21:39:09,051 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0 2021-03-29 21:39:09,061 - octoprint.util.comm - INFO - Changing monitoring state from "Paused" to "Cancelling" 2021-03-29 21:39:09,063 - octoprint.util.comm - INFO - Force-sending M108 to the printer 2021-03-29 21:39:09,115 - octoprint.printer.standard.job - INFO - Print job cancelled - origin: local, path: MrsWeaverNameplate.gcode, owner: rian.weaver, user: None 2021-03-29 21:39:09,194 - octoprint.plugins.DisplayLayerProgress - INFO - Printing stopped. Detailed progress stopped. 2021-03-29 21:39:09,246 - octoprint.plugins.filamentreload - INFO - PrintCancelled: Disabling filament sensor. 2021-03-29 21:39:09,248 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer. 2021-03-29 21:39:09,430 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0 2021-03-29 21:39:09,558 - octoprint.plugins.DisplayLayerProgress - INFO - Printing stopped. Detailed progress stopped. 2021-03-29 21:39:09,564 - octoprint.plugins.filamentreload - INFO - PrintFailed: Disabling filament sensor. 2021-03-29 21:39:09,884 - octoprint.plugins.tracking - INFO - Sent tracking event print_cancelled, payload: {'origin': 'local', 'file': 'fd2a8d9d6565b80c188aee8ae4dc4e414b680f12', 'elapsed': 10913} 2021-03-29 21:39:10,516 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {'origin': 'local', 'file': 'fd2a8d9d6565b80c188aee8ae4dc4e414b680f12', 'elapsed': 10913, 'reason': 'cancelled'} 2021-03-29 21:39:22,255 - octoprint.util.comm - INFO - Changing monitoring state from "Cancelling" to "Operational" 2021-03-29 21:39:22,262 - octoprint.plugins.printoid - INFO - //// Send alert to Printoid: 'printer-state' with value Operational (Mega X)

3dRikal commented 3 years ago

Actually I think this is related to the filament detection issue. I do get the same kind of problem but only when the filament is removed from the printer. Only way to get the printer to respond again is to reset.

knutwurst commented 3 years ago

This is a known issue with the first Mega X with original DGUS II Display (see here) which causes the Display to lock up and reset. Also in v1.2.0 the special menu handling is optimized, which should help to avoid the issue, but I can not say it for sure :/

github-actions[bot] commented 3 years ago

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.