Second Probe

How would one add a second, inverted probed onto a 7i96 card? I currently have a touch probe that closes a ground loop between my router bit and a metal plate. I built a touch probe for G-Ripper that opens a ground loop, therefore they can't be paralleled. Does one need to use motion.probe? Can one add another pin that will act like the same?

Hi

forum.linuxcnc.org/38-general-linuxcnc-q...-motion-probe-inputs

I guess if I look at the forum list, I might have seen this
I followed the text file you posted, but the error I get upon opening axis is that and2 already exists at loadrt and2 names=and2.combined.setter.
Here is what I changes the text to, in my custom.hal file if that might matter:

# --- probe signals separated for probe + toolsetter with status checking and possible bypass from macro ---
loadrt or2 names=or2.combined-touch
loadrt and2 names=and2.combined-probe
loadrt and2 names=and2.combined-setter
loadrt not names=not.combined-probe-on
loadrt not names=not.combined-setter-on
addf or2.combined-touch servo-thread
addf not.combined-probe-on servo-thread
addf not.combined-setter-on servo-thread
addf and2.combined-probe servo-thread
addf and2.combined-setter servo-thread

net touch-probe-not-in <= motion.digital-out-01
net touch-probe-not-in => not.combined-probe-on.in

net touch-setter-not-in <= motion.digital-out-02
net touch-setter-not-in => not.combined-setter-on.in

net touch-probe <= hm2_7i96.0.gpio.006.in
#net touch-probe <= hm2_7i96.0.0.input-14
net touch-probe => and2.combined-probe.in0
net touch-probe-on-psng <= not.combined-probe-on.out # M65 P1 activate / M64 P1 inhibit output from macro #motion.digital-out-01
net touch-probe-on-psng => and2.combined-probe.in1;
net touch-probe-and2-psng <= and2.combined-probe.out
net touch-probe-and2-psng => or2.combined-touch.in0

net touch-setter <= hm2_7i96.0.gpio.008.in_not
net touch-setter => and2.combined-setter.in0
net touch-setter-on-psng <= not.combined-setter-on.out # M65 P2 activate / M64 P2 inhibit output from macro #motion.digital-out-02
net touch-setter-on-psng => and2.combined-setter.in1
net touch-setter-and2-psng <= and2.combined-setter.out
net touch-setter-and2-psng => or2.combined-touch.in1

net touch-probe-combined <= or2.combined-touch.out
net touch-probe-combined => motion.probe-input

I appologize with this setup you need to use

[HAL]
TWOPASS=ON


or you need to do the loadrt in only one line like thi exemple
loadrt and2 names=and2.combined-probe, and2.combined-setter
loadrt not names=not.combined-probe-on, not.combined-setter-on

That worked, but I had to do this in the hal fil, change from
#loadrt [HOSTMOT2](DRIVER) board_ip=[HOSTMOT2](IPADDRESS) config="num_encoders=[HOSTMOT2](ENCODERS) num_stepgens=[HOSTMOT2](STEPGENS) num_pwmgens=[HOSTMOT2](PWMGENS) sserial_port_0=[HOSTMOT2](SSERIAL_PORT)"
to this
loadrt hm2_eth board_ip="192.168.1.121" config="num_encoders=1 num_stepgens=4 num_pwmgens=1 sserial_port_0=1"
The debug from starting the file was telling me I had a rtapi-app-main:permission denied in the start-up

BUT,
now when I start the cnc program, I can't home the Z axis easily, as it stops on probe input, and then the Y axis claims it is not in sync (dual motors). I took out the twopass, and tried
loadrt and2 names=and2.combined-probe, and2.combined-setter
loadrt not names=not.combined-probe-on, not.combined-setter-on
starting the cnc debuged out "Invalid parameter 'and2.combined-setter'

I'm using multiple or2s so ignore the limit switch ones. This setup is working for me.

loadrt or2 names=or2.x_limit_switch,or2.y_limit_switch,or2.z_limit_switch,or2.probe_in
addf or2.probe_in servo-thread
addf or2.x_limit_switch servo-thread
addf or2.y_limit_switch servo-thread
addf or2.z_limit_switch servo-thread

#Touch-plate
net deb-tplate-in debounce.0.0.in <= hm2_5i25.0.7i76.0.0.input-05-not
net tplate-in debounce.0.0.out
net tplate-in => or2.probe_in.in0

#3d Probe
net deb-probe-in debounce.2.0.in <= hm2_5i25.0.7i76.0.0.input-11-not
net probe-in debounce.2.0.out
net probe-in => or2.probe_in.in1

I copy past again, i use this config all the days at this moment.

the two pass option is imo a good things allow you to add more or2 and2 and other in other place in the file or in other hal llike postgui

edited message for clarification

The issue I seem to have with this setup is the probe being tripped anytime \I have the NC probe plugged in. I checked the hal pins on the HAL configuration window, and the probes show red until I trip either of the probes. When I unplug the NC probe, the Z-axis moves freely, and will home.
I by-passes the wiring from the NC probe in case there was some interference, and changed the gpio.
When I use M65/M64 to turn off the NC probe, all is well, when I activate that probe, the Z-axis
I have used the above script, only changing the and2 and not to one line for now.
Any suggestions?

It seem you need to use something like [HMOT] (CARD0) .7i76.0.0.input-14-not

Maybe your probe is NC but it is PNP or NPN can do the difference !

and2.combined-probe.in0 need to be FALSE with probe connected and TRUE when triggered or unconnected
and2.combined-setter.in0 need to be FALSE with setter connected and TRUE when triggered or unconnected

so you need "your-input-pin-not" or use a not component