Apply FILAMENT_RUNOUT_SENSOR to MKS_UI

[thinkyhead]

Fixes #22591

Partially integrate MKS UI filament runout code with Marlin.

It would be better if it didn't reinvent the wheel and just used the methods in features/runout.*, allowing it to also respond to M600, park the carriage at a configured position, and so on.

[tvonderhaar]

Posting here as you requested my answer to your request in issue #22591 to try Marlin with FILAMENT_RUNOUT_SENSOR enabled and configured.

By the way, I have tried to use the current sensor software, but as mentioned above the function "runout.reset()" is never called upon pushing the resume button. This needs to be addressed in the integration. Nothing in the "TFT_LVGL_UI" enabled user interface does this reset and as a result the filament sensor run out monitoring function "runout.run()" will never run again until a "m412 r" command is manually executed,(I used Ponterface remote control program to issue the reset), forcing a reset. Also, I discovered from this forum that "M600" can't be called with "TFT_LVGL_UI" set as the 3.5" color TFT touch screen is not supported by the current "M600" implementation. Only the user configured call to "M25" seems to be supported. This just pauses the printer and waits for the resume button to be pushed. No park, no heater timeout or any other "M600" functions are performed(Note: Advanced pause is also not supported.) The M25 pause,(currently required with the "TFT_LVGL_UI" option ), is very confusing to the operator as they may not know why the printer has paused. Also, changing filament while poised above an incomplete model seems destined for disaster.
Tom V

PS: I believe removing the MKS UI filament runout code without consideration of WiFi polling contained within will break WiFi for "TFT_LVGL_UI" option users.

[thinkyhead]

MKS UI is not our own baby, but is ostensibly maintained by MKS, so this PR is intended to point out what needs to be done to properly implement a controller. I don't anticipate spending a lot of time poring over MKS UI to fix everything that MKS got wrong. Hopefully this PR will get the ball rolling for MKS to fix the issues you cite.

CC: @MKS-Sean @mks-viva @makerbase-mks

[tvonderhaar]

I just don't want my comments to end up breaking WiFi and filament support for "TFT_LVGL_UI" option users. Thanks for attempting to get it fixed. It would be nice to get full M600 support,(park,advanced pause,temp timeout...)
Tom

[mks-viva]

MKS UI is not our own baby, but is ostensibly maintained by MKS, so this PR is intended to point out what needs to be done to properly implement a controller. I don't anticipate spending a lot of time poring over MKS UI to fix everything that MKS got wrong. Hopefully this PR will get the ball rolling for MKS to fix the issues you cite.

Thank you! I have feedback to the engineer.