Talk in English - US at OpenWest Conference 2017
Track Name:
HALL1 - Community
Short URL: https://joind.in/talk/0de71
(QR-Code (opens in new window))
PicoLabs new Pico Engine is an Internet of Things (IoT) platform. Pico Engine allows easy management of connected devices with rule based behavior, while introducing a new way to represent the real world state of “things”. This new paradigm is called Picos. Picos are very similar to device trees. While a device tree is a data structure that describes hardware, a Pico is a data structure that describe IoT devices. Picos provide concise way to represent “things” states, allowing actor model programing through KRL rules to produce dynamic control and accurate reports of IoT devices.
The distributed nature of IoT makes Building large Pico systems intimidating and difficult task to begin. This intimidation can be resolved with better documentation and examples.
My goal is to resolve the difficulty of starting a IoT project built on Pico Engine by providing a detailed documented example. This example will serve has a pattern for solving IoT problems with Pico systems. To accomplish my goal, I will present an over-engineered jack-in-the-box built on the Pico engine.
The jack-in-the-box will have an observer watching the state of a crank, an actor to trigger the latch opening and other actor playing music to the crank cranking. This demo will be built with a Pico engine running on a raspberry pi with a few components. The Pico system will show how to monitor sensors and react to specific readings.
By turning a trivial kids toy into a IoT device I will demonstrate Pico Systems provide a dynamic, informative, scalable solution to Iot problems.
The over-engineered jack-in-the-box provides an entertaining working example of all components needed to produce a complex IoT solution.
My talk will discuss the engineering behind the over-engineered jack-in-the-box, the role of an actor-model system like the Pico engine in building IoT systems, the underlying components, and the pros and cons of the approach. [277]
Comments
Comments are closed.