Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Mihini/EclipseCon2013 Tutorial

< Mihini
Revision as of 19:05, 13 February 2013 by Bcabe.sierrawireless.com (Talk | contribs) (Install mihini)

Tutorial

EclipseCon 2013 Tutorial plan.

Goals

Show Mihini

  • show key APIs such as logging, sched, airvantage, devicetree, (sms?)...
  • show how it's easy to do I/O manipulation and wireless communication

Koneki for Mihini

  • show how Lua is easy to edit thanks to LDT tooling
  • show EE and remote development for Mihini

Key steps

Installation of Mihini

Participants will compile and install Mihini on the Raspberry Pi based on the instructions available here

Install of ldt

Download ldt from official website or network, install remote feature.

IO code

Show by the speaker for the same reason as in the first step.

Remote run/debug

Log hello on the module.

Interact with the device tree

Write a first application to control the hardware

Wireless code

Upload first data on internet using MQTT and AirVantage

Install application

Show how to install an application using mihini (and airVantage)

Hardware

The main hardware will be a Raspberry Pi connected to an Arduino ; the Arduino itself being connected to several sensors/actuators.

Suggested sensors

Attached to the Modbus-capable Arduino

  • LED
  • light sensor
  • humidity sensor
  • temperature sensor

Other?

A LED matrix (managed through another arduino module?)

An LCD screen

Another idea: it can be interesting to allow light spot to be in front of the light sensor, so user can check if their light is on or off.

Bill of materials

Item Qty Total Cost (USD)
Raspberry Pi 1x 40.00
Arduino Uno 1x 30.00
Grove kit 1x 40.00
Micro USB cable 1x ?
4GB SD card 1x ?
USB 1A power supply 1x ?
USB A-B cable 1x ?
Wifi dongle (Netgear WNA1000M-100FRS)* 1x 20.00
TOTAL 130.00 USD
  • this might not be the best option for the US market (sounds look it is way more expensive than in Europe?)

Software

Because we can't provide a raspp for each democamp participant, we need to divide the soft in two parts. The first one will manage the IO and exposes theses data. This software will be develop and installed before the The others application will be the participant app and will use the given exposed value to interact with the IO.

To share data beteween application, it's possible to use the devicetree by storing a part of the tree in RAM.

Back to the top