Skip to content

Sensor

Jump to bottom
Philippe Coval edited this page Jan 29, 2020 · 51 revisions

SENSORS

INTRODUCTION:

In IoT and embedded world, sensors and Actuator are key components to interact with the external physical world, which is the base of many use cases or Concepts.

DEMO:

To illustrate Concept, watch Sensor part of the "Smart Orchid" demo video:

web-of-things-agriculture-20180712rzr.webm

The simplest use case is just basic interaction from the RaspberryPi's button to the artik ARTIK05x's LED.

To recap here are all elements we will explain in following chapters:

  • ARTIK05s on board LED is simplest Actuator running on IoT.js and TizenRT
  • "Button sensor" on RaspberryPi is simplest sensor running on IoT.js on RaspberryPi, (connected to earlier Actuator via Gateway)
  • "Clap sensor" using webthing-node (on RaspberryPI)
  • "Ambient Light" and "Temperature" using generic-sensor-lite connected to RaspberryPi
  • "Moisture" Level Sensor on Extra Arduino MCU board
  • Actuator RGB Lamp on ESP8266 MCU

ON/OFF SENSORS:

BUTTONS SENSOR:

Webthing-node is now supporting GPIO, ARTIK530 is used as reference platform because it feature 2 onboard buttons.

Or we can validate GPIO inputs using an OpenSource hardware "buttons" board "PlayPHat":

USING NODEJS

project="webthing-node"
url="https://github.com/mozilla-iot/${project}"
branch='master'
git clone --recursive --depth 1 -b "$branch" "$url" ; cd "$project"
make -C example/platform play-phat

Expected log:

NODE_PATH=.:../.. node index play-phat
log: board: play-phat: Loading
Usage:
/home/pi/.nvm/versions/node/v8.11.4/bin/node /home/pi/webthing-iotjs/example/platform/index [board] [port]
Try:
curl -H "Accept: application/json" http://localhost:8888

log: board: play-phat: Started
log: GPIO: Left: open:
log: GPIO: Right: open:
log: GPIO: Up: open:
log: GPIO: Down: open:
log: GPIO: A: open:
log: GPIO: B: open:
log: GPIO: Start: open:
log: GPIO: Select: open:

log: GPIO: Start: change: false
log: GPIO: Start: change: true

There are two onboard buttons that can be used on ARTIK 05x board, check following IoT.js code (made for TizenRT but portable to other OS):

If using Node.js and GPIO's module this example can be used as base on GPIO11 (here used for "Flex RaspberryPi hat"):

USING IOTJS

Same as nodejs but quicker but with mentioned limitations:

project="webthing-iotjs"
url="https://github.com/rzr/${project}"
branch="master"
git clone --recursive --depth 1 -b "$branch" "$url" ; cd "$project"
make -C example/platform play-phat

Expected log:

iotjs index.js play-phat
log: board: play-phat: Loading
Usage:
iotjs index.js [board] [port]
Try:
curl -H "Accept: application/json" http://localhost:8888

log: board: play-phat: Started
log: GPIO: Left: open: null (null expected)
(...)
log: GPIO: Start: change: true
(...)
  • TODO: on failure after reboot, run again

PlayPHat

RASPBERRY PI

Note that Pi's GPIOs input mode can be configured externally, using gpio tool. IoT.js and npm's gpio module are not (yet) supporting this.

For example check Pi Hats like TrafficPHat (and its 3 buttons mini hat):

project="webthing-iotjs"
url="https://github.com/rzr/${project}"
branch="master"

mkdir -p "${url}/${branch}"
cd "${url}/${branch}"

git clone --recursive --depth 1 -b "$branch" "$url" && cd "$project"
make start/board/traffic-phat

CLAP SENSOR:

"Smart Orchid Demo" showed a "Clap sensor", which is basically just a GPIO input of KY-037's digital pin:

I used it on a Raspberry Pi using node, but it should work on any other device.

For the record I used this Flex PiHat, and modified it to plug additional sensor in (clap):

Setup should be done using the WebUI:

As explained in Flex chapter, extra setup is needed:

gpio -g mode 23 up
sudo grep gpio-23 /sys/kernel/debug/gpio
gpio-23   (                    |sysfs               ) in  hi IRQ

If curious check Mozilla blog post about an alternative way to build a "Clap sensing webthing" :

clap-sensing

ADC SENSOR

Status: In development, TODO: (Double check and upstream).

Analog input signal can be monitored using ARTIK530 (or 710 this is the one I used).

USING IOTJS RUNTIME:

IoT.js is supporting Analog Digital Converter natively so it can be used easily:

Using TizenRT:

project="webthing-iotjs"
board="artik530"
image="arm32v7/debian"
url="https://github.com/rzr/${project}"
branch="master"

git clone --recursive --depth 1 -b "$branch" "$url" && cd "$project"
sed -e "s|^FROM .*|FROM $image|g" -i Dockerfile

$sudo systemctl restart docker
time docker rm "${project}"
time docker build -t "${USER}/${project}" . # <20min first time
time docker run -t \
  --volume /sys:/sys --publish 8888:8888 --net "host" \
  --name "${project}" --rm \
  "${USER}/${project}" start/board/${board}

(...)
curl -H "Accept: application/json" http://localhost:8888
(...)
log: ADC: ADC0: open: null (null expected)
log: ADC: ADC1: open: null (null expected)
(...)
log: ADC: ADC0: change: 0%
log: ADC: ADC1: change: 0%
(...)

curl http://${HOSTNAME}.local:8888/properties/ADC0


{"ADC0":0}

If using TizenRT and not iotjs defconfig make sure to enable ADC driver and device enabled:

make menuconfig

Device Drivers / Analog Device(ADC/DAC) Support (ANALOG [=y])
Hardware Configuration / Chip Selection / S5J Peripheral Support / [*] ADC

The look at generated os/.config it should be aligned to iotjs' reference defconfig files:

# build/configs/artik*/iotjs/defconfig:CONFIG_S5J_HAVE_ADC=y
# build/configs/artik*/iotjs/defconfig:CONFIG_S5J_ADC=y
# build/configs/artik*/iotjs/defconfig:CONFIG_ADC=y

USING NODE RUNTIME:

Node.js is not supporting ADC natively but it's easy to get access to ADC driver, trough Linux kernel's sysfs interface (and docker needs to be exported to be used as RW):

sudo="sudo" # or setup docker for user
board="artik530"
project="webthing-node"
url="https://github.com/mozilla-iot/${project}"
branch="master"
image="node:10"
service_image="webthingnode_web"

git clone --recursive --depth 1 -b "$branch" "$url" && cd "$project"
sed -e "s|^FROM .*|FROM $image|g" -i Dockerfile
$sudo docker-compose up

time $sudo docker build -t "${service_image}" . # <20min
time $sudo docker run \
  --volume /sys:/sys --publish 8888:8888 --net "host" \
  --name "${project}" --rm \
  "${service_image}" make -- -C example/platform board/${board}

(...)
log: ADC: ADC1: update: 0x791
log: ADC: ADC1: change: 41%
(...)

curl http://${HOSTNAME}.local:8888/properties/ADC0
{"ADC0":42}

Note: --net "host" option is needed, because you'll face an Express's 403 issue if not using localhost.

Related:

COLOR SENSOR

A good example to practice is this color sensor kit that provides a simulator and also a driver for I2C TCS34725 sensor.

It should work with Adafruit RGB Color Sensor with IR Filter and White LED - TCS34725 [ADA1334] :

color

More hints shared at:

Relate to:

GENERIC SENSORS:

Note: It's possible to use I2C sensors on IoT.js but since some sensors changes are not yet upstreamed this chapter starts to explain the currently supported use.

In "Smart Orchid demo" "I2C sensors were connected to RaspberryPi's bus of Gateway (using Node,js runtime), then the "Generic sensors adapter" was installed as Gateway's addon (released since mozilla-iot-gateway-0.4).

mozilla-iot-gateway-sensors-20180406rzr

The adapter is built on a high level wrapper abstract drivers, "generic-sensor-lite" module can be also used outside Gateway, check more detail on project page:

Check supported sensors For now I recommend to use either BH1650 (i2c=0x23) or BMP082 (i2c=0x77) modules, community implemented drivers, which are supported by NPM community, since my fixes were upstreamed.

Now you can try to create webthings, I suggest to start making them for supported Node.js and then port to IoT.js (in development).

I2C SENSORS

IoT.js is supporting I2C API, so more sensors can be supported:

While node needs an external module:

Usage on GNU/Linux (here Raspbian):

sudo apt-get install i2c-tools make git
sudo raspi-config # Enable i2c
lsmod  | grep i2c
# i2c_bcm2835            16384  0
# i2c_dev                16384  0
ls -l /dev/i2c* || sudo reboot

sudo /usr/sbin/i2cdetect -y 1

git clone --recursive https://github.com/rzr/generic-sensors-lite
make -C generic-sensors-lite runtime=iotjs run
# (...)
# log: ambientlight: 30.833333333333336
# (...)

Then check example to make a real webthing, on GNU/Linux:

make runtime=iotjs run
make -C example/webthing runtime=iotjs run
# (...)
# log: AmbientLight: AmbientLight: change: 28.333333333333336
# log: Temperature: Temperature: change: 33
# (...)

TODO: I2C on ARTIK10

Test on Fedora 22 - armhfp on ARTIK10 (on J27):

sudo dnf install i2c-tools
ls -l /dev/i2c*
sudo /usr/sbin/i2cdetect -y 0
#      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
# (...)
# 60: -- -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- 


sudo /usr/sbin/i2cdetect -y 9
Error: Can't use SMBus Quick Write command on this bus

Related:

TODO: I2C ON TIZENRT

On TizenRT i2c tool can be enabled for scanning bus:

TASH>> 
i2c bus
BUS   EXISTS?
Bus 0: YES
Bus 1: YES
Bus 2: YES
Bus 3: YES

i2c dev -b 0 03 77
i2c dev -f 40000 -b 1 0x20 0x2f

ToDo:

STATUS: UPSTREAMING

For the record following repos were used:

RESOURCES:

LICENSE: CC-BY-SA-4.0

LOST ?

Check Concept page for overview, Gateway to get started, IotJs page to install runtime to build webthing as explained in Home page.

For further experiments check Social and Sensor, or Extra parts like WebApp (for Tizen or PWA) or MCU info about running on other microcontrollers not supported by TizenRT.

While Home focus mostly on using iotjs to build webthings (on GNU/Linux or TizenRT for ARTIK05X devices).

FEEDBACK: WELCOME

This document is still in draft state, but reviews are always welcome, if you try to replicate it and stuck on missing instructions I would appreciate that you file issues or even better make pull request (just edit in github) that insert "TODO marks" in following chapters, like:

  • TODO: please explain more this chapter and then remove this TODO line

Community contributions are welcome at:

Support is also possible, ask in:

DISCLAIMER:

WARNING: Developement branches could break over time.

Instead of maintaining "quick and dirty" demo code, I decided to split demo in smaller independents parts (which can reused) and I am upstreaming the most I can.

Then support can be done on mainline branches (or released versions).

Note that, Upstreaming can be a slow process, so snapshots links will remain until 100% of code is upstreamed.

Licence:

Reference documentation is at:

INDEX

Clone this wiki locally