Which MCU functions like am "IF" statement?

[JG7_X-Man]

I am thinking I need an MCU that would check for Target ID A, If "NULL", then check for for Target ID B, and so on until it finds one. Anyone know off head what would do the trick?

[JimTM]

This post may help you.

[JG7_X-Man]

Thanks! Now let me see if I can figure out which one I need LOL!

[JimTM]

I haven't played with the logic in the post so I don't know if it fits your use case closely. There could be an easier way to get what you need. Can you give a more concreate example of your logic?

[Gambit21]

X-Man - I did this exact thing recently while designing some radar logic for over the continent.

 

I’ll try and describe but a screen shot later might be easier. Also you can do this a few ways.

 

Basically a node with consecutive timers radiating from it. If the first timer connects to its logic and that triggers says YES, then it deactivates the subsequent timers in the array.

 

If NO, then the following timer (having not received the YES deactivation) will fire - and so on. If that makes sense.

 

I also designed a boleeen switchboard but I can’t really describe it (especially typing on my phone) but only lets the signal through if all nodes are open. Any single node in OFF mode will stop the signal.

 

I’m not on the puter today or I’d post a screen.

 

 

 

Edited November 15, 2020 by Gambit21

[JG7_X-Man]

16 hours ago, Gambit21 said:

X-Man - I did this exact thing recently while designing some radar logic for over the continent.

 

I’ll try and describe but a screen shot later might be easier. Also you can do this a few ways.

 

Basically a node with consecutive timers radiating from it. If the first timer connects to its logic and that triggers says YES, then it deactivates the subsequent timers in the array.

 

If NO, then the following timer (having not received the YES deactivation) will fire - and so on. If that makes sense.

 

I also designed a boleeen switchboard but I can’t really describe it (especially typing on my phone) but only lets the signal through if all nodes are open. Any single node in OFF mode will stop the signal.

 

I’m not on the puter today or I’d post a screen.

 

 

 

@Gambit21That is exactly what I am looking for! Whenever you get around to posting a screenshot would be fantastic! Thank you!

[Gambit21]

 

I just looked at my "switch" and I'd have to paste it, make it more compact, simplify it and add notations so that it made sense to you, which I don't have time to do. (I started to, but the damn editor crashed on me 3 times and ate up the few minutes that I did have tonight)

 

It's a big piece of logic because of the stuff that it's plugged into. I’ll see if I can find time tomorrow to send along the pertinent chunk of it.

 

It's fairly simple.

A node that fires to sequential timers, picture the node in the center of a clock face, and the sequential timers like the numbers on the clock. Each of those sequential

timers is plugged into whatever trigger etc you're using. In my instance, a proximity trigger on each set to an increasingly further distance.

 

If the first timer's proximity trigger is a "yes"  then along with it's other logic, it also fires a "deactivate" to a node along the second, third, and fourth timer's logic etc.

 

If this first timer's proximity trigger doesn't fire, then of course the deactivation to the following timers is also not triggered, so the sequence continues and the second timer is now free to fire (which it does) and so on. Hope that makes sense. 

 

Essentially a linear sequence of triggers, when one goes off, it deactivates all those following it.

Edited November 16, 2020 by Gambit21

[JG7_X-Man]

9 hours ago, Gambit21 said:

 

I just looked at my "switch" and I'd have to paste it, make it more compact, simplify it and add notations so that it made sense to you, which I don't have time to do. (I started to, but the damn editor crashed on me 3 times and ate up the few minutes that I did have tonight)

 

It's a big piece of logic because of the stuff that it's plugged into. I’ll see if I can find time tomorrow to send along the pertinent chunk of it.

 

It's fairly simple.

A node that fires to sequential timers, picture the node in the center of a clock face, and the sequential timers like the numbers on the clock. Each of those sequential

timers is plugged into whatever trigger etc you're using. In my instance, a proximity trigger on each set to an increasingly further distance.

 

If the first timer's proximity trigger is a "yes"  then along with it's other logic, it also fires a "deactivate" to a node along the second, third, and fourth timer's logic etc.

 

If this first timer's proximity trigger doesn't fire, then of course the deactivation to the following timers is also not triggered, so the sequence continues and the second timer is now free to fire (which it does) and so on. Hope that makes sense. 

 

Essentially a linear sequence of triggers, when one goes off, it deactivates all those following it.

 

@Gambit21 Thank you so much! I can work with this!