HSC2011/Project history: Unterschied zwischen den Versionen
Keine Bearbeitungszusammenfassung |
Keine Bearbeitungszusammenfassung |
||
| Zeile 37: | Zeile 37: | ||
Handling all the communication in javascript is of course not the way to do things, so we implemented a RF protocol for the devices in hardware. | Handling all the communication in javascript is of course not the way to do things, so we implemented a RF protocol for the devices in hardware. | ||
The sessiontracking and device management is handeled by the [[HSC2011/Software/ | The sessiontracking and device management is handeled by the [[HSC2011/Software/ygor|middleware server]] written in java. | ||
Get all these different components to work on their own was a big thing to do, but getting all things work together in 6 weeks solely on time spent after our dayjobs was .. '''a real challenge''' ;) | Get all these different components to work on their own was a big thing to do, but getting all things work together in 6 weeks solely on time spent after our dayjobs was .. '''a real challenge''' ;) | ||
Version vom 2. Mai 2011, 16:54 Uhr
< HSC2011
HISTORY
The idea was quite simple in the beginning but grow into something really impressive over the next 6 weeks.
In the beginning we taught of a device with some leds and buttons to enable students to participate in multiple choice quiz shows.
But as the ideas grew how such a quizshow could look like we found out that we need a more universal approach.
We wanted blinking leds, playing sounds, multiple buttons, personalisation, but also unpersonalisation, and give some kind of feedback to the user that creates no sound but is visible
So we came up with a device that conists of
- 4 5mm leds (blue,green,yellow,red)
- 4 buttons
- 1 piezo beeper
- 1 RGB led to change the color of the enclosure
- 1 iButton reader for personalisation
- 1 RF module (RFM12B)
On the software side we used a lot of hacking wizardry a total of 5 different programming languages including a language designed exclusively for the virtual machine that grew out of this contest.
Each student gets one of these devices (battery powered or in a future design accu powered), and the teacher gets one of these devices too.
The teachers device is connected to a computer over n FTDI cable.
A really slow old one will do as long as it can run a webbrowser :)
On the teachers computer we lauch a small server that acts as the middleware connecting the serial line from the EduBuzzer to a webinterface thats available on the teachers computer.
The teacher then opens a webbrowser and navigates to this local webserver, there he picks one of the available applications and the students devices are initalized with the application logic over the radio link.
Handling all the communication in javascript is of course not the way to do things, so we implemented a RF protocol for the devices in hardware.
The sessiontracking and device management is handeled by the middleware server written in java.
Get all these different components to work on their own was a big thing to do, but getting all things work together in 6 weeks solely on time spent after our dayjobs was .. a real challenge ;)
