classicrocker883 / MRiscoCProUI

This is optimized firmware for Voxelab Aquila & Ender3 V2/S1 3D printers.
https://classicrocker883.github.io/
Other
74 stars 17 forks source link

Timer never starts again after screen turns off [BUG] #110

Closed acousticpunker00 closed 5 months ago

acousticpunker00 commented 5 months ago

Did you test the latest release build?

Yes, and the problem still exists.

Bug Description

The print timer will stop counting as soon as the screen goes to sleep, and never updates again even after you wake the screen back up. Bug

Printer Model

Voxelab Aquila

Model Type

X2

Your Mainboard

Aquila N32

Other Mainboard Type

No response

Add-ons that could be involved

No response

ProUI?

ProUI

Bed Leveling

BLT - BL Touch Bilinear mesh

Did you include your own configuration files?

Additional information & file uploads

No response

classicrocker883 commented 5 months ago

in my testing I havent been able to reproduce this. so what I did was manually turn off the screen when its printing. and set the timer to like 1 minute instead of waiting. upon returning it was still counting. so when this happens, I know that turning the knob alone might bring back the display, but it doesn't allow any interface unless you actually push in the knob.

can you confirm that? see if theres a difference when turning the knob vs pushing in the knob. also, you can put M111 S8 in the beginning of the start Gcode, this enables DryRun mode. basically it pretends/thinks to print without actually heating or printing.

and to actually start printing again, youll need to enter M111 and whatever the disable command is, i dont remember maybe its S0 or 1

acousticpunker00 commented 5 months ago

Looks like you're right. On the second button press, the timer updated. I can't believe I didn't try that before, but maybe it wasn't working on the last firmware, but is now on the new one.

Thank you!

github-actions[bot] commented 2 months 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.