Adapting ManualToolChangeMacro for use with LCNC Master

As a novice, I will appreciate guidance on adapting the attached Python script (based on that found - thanks to AP - at wiki.linuxcnc.org/cgi-bin/wiki.pl?ManualToolChangeMacro) for use with LCNC Master.

Prior 'emc' module name has been replaced with 'linuxcnc' (per LCNC Python interface guidance), but LCNC start-up fails with NML file not found. Is it necessary to declare the NML file name (tried 'linuxcnc.nml')?

Commenting out line 10 of the script allows LCNC to start, but manual / mdi control is inhibited.

Aware that this macro is not recommended, it is hoped to provide the basis of interim solution for manual tool change.

Now working (as attached) with two additional replacements of 'emc' with 'linuxcnc' (lines 27 & 28), and revised start-up text window to caution the user.

Tested with Axis and Gmoccapy GUIs, a fix is required for full screen mode (of Gmoccapy). While the prompt to change the tool appears on top, it is hidden behind the Gmoccapy window as soon as jogging/touch-off is initiated, meaning that the required keystroke to continue after tool change is not seen by the tool change script (and is of no consequence in the active Gmoccapy window).

An external button linked via halui is a solution (with appropriate script 'h.newpin("done" ...' and 'except (KeyboardInterrupt OR h.done)' ? ), but is there some readily available on-screen means by which the confirmation can be given that the tool is changed and execution can proceed?

Creation of a custom Gmoccapy is expected to be an option, but perhaps there is a simple way of returning focus to the required tool change confirmation window, specifically in Gmoccapy full-screen mode. Can a keyboard function key be programmed to be seen by the script (line 67), ignored (or passed) by Gmoccapy?

I'm not really an expert with Python, but I am sure you will find that Gmocappy uses a different method to raise an error window as I have debugged it.

Have a look in the Gmocappy.py source file and use the same method. You might need to add some libraries to your tool changer code.