Contents


Overview

Skill Level: Beginner

Developers interested in analytics at the edge.

This recipe will show you how to connect a range sensor up to your Raspberry Pi, launch an Edgent sample that reads sensor data and runs analytics locally, then sends filtered data to Watson IoT Platform where we can visualize it and integrate it with the

Ingredients

  • Raspberry Pi
  • HC-SR04 Range Sensor (you can also use a simulated sensor)

Step-by-step

  1. Introduction

    edgent_logo_large_transparent

    Apache Edgent (incubating*) is a programming model and micro-kernel style runtime that can be embedded in gateways and small-footprint edge devices. It makes it easy to process sensor streams on edge devices like a Raspberry Pi, run local analytics, then send only the useful information to cloud services like Watson IoT Platform.

    This recipe will show you how to connect a range sensor up to your Raspberry Pi, launch an Edgent sample that reads sensor data and runs analytics locally, then sends filtered data to Watson IoT Platform where we can visualize it and integrate it with the rest of the world.

    You can find the latest version of the recipe here: https://developer.ibm.com/recipes/tutorials/send-events-to-the-watson-iot-platform-from-a-raspberry-pi-running-apache-edgent

     

3 comments on"Apache Edgent on Pi to Watson IoT Platform"

  1. KiranShashi May 29, 2016

    Interesting application, but is there a Python version of it ?
    Shashi

  2. Stan Bradbury March 14, 2017

    Just a nit. The word Quarks needs to be selectively replaced in two places in NOTE at the beginning. It currently incorrectly states:

    [Editor’s Note: Apache Edgent has been renamed to “Apache Edgent.” The post below was written before the name change. All references to Edgent in this post now apply to the Apache Edgent project.]

    • I’ve tried editing in 3 different browsers over 3 days, with no luck at being able to save my changes. Here is how it should read:

      Note: Apache Quarks has been renamed to “Apache Edgent.” The post below was written before the name change. All references to Quarks in this post now apply to the Apache Edgent project.

      Thanks for heads up!

Join The Discussion