Bridgeport textron Series 1 CNC

Phil,Try the attached example that  works fine in axis. Just include it in your ini file. Based on the run/step pause/resume example on the forum here forum.linuxcnc.org/47-hal-examples/13201...-hold-resume-buttons

But I revised the code so it was a standalone hal file.

There are significant conflicts with this qtplasmac library hal file file.github.com/LinuxCNC/linuxcnc/blob/master...b/qtplasmac_comp.hal

My MPG hal file was easier and does not conflict. The guts of it is done but there are a couple of buttons I want to enhance the behavoiur to select jog/rapid speed from a shift/button press so its still a work in progress. Here QTPlasmac is actually nice as I have a couple of spare axis selects that can be used for MPG based speed overrides etc. 

back on topic. Here is my Lam stepboost component for the OP.
The plan is to tidy this up to us variable number of axes and maybe do a pull request for it.
Once again, I'm tryng to add this in a seperate hal files
 

@Phil,
They are not 100% compatible with BigJohns Run/Step and Pause/Resume options
I already have engraved  labels for Run/Step and Pause/Resume
There is no single step option.
But I was planning on redoing the hal code from scratch so I might be able to use some of them.

Do I have to connect every limit switch separately to boar or can I connect all together in parallel and program can understand what switch was activated because she knows which way she is moving?
If separately then I have to replace all factory switches but I have not found 1:1 replacement with two action switch.

phillc54 wrote:

I don't see the point of single step for plasma but I am sure you could use the run, pause and abort pins then use the halui step pin.
​​I any case there are only three pins involved and not the "so many" that you intimated earlier, so no big deal.

I did work it out in the end. There are a number of other pins that QTplasmac has used in addition to the jog pins that needed unlinking. So its a lot more than it first looks.

turbohoolik wrote:

Do I have to connect every limit switch separately to boar or can I connect all together in parallel and program can understand what switch was activated because she knows which way she is moving?
If separately then I have to replace all factory switches but I have not found 1:1 replacement with two action switch.

Read the chapter called homing configuration in the docs carefully. There are so many ways to do it. There is an IS_SHARED setting that may help. Deviating to much from the expected homing method may make your hal file complex.
Life is easier if the home switches are on seperate circuits in my experience. The rest of the limits don't really matter.

It took lot of time but finally got my computer and 7I95 communicate.
I got help from this video:

This all is new for me and it's not for me, mechanical part is no problem.