By Alan
Ever feel like you are being watched? Increasingly, this is true, since security cameras, traffic cameras, monitoring systems, and other kinds of video are in more and more locations. But, if you consider the definition of watching being something other than just visual pictures, you have lots of other things observing you. Motion detectors, audio detection, radar systems, all "watch" you to see if you trigger their programming.
We often never really think about the sophistication of designing automatic things that react to you. There are sensors to figure out the proximity of a person, either by infra-red lights, noise, or motion. Lots of ways to determine if a human (or at least an upright, warm, moving body) actually is nearby. Oh, the infra-red sensors know you are there. <click>
But, that's where people make a mistake. Hollywood movie science would let you believe that the sensor is on or off, and that's all that's needed. They think that the sensor is everything. They forget that you actually need to add some logic to the problem. There are tiny little controllers that use logic with the sensors to perform the behavior you need. It's not as simple as you might think.
For example, take the ultramodern public bathroom, where you have things "watching" you, even though there are no video cameras. Anything with the word automatic in their names stresses their ability to perceive if they were supposed to do something because someone was there, or wasn't there, or just arriving, or just leaving. But, they aren't just simple on/off devices. Let's look at each one with its unique behavior:
Imagine if the digital programmer got the sensor logic switched around.
Literally all of the examples here could happen. The sensors are capable of seeing when someone arrives, stays there, leaves, and when someone isn't there at all. The logic just has to be right, too.
It's the simple things that are actually harder to do than you might believe.