uwetaz

Hello, I got exactly the same problem as user EnableDevice describes in detail (sporadic no continue button at M600 at nearly 50% of the print jobs). I have the same...

Here I post terminal output in bad and good case of not occured Contiunue button. But it seems not containing enough details. **1) not occured continue button at M600** echo:Now...

Test with triggered filament sensor (for easy and fast M600) can provoke the same issue (sometime button occures sometime not). Trying to activate ANYCUBIC_LCD_DEBUG in code was not successfull. I...

I found the right define for more verbosity on serial port: ANYCUBIC_TFT_DEBUG But unfortunately in both cases (Continue button occures or not) the output is the same: _TFT Serial Debug:...

After long nights I could understand and fix it. 1) cause The root cause is the display with its UART interface behaviour. During printing the display requests in 1.1s intervalls...

@knutwurst I'm on a journey until sunday. I will make the pull request probably on sunday evening. There are sources from Anycubic? I also know the hex files.

Sorry I'm not finished today with the pull request. I'm not so firm with github and it is the first time to publish something in not own repo and I...

I could now create the pull request. I hope I understood the process for PRs in github right.