Professional Documents
Culture Documents
Slides:
http://senzations.net/wp-content/uploads/2014/66/Senzations14-GallileoOverview.pdf
Slides:
http://senzations.net/wp-content/uploads/2014/66/Senzations14-GallileoConnectivity-v3.pdf
I/O Basics
o Available I/O options on the Galileo
o Serial I/O using Arduino
Sensing and actuating with the Grover Starter Kit
o Digital I/O
o Analog I/O
Slides:
http://senzations.net/wp-content/uploads/2014/66/Senzations14-Gallileo-IOSensing.pdf
Xively integration
Slides:
IoT.pdf
http://senzations.net/wp-content/uploads/2014/66/Senzations-14-Galileo-
Basics of node.js
How to deploy a node.js server on Galileo
Interacting with Galileo through the browser
Reading and displaying sensor data
Slides: http://senzations.net/wp-content/uploads/2014/66/Senzations14-Networkingnodejs.pdf
Slides:
http://senzations.net/wp-content/uploads/2014/66/Senzations14-GallileoAdvanced-Python.pdf
All lectures were video recorded and should be available on youtube in the coming
weeks.
The tutorial requires and ssh/sftp client on the laptops. While most MAC and
Linux installations come out of box with one, you may need to provide
additional clients for Windows (e.g. putty/WinSCP).
We distributed the Galileo Arduino IDE on three memory sticks just before the
tutorial start and it took the crowd only 15 mins to copy all files needed,
which seems a good way in getting the development infrastructure set up, in
the lack of a very high bandwidth internet connection.
Various people did not get the Arduino IDE to work out of the box on their
Windows machines. The main issue seems to be a non-English locale setting
on their laptops (expect this with international students!!!), preventing the
IDE to start. It took quite some time to figure this one out at the expense of
time available for the tutorial.
The whole tutorial took longer time than initially expected. We had 3 hours as
initial plan but then ended up to use 5 hours, which we kindly got from the
organisers.
Expect participants to arrive with all kinds of OS on their laptops (different
versions of Windows, Linux and MAC) provide adequate IDEs/tools for these
on the memory stick and be prepared to have some trouble shooting
experience on all these systems.
Make all tutorial slides available at the beginning of the event so the
participants can use it as a reference during the tutorial. This is sth that we
initially overlooked - we spend quite some time flipping between slides on the
projector.
Expect participants to have different levels of expertise and experience. Try
to leverage experienced participants to help with the less experienced ones
(or team up) so you can effectively move forward with the tutorial material.
An excellent network connectivity is key for the tutorial. Each participant will
use at least two network connections, one for its Galileo and the other for its
laptop ( I am not counting in personal mobiles). This can quickly overload any
Wifi access point that you may use. Make sure you have multiple alternative
access points available or even better a set of Ethernet ports for all Galileos
in the tutorial. One issue we discovered with our Wifi router was that failed to
provide DHCP leases to participants. This was due to default setting in the
router, limiting the maximum number of client devices to 30. Again this took
us some time to figure out - increase this limit to avoid any issues.
If you run this tutorial in a hotel or typical conference site, you are often
required to first register your wireless Internet device with a browser based
authentication step. This cannot be easily done with a Galileo that does not
run a UI. Make sure you have an access point for the Wifi that is under your
control and where you can run with WPA like encryption instead. A
workaround is to use some script that performs the authentication on your
behalf. A student wrote a nice python script that he shared later with other
participants.
We pre-provisioned an SD card image that included all basic configs (e.g. wifi
config, ssh server setup) and some coding examples for nodejs and python.
This saved considerable time during tutorial that would be otherwise wasted.
Various people may come with their own Arduino IDE installed and will try to
program the Galileo with it. Make sure you explicitly tell them to use Intels
IDE.