gcode hal iocontrol pin association

how are pin names called across the various and sundary files ??? if I have
net iocontrol.1.turnmeon <=  input.1.1.1.card


in my gcode I have 

m66 P?????  wait.for.turnmeon, where is PX coming from, how is it named, etc

how are the gcode pins mapped to the hal file ? search as I might, there is I haven't found any documentation that clearly and explicitly declares these relationships and how they are established. Do I delcare these in the hal file ? is there a invislble file somewhere that decides this ? are these runtime settings ? 

 where are these "digital io pins stores or named" and how are they associated ?

• M62 P- - turn on digital output synchronized with motion. The P- word specifies the digital output number.
  • M63 P- - turn off digital output synchronized with motion. The P- word specifies the digital output number.
    • M64 P- - turn on digital output immediately. The P- word specifies the digital output number.
      • M65 P- - turn off digital output immediately. The P- word specifies the digital output number.
        
        
         
        
        
        

M62 P0
will turn on
motion.digital.out-0 <<< check the naming, this is of the top of my head
M62 P1
will turn on
motion.digital.out-1
etc
so, something like this
-
net turn.the.lights.on => motion.digital.out-0 => hm2_pci.5i25.0.0.output-0
-
-turn.the.lights.on <<<<is any name for that pin, no spaces allowed
-motion.digital.out-0 <<<<are LinuxCNC internal pins, again please check the correct naming in your hal file
-hm2_pci.5i25.0.0.output0 <<<<are hardware pins on a mesa board, edit to your setup.
It is much easier to think of these as wires that connect to each other, so you add a Yellow wire(turn.the.lights.on) that you wire to the blue wire(motion.digital.out-0) on one side and to the green wire(hm2_pci_5i25.0.0.output-0) on he other side.

so

Gcode
m62 P1 is motion.digital.out-1
M62 P2 is motion.digital.out-2

etc and so forth, is the same also true for

M66 P1 is motion.digital.in-1 ??

just trying to make sure I have a solid grasp of the IO naming scheme, I am trying to debug, so I am planning to make a flow chart of the code and commands to try and sort out my failure mode.

hal

net  motion.digital.out-1   <= some.hardware.outpout.card.0.0  

Same goes for inputs.
And this
net motion.digital.out-1 <= some.hardware.outpout.card.0.0 
will most probably not work as those pins are used by LinuxCNC
Again,
net ANY.WHATEVER.NAME => motion.digital.out-1 <= some.hardware.outpout.card.0.0
Also, => and <= do nothing, they are just to make it easier to follow things.

so which inputs and outputs are used by linuxcnc versus the Gcode ? Iis there a document describing this anywhere ?

I don't entirely understand the question, but the M65 etc pins work on the motion.digital-in/out and motion.analog-in/out pins.

The coolant commands toggle iocontrol.0.coolant-mist/flood

But pretty much _every_ HAL pin is under the influence of G-code in some way.

linuxcnc.org/docs/stable/html/man/man9/motion.9.html
linuxcnc.org/docs/stable/html/man/man1/io.1.html
linuxcnc.org/docs/stable/html/man/man1/halui.1.html

linuxcnc.org/docs/stable/html/man/man1/i...LINUXCNC_HOME/bin/io

that's the piece of info I was looking for. I think what I will end up doing is building a hal file that handles the pins as almost a translation layer, to reduce the ease of mangling signals /.  pins etc. I have a mild form of dyslexia and this  is totally disorganized and it's driving me batshit.