multiple motion probe inputs

Use the NOT component to invert those inputs:
net invert_pin_1 ==== hm2_7i76e.0.7i76.0.0.input-08-not >> not.0.in
net inverted_out_1==== probe-in << not.0.out

Something like that. Added = <> so it is easier to follow.

hmm the official documentation for the NOT component is very sparse...

How would that change my Situation, i already invert my inputs with -not so im confused what it would change to invert them again (back to normal state)

Imo this change nothing

You need to add a logic for deativate the output from Or2 if probe is see as unconnected

I have copy past my config that is close to be able to do that using M64 M65

maybe something like this can work :

[strike]
# --- probe signals separated for probe + toolsetter with status managing (beta)
loadrt or2 names=or2.combined-touch
loadrt and2 names=and2.combined-probe
addf or2.combined-touch servo-thread
addf and2.combined-probe servo-thread


net touch-probe <= [HMOT](CARD0).7i76.0.0.input-14-not
net touch-probe => and2.combined-probe.in0
net touch-probe-on-psng <= [HMOT](CARD0).7i76.0.0.input-14
# i think this is too easy and need to add some timedelay else the probe stop to work if you simply use it
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 <= [HMOT](CARD0).7i76.0.0.input-15
net touch-setter => or2.combined-touch.in1

net touch-probe-combined <= or2.combined-touch.out
net touch-probe-combined => motion.probe-input
[/strike]
100% untested and 100% sure that need more to allow working

not sure what this part means

Stran_ge wrote: not sure what this part means

Code:

[HMOT](CARD0)

HMOT section in the ini file, CRAD0 name <<< used for Mesa boards so in case of changing the card from say 7i96 to 7i76E there is only one entry that needs to be changed, not every line in hal pertaining to that card.