Using I/O pins on teh mesa card

How do you setup teh Mesa I/O pins to be used by PathPilot in calls like M65/M66. It calls for a pin number. So how do you associate teh M65 pin # to teh Mesa Pin # ?

I hope I asked that correctly. I think I see how it is done in the HAL but not exactly sure it is what I think it is.

( TP

You have to connect Linuxcnc/PathPilots digital-out pins to the appropriate physical pin,
see:

linuxcnc.org/docs/html/gcode/m-code.html#mcode:m62-m65

Something like this on a 7I80:
First setup the hardware pin
setp hm2_7i80.0.gpio.023.is_output true # set GPIO23 into output mode
and possibly
setp hm2_7i80.0.gpio.023.invert_output true # invert output

then connectPathPilots digital output to the hardware pin
net some_signal_name motion.digital-out-00 ==> hm2_7i80.0.gpio.023.out

That was what I was seeing in the hal file just wanted to make SURE before I murdered the script.

Thanks for teh Time, ( TP

In PP the M65 are mapped for the USBIO card. you can however change this to map to real pins in the HAL file.

look in the postgui hal file for
# USBIO
net usbio-enabled tormach.usbio-enabled => usbio.enabled
net dig-out-0 tormach.usbio-output-0
net dig-out-1 tormach.usbio-output-1
net dig-out-2 tormach.usbio-output-2
net dig-out-3 tormach.usbio-output-3

net dig-in-0 tormach.usbio-input-0
net dig-in-1 tormach.usbio-input-1
net dig-in-2 tormach.usbio-input-2
net dig-in-3 tormach.usbio-input-3

change as you need for you pins

Yes that is what I was looking to do . In the PP hal there are 16 ins and 16 outs for teh USBI/O. I was going to redirect them to mesa pins.

Easy peazy I hope , ( TP

Actually yes it was . It is a lot of typing even with cut and paste but doable.

The next hard project will be trying to integrate a tool changer into teh PP way of doing things. THAT is going to be a tuffy . IF one could buy their ATC control card it might be very easy BUT they said sorry no deal . I even tried teh MANF of teh ATC and they also said no deal. The actual working of teh add on ATC is VERY simple just some inouts and outputs and waits and spin teh carrosel to position and some more ouputs and inouts and waits BUT trying to unwind how PP does it is a tuff cookie.

I might try and unwind the logic of the ATC card and use an Adurino to run it BUT that is another story in itself and I am not a programmer.

( TP

Their tool changer card is basically their usbio card with slightly modified commands

I’ve got a hdr for the various cards I threw together then you can use the teensyio mentioned in the forum to implement

OK what is an hdr ?? What appears to be the firmware for teh ATC card is in PP folder. IT appearantly updates when needed

The ATC cards has to be able to do motor control as well as I/O

IF you have more info on teh cards I am all ears (

The ATC I am working to interface needs 10 outputs and 12 inputs and 1 channel of S/D to run a servo to spin the carrosel into position.

It has been run in Mach3 and UCCNC so it is not really rocket science. The real trick will be to integrate it into teh PP tool change process without a lot of changes to teh PP code. The PP code can handle between 8 tool pockets up to 16 tool pockets for the MX and a BT30 spindle with spindle orientation.

( TP