All posts by admin

Mqtt with Beaglebone and ESP8266 – Freeboard

2017-04-22 admin

After the Mqtt web client installation

MQTT with Beaglebone and ESP8266 – WebServer and MQTT WebSocket

let’s install now the dashboard freeboard

In a ssh commad shell go into the /var/www/html folder on Beaglebone as root and clone the freeboard github respository; change the owner of the freeboard folder in www-data:www-data

#cd /var/www/html
#git clone https://github.com/Freeboard/freeboard.git freeboard
#chown www-data:www-data -R freeboard

#cd /var/www/html

#git clone https://github.com/Freeboard/freeboard.git freeboard

#chown www-data:www-data -R freeboard

With a web browser go to the freeboard folder on Beaglebone webserver to access the dashboard

We have to add now Freeboard additional plugins. We add the following

freeboard-mqtt

Clone the https://github.com/alsm/freeboard-mqtt github

#cd
#git clone https://github.com/alsm/freeboard-mqtt

1 2	#cd #git clone https://github.com/alsm/freeboard-mqtt

Download the mqtt paho javascript library

Paho mqtt javascript library

#cd
#git clone https://github.com/eclipse/paho.mqtt.javascript.git

1 2	#cd #git clone https://github.com/eclipse/paho.mqtt.javascript.git

Here is the direct link to the library

Last Version mqttws31.js

Create the mqtt folder under the Freeboard plugins folder and copy the mqttws31.js and paho.mqtt.plugin.js files

#cd /var/www/html/freeboard/plugins/mqtt
# ls
mqttws31.js  paho.mqtt.plugin.js

#cd /var/www/html/freeboard/plugins/mqtt

# ls

mqttws31.js paho.mqtt.plugin.js

Edit the paho.mqtt.plugin.js file and insert the reference to the mqttws31.js library in the external_scripts section; in this case too we have to change the folder and contents owner

// # A Freeboard Plugin that uses the Eclipse Paho javascript client to read MQTT messages

(function()
{
        // ### Datasource Definition
        //
        // -------------------
        freeboard.loadDatasourcePlugin({
                "type_name"   : "paho_mqtt",
                "display_name": "Paho MQTT",
        "description" : "Receive data from an MQTT server.",
                "external_scripts" : [
                        "plugins/mqtt/mqttws31.js"
                ],
                "settings"    : [

// # A Freeboard Plugin that uses the Eclipse Paho javascript client to read MQTT messages

(function()

{

// ### Datasource Definition

// -------------------

freeboard.loadDatasourcePlugin({

"type_name" : "paho_mqtt",

"display_name": "Paho MQTT",

"description" : "Receive data from an MQTT server.",

"external_scripts" : [

"plugins/mqtt/mqttws31.js"

"settings" : [

Change the owner

#cd /var/www/html/freeboard/plugins
#chown www-data:www-data -R mqtt

1 2	#cd /var/www/html/freeboard/plugins #chown www-data:www-data -R mqtt

Edit the /var/www/html/freeboard/index.html file and insert the reference to the paho.mqtt.plugin.js plugin in the heads.js section

<!DOCTYPE html>
<html>
<head>
    <meta charset="UTF-8">
    <title>freeboard</title>
        <meta name="mobile-web-app-capable" content="yes">
    <meta name="apple-mobile-web-app-capable" content="yes" />
    <meta name="apple-mobile-web-app-status-bar-style" content="black" />
    <meta name="viewport" content = "width = device-width, initial-scale = 1, user-scalable = no" />
    <link href="css/freeboard.min.css" rel="stylesheet" />
    <script src="js/freeboard.thirdparty.min.js"></script>
    <script type="text/javascript">
        head.js("js/freeboard_plugins.min.js",
                "plugins/mqtt/paho.mqtt.plugin.js",
                // *** Load more plugins here ***
                function(){

<!DOCTYPE html>

<html>

<head>

<title>freeboard</title>

head.js("js/freeboard_plugins.min.js",

"plugins/mqtt/paho.mqtt.plugin.js",

// *** Load more plugins here ***

function(){

Add the dynamic-highcharts plugin

Clone in a folder the github

git clone https://github.com/onlinux/freeboard-dynamic-highcharts-plugin

1	git clone https://github.com/onlinux/freeboard-dynamic-highcharts-plugin

Copy the plugin_highcharts.js to the folder /var/www/html/plugins/thirdparty and change the owner

#cd /var/www/html/freeboard/plugins/thirdparty
#chown www-data:www-data plugin_highcharts.js

1 2	#cd /var/www/html/freeboard/plugins/thirdparty #chown www-data:www-data plugin_highcharts.js

Edit again the file /var/www/html/freeboard/index.html and add the plugin as done above

<!DOCTYPE html>
<html>
<head>
    <meta charset="UTF-8">
    <title>freeboard</title>
        <meta name="mobile-web-app-capable" content="yes">
    <meta name="apple-mobile-web-app-capable" content="yes" />
    <meta name="apple-mobile-web-app-status-bar-style" content="black" />
    <meta name="viewport" content = "width = device-width, initial-scale = 1, user-scalable = no" />
    <link href="css/freeboard.min.css" rel="stylesheet" />
    <script src="js/freeboard.thirdparty.min.js"></script>
    <script type="text/javascript">
        head.js("js/freeboard_plugins.min.js",
                "plugins/thirdparty/plugin_highcharts.js",
                "plugins/mqtt/paho.mqtt.plugin.js",
                // *** Load more plugins here ***
                function(){

<!DOCTYPE html>

<html>

<head>

<title>freeboard</title>

head.js("js/freeboard_plugins.min.js",

"plugins/thirdparty/plugin_highcharts.js",

"plugins/mqtt/paho.mqtt.plugin.js",

// *** Load more plugins here ***

function(){

Access now the Freeboard dashboard and add the links to the temperature and humidity topics, the gauges and timeseries mesauring the values in real time and in a specific range of time . Here are some settings:

Datasource

Gauge

Timeseries

Chrome/Chromium browser allows to save the settings in a json file. This settings can be loaded locally or loaded from the web server, saving for example the dashboard.json file in /var/www/html/freeboard, with the url

http://beaglebone.local/freeboard/index.html?load=dashboard.json

1	http://beaglebone.local/freeboard/index.html?load=dashboard.json

The image shows the Freeboad interface with various widgets showing the status and timeseries of the ESP8266 relay and sensors

In these series of articles we configured the envinronment to access the Beaglebone using the beaglebone.local/beaglebone alias

Debian sd card setup for Beaglebone Black

but you can use anyway the Beaglebone IP tho access the services provided by the board.

In the next article we’ll treat the Mqtt Android client

Mqtt with Beaglebone and ESP8266 – Android Client

Development, Software

Libreelec8 in OrangePI PC

2017-04-13 admin

This article describes the steps that I ran to prepare a first version of Libreelec 8 in Orange PI PC cards and other H3 socs.

Starting from the Debian development envinronment, with its installed packages, already used for the compilation of OpenELEC 7

Openelec compilation for Orange PI PC

we proceed to build an Libreelec 8 image.

We started as basis from the work done for Openelec 7 and Libreelec 7 available on the two github repositories

H3 Openelec 7 Github

H3 Libreelec 7 Github

sviluppo@debian8:~/orangepi$ mkdir libreelec
sviluppo@debian8:~/orangepi$ cd libreelec
sviluppo@debian8:~/orangepi/libreelec$

sviluppo@debian8:~/orangepi$ mkdir libreelec

sviluppo@debian8:~/orangepi$ cd libreelec

sviluppo@debian8:~/orangepi/libreelec$

Clone the Libreelec8 github

git clone -b libreelec-8.0 https://github.com/LibreELEC/LibreELEC.tv.git libreelec-8.0

1	git clone -b libreelec-8.0 https://github.com/LibreELEC/LibreELEC.tv.git libreelec-8.0

The patches have been created for a specific version of the commit, so we align our github clone to that version

cd libreelec-8.0
git checkout 745f6790ec0456aa8478fff5360107c148ea5204

1 2	cd libreelec-8.0 git checkout 745f6790ec0456aa8478fff5360107c148ea5204

Download from the following link the patches, the H3 project and other stuff

H3 Libreelec 8

Unzip this file in /home/sviluppo/orangepi/libreelec

Run the following steps

1)Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/projects the folder

2) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/multimedia the folders

cedarx
libmpeg2

3) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/tools the folder

sunxi-tools

4) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/sysutils the folder

sunxi-sys-utils

5) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/graphics the folder

sunxi-mali

6) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/linux-drivers the folder

mt7601u

7) The following patches are available in /home/sviluppo/orangepi/libreelec/H3LE8/patches folder

linux.patch

image.patch

mkimage.patch

kodi.patch

libcec.patch

u-boot.patch

u-boot-release.patch

u-boot-update.patch

Patch the code from the /home/sviluppo/orangepi/libreelec folder running the following commands

patch  libreelec-8.0/packages/linux/package.mk < H3LE8/patches/linux.patch
patch  libreelec-8.0/scripts/image < H3LE8/patches/image.patch
patch  libreelec-8.0/scripts/mkimage < H3LE8/patches/mkimage.patch
patch libreelec-8.0/packages/mediacenter/kodi/package.mk < H3LE8/patches/kodi.patch 
patch  libreelec-8.0/packages/devel/libcec/package.mk < H3LE8/patches/libcec.patch
patch libreelec-8.0/packages/tools/u-boot/package.mk < H3LE8/patches/u-boot.patch
patch libreelec-8.0/packages/tools/u-boot/release < H3LE8/patches/u-boot-release.patch
patch libreelec-8.0/packages/tools/u-boot/scripts/update.sh < H3LE8/patches/u-boot-update.patch

patch libreelec-8.0/packages/linux/package.mk < H3LE8/patches/linux.patch

patch libreelec-8.0/scripts/image < H3LE8/patches/image.patch

patch libreelec-8.0/scripts/mkimage < H3LE8/patches/mkimage.patch

patch libreelec-8.0/packages/mediacenter/kodi/package.mk < H3LE8/patches/kodi.patch

patch libreelec-8.0/packages/devel/libcec/package.mk < H3LE8/patches/libcec.patch

patch libreelec-8.0/packages/tools/u-boot/package.mk < H3LE8/patches/u-boot.patch

patch libreelec-8.0/packages/tools/u-boot/release < H3LE8/patches/u-boot-release.patch

patch libreelec-8.0/packages/tools/u-boot/scripts/update.sh < H3LE8/patches/u-boot-update.patch

Proceed to the image build for Orange PI PC from the folder /home/sviluppo/orangepi/libreelec/libreelec-8.0 running

ARCH=arm PROJECT=H3 SYSTEM=opipc  make image

1	ARCH=arm PROJECT=H3 SYSTEM=opipc make image

At the end of the compilation in the /home/sviluppo/orangepi/libreelec/libreelec-8.0/target folder we find the files to install or update Libreelec 8

At the link

Openelec 7 H3 FAQ

we find the boards we can build changing the SYSTEM parameter in the building command

SYSTEM=opi2
SYSTEM=opione
SYSTEM=opipc
SYSTEM=opiplus
SYSTEM=opilite
SYSTEM=opipcplus
SYSTEM=opiplus2e
SYSTEM=bpim2p
SYSTEM=bx2

ARCH=arm PROJECT=H3 SYSTEM=BOARD  make image

1	ARCH=arm PROJECT=H3 SYSTEM=BOARD make image

This image is a first attempt to build Libreelec 8 for H3 socs. The image was installed on Orange PI PC and the system worked well, but still bugs and malfunctions may occur.

Here is the built Libreelec 8 image for Orange PI PC

Orange PI PC Libreelec 8 Image

We tested this image on an Orange PI PC board.

Here are other images we did’t test on the devices

Orange Pi2 Libreelec 8 Image

Orange Pi Lite Libreelec 8 Image

Orange Pi One Libreelec 8 Image

Orange Pi PC Plus Libreelec 8 Image

Orange Pi Plus Libreelec 8 Image

Orange Pi Plus 2e Libreelec 8 Image

WARNING: The image installation on the device is at your own risk. We accept no responsibility if the installation leads to malfunction or block of the device.

The following article shows how to build the addons

Libreelec 8 addon building for Orange PI PC

Configuration, Software

MQTT with BeagleBone and ESP8266 – WebServer and MQTT WebSocket

2017-04-08 admin

After the MQTT server and ESP8266 nodes configurations

MQTT with BeagleBone and ESP8266 – Mosquitto installation on Beaglebone

MQTT with BeagleBone and ESP8266-MQTT ESP8266

MQTT with BeagleBone and ESP8266 – MQTT on ESP8266 with temperature sensor

MQTT with BeagleBone and ESP8266 – MQTT on ESP8266 with Relay

we analize now the webserver configuration on BeagleBone and the Websocket configuration for the broker MQTT mosquitto always on Beaglebone.

First step is to access on the Beaglebone in ssh and disable the following services

$sudo systemctl stop cloud9.service 
$sudo systemctl stop cloud9.socket 
$sudo systemctl disable cloud9.service
$sudo systemctl disable cloud9.socket
$sudo systemctl stop bonescript-autorun.service
$sudo systemctl stop bonescript.service
$sudo systemctl stop bonescript.socket
$sudo systemctl disable bonescript-autorun.service
$sudo systemctl disable bonescript.service
$sudo systemctl disable bonescript.socket
$sudo systemctl daemon-reload

$sudo systemctl stop cloud9.service

$sudo systemctl stop cloud9.socket

$sudo systemctl disable cloud9.service

$sudo systemctl disable cloud9.socket

$sudo systemctl stop bonescript-autorun.service

$sudo systemctl stop bonescript.service

$sudo systemctl stop bonescript.socket

$sudo systemctl disable bonescript-autorun.service

$sudo systemctl disable bonescript.service

$sudo systemctl disable bonescript.socket

$sudo systemctl daemon-reload

Go into the folder /etc/apache2/sites-enabled and modfy 000-default.conf changing the webserver port from 8080 to 80

<VirtualHost *:80>

1	<VirtualHost *:80>

In /etc/apache2/port.conf modify the listening port from 8080 to 80

# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf

Listen 80

# If you just change the port or add more ports here, you will likely also

# have to change the VirtualHost statement in

# /etc/apache2/sites-enabled/000-default.conf

Listen 80

Restart the Http server

sudo systemctl restart apache2

1	sudo systemctl restart apache2

Go into folder /etc/mosquitto/conf.d and create a new file websockets.conf with the following contents inside

listener 1883
protocol mqtt

listener 9001
protocol websockets

listener 1883

protocol mqtt

listener 9001

protocol websockets

Save the file and restart Mosquitto

sudo systemctl restart mosquitto

1	sudo systemctl restart mosquitto

Disable the IPV6 protocol on Beaglebone as described at the following link

Disable IPV6 in Debian

In the file /etc/sysctl.conf add

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.eth0.disable_ipv6 = 1

net.ipv6.conf.all.disable_ipv6 = 1

net.ipv6.conf.default.disable_ipv6 = 1

net.ipv6.conf.lo.disable_ipv6 = 1

net.ipv6.conf.eth0.disable_ipv6 = 1

Restart the Beaglebone.

We proceed at this point to install on the http server a MQTT Websocket client and the Freeboard dashboard.

As for the MQTT Websocket client hive-MQTT we download the code from github

Hive mqtt

Log in as root in ssh on Beaglebone and go into /var/www/html folder; clone the Mqtt client into mqtt-web folder and change the owner of this folder

#cd /var/www/html/
#git clone https://github.com/hivemq/hivemq-mqtt-web-client.git mqtt-web
#chown www-data:www-data -R mqtt-web

#cd /var/www/html/

#git clone https://github.com/hivemq/hivemq-mqtt-web-client.git mqtt-web

#chown www-data:www-data -R mqtt-web

With a web browser navigate on our Http server to the mqtt-web link obtaining the Mqtt Web client; we can now set the parameters for the connection to the Mosquitto Mqtt Broker

Populating the values for the subscription and publishing topics we can access to the messages of the topics and the ability to perform a command to the publishing topic

In the next article we’ll install the Freeboad dashboard on the Beaglebone

Mqtt with Beaglebone and ESP8266 – Freeboard

Development, Hardware, Software

MQTT with BeagleBone and ESP8266 – MQTT on ESP8266 with Relay

2017-04-01 admin

After the article about the connection with the temperature and humidity sensor

MQTT with BeagleBone and ESP8266 – MQTT on ESP8266 with temperature sensor

in this article we set the esp8266 to run a relay. Here is how we connect the relay to the ESP module

In this example too we will consider the option of putting the nodemcu in sleep. To have the node back form the sleep the system has to reboot and it is necessary to connect the PIN D0 (GPIO16) to RST PIN as specified in the nodemcu documentation

Nodemcu sleep

Let us take a look at the lua code; It consists of init.lua and relay.lua files.

We analyze now the main points of each file

init.lua

-- init.lua
SSID="SSID" -- SSID 
PASSWORD="password" -- SSID password
TIMEOUT=10000   -- timeout to check the network status
EXSENSOR1="relay.lua"   -- module to run
MQTTSERVER="mqttaddress"   -- mqtt broker address
MQTTPORT="1883" -- mqtt broker port
MQTTQOS="0" -- qos used

-- Set the netowrk parameters and get ip address
wifi.setmode(wifi.STATION)
wifi.sta.config(SSID, PASSWORD)
wifi.sta.getip()


-- Check the network status after the TIMEOUT interval
tmr.alarm(0, TIMEOUT,tmr.ALARM_SINGLE, function()
    status=wifi.sta.status()
   -- if esp8266 got the ip
   if (status == wifi.STA_GOTIP ) then

        dofile(EXSENSOR1)
        
    
    else
        -- Without up restart the node
        print("Error acquiring ip address=",status)
        node.restart()
    end


end

)

-- init.lua

SSID="SSID" -- SSID

PASSWORD="password" -- SSID password

TIMEOUT=10000 -- timeout to check the network status

EXSENSOR1="relay.lua" -- module to run

MQTTSERVER="mqttaddress" -- mqtt broker address

MQTTPORT="1883" -- mqtt broker port

MQTTQOS="0" -- qos used

-- Set the netowrk parameters and get ip address

wifi.setmode(wifi.STATION)

wifi.sta.config(SSID, PASSWORD)

wifi.sta.getip()

-- Check the network status after the TIMEOUT interval

tmr.alarm(0, TIMEOUT,tmr.ALARM_SINGLE, function()

status=wifi.sta.status()

-- if esp8266 got the ip

if (status == wifi.STA_GOTIP ) then

dofile(EXSENSOR1)

else

-- Without up restart the node

print("Error acquiring ip address=",status)

node.restart()

end

)

In the file we set the the parameters to access the wifi network, the address and port of the MQTT broker and the file to be run on the ESP after wifi connection to the access point is estabilished. If the ESP doesn’t acquire the network address the system is restarted.

relay.lua

-- relay.lua
CNAME="relay1" -- Client name 
AMBIENT="home"  -- Ambient name 
STOPIC     = AMBIENT.."/"..CNAME.."/status"  -- Status topic
CTOPIC     = AMBIENT.."/"..CNAME.."/command" --Command topic   
MTOPIC     = AMBIENT.."/"..CNAME.."/monitor" --Monitor topic


sleep_in_seconds= nil --Sleep in seconds


TUPDATE = 20 -- Time interval for update monitor in seconds
RPIN        =1 -- Relay Pin
TGEN = 5 -- Time interval in seconds usend in various trm
gpio.mode(RPIN,gpio.OUTPUT) -- Set Relay pin mode
gpio.write(RPIN,gpio.LOW) -- Default output is OFF





-- Define Client Name and connection parameters
mqt = mqtt.Client(CNAME, 60, "", "", 1) 

-- Subscribe to the topics and send status to the status topic
mqt:on("connect", function() 
    mqt:subscribe(STOPIC, MQTTQOS)
    mqt:subscribe(CTOPIC, MQTTQOS)
    mqt:subscribe(MTOPIC, MQTTQOS)
    send_status("Relay ready again")
end )

-- Callback when mqtt is offline
mqt:on("offline", function() print("mqtt offline");  end)

--Callback to manage messages 
mqt:on("message", function(client, topic, data) 
    manage_message(client, topic, data) 
end)

-- Function to filter the messages
function manage_message(client, topic, data) 
    -- If CTOPIC: command topic
    if topic == CTOPIC then

        -- If the command is Restart
        if data == "Restart" then
            send_status("Restarting")
            send_mstatus("Restarting")
            tmr.alarm(2, TGEN*1000, tmr.ALARM_SINGLE, node.restart)
        -- If the command is null    
        elseif data == nil then
            send_status("Command not valid")
        -- Command to turn on the Relay    
        elseif data == "ON" then
            relay_on()
        -- Command to turn off the Relay    
        elseif data == "OFF" then
            relay_off()  
        -- Command to check the state of the Relay    
        elseif data == "Status" then
            relay_status()         
            
        else
            -- Check the Sleep command
            i=string.len(data)
            dato=string.sub(data,1,5)

            if dato == "Sleep" then
                ndato=string.sub(data,6)
                TSLEEP=tonumber(ndato)
                if TSLEEP ~= nil then

                    if TSLEEP >= 1 then
 
                        -- Sets the interval in seconds to sleep
                        sleep_in_seconds=TSLEEP*60
                        esp_sleep()
                    else
                        -- Send an error in Sleep command
                        send_status("Sleep command error")
                    
                    end
                else
                    -- Send an error in Sleep command 
                    send_status("Sleep command error")
                end

            else
                -- Command not managed           
                send_status("Command not valid")      

            end
            
        end
        
    end
end

-- Function to turn on the relay
function relay_on()
    
    gpio.write(RPIN,gpio.HIGH)
    send_status("Relay ON")
end

-- Function to turn off the relay
function relay_off()
    
    gpio.write(RPIN,gpio.LOW)
    send_status("Relay OFF")
end

-- Function to check if the the relay is on or off
function relay_status()
    
    risultato=gpio.read(RPIN)

    if(risultato==1) then
        send_status("Relay ON")
    elseif(risultato==0) then
        send_status("Relay OFF")
    end
end


-- Function to send messages to to STOPIC: status topic
function send_status(message)
    mqt:publish(STOPIC, message, MQTTQOS, 0)
    
end

-- Fucntion to send messages to MTOPIC: monitor topic
function send_mstatus(message)
    mqt:publish(MTOPIC, message, MQTTQOS, 0)
    
end


-- Function that sleeps esp8266
function esp_sleep()
 
    send_status("Relay going to sleep now")
    send_mstatus("Relay going to sleep now")
    -- Delayd sleep to send the message above.
    tmr.alarm(3, TGEN*1000, tmr.ALARM_SINGLE, function() 
        node.dsleep(sleep_in_seconds*1000000) 
    end)
end


-- Connection to the mqtt server at the msttport
mqt:connect(MQTTSERVER, MQTTPORT, 0, 1)



-- Send periodically a message to the monitor topic
tmr.alarm(4, TUPDATE*1000, tmr.ALARM_AUTO, function() send_mstatus("Relay Ready") end)

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

-- relay.lua

CNAME="relay1" -- Client name

AMBIENT="home" -- Ambient name

STOPIC = AMBIENT.."/"..CNAME.."/status" -- Status topic

CTOPIC = AMBIENT.."/"..CNAME.."/command" --Command topic

MTOPIC = AMBIENT.."/"..CNAME.."/monitor" --Monitor topic

sleep_in_seconds= nil --Sleep in seconds

TUPDATE = 20 -- Time interval for update monitor in seconds

RPIN =1 -- Relay Pin

TGEN = 5 -- Time interval in seconds usend in various trm

gpio.mode(RPIN,gpio.OUTPUT) -- Set Relay pin mode

gpio.write(RPIN,gpio.LOW) -- Default output is OFF

-- Define Client Name and connection parameters

mqt = mqtt.Client(CNAME, 60, "", "", 1)

-- Subscribe to the topics and send status to the status topic

mqt:on("connect", function()

mqt:subscribe(STOPIC, MQTTQOS)

mqt:subscribe(CTOPIC, MQTTQOS)

mqt:subscribe(MTOPIC, MQTTQOS)

send_status("Relay ready again")

end )

-- Callback when mqtt is offline

mqt:on("offline", function() print("mqtt offline"); end)

--Callback to manage messages

mqt:on("message", function(client, topic, data)

manage_message(client, topic, data)

end)

-- Function to filter the messages

function manage_message(client, topic, data)

-- If CTOPIC: command topic

if topic == CTOPIC then

-- If the command is Restart

if data == "Restart" then

send_status("Restarting")

send_mstatus("Restarting")

tmr.alarm(2, TGEN*1000, tmr.ALARM_SINGLE, node.restart)

-- If the command is null

elseif data == nil then

send_status("Command not valid")

-- Command to turn on the Relay

elseif data == "ON" then

relay_on()

-- Command to turn off the Relay

elseif data == "OFF" then

relay_off()

-- Command to check the state of the Relay

elseif data == "Status" then

relay_status()

else

-- Check the Sleep command

i=string.len(data)

dato=string.sub(data,1,5)

if dato == "Sleep" then

ndato=string.sub(data,6)

TSLEEP=tonumber(ndato)

if TSLEEP ~= nil then

if TSLEEP >= 1 then

-- Sets the interval in seconds to sleep

sleep_in_seconds=TSLEEP*60

esp_sleep()

else

-- Send an error in Sleep command

send_status("Sleep command error")

end

else

-- Send an error in Sleep command

send_status("Sleep command error")

end

else

-- Command not managed

send_status("Command not valid")

end

-- Function to turn on the relay

function relay_on()

gpio.write(RPIN,gpio.HIGH)

send_status("Relay ON")

end

-- Function to turn off the relay

function relay_off()

gpio.write(RPIN,gpio.LOW)

send_status("Relay OFF")

end

-- Function to check if the the relay is on or off

function relay_status()

risultato=gpio.read(RPIN)

if(risultato==1) then

send_status("Relay ON")

elseif(risultato==0) then

send_status("Relay OFF")

end

-- Function to send messages to to STOPIC: status topic

function send_status(message)

mqt:publish(STOPIC, message, MQTTQOS, 0)

end

-- Fucntion to send messages to MTOPIC: monitor topic

function send_mstatus(message)

mqt:publish(MTOPIC, message, MQTTQOS, 0)

end

-- Function that sleeps esp8266

function esp_sleep()

send_status("Relay going to sleep now")

send_mstatus("Relay going to sleep now")

-- Delayd sleep to send the message above.

tmr.alarm(3, TGEN*1000, tmr.ALARM_SINGLE, function()

node.dsleep(sleep_in_seconds*1000000)

end)

end

-- Connection to the mqtt server at the msttport

mqt:connect(MQTTSERVER, MQTTPORT, 0, 1)

-- Send periodically a message to the monitor topic

tmr.alarm(4, TUPDATE*1000, tmr.ALARM_AUTO, function() send_mstatus("Relay Ready") end)

The relay.lua file manages the relay, the subscription on MQTT broker with submission of the data. Global parameters have been set to manage the topic, the waiting time in tmr.alarm. There are in particular the following topics

/home/relay1/status : Status topic. The status is sent at the start and at request from the command topic /home/relay1/command.
/home/relay1/monitor: Status of the esp sent periodically to this topic.
/home/relay1/command: Other clients can send commands to the esp:
- Restart: Restarts the esp.
- Sleep n: Put to sleep for n seconds the esp.
- ON: Turn on the relay.
- OFF: Turn off the relay.
- Status: Request of tthe relay status (ON or OFF).

There are various service functions to manage all. The comments in the code describe each feature.

In the next article we will set up the webserver on Beaglebone and the websocket configuration for Mosquitto always on the Beaglebone

MQTT with BeagleBone and ESP8266 – WebServer and MQTT WebSocket

Development, Hardware, Software

MQTT with BeagleBone and ESP8266 – MQTT on ESP8266 with temperature sensor

2017-03-23 admin

After loading the firmware into the device esp8266

MQTT with BeagleBone and ESP8266-MQTT ESP8266

we now connect this module with a DHT11 temperature and humidity sensor. Here is how we connect the sensor to the ESP module

In this example we will consider the option of putting the nodemcu in sleep. To have the node back form the sleep the system has to reboot and it is necessary to connect the PIN D0 (GPIO16) to RST PIN as specified in the nodemcu documentation

Nodemcu sleep

Let us take a look at the lua code; It consists of init.lua and tempumid.lua files.

We analyze now the main points of each file

init.lua

-- init.lua
SSID="SSDNAME" -- SSID 
PASSWORD="passwordssid" -- SSID password
TIMEOUT=10000    -- timeout to check the network status
EXSENSOR1="tempumid.lua"    -- module to run
MQTTSERVER="mqttbrokeraddress"   -- mqtt broker address
MQTTPORT="1883"  -- mqtt borker port
MQTTQOS="0" -- qos used

-- Set the netowrk parameters and get ip address
wifi.setmode(wifi.STATION)
wifi.sta.config(SSID, PASSWORD)
wifi.sta.getip()

-- Check the network status after the TIMEOUT interval
tmr.alarm(0, TIMEOUT,tmr.ALARM_SINGLE, function()
    status=wifi.sta.status()
    
    -- if esp8266 got the ip
   if (status == wifi.STA_GOTIP ) then

       dofile(EXSENSOR1)
        
    
    else
        -- Without ip restart the node
        print("Error acquiring ip address=",status)
        node.restart()
    end


end

-- init.lua

SSID="SSDNAME" -- SSID

PASSWORD="passwordssid" -- SSID password

TIMEOUT=10000 -- timeout to check the network status

EXSENSOR1="tempumid.lua" -- module to run

MQTTSERVER="mqttbrokeraddress" -- mqtt broker address

MQTTPORT="1883" -- mqtt borker port

MQTTQOS="0" -- qos used

-- Set the netowrk parameters and get ip address

wifi.setmode(wifi.STATION)

wifi.sta.config(SSID, PASSWORD)

wifi.sta.getip()

-- Check the network status after the TIMEOUT interval

tmr.alarm(0, TIMEOUT,tmr.ALARM_SINGLE, function()

status=wifi.sta.status()

-- if esp8266 got the ip

if (status == wifi.STA_GOTIP ) then

dofile(EXSENSOR1)

else

-- Without ip restart the node

print("Error acquiring ip address=",status)

node.restart()

end

In the file we set the the parameters to access the wifi network, the address and port of the MQTT broker and the file to be run on the ESP after wifi connection to the access point is estabilished. If the ESP does’t acquire the netowrk address the system is restarted.

tempumid.lua

-- tempumid.lua
CNAME="room1" -- Client name 
AMBIENT="home"  -- Ambient name
TTOPIC     = AMBIENT.."/"..CNAME.."/temperature"  -- Temperature topic
HTOPIC     = AMBIENT.."/"..CNAME.."/humidity"  -- Humidity topic 
STOPIC     = AMBIENT.."/"..CNAME.."/status"  -- Status topic
CTOPIC     = AMBIENT.."/"..CNAME.."/command" --Command topic   
MTOPIC     = AMBIENT.."/"..CNAME.."/monitor" --Monitor topic


sleep_in_seconds= nil --Sleep in seconds


TUPDATE = 15 -- Time interval for update monitor in seconds
TUPTEMP = 10 -- Time interval for update temperature and humidity values
SPIN         = 4  -- Sensor pin
TGEN = 5 -- Time interval in seconds usend in various trm


-- Define Client Name and connection parameters
mqt = mqtt.Client(CNAME, 60, "", "", 1) 

-- Subscribe to the topics and send status to the status topic
mqt:on("connect", function() 
    mqt:subscribe(STOPIC, MQTTQOS)
    mqt:subscribe(CTOPIC, MQTTQOS)
    mqt:subscribe(MTOPIC, MQTTQOS)
    mqt:subscribe(TTOPIC, MQTTQOS)
    mqt:subscribe(HTOPIC, MQTTQOS)
    send_status("Sensor ready again")
end )

-- Callback when mqtt is offline
mqt:on("offline", function() print("mqtt offline");  end)

--Callback to manage messages 
mqt:on("message", function(client, topic, data) 
    manage_message(client, topic, data) 
end)


-- Function to filter the messages
function manage_message(client, topic, data) 
    -- If CTOPIC: command topic
    if topic == CTOPIC then
        --print("Command")
        -- If the command is Restart
        if data == "Restart" then
            send_status("Restarting")
            send_mstatus("Restarting")
            tmr.alarm(2, TGEN*1000, tmr.ALARM_SINGLE, node.restart)
            --print("restart")
        -- If the command is null    
        elseif data == nil then
           -- print("Command not valid")
            send_status("Command not valid")
        
        
        else
            -- Check the Sleep command           
            i=string.len(data)
            dato=string.sub(data,1,5)
          
            if dato == "Sleep" then
                ndato=string.sub(data,6)
                TSLEEP=tonumber(ndato)
                if TSLEEP ~= nil then
                    if TSLEEP >= 1 then
                        -- Sets the interval in seconds to sleep
                        sleep_in_seconds=TSLEEP*60
                        esp_sleep()
                    else
                        -- Send an error in Sleep command
                        send_status("Sleep command error")
                    
                    end
                else
                    -- Send an error in Sleep command 
                    send_status("Sleep command error")
                end

            else
                -- Command not managed           
                send_status("Command not valid")      

            end
            
        end
        
    end
end

-- Function to send messages to STOPIC: status topic
function send_status(message)
    mqt:publish(STOPIC, message, MQTTQOS, 0)
    
end

-- Fucntion to send messages to MTOPIC: monitor topic
function send_mstatus(message)
    mqt:publish(MTOPIC, message, MQTTQOS, 0)
    
end

-- Function to display temp and hum
function display_temphum(temp,humi)
    print("Temperature=%d, Humidity=%d",temp,humi)
end

 
-- Function to read and publish temperature and humidity
function read_temp_hum(client)
    status, temp, humi, temp_dec, humi_dec = dht.read(SPIN)
    if status == dht.OK then
    
        mqt:publish(TTOPIC, temp,MQTTQOS, 0)
        mqt:publish(HTOPIC, humi, MQTTQOS, 0)
        
       -- display_temphum(temp,humi)
       
    elseif status == dht.ERROR_CHECKSUM then
        print( "DHT Checksum error." )
    elseif status == dht.ERROR_TIMEOUT then
        print( "DHT timed out." )
    end
end


-- Function that sleeps esp8266
function esp_sleep()
 
    send_status("Sensor going to sleep now")
    send_mstatus("Sensor going to sleep now")
    -- Delayd sleep to send the message above.
    tmr.alarm(3, TGEN*1000, tmr.ALARM_SINGLE, function() 
        node.dsleep(sleep_in_seconds*1000000) 
    end)
end

-- Connection to the mqtt server at the mqttport
mqt:connect(MQTTSERVER, MQTTPORT, 0, 1)

--Sends periodically the temperature and humidity to the topics
tmr.alarm(1, TUPTEMP*1000, tmr.ALARM_AUTO, function() read_temp_hum(mqt) end)

-- Sends periodically a message to the monitor topic
tmr.alarm(4, TUPDATE*1000, tmr.ALARM_AUTO, function() send_mstatus("Sensor Ready") end)

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

-- tempumid.lua

CNAME="room1" -- Client name

AMBIENT="home" -- Ambient name

TTOPIC = AMBIENT.."/"..CNAME.."/temperature" -- Temperature topic

HTOPIC = AMBIENT.."/"..CNAME.."/humidity" -- Humidity topic

STOPIC = AMBIENT.."/"..CNAME.."/status" -- Status topic

CTOPIC = AMBIENT.."/"..CNAME.."/command" --Command topic

MTOPIC = AMBIENT.."/"..CNAME.."/monitor" --Monitor topic

sleep_in_seconds= nil --Sleep in seconds

TUPDATE = 15 -- Time interval for update monitor in seconds

TUPTEMP = 10 -- Time interval for update temperature and humidity values

SPIN = 4 -- Sensor pin

TGEN = 5 -- Time interval in seconds usend in various trm

-- Define Client Name and connection parameters

mqt = mqtt.Client(CNAME, 60, "", "", 1)

-- Subscribe to the topics and send status to the status topic

mqt:on("connect", function()

mqt:subscribe(STOPIC, MQTTQOS)

mqt:subscribe(CTOPIC, MQTTQOS)

mqt:subscribe(MTOPIC, MQTTQOS)

mqt:subscribe(TTOPIC, MQTTQOS)

mqt:subscribe(HTOPIC, MQTTQOS)

send_status("Sensor ready again")

end )

-- Callback when mqtt is offline

mqt:on("offline", function() print("mqtt offline"); end)

--Callback to manage messages

mqt:on("message", function(client, topic, data)

manage_message(client, topic, data)

end)

-- Function to filter the messages

function manage_message(client, topic, data)

-- If CTOPIC: command topic

if topic == CTOPIC then

--print("Command")

-- If the command is Restart

if data == "Restart" then

send_status("Restarting")

send_mstatus("Restarting")

tmr.alarm(2, TGEN*1000, tmr.ALARM_SINGLE, node.restart)

--print("restart")

-- If the command is null

elseif data == nil then

-- print("Command not valid")

send_status("Command not valid")

else

-- Check the Sleep command

i=string.len(data)

dato=string.sub(data,1,5)

if dato == "Sleep" then

ndato=string.sub(data,6)

TSLEEP=tonumber(ndato)

if TSLEEP ~= nil then

if TSLEEP >= 1 then

-- Sets the interval in seconds to sleep

sleep_in_seconds=TSLEEP*60

esp_sleep()

else

-- Send an error in Sleep command

send_status("Sleep command error")

end

else

-- Send an error in Sleep command

send_status("Sleep command error")

end

else

-- Command not managed

send_status("Command not valid")

end

-- Function to send messages to STOPIC: status topic

function send_status(message)

mqt:publish(STOPIC, message, MQTTQOS, 0)

end

-- Fucntion to send messages to MTOPIC: monitor topic

function send_mstatus(message)

mqt:publish(MTOPIC, message, MQTTQOS, 0)

end

-- Function to display temp and hum

function display_temphum(temp,humi)

print("Temperature=%d, Humidity=%d",temp,humi)

end

-- Function to read and publish temperature and humidity

function read_temp_hum(client)

status, temp, humi, temp_dec, humi_dec = dht.read(SPIN)

if status == dht.OK then

mqt:publish(TTOPIC, temp,MQTTQOS, 0)

mqt:publish(HTOPIC, humi, MQTTQOS, 0)

-- display_temphum(temp,humi)

elseif status == dht.ERROR_CHECKSUM then

print( "DHT Checksum error." )

elseif status == dht.ERROR_TIMEOUT then

print( "DHT timed out." )

end

-- Function that sleeps esp8266

function esp_sleep()

send_status("Sensor going to sleep now")

send_mstatus("Sensor going to sleep now")

-- Delayd sleep to send the message above.

tmr.alarm(3, TGEN*1000, tmr.ALARM_SINGLE, function()

node.dsleep(sleep_in_seconds*1000000)

end)

end

-- Connection to the mqtt server at the mqttport

mqt:connect(MQTTSERVER, MQTTPORT, 0, 1)

--Sends periodically the temperature and humidity to the topics

tmr.alarm(1, TUPTEMP*1000, tmr.ALARM_AUTO, function() read_temp_hum(mqt) end)

-- Sends periodically a message to the monitor topic

tmr.alarm(4, TUPDATE*1000, tmr.ALARM_AUTO, function() send_mstatus("Sensor Ready") end)

The temumid.lua file manages the measurement of temperature and humidity, the subscription on MQTT broker with submission of the data. Global parameters have been set to manage the topic, the waiting time in tmr.alarm. There are in particular the following topics

/home/room1/temperature: measured temperature topic.
/home/room1/humidity: measured humidity topic.
/home/room1/status : Status topic. The status is sent at the start and at request from the command topic /home/room1/command.
/home/room1/monitor: Status of the esp sent periodically to this topic.
/home/room1/command: Other clients can send commands to the esp:
- Restart: Restarts the esp.
- Sleep n: Put to sleep for n seconds the esp.

There are various service functions to manage all. The comments in the code describe each feature.

In the next article we will set up the esp with the relay

MQTT with BeagleBone and ESP8266 – MQTT on ESP8266 with Relay

Configuration, Software

Mqtt with Beaglebone and ESP8266-MQTT ESP8266

2017-03-19 admin

After installing the MQTT server on BeagleBone

Mqtt with Beaglebone and ESP8266-Mosquitto installation on Beaglebone

let us set the MQTT nodes on ESP8266.

As first operation we must generate the nodemcu firmware, as described in the previous article

Nodemcu compilation on Linux

with at least the following parameters activated in user_module.h file

DHT
file
GPIO
MQTT
net
node
timer
UART
WiFi

These settings are the default in the user_module.h file.

At present the latest version 2.0 of nomemcu firmware was released. Here are the compiled files for this version of the firmware

Nodemcu2.0.0 firmware

As already described in previous articles and from the nodecmu link on flashing

Flashing the firmware

we have to set the correct parameters for the esp8266 model.

In our case, with 4MB flash, we used the parameters shown in the image to load the firmware on the device with nodemcu-flasher tool. You can also use other tools for loading the firmware. In our case, the settings used are as follows

In the next article we’ll treat the ESP8266 node that detects temperature and humidity

MQTT with BeagleBone and ESP8266 – MQTT on ESP8266 with temperature sensor

Configuration, Software

MQTT with BeagleBone and ESP8266 – Mosquitto installation on Beaglebone

2017-03-12 admin

After summarizing the architecture that we are implementing in the previous article

Mqtt with Beaglebone and ESP8266-Architecture

We proceed now with the installation of the MQTT broker on Beaglebone Black with the following version of Debian

root@beaglebone:~#  cat /etc/dogtag
BeagleBoard.org Debian Image 2016-11-06
root@beaglebone:~# uname -a
Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Lux

root@beaglebone:~# cat /etc/dogtag

BeagleBoard.org Debian Image 2016-11-06

root@beaglebone:~# uname -a

Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Lux

The image used is the following

Beaglebone Black Image

We proceed to the configuration as described in the article

Debian sd card setup for Beaglebone Black

Proceed to extend the space on the SD card with the application gparted in a linux host or using the grow_partition.sh tool on BeagleBone in the /opt/scripts/tools folder

root@beaglebone:/opt/scripts/tools# ./grow_partition.sh

1	root@beaglebone:/opt/scripts/tools# ./grow_partition.sh

Performing the upgrade with this image we have had space issue with 4Gb partition.

The message broker we’ll use is mosquitto

Mosquitto

The version of Mosquitto with Debian Jessie doesn’t not have the Wesockets services, which we’ll use for the Dashboard. For this reason, we have to install a more recent version of Mosquitto (or recompile it from source).

Log on as root in a command shell on BeagleBone and add the Debian testing repository

cd /etc/apt
vi sources.list

1 2	cd /etc/apt vi sources.list

deb http://httpredir.debian.org/debian stretch main contrib non-free

1	deb http://httpredir.debian.org/debian stretch main contrib non-free

Run the following

apt-get update
apt-get install mosquitto
apt-get install mosquitto-clients

apt-get update

apt-get install mosquitto

apt-get install mosquitto-clients

After the installation comment the reference of the debian testing repository in /etc/apt/sources.list

#deb http://httpredir.debian.org/debian stretch main contrib non-free

1	#deb http://httpredir.debian.org/debian stretch main contrib non-free

and run

apt-get update

1	apt-get update

We test at this point if the server is installed correctly by running in a shell the subscription to a topic

mosquitto_sub -h localhost -t "topic/test"

1	mosquitto_sub -h localhost -t "topic/test"

In another command shell run the publishing on topic “topic / test”

mosquitto_pub -h localhost -t "topic/test" -m "Prova"

1	mosquitto_pub -h localhost -t "topic/test" -m "Prova"

The first shell has to show the message “Prova”

With MQTT protocol we can define different QOS, as described in the Mosquitto FAQ

QOS Mosquitto

With QoS = 0 the message is sent only once and is not required confirmation of receipt by the subscribers; the MQTT implementation in these articles is without protection with name/password or ssl channel encryption and with QOS=0.

In the next article we’ll proceed to the preparation of ESP9266 module with the Mqtt lua library inside the nodemcu firmware

MQTT with BeagleBone and ESP8266-MQTT ESP8266

Configuration, Software

Mqtt with Beaglebone and Esp8266-Architecture

2017-03-12 admin

In this series of articles we treat a MQTT message broker installed on BeagleBone Black; this componet allows to manage various esp8266 devices, to which we connect various probes such as temperaure sensors, relays.

All this is handled with the help of apps on Android and a Dashboard installed on Apache on BeagleBone.

We start from the message MQTT broker (Message Queue Telemetry Transport); here there is the description of the protocol

MQTT

In particular in the FAQ section there are the first indications on the protocol and its use

MQTT Faq

The system is formed by three components:

MQTT Broker: relays the messages published to all subscribers.
Publisher: Publish messages in the registered topics on MQTT Broker.
Subscriber: Receives messages for its registered topics from MQTT Broker.

The following shows the topology for two topics used in our example

The system is composed of a MQTT broker on BeagleBone. In this MQTT broker server you can define topics; different devices can be registered to these topics. For each topic the action can be subscription and publishing. By subscribing you receive all messages of topics, while with the publishing we can perform actions on the topic (for example, turn on a relay, restart a device, send sensor measurement,etc.). In the example we treat there will be, for example, a queue for the temperature monitor, hooked to esp8266 temperature reading device, another for the management of a relay, always run with esp8266. The MQTT broker relays the received messages among all subscribers/ publishers for each topic.

We can subcribe/publish to the topics on the MQTT broker using Android apps; the apps can receive messages and send commands to the esp8266 end device (Turn onRelay, Restart sensor, etc.).

With the javascript framework Freeboard

Freeboard

installed on the Beablebone Apache web server we can monitor in real time the end devices.

For more informations on MQTT system, consult the web site listed above.

In the next article we’ll start by installing the MQTT broker on BeagleBone Black

MQTT with BeagleBone and ESP8266 – Mosquitto installation on Beaglebone

Configuration, Software

Generating Images for BeagleBone with Omap Image Builder

2017-02-26 admin

This article describes how to proceed to the autonomous creation of an image for the BeagleBone Black /Green using the Omap Image Builder. In this specific example we create the image for the BeagleBone Black Rev. C.

The informations on the procedure to be followed are available on the site

Omap image builder

As a prerequisite to the creation of the image there is the need to perform the operations on arm hardware; with other systems it is possible to have issues. To this end, we will proceed to perform tasks on a Orange PI PC with Armbian operating system. After preparing the Armbian system for Orange PI PC, as described in

Armbian Boot on Orange PI PC

It is possible also to connect by enabling Remote Desktop

Remote desktop setup for Armbian on Orange PI PC

Create a folder named beaglebone

mkdir beaglebone
cd beaglebone

1 2	mkdir beaglebone cd beaglebone

Clone the code to create the image

git clone git://github.com/beagleboard/image-builder.git

1	git clone git://github.com/beagleboard/image-builder.git

The folder tree is the following

image-builder
├── configs
├── docs
├── emacs
├── machinekit
├── publish
├── scripts
├── target
│   ├── boot
│   ├── chroot
│   ├── init_scripts
│   ├── keyring
│   └── other
└── tools
    └── hwpack

image-builder

├── configs

├── docs

├── emacs

├── machinekit

├── publish

├── scripts

├── target

│ ├── boot

│ ├── chroot

│ ├── init_scripts

│ ├── keyring

│ └── other

└── tools

└── hwpack

We proceed first to the creation of a standard Debian 8 image for Beaglebone Black

cd image-builder
sudo ./beagleboard.org_jessie_image.sh

1 2	cd image-builder sudo ./beagleboard.org_jessie_image.sh

The task takes a long time and creates other folders including the deploy folder within which we will find the images. At the end go into deploy /image folder and run

sudo ./setup_sdcard.sh --img-4gb BBB-debian-8.6-lxqt-aaaa-mm-dd --dtb beaglebone --enable-systemd --boot_label BEAGLEBONE --bbb-old-bootloader-in-emmc --hostname beaglebone

1	sudo ./setup_sdcard.sh --img-4gb BBB-debian-8.6-lxqt-aaaa-mm-dd --dtb beaglebone --enable-systemd --boot_label BEAGLEBONE --bbb-old-bootloader-in-emmc --hostname beaglebone

Compress the created image with the command

sudo xz -z -8 -v BBB-debian-8.6-lxqt-aaaa-mm-dd-4gb.img

1	sudo xz -z -8 -v BBB-debian-8.6-lxqt-aaaa-mm-dd-4gb.img

To create a customized image proceed as follows:

Go into the image-builder/configs folder and copy a configuration as base named custom-debian.conf. We have used as a base configuration bb.org-debian-jessie-lxqt-4gb-v4.1.conf. In custom-debian.conf add the following changes in the deb_include section; as example we add the vsftpd server; change the chroot_script value too

deb_include=="   \         alsa-utils      \ ....... xserver-xorg-video-modesetting \         vsftpd \ "

1
2
3
4
5
6
7

deb_include=="   \
        alsa-utils      \
.......

xserver-xorg-video-modesetting \
        vsftpd \
"

chroot_script="custom-debian.sh"

1

chroot_script="custom-debian.sh"

To exclude packages to be installed use the deb_exclude section. In the script are commented the various sections, among which we find those about the definition of the hostname, passwords, user name creation, etc.
Navigate to the image-builder/target/chroot folder and copy beagleboard.org-jessie.sh as custom-debian.sh.
If you want to add python packages edit the custom-debian.sh file and add the other packages in install_pip_pkgs function

install_pip_pkgs () {
        if [ -f /usr/bin/python ] ; then
                wget https://bootstrap.pypa.io/get-pip.py || true
                if [ -f get-pip.py ] ; then
                        python get-pip.py
                        rm -f get-pip.py || true

                        if [ -f /usr/local/bin/pip ] ; then
                                echo "Installing pip packages"
                                #Fixed in git, however not pushed to pip yet...(use git and install)
                                #libpython2.7-dev
                                #pip install Adafruit_BBIO

                                git_repo="https://github.com/adafruit/adafruit-beaglebone-io-python.git"
                                git_target_dir="/opt/source/adafruit-beaglebone-io-python"
                                git_clone
                                if [ -f ${git_target_dir}/.git/config ] ; then
                                        cd ${git_target_dir}/
                                        python setup.py install
                                fi
                                pip install --upgrade PyBBIO
                                pip install iw_parse
#Add other python packages here
                        fi
                fi
        fi
}

install_pip_pkgs () {

if [ -f /usr/bin/python ] ; then

wget https://bootstrap.pypa.io/get-pip.py || true

if [ -f get-pip.py ] ; then

python get-pip.py

rm -f get-pip.py || true

if [ -f /usr/local/bin/pip ] ; then

echo "Installing pip packages"

#Fixed in git, however not pushed to pip yet...(use git and install)

#libpython2.7-dev

#pip install Adafruit_BBIO

git_repo="https://github.com/adafruit/adafruit-beaglebone-io-python.git"

git_target_dir="/opt/source/adafruit-beaglebone-io-python"

git_clone

if [ -f ${git_target_dir}/.git/config ] ; then

cd ${git_target_dir}/

python setup.py install

pip install --upgrade PyBBIO

pip install iw_parse

#Add other python packages here

}

In this example we added only the ftp server. Go into the image-builder folder and run the command

sudo ./RootStock-NG.sh -c custom-debian

1	sudo ./RootStock-NG.sh -c custom-debian

The task takes a long time. At the end access to the deploy/imagename folder and run

sudo ./setup_sdcard.sh --img-4gb BBB-custom-debian-8.6-aaa-mm-dd --dtb beaglebone --enable-systemd --boot_label BEAGLEBONE --bbb-old-bootloader-in-emmc --hostname beagleboneblack

1	sudo ./setup_sdcard.sh --img-4gb BBB-custom-debian-8.6-aaa-mm-dd --dtb beaglebone --enable-systemd --boot_label BEAGLEBONE --bbb-old-bootloader-in-emmc --hostname beagleboneblack

Compress the created image with the command

sudo xz -z -8 -v BBB-custom-debian-8.6-aaa-mm-dd-4gb.img

1	sudo xz -z -8 -v BBB-custom-debian-8.6-aaa-mm-dd-4gb.img

You can create now the micro sd card with the FTP server available in the image and the hostname changed in beagleboneblack.

The microSD burning is already described in the article

Debian sdcard setup for Beaglebone Black

On Omap image builder site you’ll find other images types among which we highlight those for BeagleBone Black, Green, Iot, Machine Kit (image to manage Machinekit CNC machines), etc.

Development, Software

C Eclipse project reading temperature and humidity on Beaglebone

2017-02-15 admin

After the cross building and DHT11 sensor setup on Beaglebone Black

Remote debug on Beaglebone

Sensors on Beaglebone

Temperature and humidity reading on Beaglebone in python

now we show how to create a C project , using the C source code available with the Adafruit library

Adafruit Python DHT Sensor Library

Using Eclipse, we create a project for the reading of our sensor. It calls the functions in the C code of the Adafruit library. These sources are imported into the Eclipse project

and using the sample C code dhtSensor.c, which contains the main C program, we read the sensors by calling the funtions available in Adafruit C sources; the usage is similar to what seen in Python.

Running

./dhtSensor

1	./dhtSensor

it shows the help instructions

root@beaglebone:~/examples# ./dhtSensor
Usage:  sudo ./dhtSensor [11|22|2302] GPIOpin#
Example: sudo ./dhtSensor 11 P8_11 - Read from a DHT11 sensor connected to P8_11 Pin
root@beaglebone:~/examples#

root@beaglebone:~/examples# ./dhtSensor

Usage: sudo ./dhtSensor [11|22|2302] GPIOpin#

Example: sudo ./dhtSensor 11 P8_11 - Read from a DHT11 sensor connected to P8_11 Pin

root@beaglebone:~/examples#

To read the DHT11 sensor on pin P8_11 we have to run

./dhtSensor 11 P8_11

1	./dhtSensor 11 P8_11

The output is the following

Here is the Eclipse C project

dhtSensor Eclipse project

Micro Devices

All posts by admin

Mqtt with Beaglebone and ESP8266 – Freeboard

Libreelec8 in OrangePI PC

MQTT with BeagleBone and ESP8266 – WebServer and MQTT WebSocket

MQTT with BeagleBone and ESP8266 – MQTT on ESP8266 with Relay

MQTT with BeagleBone and ESP8266 – MQTT on ESP8266 with temperature sensor

Mqtt with Beaglebone and ESP8266-MQTT ESP8266

MQTT with BeagleBone and ESP8266 – Mosquitto installation on Beaglebone

Mqtt with Beaglebone and Esp8266-Architecture

Generating Images for BeagleBone with Omap Image Builder

C Eclipse project reading temperature and humidity on Beaglebone

Blog about embedded devices