-
Hello there 👋, I am having some trouble with the custom G-code input feature. When I just flashed my mainboard everything works fine and I am able to use the custom G-code input screen. But when I reboot my printer I can't access the screen anymore, it gives me a status message to "GUI/OS update required" which I already did before flashing my mainboard and confirmed because I could access it before. I looked into the marlin firmware and found out that after a fresh firmware install the board was able to read the os and gui version from the display, but after a reboot it came back with os version 0 and gui version 0 (logged the versions to the serial console). I edited the code a bit to force a check of the os and gui version when pressing the button on the screen and after a manual called check it was able to read the versions again and access the screen after a second tap on the G-code input button. Do you maybe have any idea what is causing this issue? I hope you may have an idea, that may help me fix the problem. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
I'm not sure but I think I've had this happen a while ago while using the DGUS serial tool to directly communicate with the touchscreen. Sadly, I have no idea why this happened, or how I got around it... Does it happen often? |
Beta Was this translation helpful? Give feedback.
I'm not sure but I think I've had this happen a while ago while using the DGUS serial tool to directly communicate with the touchscreen. Sadly, I have no idea why this happened, or how I got around it...
Does it happen often?