174
edits
Classroom HackSpaceChallenge/Report/4: Difference between revisions
From London Hackspace Wiki
→Draft
(→Draft) |
(→Draft) |
||
| Line 13: | Line 13: | ||
[[File:protobuzzer1.jpg|thumb|The Pupil Handset]][[File:v1Hub.1.jpg|thumb|The Hub]][[File:v1dongle.1.jpg|thumb|The Teacher USB Receiver]] | [[File:protobuzzer1.jpg|thumb|The Pupil Handset]][[File:v1Hub.1.jpg|thumb|The Hub]][[File:v1dongle.1.jpg|thumb|The Teacher USB Receiver]] | ||
The software is somewhat complete, we have the back-end of a multiple choice quiz system (using Python and Twisted), it is not pretty and lots of work needs to be done on making it pretty and user friendly. It also has a web based handset simulator so we could test the software using web-enabled smart phones, rather than wait for the hardware and electronics to be finished. | The software is somewhat complete, we have the back-end of a multiple choice quiz system (using Python and Twisted), it is not pretty and lots of work needs to be done on making it pretty and user friendly. Things it currently can do: | ||
- Takes a lesson plan with one of a variety of sensible formattings (Such as Q1 Question (a) Answer). Meaning that the teachers don't have to learn a complex XML schema or other method for defining their lesson. | |||
- It has a registration scheme so that the teacher can associate the button presses with a specific student. This is done by asking the students to press the buttons on their handsets in a set order. This also doubles as a chance to see that the handset is working as the light on the handset switches colour when the handset is awaiting registration and becomes registered. | |||
- It has a powerpoint style display (done with AJAX) so that when the next question is indicated by the teacher the display of the question is updated. This allows the students to not get confused by what question they are answering. | |||
- It collects basic statistics of who pressed what buttons. Currently there is no notion of the right or wrong answer but that could be added on easily. | |||
It also has a web based handset simulator so we could test the software using web-enabled smart phones, rather than wait for the hardware and electronics to be finished. | |||
A PCB for an Arduino shield that houses an RF transmitter and an LED driver for the handset hubs. We also are working on the design of the PCB for the handset. These are very simple, just a voltage divider so we can tell what button was pressed and a RGB LED. Once these are done, it will just be a matter of soldering up some PCBs and coding up the simple software to control the Arduinos. | A PCB for an Arduino shield that houses an RF transmitter and an LED driver for the handset hubs. We also are working on the design of the PCB for the handset. These are very simple, just a voltage divider so we can tell what button was pressed and a RGB LED. Once these are done, it will just be a matter of soldering up some PCBs and coding up the simple software to control the Arduinos. | ||
| Line 29: | Line 36: | ||
Ciarán Mooney | Ciarán Mooney | ||
Will Pearson | |||
.... | .... | ||
.... | .... | ||
