Our Pre-Arduino Day event was a huge success!
We hope to finalize the Arduino Day Agenda by next week.
I think we can easily say that we'll have space for ongoing displays of projects. I'd like to have some keynotes scheduled, but also do some unconference-style scheduling as well. That would mean that anyone who shows up with their Arduino project early enough can get not only table space for ongoing display, but can also put themselves on a schedule to let people know there's going to be a demo. That way, people can self-schedule demos during times that we won't have a keynote, like during workshop hacking time.
I think we should do a workshop with a name like "LOL! LOTs of LEDs!", inspired by the shield of the same name. We have lots of NeoPixel projects to demo, it's perhaps the next logical skillset to blinking an LED, and is a very versatile, useful, and accessible Arduino skill to have. We should also turn out the lights and rave for a few minutes. Maybe we even call it "NeoPixel Microrave". Let's teach people how to control light!
It would be really interesting if some pyroartists could do a presentation about Arduinos in flame effects. ;)
The room will already have some tools, and we should bring our field kit too.
I have an idea for combining an Open Hack with a Hackathon that can be ongoing, and could also tie into some of the workshops. Basically, the Holiday Hackathon required people to bring their own materials, but not everyone thought to be prepared like that. Maybe, we have some stations with certain sensors and outputs, where people can learn about using them and their libraries. People could borrow an Arduino/breadboard combo mounted side-by-side, or bring their own, learn about different sensors, and maybe eventually sign out some of the sensors. Perhaps they could gather points by completing certain exercises, or maybe they could just get points for saying how they would use it in their Hackathon project. The people who are the most interested in those boards/sensors might have their own, maybe people could sign them out to use in their hackathon projects, and if there are fewer than amount of teams who want to use them, we could choose a team whose applications we like the most. We could also offer bonuses for computing certain things with code, such as bonuses for use of conditionals, loops, strings, arrays, and helpful comments. That way, people could get their hands dirty with I/Os, while the less hardware-intensive projects could also gain points for programming. It would be great if we could integrate these stations with some of the demo projects that will be setup against the walls around the room. Perhaps instead of giving points at stations, we could just "stamp" their "passport" at each station and help them install the proper libraries.
Some example I/O Stations might be:
-ADC (analog variable resistors like pots, photocells, and FSRs...)
-Optical Couples (digital light-based communications, beam-break detection, Passive IR sensor, optoisolators...)
-Environmental Sensors (Temperature/Humidity/Dewpoint, particulate sensor, flame sensor, maybe a gas sensor...)
-Color (color sensing, UV sensing, NeoPixels, other light sensors)
-Switches (wiring buttons, sensors, pullup and pulldown resistors, debouncing with software and hardware...)
-Relays/Solenoids/Transistors (5 VDC triggering 12 VDC and 120 VDC, water valves, air and vapor valves...)
-Motors (maybe different stations for different kinds)
-Using Loops
-Using Variables
-ISP programming