multiple motion probe inputs

I have write 3 component for now i allways need to use some external component for add security logic :
-toolchanger (for lathe with past to pawl) with some built in security + auto home tool finder + allow to use additional gang tool
-orientV2 for make config simpler and more flexible + adding a jog mode + auto homing (bye-bye and2 scale and other stuff)
-spinload for managing spindle with retarded relay timing + prevent start if Touch probe is connected (bye-bye and2 scale and other stuff)

trying to do the stuff each time for use near the same config for my lathe with +-10v analog and mill with 5v analog + relay for direction so i try to have something "universal" and reusable.

Maybe the fourth need to be "probemanager" lol but i'm not really good coder so this is a lot of trial and error...
Imo i really need some reviewer but for the moment nobody seem to want to try my orientv2 so the other isn't not available online...

roland wrote:

I also use a tool length sensor and a touch-probe. Each sensor is connected to a separate input on the Mesa card.
I use the gen_muxeric component to switch between the inputs.

To switch the inputs you need G64P0 and G63P0 in the 3D-Probe macro.

This works with NO and NC. The unused touch probe can be unplugged.

Code:

# ---probe signal--- loadrt mux_generic config=bb2 addf mux-gen.00 servo-thread net probe-is-3d mux-gen.00.sel-bit-00 motion.digital-out-00 net probe-in-wzl1 mux-gen.00.in-bit-00 hm2_7i92.0.7i76.0.0.input-30-not net probe-in-3d mux-gen.00.in-bit-01 hm2_7i92.0.7i76.0.0.input-31-not net probe-in mux-gen.00.out-bit motion.probe-input -- Roland

Roland,

would you mind posting your hal file for this with any other sections or changes required?  I would like to add this functionality to probe basic macros to make it easier for those using both to be able to get up and running!  your help is greatly appreciated!!

Chris

I think a better solution is to have two probe inputs to motion. You could disable/enable them with mcode. This is the simplest for the integrator.

Chris,
I no longer use this setup. I would have to look for a backup of the old configuration.
But more than the few lines is not really necessary.
Let me know if you need more infos

Reopening an old tread, happy to add a new one if this has no traction.

I read the above and get some of the concepts but no idea what I would need to do. Two probes. A and B which cannot be linked manually without hardware.

What I need is probe = input A OR NOT(input B  ).

I dont mind if that OR is a MUX or other construct. I dont mind if the probe has to stay plugged in or not, at this point just trying to get the most basic first step.

currently I have:
motion.probe-input = probe-in = hm2 7i96s.0.gpio.000.in

How do I add in:
hm2 7i965.0.gpio.001.in_not

Forgive me but the very very basics are tripping me up, I need a toe hold. I think I'll be fine after that.

If needed I'll make it out of hardware - for me this right now seems the easier solution which makes me think I'm missing something.

Kind regards.

You can simply use the "or" component to
combine hm2 7i96s.0.gpio.000.in and
hm2 7i965.0.gpio.001.in_not pins but this
assumes that the unused input cannot be true.

The mux system is a bit safer but requires
a signal to select which input you want to use.