Alright, I’ll admit it…I was on a quiz team of some variety for six years. Nearly half of my public education.
While I’ve since realized that FIRST is a whole lot more fun, there are still times where a buzzer system is useful.
So here’s what I’m thinking…
Red buzzer: Sensor 1
Blue buzzer: Sensor 2
Teacher clearing buzzer: Sensor 3
Then have lights/motors/whatever on A, B, and C, with the same order.
Here’s what I had in mind: The teacher hits her (note: his and her can refer to anyone–it’s just that writing his/her every time is a pain) touch sensor to clear the buzzer, then starts reading the question. If a student buzzes early (by pressing the sensor), their light/motor cuts on and locks out the other sensor. If neither student buzzes, then the teacher pushes again to start a five (or ten, or whatever) countdown after the question. Buzz, and it stops the clock and the other sensor. If the timer buzzes, then the teacher light comes on, and both students are locked out. (In effect, it acts like another buzzer, except that it’s automated.)
Here’s my english coding:
On teacher sensor press: Buzzerstatus=0 Timer=0 On teacher sensor repress: Start timer, display on RCX If timer=5 seconds buzzerstatus=1 Activate output C Goto start On red buzzes: If buzzerstatus=1, do nothing If buzzerstatus=0, make buzzerstatus=1 Activate output A On blue buzzes: If buzzerstatus=1, do nothing If buzzerstatus=0, make buzzerstatus=1 Activate output B
From there, it’s just a matter of making it purdy. If you’d like to allow multiple students to buzz for a team and don’t care who exactly buzzes, then just stack the touch sensors on top of each other for a nice big OR sensor. (If you’ve got another RCX, then I guess you could use it for scoring, but that’s another post.)