Make a simple Alarm System! For Beginners! Tutorial # 2

[ccsteph22]

Hey, if you don't know me, I'm the guy who made the Beginners Hover Drive tutorial...
Well, here is one for a simple Alarm System ^_^...




Thanks!

[mattwd0526]

The reason it kept beeping is because it had a distance of less than 200: the distance was 0 because it had no target. Use an inrange (exclusive) or whatever it's called, which says if 0<X<200 then trigger, else don't do it. This way it won't keep beeping after it loses its target.

But nice job, nice effort.

[ccsteph22]

Okay, thanks!

[mattwd0526]

By the way, the "exclusive" means that it is only numbers between the two, whereas "inclusive" is numbers between the two, as well as the given two.

[Divran]

By the way, the "exclusive" means that it is only numbers between the two, whereas "inclusive" is numbers between the two, as well as the given two.

So then exclusive is "num1 < x < num2" and inclusive is "num1 <= x <= num2"

[computerkid2000]

wow i am suprised that no one had the idea of adding a turret in front of what ever your trying to protect! so it shoots the person when he gets too close!

[-=Fox=-]

wow i am surprised that no one had the idea of adding a turret in front of what ever your trying to protect! so it shoots the person when he gets too close!

Wow... my sarcasm meter just blew the hell up... :lol:

[Smb1014]

i followed all of your steps but this damn thing won't stop beeping. Even when I'm not in range anymore it continues to beep. Any help?

[NiiroKitsune]

There's plenty of ways to go about fixing it, but I personally believe it's not efficient, and if you want to use the minimum amount of chips, I suggest you do:
1) Make your Target Finder with the settings like in the video.
2) Make a Sound Emitter with the sound you want to use, place it on the board.
3) Wire the Sound Emitter to the Target Finder.

It should now work as normally.

-Wait, why?
Simple, the Target finder gives off the number 1 or 0 if it has something in range, or not. So, when something IS in range (1) it will send that to the Sound Emitter. And the general rule about everything is 1 is on, 0 is off. And since you DON'T even need the beacon to make this 1 and 0 happen, it still works! and you only needed 2 chips vs the 6 with solution?

Hope this helps anyone who still had issues (like me)

[thetree]

There's plenty of ways to go about fixing it, but I personally believe it's not efficient, and if you want to use the minimum amount of chips, I suggest you do:
1) Make your Target Finder with the settings like in the video.
2) Make a Sound Emitter with the sound you want to use, place it on the board.
3) Wire the Sound Emitter to the Target Finder.

It should now work as normally.

-Wait, why?
Simple, the Target finder gives off the number 1 or 0 if it has something in range, or not. So, when something IS in range (1) it will send that to the Sound Emitter. And the general rule about everything is 1 is on, 0 is off. And since you DON'T even need the beacon to make this 1 and 0 happen, it still works! and you only needed 2 chips vs the 6 with solution?

Hope this helps anyone who still had issues (like me)

Surely this doesnt work as target finders have no range, as long as the target finder has a target the soundemitter will play which could get just a tad annoying.