Thanks.
Runout or pauses seem like good places to start. It’s clear there’s logic for initializing and checking the runout sensor in the Marlin firmware. But it’s also obviously not tied to the standard Marlin runout code, and having a hard time seeing where it’s then monitored and alarmed.
Since it monitors filament motion and not just a presence sensor, I guess it only works while extruding. Marlin (non-Snapmaker) base code only checks for filament presence? All that stuff is flagged off.
I was having a look in the Android “binary” apk after decompiling, but that’s much more of a labyrinth to me trying to find the business logic.It would help so much to understand what’s happening on the other side.
I’d really still like to see the screen react to OctoPrint: 1) stop/start job, 2) M600 pause, 3) filament runout and 4) M2000 S200 fast swap.
Anyway, thank you. That confirms runout isn’t picked up.