Hardware Block

[mikeal]

Being that talks are only 20 minutes it would be a good idea to get an understanding of what each speaker is talking about so that we can order the talks in such a way that we can limit overlap and let the talks build on each other a bit.

@nexxy @tmpvar @mcollina what are you thinking?

[mcollina]

I'll be speaking about the MQTT protocol, the MQTT.js, the Mosca broker and how to use this stuff from node.js, on Arduino, and directly inside your web app.

I think I'll be reusing some of the materials from http://www.slideshare.net/matteocollina/exposing-m2m-to-the-rest-of-us

If there is time we can build a standalone tweetting button/alarm in the evenings on top of Arduino Yun, but I need HW for the attendees.

[mikeal]

there are additional hands-on sessions and hack time in the evening. this thread is mostly just for the 20 minute presentations in the beginning of the day. the format is posted in the README for this repo.

[tmpvar]

torn, let me get back at ya

[KarbonDallas]

I believe I will be doing something with fire this time...

I'm happy to fill-in whatever needs explaining, or do a simple demo of "getting started" with node & arduino.

I could also demo a 'color sensor', some sort of ridiculous multimedia hardware demo, or something else interactive.

[mcollina]

Would you like to do this in a two step format, first controlling the arduino with node, and then through the cloud, over the MQTT protocol? Do you think we could fit in one hour?

[mikeal]

@spikeburroughs can you make sure the venue is cool with controlled flames? we may have to shift @nexxy to an outside slot if they aren't.

[mikeal]

@mcollina i would make the 20 minute talk about whatever the most interesting thing you have to talk about is :) you should spend the 20 minutes showing something off and then making it seem accessible, but don't worry about getting people to the point they can actually use it, that's what the hands-on training sessions are for. @tmpvar would be the best person to ask what can fit in an hour trainging and what cant' since he helped run the hardware session at NodeConf.

[mcollina]

20 minutes talks are much harder then 30 or 40 minutes ones ;).

[tmpvar]

typical session flow:

• ~5 minutes intro
• ~20 minutes installing stuff and getting an led to blink with j5
• ~10 minutes to rig up a button and get it working

that leaves about 15-20 minutes of open hack time before we had them pack up the inventors kit.

We spent the majority of time getting the right version of node installed, installing serialport (which pulls down the node source tarball), etc..

Good wifi is imperative to give them more open hack time.

[mikeal]

@spikeburroughs how reliable is the wireless going to be in the venue for the talks? @mcollina kinda needs the wireless, can we get a speaker-only network?

[mikeal]

@spikeburroughs a wired connection would also work.

[mcollina]

If there is no network, I can do with a physical setup using a local ethernet network. In that case I'll need an hand in setting up everything: you'll need to do the eth network and get me an arduino, an ethernet shield, a led, a breadboard, a button and some wires.

[mcollina]

@tmpvar my thing is almost similar, but I can control arduinos through the Internet over the MQTT protocol. However, this requires some coding on the arduinos, because we need to listen for messages and react on them.