Proof of Concept¶

This page will contain the plans for the Proof of Concept.

• Table of contents
• Proof of Concept
• Summary
• Block Diagram
• Components
  • Server Node
    • UI
    • Wifi
  • IoT Node
    • Hardware Components
    • Software Components
    • Mechanical Device

Summary¶

Show a server node managing an IoT node. The server node should be a Raspberry Pi running PiBox with the Media Server UI and the IoT should be a board utilizing an Atmel or similar chip capable of controlling a physical device. The physical device should be a vent whose fins can be opened and closed with the IoT device. The server node and IoT node should communicate over WiFi or, possibly, Bluetooth.

The goal of this phase of development is to prove we understand enough about the following concepts to produce a minimal viable product (MVP).

• Server OS
• UI implementation
• Wireless communication
• Microcontroller platform hardware integration
• Microcontroller programming
• Control of mechanical devices, specifically motors

Block Diagram¶

Components¶

Server Node¶

PiBox will serve as the server node OS. This platform already supports Wifi and the Media Server release has a simple, easy to see (for demos) custom UI that should be easily extendable using examples like PiClock.

UI¶

The UI will require a new app developed. This will be a GTK+ 2.x app that conforms to the app specification for PiBox's Media Server, which just means it provides its app icon for the navigation and installs an app configuration file with its opkgs.

The app will consist of two buttons and a text window. The first button will be use to open the vent. The second to close it. A text field will show the current status of the vent provided by the IoT Node.

Wifi¶

Wifi setup can either use a router or use PiBox's configuration option for running as an access point. The latter may be more useful for demos.

IoT Node¶

Hardware Components¶

Software Components¶

Mechanical Device¶