qtDragon: Auto Return to Manual Mode After an MDI Command so MPG works

qtDragon: Automatically Return to Manual Mode After an MDI CommandThe ProblemIf you use a pendant with qtDragon, you've probably run into this annoyance: after executing an MDI command, LinuxCNC stays in MDI mode. Before your pendant will respond to jog inputs, you have to manually click a movement button (or otherwise trigger a mode switch) to get back into manual mode. On a busy machine this gets old fast.  I use a VistaCNC P4-S.The FixThe solution is a small addition to your. We connect to LinuxCNC'sSTATUS signal, which fires whenever the interpreter finishes executing. When that signal fires and we're still in MDI mode, we automatically switch back to manual.Step 1 — Get a local copy of the handlerIf you don't already have ain your config directory, copy the system default there. LinuxCNC will automatically prefer the local copy over the system one.Step 2 — Edit the handlerOpen your localand make two small changes:In the method, add the signal connection:Add the callback method somewhere in the class:That's it.How It Works

• interp-idle

  fires whenever the interpreter becomes idle — MDI command finished, program finished, etc.
• The

  STATUS.is_mdi_mode()

  guard ensures we only switch to manual when we're actually in MDI mode, so it won't interfere with the end of a normal G-code program run.

• ACTION.SET_MANUAL_MODE()

  does exactly what it says — same as clicking the Manual button in the UI.

Notes

• Tested on LinuxCNC 2.9.6 with qtDragon.
• This should work on any 2.9.x build without modification.
• If you're on 2.8, the same approach should work but

  STATUS

  and

  ACTION

  import paths may differ slightly depending on your build.
• This does not affect program (auto) mode — when a G-code program finishes it will stay in auto mode as expected, since

  is_mdi_mode()

  will return False.

CreditFigured this out with a little help. Posting here so the next person doesn't spend 3 hours on it.Hope this helps someone!