Parse Error

Second PDF on your post shows it erroring due to hal plasmac feed rate , so probably from SheetCAM using the PlasmaC post, change the post to LinuxCNC with no plasma.

A .tap file is not an image file, it is a SheetCam g-code file so you would not want it to call image-to-gcode. Try commenting it out in the FILTER section.

Well today has resulted in some good things. I did change the Post Processor in SheetCam to LinuxCNC and created a G-code (2 one with NGC and the other with TAP). TAP not working very well but the NGC did, But I still got the Parse error on the load. And it also had a menu come up stating to insure the tool was set. Well removing the line in the G-code calling out what tool is used. That error went away. It now operated like the G-code generated by EstlCam. It loads and runs without errors. Not sure if there is a way for Axis to use a G-code with a TAP extension.  Of if there is another LinuxCNC post processor that does not place the tool number in the G-code.
Thanks for your help

This is all using the axis_mm sim config.
Downloaded your zip file 4washersLinuxcnc.zip and extracted the contents.
Created a tool #23.
Loaded 4washersLinuxcnc.tap which gave a parse_file interp_error.
Duplicated 4washersLinuxcnc.tap and renamed it 4washersLinuxcnc.ngc
Loaded 4washersLinuxcnc.ngc which gave a parse_file interp_error.
Created several tools, #9, #10, #19, #20.
Changing tool numbers in the files and then loading the files showed that tool numbers greater than #9 always gave a parse error and tools #9 and below mostly loaded without error.
I did see that your file had dos style line endings so I changed that to unix style and it made no difference to the above.

The above makes no sense to me and is all I have time for at the moment.
​​​​​​​

Thanks for you time Phill The tool numbers were generated by the sequence they were created in SheetCam. As it sits now it is usable for me to do work. As I assume the bit size and positions (inside, out side, and one the line) should be kept correct by SheetCam and EstlCam. This should keep the dimensional size correct for my projects.
your statement

This is all using the axis_mm sim config.
does that mean I need to use metric measurements or is there an inch version??

I am having virtually the same problem, but with a twist. Using the qtvcp gcode_graphics widget, which uses qt5_graphics, I can load any .ngc file with any tool number no problem. However, when the display is a VTK render window, any ngc file that specifies a tool greater than 9 causes a gcode interp error. For example, if line 3 in the ngc file contains: it works fine. If I change the line to: it throws: I looked for the reason in gcodemodule.cc but C++ is beyond my brain capacity.
BTW, T13 is a valid tool. If I specify an invalid tool, so long as it's less than 10, it only throws a tool not found in tool table error, which is perfectly normal. Any insights would be greatly appreciated.
Jim