-
Notifications
You must be signed in to change notification settings - Fork 20
EN Installing firmware
Language: DE
Previous page | Next page |
---|---|
Components supply | Assembly of components |
The operating system of the computer which will upload the sensor software or "firmware" to the NodeMCU - also called to flash - will need a driver to communicate with it. The computer will interact with the USB2Serial chip on the NodeMCU. This will also depend on the version of the NodeMCU. Linux natively provides drivers already.
If the version of the NodeMCU is unknown, a description of either CP2102
or CH340G
can be found on the back. Alternatively one of the chips are marked,in which case you will most likely need a magnifying glass.
CP210x USB TO UART Bridge Drivers
CH340G Bridge Drivers
- Driver page of manufacturer (Chinese)
- Mac drivers, or for Sierrra see these successfully tested instructions
- Windows drivers
- Raspberry Pi drivers
Restart the computer after installing the drivers. Comment MacOS >10.9: Unsigned drivers have to be explicitly allowed. A good description can be found here.
Caution: Do not use USB cables longer then 1m for uploading the firmware to NodeMCU.
We will be describing two variants of installing the sensor software. VARIANT 1 includes compilation of the source code, whereas with VARIANT 2 you use the esptool of the Arduino IDE to upload binaries. VARIANT 2 is recommended as fast path or for beginners. For both variants you'll need the follow these instructions:
- Download and install Arduino IDE.
- Install platform packages for ESP8266 with Boards Manager following these instructions.
- Close Arduino IDE.
In order to upload the firmware you will need to supply information of the USB port the operating system is supposed to use. You can do this by connecting the NodeMCU to the port you want use later on and then start the Arduino IDE. At Tools → Port the available ports will be listed and the NodeMCU should be easy to find. To confirm this is actually the right port: Select the port and select Tools → Get Board Info. In the status bar, under VID
and PID
you should now see codes. Close the IDE now to free up the ports.
- MAC:
CP2102
on/dev/cu.SLAB_USBTOUART
andCH340G
on/dev/cu.wchusbserialXXXXXXXX
. - Windows:
COM3
. If its not that port, just try the next ones in the list of available ports. - Linux:
/dev/ttyUSB0
or similar
Here we show how to compile the firmware yourself and upload it to the NodeMCU.
- Start Arduino IDE (after previously installing platform packages and closing it).
- Install the following libraries. Compare Readme.md and note license:
- ArduinoJson (5.13.1) (MIT)
- Adafruit Unified Sensor (1.0.2) (Apache)
- Adafruit BMP085 library (1.0.0) (BSD)
- Adafruit BMP280 library (1.0.2) (BSD)
- Adafruit BME280 library (1.0.7) (BSD)
- DallasTemperature (3.8.0)
- DHT sensor library (1.1.1) (MIT)
- ESP8266 and ESP32 Oled driver for SSD1306 display (4.0.0) (MIT)
- OneWire (2.3.4)
- LiquidCrystal I2C (1.1.2)
- Adafruit HTU21DF Library (1.0.1)
- SoftwareSerial (1.0.0) (GNU Lesser Public License >=2.1)
- In the IDE at Tools → Board select
- NodeMCU 0.9 (ESP-12 Module) for NodeMCU v1
- NodeMCU 1.0 (ESP-12E Module) for NodeMCU v2 und v3
- Now connect NodeMCU via USB and select the port at Tools → Port.
- Copy the source code to your computer. Best and most convenient method is to clone the repository or download the repository as archive and unpack it. Alternatively all files from the source code directory can be manually copied as well. If you do choose the latter, the RAW button might help.
- Open the sketch (
INO
) file in Arduino IDE. - Change the
ext_def.h
to meet your requirements (WLAN configuration, sensors, ...) - Now flash the NodeMCU with Sketch → Upload or the upload button (right arrow).
In this variant we will use the command line tool esptool, which came with the Arduino IDE installation.
- Download the compiled firmware in English or another language
- Open a command prompt or terminal in your operating system.
- Paths below may differ due a different version number - also the location of the esptool might have changed with your installation:
- Windows:
"%USERPROFILE%\AppData\Local\Arduino15\packages\esp8266\tools\esptool\0.4.13\esptool.exe" -vv -cd nodemcu -cb 57600 -ca 0x00000 -cp COM11 -cf "_PATH-TO-DOWNLOADED-FIRMWARE-FILE_"
- Change the port after
-cp
to yours - Use quotation marks as documented
- Change the port after
- Linux/MacOS:
$PATH-TO-ESPTOOL -vv -cd nodemcu -cb 57600 -ca 0x00000 -cp $USBPORT -cf $BINARY
-
$PATH-TO-ESPTOOL
mit look something like~/Library/Arduino15/packages/esp8266/tools/esptool/0.4.13/esptool
or~/.arduino15/packages/esp8266/tools/esptool/0.4.13/esptool
-
$USBPORT
might look like something like this/dev/cu.wchusbserial1410
or/dev/ttyUSB0
-
$BINARY
is the path to the binary, eg.latest_en.bin
orsensors-software/airrohr-firmware/airrohr-firmware.ino.nodemcu.bin
-
- Windows:
Description of parameters:
-vv show additional information while flashing (useful for troubleshooting)
-cd nodemcu which reset method should be used
-cb 57600 baud rate for flashing
-ca 0x00000 start address in flash memory
-cp <pfad> path to the port the NodeMCU is connected to
-cf <pfad> path to downloaded firmware file
You can delete the config with Arduino IDE and the ESP8266fs Plugin.
- First you need to install the plugin. Follow the instruction on the plugin page.
- Once the installation done, re-open Arduino IDE and be sure to have an empty sketch. Click on Tools>ESP8266 Sketch Data Upload. You'll have to confirm that you want to upload an empty SPIFFS image. The upload process (3 MB) might take a while. You are done when the output displays "Hard resetting via RTS pin...".
- Download this image file
- Download ESP8266 Download Tool
- Unzip the ESP8266 Download Tool and click on flash_download_tools_vX.X.X.exe
- Select ESP8266 DownloadTool
- Choose the path to the bin, add
0x100000
after @, set the right COM and click start
For Linux, yet untested with MacOs, there's a script to delete the config here.
In Arduino IDE activate Tools → Serial Monitor to review debug information via USB. The output can be read at a baud rate of 9600. Errors such as WLAN login failures or unsuccessful upload of data can be monitored here.
- Wiki home, EN
- Bezugsquellen Einzelteile, EN
- Firmware einspielen, EN
- Zusammenbau der Komponenten (Schaltung), EN
- Zusammenbau der Komponenten (Montage Einzelteile), EN
- Sensor-Konfiguration, EN
- Eintrag in der Datenbank, EN
- Links (Grafiken, Sensor-Infos), EN
- Translations
- Data format
- APIs, EN
- Anschluss weitere Sensoren und Hardware
- Senden an Sensor.Community (z.B. mit Raspberry Pi)
- NodeMCU Pinouts v2, v3
- Datenblätter, Spezifikationen
- Unterstützte Sensoren
- Studien
- ähnliche Projekte
- Korrektur Luftfeuchte, EN
- EN: How to use the SDS011 as a mobile sensor
- FR: Comment utiliser SDS011 comme capteur PM mobile
- 2020-04-0 Stadtbücherei - Weihnachtsferien
- 2020-04-0 Shackspace
- 2020-03-24 Stadtbücherei - Weihnachtsferien
- 2020-03-10 Shackspace
- 2020-02-23 Stadtbücherei
- 2020-02-09 Shackspace
- 2020-01-0 Stadtbücherei
- 2020-01-0 Shackspace
- 2019-12-24 Stadtbücherei - Weihnachtsferien
- 2019-12-10 Shackspace
- 2019-11-26 Stadtbücherei
- 2019-11-12 Shackspace
- 2019-10-22 Stadtbücherei
- 2019-10-08 Shackspace
- 2019-09-24 Stadtbücherei
- 2019-09-10 Shackspace
- 2019-09-24 Stadtbücherei
- 2019-09-10 Shackspace
- 2019-08-27 Stadtbücherei
- 2019-08-13 Shackspace - Sommerferien
- 2019-07-23 Stadtbücherei
- 2019-07-09 Shackspace
- 2019-06-25 Stadtbücherei
- 2019-06-11 Shackspace - Pfingstferien
- 2019-05-28 Stadtbücherei
- 2019-05-14 Shackspace
- 2019-04-23 Stadtbücherei - Osterferien
- 2019-04-09 Shackspace
- 2019-03-26 Stadtbücherei
- 2019-03-12 Shackspace
- 2019-02-26 Stadtbücherei
- 2019-02-12 Shackspace
- 2019-01-22 Stadtbücherei
- 2019-01-08 Shackspace
- 2018-12-18 Stadtbücherei - Weihnachtsferien
- 2018-12-11 Shackspace
- 2018-11-27 Stadtbücherei
- 2018-11-13 Shackspace
- 2018-10-23 Stadtbücherei
- 2018-10-09 Shackspace
- 2018-09-25 Stadtbücherei
- 2018-09-11 Shackspace
- 2018-08-28 Stadtbücherei
- 2018-08-14 Shackspace - Sommerpause
- 2018-07-24 Stadtbücherei
- 2018-07-10 Shackspace
- 2018-06-26 Stadtbücherei
- 2018-06-12 Shackspace
- 2018-05-22 Stadtbücherei
- 2018-05-08 Shackspace
- 2018-04-24 Stadtbücherei
- 2018-04-10 Shackspace
- 2018-03-27 Stadtbücherei
- 2018-03-13 Shackspace
- 2018-03-03 Open Data Day 2018
- 2018-02-27 Stadtbücherei
- 2018-02-13 Shackspace
- 2018-01-23 Stadtbücherei
- 2018-01-09 Shackspace
- 2017-12-26 Stadtbücherei
- 2017-12-12 Shackspace
- 2017-11-28 Stadtbücherei
- 2017-11-14 Shackspace
- 2017-10-24 Stadtbücherei
- 2017-10-10 Shackspace
- 2017-09-26 Stadtbücherei
- 2017-09-12 Shackspace
- 2017-08-22 Stadtbücherei
- 2017-08-08 Shackspace
- 2017-07-25 Stadtbücherei
- 2017-07-11 Shackspace
- 2017-06-27 Stadtbücherei
- 2017-06-13 Shackspace
- 2017-05-23 Stadtbücherei
- 2017-05-09 Shackspace
- 2017-04-25 Stadtbücherei
- 2017-04-11 Shackspace
- 2017-03-28 Stadtbücherei
- 2017-03-14 Shackspace
- 2017-03-04 Open Data Day 2017
- 2017-02-28 Stadtbücherei
- 2017-02-14 Shackspace
- 2017-01-24 Stadtbücherei
- 2017-01-10 Shackspace
- 2016-12-20 Stadtbücherei
- 2016-12-13 Shackspace
- 2016-11-22 Stadtbücherei
- 2016-11-08 Shackspace
- 2016-10-25 Stadtbücherei
- 2016-10-11 Shackspace
- 2016-09-27 Stadtbücherei
- 2016-09-13 Shackspace
- 2016-08-23 Stadtbücherei
- 2016-08-09 Shackspace
- 2016-07-26 Stadtbücherei
- 2016-07-12 Shackspace
for more, see Protokolle