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

Difference between revisions of "Mihini/EclipseCon2013 Tutorial"

(DemoCamp)
m
Line 1: Line 1:
= DemoCamp =
+
= Tutorial =
 
EclipseCon 2013 Tutorial plan.
 
EclipseCon 2013 Tutorial plan.
  

Revision as of 11:07, 23 January 2013

Tutorial

EclipseCon 2013 Tutorial plan.

Goals

Show mihini

  • show key api such as log, sched, airvantage, devicertee, ...
  • show how it's easy to operate IO and wireless communication


Koneki for mihini

  • show how lua is easy to edit
  • show EE and remote targeting for mihini


Key steps

Install mihini

Maybe this step is only shown by the speaker as it's impossible to provide a raspp by participant. If some participant take their own raspp, they have to try it. See existing tuto:

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 Raspp connected to one or several asset. 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.

asset proposals:

Serre (arduino connnected by modbus)

  • light
  • light sensor
  • humidity sensor
  • temperature sensor

A matrice of Led (managed througt an arduino module)

A ldc screen

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