1,885
edits
Changes
no edit summary
The device codename, ''Peapod'', comes from the device size and the folded-over-circuit design, which are both reminiscent of a pea pod.
== Software for FSOSS ==
The ESP8266 controller used in the ESP12F modules has a large and useful software library available. It can be programmed in Lua or C, with or without an OS (RTOS). There is 4MB of flash memory and 36M of (available) RAM. Software is loaded via a serial interface at 230kbps and further OTA updates to that software are possible.
The AP signal strength information is sufficient to determine the physical location of the device during the conference; this may be aided by additional access points added at strategic locations (which themselves could be ESP12F devices). Rather than perform the location determination on the Peapod (consuming energy), this analysis will be done on the server side. Various projects report that 2-3m accuracy is possible, but in our case, room-level accuracy is sufficient.
'''This configuration will enable:
* A count of the number of attendees present at each of the presentations and workshops
* Immediate feedback on the presentations and workshops (via the button-presses), correlated with location and time information to determine which presentation/workshop is being rated'''
'''In addition, it is proposed that the raw collected data be made available in real-time to the attendees, and that a contest be held for the most interesting use of that data by the end of the conference ''' (such as: mapping attendee travels; heat-mapping sessions; doing fine-grained user location to determine who interacted with who at the conference; determining how many people left in the middle of each session; calculating the number of trips to non-session areas such as the break room, Tim Horton's, the registration desk, or washrooms; mapping when people gave feedback on a presentation; calculating tardiness; figuring out which presentations ran overtime; etc...)
== Peapod after FSOSS ==