Toma/Proma HAL for Mesa Board -Basics

I'm trying to modify an existing configuration from stepconf (Toma) to pncconf (parallel to ether/mesa). I'm finding out that I know very little about these systems; which isn't surprising as I'm new to linuxcnc, and linux in general. I've a few relatively simple questions that would be great to get some clarification on. I'll link the files to make things easier. NOTE: "Toma" is a reference to Proma's parallel port linuxcnc build.

The "thc_parport.hal" file obviously shows parport pins; to switch that to the hm2, is it really as simple as just replacing these lines with the proper hm2 pin?

How do I write the dir+/- step+/- for these pins? Example below for 7i96 specifically
setp hm2_7196.0.stepgen.00.steplen <-step+?
setp hm2_7196.0.stepgen.00.stepspace <-step-?
setp hm2_7196.0.stepgen.00.dirsetup <-dir+?
setp hm2_7196.0.stepgen.00.dirhold <dir-?

Nope, those are timing settings but it should go something like that.
I do have a config for Mesa 6i25/7i77 but i have added a stepper drive and motor to the parallel port, so not exactly what you need.
I would also like to know what would be the equivalent of
stepgen.2.position-cmd
stepgen.2.position-fb
so it can work with Mesa stepper and servo cards.

I'm trying to marry the two ini/hal files, I built a pncconf for my 7i96 (from 7i76e), however the two files are so different that I cannot, at my current experience level, reconcile the two configurations to work with my mesa card; which seems a helluva lot easier than trying to program in all of the hal settings from the Toma build to my, untested, 7i96 build.

I'm willing to pay for someone to build this for me, and posterity, as long as they help troubleshoot the build.

Hi Snuggly,

Are you using a proma thc in your current hardware version?

By far the easiest path to integrate the Proma THC control would be to take a working 7I96 config and add the code from thc.hal, translating signal/pin names as needed.

Yes, I have a proma 150 THC wired up and ready to go. It's expensive but it seemed relatively plug and play.

@Hi Snuggly,

Wich gui are you using? Axis with Toma pyvcp add on screen?

Okay, so I just need to copy pasta in the hal files from the Toma and write in the pins? Still don't quite know how to do that yet.

Have mercy on my soul PCW! Lol. I'll try to figure out the contextual commands and adapt them to my build.

I would also like to know what would be the equivalent of
stepgen.2.position-cmd
stepgen.2.position-fb
so it can work with Mesa stepper and servo cards.

Good question.

1. It can be the equivalent as : position.in + postition.offset = position.out
That is the core function of making the up and down signal possible without following errors.

In my case axis 3 is z axis.
net zpos-cmd joint.3.motor-pos-cmd stepgen.3.position-cmd
net zpos-fb stepgen.3.position-fb => joint.3.motor-pos-fb

If i want to make a component myself for thc it would be connected something like this :

net zpos-cmd joint.3.motor-pos-cmd position.in
net zpos-in position.in stepgen.3.position-cmd

net zpos-fb stepgen.3.position-fb position.out
net zpos-out position.out joint.3.motor-pos-fb

Then the calculation would be like item.1
The orginal offset component to see at man page is calculating in different way.
The component name is here for example : position
The component signal names are for example : in, out
The component variable name is for example : offset. It can have a offset value of 0-100mm for example.

If you read it other way :
position.offset = 50 (input value from thc)
g-code position = 1050
net zpos-cmd joint.3.motor-pos-cmd 1050
net zpos-in 1050 stepgen.3.position-cmd
net zpos-fb stepgen.3.position-fb 1100
net zpos-out 1100 joint.3.motor-pos-fb

For Snuggly,

Hacking into the Toma code is not a good idea to start with.
Maybe ask PCW for advise, he knows what you need to start good with Mesa.

Proma's thc.hal file would need to be edited for any hardware other than a parallel port using their pinout and used with LinuxCNC <2.8. In addition, some parts of their ini file would be needed. Also, their example is for LinuxCNC 2.7 so would need adjustments for 2.8 (mainly changing "axis" to "joint") This requires some hal knowledge but this is not Mesa specific.