multiple motion probe inputs
29 Jan 2024 15:55 - 29 Jan 2024 15:56 #291898
by Drillbit
Replied by Drillbit on topic multiple motion probe inputs
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.
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.
Last edit: 29 Jan 2024 15:56 by Drillbit.
Please Log in or Create an account to join the conversation.
29 Jan 2024 16:24 #291903
by PCW
Replied by PCW on topic multiple motion probe inputs
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.
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.
Please Log in or Create an account to join the conversation.
29 Jan 2024 20:47 #291934
by Drillbit
Replied by Drillbit on topic multiple motion probe inputs
Sorry for not getting these things earlier.
So in the custom hal I added two objects.
or2 and and2.
then I did
or2.0.in0 = probe A
and2.0.in0 = motion.digital-out-00
and2.0.in1 = probe B
or2.0.in1 = and2.0.out
motion.probe-input = or2.o.out
In other words, if P64 P0 is on then the and gate enables probe B. P65 P0 will then disable it again.
It seems to work but around long enough to know that I've missed something.
ps. I see a custom.hal, does a custom.ini exist?
So in the custom hal I added two objects.
or2 and and2.
then I did
or2.0.in0 = probe A
and2.0.in0 = motion.digital-out-00
and2.0.in1 = probe B
or2.0.in1 = and2.0.out
motion.probe-input = or2.o.out
In other words, if P64 P0 is on then the and gate enables probe B. P65 P0 will then disable it again.
It seems to work but around long enough to know that I've missed something.
ps. I see a custom.hal, does a custom.ini exist?
Please Log in or Create an account to join the conversation.
30 Jan 2024 12:14 #291974
by Aciera
Replied by Aciera on topic multiple motion probe inputs
There is no 'custom.ini'. To load your 'custom.hal' file add this to the [HAL] section of your .ini:
HALFILE = custom.hal
HALFILE = custom.hal
Please Log in or Create an account to join the conversation.
Time to create page: 0.114 seconds