Post GUI HAL not loading and "Bad character '[' used" error on E-Stop

I am having an issue with a machine using probe basic where the post gui hal files are not loading. Looking at the console output when running linuxcnc from the terminal does not show an obvious error to me. It just gets to the line where it is trying to load the first post gui hal file and stops. I have tried removing any customizations but it has no effect. Attached are my hal and ini files.

Another possibly related issue I am having is that if I ever use the e-stop, I get 2 "Bad character '[' used" errors. The error shown in the terminal is "emc/task/emctask.cc 68: interp_error: Bad character '[' used" and it happens even if I have no file loaded.

Has anyone encountered either of these problems? I am at a loss of where to look next on either and would appreciate any help.

You've got a lot going on there.
Only thing I see are these MDI_COMMANDS that will cause syntax errors due to comma instead of semicolon but I have no idea if those are actually used anywhere.:

If you run this in MDI do you also get the error about the Bad character '[':

Another thing that comes to mind is that only one POSTGUI_HALFILE entry is allowed (unless that has changed):
So if you wanted to load more than one postgui_hal file you would have to create a single (eg 'postgui_call_list.hal') file like this:
Then you would replace the three POSTGUI_HALFILE entries with this single line:

Maybe that helps

Thank you very much for the help! I feel a bit lame for not realizing that you could only have one postgui_halfile. That has solved that issue.

As for the bad character issue, yes (abort, aborting) does trigger that error but only once instead of twice like an e-stop would.

Not sure if you can have a mix of G- and M-commands like that for an 'ON_ABORT_COMMAND' so try commenting out this line in your ini and see if the error still occurs:
If that fixes it then you may want to use a subroutine call instead. Something like this:
and create a subroutine 'on_abort.ngc' with all the command you want to run on abort

You were correct about the 'ON_ABORT_COMMAND' not working with all those commands. I will go the subroutine route.

I realized I forgot to comment on the MDI_COMMANDS section. Those are formatted that way to show up as buttons in the UI. Everything after the comma is treated as the button text. I just used an example bit of code from the pull request on github to set it up. github.com/kcjengr/probe_basic/pull/84

That example code uses the INI format from QTDragon.

turns out that a traditional sub call does not work in the ON_ABORT_COMMAND option either. It appears that it strips out the <> characters. It errors on a e-stop saying it can't find a subroutine called "Oon_abort". I think I will have to go the custom M code route instead.

Certainly works for me:
github.com/Sigma1912/LinuxCNC_Demo_Confi...ort_no_twp_reset.ngc

with this in the [RS247NGC] section of the ini:

Turns out the issue was no M2 or M30 at the end of the file. I was just using the % markers at the beginning and end which is the wrong way to do that.