Category Archives: Configuration

Configuration, Software

OctoPrint installation on Orange PI PC – HAProxy Installation

2017-12-13 admin

After the automatic start of OctoPrint configuration

OctoPrint Autostart

at this point we can set up the system to answer to the standard port of an Http server.

For this purpose we install and configure the HAProxy reverse proxy

HAproxy

Proceed to the installation

sudo apt-get install haproxy

1	sudo apt-get install haproxy

Edit the /etc/haproxy/haproxy.cfg file and add to the default the directives including also the use of webcam

frontend public
        bind :::80 v4v6
        use_backend webcam if { path_beg /webcam/ }
        default_backend octoprint

backend octoprint
        reqrep ^([^\ :]*)\ /(.*)     \1\ /\2
        option forwardfor
        server octoprint1 127.0.0.1:5000

backend webcam
        reqrep ^([^\ :]*)\ /webcam/(.*)     \1\ /\2
        server webcam1  127.0.0.1:8080

frontend public

bind :::80 v4v6

use_backend webcam if { path_beg /webcam/ }

default_backend octoprint

backend octoprint

reqrep ^([^\ :]*)\ /(.*) \1\ /\2

option forwardfor

server octoprint1 127.0.0.1:5000

backend webcam

reqrep ^([^\ :]*)\ /webcam/(.*) \1\ /\2

server webcam1 127.0.0.1:8080

Restart the proxy with the command

sudo systemctl restart haproxy

1	sudo systemctl restart haproxy

Restart the Orange PI. If everything is configured correctly, the 3D print server answers on port 80 of the Orange Pi PC ip address

http://ORANGEPIPC_IP

It is possible to map the Octoprint service on port 5000 only to the loopback interface by editing the file ~/.octoprint/config.yaml

nano ~/.octoprint/config.yaml

1	nano ~/.octoprint/config.yaml

and adding the host reference under the server directive

server:
    host: 127.0.0.1

1 2	server: host: 127.0.0.1

Restart OctoPrint

sudo systemctl restart octoprint

1	sudo systemctl restart octoprint

Now the 5000 port is mapped only with the address 127.0.0.1.

In the next article, we’ll configure Linux to publish the hostname on the network so that it can be accessed through this reference without using the IP address

Local Hostname Resolution

Configuration, Software

OctoPrint installation on Orange PI PC – Autostart

2017-11-23 admin

After the installation of OctoPrint and CuraEngine in the previous article

OctoPrint Package Installation

we treat now the configuration of the 3d print server.

As first operation, we set up the automatic startup of OctoPrint.

Run the following commands

sudo cp /opt/octoprint/OctoPrint/scripts/octoprint.init /etc/init.d/octoprint
sudo chmod +x /etc/init.d/octoprint
sudo cp /opt/octoprint/OctoPrint/scripts/octoprint.default /etc/default/octoprint

sudo cp /opt/octoprint/OctoPrint/scripts/octoprint.init /etc/init.d/octoprint

sudo chmod +x /etc/init.d/octoprint

sudo cp /opt/octoprint/OctoPrint/scripts/octoprint.default /etc/default/octoprint

Edit the /etc/ defaults/octoprint file changing the pointing to the executable to start OctoPrint using vi

sudo vi /etc/default/octoprint

1	sudo vi /etc/default/octoprint

or nano

sudo nano /etc/default/octoprint

1	sudo nano /etc/default/octoprint

and edit the file from

# Configuration for /etc/init.d/octoprint

# The init.d script will only run if this variable non-empty.
OCTOPRINT_USER=pi

# base directory to use
#BASEDIR=/home/pi/.octoprint

# configuration file to use
#CONFIGFILE=/home/pi/.octoprint/config.yaml

# On what port to run daemon, default is 5000
PORT=5000

# Path to the OctoPrint executable, you need to set this to match your installation!
#DAEMON=/home/pi/OctoPrint/venv/bin/octoprint

# What arguments to pass to octoprint, usually no need to touch this
DAEMON_ARGS="--port=$PORT"

# Umask of files octoprint generates, Change this to 000 if running octoprint as its own, separate user
UMASK=022

# Process priority, 0 here will result in a priority 20 process.
# -2 ensures Octoprint has a slight priority over user processes.
NICELEVEL=-2

# Should we run at startup?
START=yes

# Configuration for /etc/init.d/octoprint

# The init.d script will only run if this variable non-empty.

OCTOPRINT_USER=pi

# base directory to use

#BASEDIR=/home/pi/.octoprint

# configuration file to use

#CONFIGFILE=/home/pi/.octoprint/config.yaml

# On what port to run daemon, default is 5000

PORT=5000

# Path to the OctoPrint executable, you need to set this to match your installation!

#DAEMON=/home/pi/OctoPrint/venv/bin/octoprint

# What arguments to pass to octoprint, usually no need to touch this

DAEMON_ARGS="--port=$PORT"

# Umask of files octoprint generates, Change this to 000 if running octoprint as its own, separate user

UMASK=022

# Process priority, 0 here will result in a priority 20 process.

# -2 ensures Octoprint has a slight priority over user processes.

NICELEVEL=-2

# Should we run at startup?

START=yes

# Configuration for /etc/init.d/octoprint

# The init.d script will only run if this variable non-empty.
OCTOPRINT_USER=octoprint

# base directory to use
#BASEDIR=/home/octoprint/.octoprint

# configuration file to use
#CONFIGFILE=/home/octoprint/.octoprint/config.yaml

# On what port to run daemon, default is 5000
PORT=5000

# Path to the OctoPrint executable, you need to set this to match your installation!
DAEMON=/opt/octoprint/OctoPrint/venv/bin/octoprint

# What arguments to pass to octoprint, usually no need to touch this
DAEMON_ARGS="--port=$PORT"

# Umask of files octoprint generates, Change this to 000 if running octoprint as its own, separate user
UMASK=022

# Process priority, 0 here will result in a priority 20 process.
# -2 ensures Octoprint has a slight priority over user processes.
NICELEVEL=-2

# Should we run at startup?
START=yes

# Configuration for /etc/init.d/octoprint

# The init.d script will only run if this variable non-empty.

OCTOPRINT_USER=octoprint

# base directory to use

#BASEDIR=/home/octoprint/.octoprint

# configuration file to use

#CONFIGFILE=/home/octoprint/.octoprint/config.yaml

# On what port to run daemon, default is 5000

PORT=5000

# Path to the OctoPrint executable, you need to set this to match your installation!

DAEMON=/opt/octoprint/OctoPrint/venv/bin/octoprint

# What arguments to pass to octoprint, usually no need to touch this

DAEMON_ARGS="--port=$PORT"

# Umask of files octoprint generates, Change this to 000 if running octoprint as its own, separate user

UMASK=022

# Process priority, 0 here will result in a priority 20 process.

# -2 ensures Octoprint has a slight priority over user processes.

NICELEVEL=-2

# Should we run at startup?

START=yes

taking into account also the different user being used.

Add the script to startup automatically OctoPrint

sudo update-rc.d octoprint defaults

1	sudo update-rc.d octoprint defaults

Start OctoPrint with the command

sudo systemctl start octoprint

1	sudo systemctl start octoprint

Check that OctoPrint is active on port 5000 of the Orange PI PC by accessing the address

http://IPORANGEPIPC:5000

1	http://IPORANGEPIPC:5000

Rebooting the Orange PI PC, the OctoPrint server now starts automatically.

In the next article, Linux will be configured to connect to OctoPrint on the Http standard port, i.e. on port 80

HAProxy Installation

Configuration, Software

Enigma 2 – How to read the contents of an image

2017-08-20 admin

In the previous article

OpenaATV Enigma2 image compilation

we built an Enigma2 image.

This shows how to view the content of an Enigma2 image.

As an example we will always use the image for Zgemma H2H.

In a Linux environment, Debian 8 in our case, download the image to a folder, for example enigma2

In a terminal unzip it with the command

unzip imagename.zip

1	unzip imagename.zip

In the unpacked folder we have several files

What we are interested in is rootfs.bin.

The command

file filename

1	file filename

provides informations about the file type. In the case of rootfs.bin

the command indicates that this is an image with ubi filesystem.

Now install the memory technology device utilities as the first step. In a terminal run

sudo apt-get install mtd-utils

1	sudo apt-get install mtd-utils

To view the contents run

sudo modprobe nandsim first_id_byte=0x2c second_id_byte=0xda third_id_byte=0x90 fourth_id_byte=0x95
sudo flash_erase /dev/mtd0 0 0
sudo ubiformat /dev/mtd0 -O 2048 -f ./rootfs.bin
sudo modprobe ubi
sudo ubiattach -p /dev/mtd0  -O 2048
sudo mkdir /mnt/ubifs
sudo mount -t ubifs /dev/ubi0_0 /mnt/ubifs

sudo modprobe nandsim first_id_byte=0x2c second_id_byte=0xda third_id_byte=0x90 fourth_id_byte=0x95

sudo flash_erase /dev/mtd0 0 0

sudo ubiformat /dev/mtd0 -O 2048 -f ./rootfs.bin

sudo modprobe ubi

sudo ubiattach -p /dev/mtd0 -O 2048

sudo mkdir /mnt/ubifs

sudo mount -t ubifs /dev/ubi0_0 /mnt/ubifs

The file content is now visible under /mnt/ ubifs

To unmount the filesystem run

sudo umount /mnt/ubifs

1	sudo umount /mnt/ubifs

Finally to detach the UBI from the mtd device use the command

sudo ubidetach /dev/ubi_ctrl -m 0

1	sudo ubidetach /dev/ubi_ctrl -m 0

Below the links to find more informations about mtd and ubi filesystem

UBIFS

Linux MTD UBIFS

Configuration, Software

LEDE on Linkit 7688 Duo – Timecheck example

2017-08-13 admin

After the Python ad Firmata example

Firmata and Python

in this example we use the following programming model

We enable the board to work like Arduino Yun

Linkit 7688 Duo Arduino Yun

As specified in the Mediatek link, you must enable the bridge on the board; from a terminal in Lede run

uci set yunbridge.config.disabled='0'  
uci commit  
reboot

uci set yunbridge.config.disabled='0'

uci commit

reboot

At the reboot go to the Arduino Ide and choose File->Examples->Bridge->TimeCheck

We used the 1.6.5 Arduino Ide; we had issues whith the 1.8 version to build the sketch.

From the Arduino Ide, after the code upload, go to Tool->Serial Monitor to open the serial monitor

The serial monitor window shows the current time.

After that, to run the other examples , disable the bridge setting with the commands

uci set yunbridge.config.disabled='1'  
uci commit  
reboot

uci set yunbridge.config.disabled='1'

uci commit

reboot

Configuration, Software

LEDE on Linkit 7688 Duo – Firmata and Python

2017-08-05 admin

After the python test in the previous article

LEDE on Linkit 7688 Duo – MPU-MCU Uart communication

here we describe how to do the same operation using the Firmata python library

Firmata Protocol

In this case, the programming model is the following

As first step, described in the Mediatek article

Using Firmata with Python

we install the Firmata python library; in a linux terminal on LEDE run

pip install pyfirmata

1	pip install pyfirmata

In the Arduino IDE choose File->Examples->Firmata->StandardFirmata

Make the following change in sketch code:

Look for the code

Firmata.begin(57600);
while (!Serial) {

and replace it with

Serial1.begin(57600);
Firmata.begin(Serial1);

while (!Serial1) {

Save the file and perform the compilation and upload on the Linkit 7688 Duo.

In a linux terminal in Lede create the blink_with_firmata.py file and copy the following code inside

from pyfirmata import Arduino, util
from time import sleep
 
board = Arduino('/dev/ttyS0')
print "Start blinking D13"
while True:
    board.digital[13].write(1)
    sleep(0.5)
    board.digital[13].write(0)
    sleep(0.5)<span class="kwd">  </span>

from pyfirmata import Arduino, util

from time import sleep

board = Arduino('/dev/ttyS0')

print "Start blinking D13"

while True:

board.digital[13].write(1)

sleep(0.5)

board.digital[13].write(0)

sleep(0.5)<span class="kwd"> </span>

Save and quit.

Always in a linux terminal run now

python ./blink_with_firmata.py

1	python ./blink_with_firmata.py

The LED on the card should turn on and off.

Below is the link to download the two files ready for the Link 7688 Duo

Lede Python Firmata files

In the next article we’ll enable the board to work like Arduino Yun

LEDE on Linkit 7688 Duo – Timecheck example

Configuration, Software

Mqtt with Beaglebone and ESP8266 – Articles List

2017-05-21 admin

Below is a list of the articles to follow to build your IOT environment consisting of sensors and relays with Beaglebone, ESP8266 and MQTT Mosquitto server.

Configuration, Software

Mqtt with Beaglebone and ESP8266 – Android Client

2017-05-05 admin

After Mosquitto server, ESP8266 nodes and Freeboard configuration

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

Mqtt with Beaglebone and ESP8266 – Freeboard

now we can proceed to use a Mqtt Client on an Android device.

In the Playstore various Mqtt applications are available

After the publishing and subscriber topics configuration in the Android client , analogous to what has been done for Freeboard widgets

Mqtt with Beaglebone and ESP8266 – Freeboard

it is possible to monitor the sensor temperature and humidity, the devices status and send commands to the relay (Turn On, Turn Off, Status, Restart, Sleep) and to the sensor (Restart, Sleep, Status).

Here is a screenshot with some subcriber topic and publisher topics of our installation using MQTT Dashboard

With the relay on

Configuration, Software

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

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

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

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

Micro Devices

Category Archives: Configuration

OctoPrint installation on Orange PI PC – HAProxy Installation

OctoPrint installation on Orange PI PC – Autostart

Enigma 2 – How to read the contents of an image

LEDE on Linkit 7688 Duo – Timecheck example

LEDE on Linkit 7688 Duo – Firmata and Python

Mqtt with Beaglebone and ESP8266 – Articles List

Mqtt with Beaglebone and ESP8266 – Android Client

Mqtt with Beaglebone and ESP8266 – Freeboard

MQTT with BeagleBone and ESP8266 – WebServer and MQTT WebSocket

Mqtt with Beaglebone and ESP8266-MQTT ESP8266

Blog about embedded devices