Basics on Internet of Things with the NanoESP

Driver -NanoESP & Pretzelboard

Sun, 23 Aug 2015 10:02:42 +0200

The Pretzelboard (NanoESP) needs a driver for the USB-to-Serial Chip CH340G to work properly. You can download the driver here:

Windows (Windows 98 - Windows 10, 32-Bit/64-Bit)

Linux Version

Mac Version (Attention: There seems to be a problem with MAC OS Sierra. Bellow are two links with walkthroughs:
https://github.com/jimaobian/CH34x_Install_V1.3/blob/master/CH34x_Install_V1.3.zip
https://github.com/adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver )

Android Version

There is a Setup.exe file (Windows Version) in the Zip-Folder which needs to be executed. Choose Install in the following Window.

Day 4: Setting up Internet connection

Sun, 04 Dec 2016 00:01:49 +0100

Behind today’s door is a 1-kohm resistor. We’re not going to do much with it today, but tomorrow it becomes important. In today’s test, we want to set up an initial connection to your home WLAN network. For this purpose, you need, as you will on many days to come, to enter your WLAN data in the programme.

The Board pings the Goolge server

But first you need to download today’s programme. You can download it via the right button on the from the Arduino Create Iframe.

Day 3: The NanoESP in access point mode

Sat, 03 Dec 2016 00:01:18 +0100

Behind the third door is the jumper wire, which is important for many tests. To prepare for later tests, you can place the supply lines GND and VCC on the outermost lanes. You’ll thereby have better access to these important lines later.

The jumpers to GND and VCC

In the project for today, you now get around to changing something in a programme even on your own. The following sample programme serves as a basis:

Day 2: The Arduino IDE

Fri, 02 Dec 2016 00:01:47 +0100

This time there’s a breadboard behind the door. On it, you can quickly and easily assemble the hardware layouts of the Advent calendar. Since only the NanoESP is available so far, we’ll start with it.

NanoESP on a breadboard

It’s best if you plug the controller into the breadboard as shown in the picture. That way, the greatest space remains free for experiments; the WLAN module sticks out behind past the breadboard. The micro-USB cable then hangs between the contact sides and is only a minimal disruption. The board needs to be pressed in gently until it touches the contacts.

Tag 1: Das NanoESP-Board

Thu, 01 Dec 2016 00:01:19 +0100

It’s the first of December and thus time to open the first door. Behind it is arguably the most important element of the calendar: the NanoESP board. This Arduino-compatible controller with WLAN function is at the centre of the 24 tests.

The NanoESP Board

To s briefly, it can be said that the board is most likely a cross between a board similar to an Arduino Nano and a WLAN module with the name ESP8266. The communication between the two elements runs through a serial port generated via software, which is connected to Pins D11 and D12. You should thus avoid these pins with your own projects.

Day 11: TCP-Webserver

Fri, 11 Dec 2015 00:01:31 +0100

In the previous experiments, we dealt with the subject of TCP and access to web servers a lot. Today, the module is to act as a web server of its own for the first time.

Behind the door of the 11th day, there is a special cable that will be very useful soon. A special setup is not necessary today, since the program works similarly to the serial monitor programme of day one.

Day 8: A browser

Tue, 08 Dec 2015 00:01:36 +0100

In the last days, we mostly dealt with the UDP protocol with which data can be sent out simply and directly. In the next few days, we will deal with the TCP (Transmission Control Protocol). TCP only permits one connection at a time between precisely two computers. It is mostly used online for browsing on websites.

Behind today’s door, there is another resistor with 1 kΩ (brown, black, red). As with all other parts: keep it safe, even though you are not using this part today yet.

Day 3: UDP-Send

Thu, 03 Dec 2015 00:01:45 +0100

In today’s project, data are exchanged between the board and the PC through the WLAN for the first time. The prerequisite for this is that your computer has a WLAN adapter. The UDP (User Datagram Protocol) is used. Another program on the PC-side ensures successful receipt of the messages.

Behind the third door of the calendar, you can find an insulated cable that you will need to build circuits. To prepare for later experiments, you can place the supply lines ground and VCC on the outer tracks.

Day 2: Google Ping

Wed, 02 Dec 2015 00:01:40 +0100

With today’s project, you test whether you can reach the Google server. This is used as a test of whether there generally is a connection to the Internet or, e.g., a firewall is blocking the NanoESP-board.

You will find a plug board behind today’s door. The plug board is used as an experimenting platform later, to connect sensors and other elements. It is best if you plug the controller onto the plug board as shown in the following figure. This leaves you the most space for experiments, while the WLAN module protrudes over the plug board at the rear. The micro USB cable is then suspended between the contact sides and will only interfere minimally.

Day 1 - First Steps

Tue, 01 Dec 2015 00:01:38 +0100

It is the first day of December and thus time to open the first door. Behind the door, you will find the most important part of this calendar: the Arduino™-compatible NanoESP-board with integrated WLAN module that this calendar is about.

The NanoESP Board

As you can see quite well on the PCB, the board is made up of two components. The left half is an Arduino™-compatible micro controller system that can be compared to the Arduino™ Nano. The right part is the WLAN module with the designation ESP8266. These two components communicate via a serial interface generated by software. The Arduino™-side rather acts as the boss, forwarding the commands to the WLAN module. Some of these commands will already be tried out today on the first day.

Board specifications NanoESP & Pretzel Board

Wed, 23 Sep 2015 08:05:57 +0200

On this page you can find the specifications of the Board

Specifications:

Microcontroller: ATmega328
Flash memory: 32 KB (including 0,5 KB for the Bootloader)
SRAM: 2 KB
EEPROM: 1 KB
Taktrate: 16 MHz
I/O-Pins: 20 (including 2 for communication with the WiFi module)
- Included PWM: 6
- Included analog inputs: 6
USB-to-Serial Chip: CH340G
Operating voltage: 5 V
Recommended input voltage:: 7-12 V
Maximum current per I/O pin: 40 mA
Load capacityof the 3.3 V output: 50 mA

WLAN-Modul: ESP8266

Quick Start - NanoESP & Pretzelboard

Tue, 22 Sep 2015 08:05:40 +0200

When you attach the board for the first time via the MicroUSB connector, your PC will try to install a driver. If this does not work automatically download and install the driver here.

The ArduinoTM IDE provides the simplest way of programming the development board. Download the IDE from www.Arduino.cc. When you start the software, you first have to choose the correct port and board. For the latter, you select the Arduino NanoTM (ATmega328 processor).

AT Commands -NanoESP & Pretzelboard

Sun, 20 Sep 2015 10:11:14 +0200


Description	Command
Basics
Test Command	AT
Reset	AT+RST
Firmware Infos	AT+GMR
Echo On/Off	ATE<1/0>

WiFi Commands
WiFi-Modus (1 = Client, 2 = AP, 3 = Dual)	AT+CWMODE=
Search WiFi network	AT+CWLAP
Connect to Wifi	AT+CWJAP=““,““
Disconnect WiFi	AT+CWQAP
Settings WiFi -AccesPoint	AT+CWSAP=““,““[,,]
Show IP	AT+CIFSR
activate/deactivate DHCP	AT+CWDHCP=<1/0>
Auto connect to WiFi	AT+CWAUTOCONN=<1/0>
Change MAC address of AP	AT+CIPSTAMAC=
Set IP address of station	AT+CIPSTA=
Set IP address of AccesPoint	AT+CIPAP=
Start SmartConfig	AT+CWSTARTSMART=
Stop SmartConfig	AT+CWSTOPSMART

Communication
Ping	AT+PING=
Accept multiple connections	AT+CIPMUX=
Set transfer mode (0=normal, 1= unvarnished transmission mode, only for TCP single connection)	AT+CIPMODE=
Structure of received data	+IPD,,:
Start connection	AT+CIPSTART=““,“ “,
Send data	AT+CIPSEND=,
Close connection	AT+CIPCLOSE=

Server Commands
Start TCP server	AT+CIPSERVER=1,
Stop TCP server	AT+CIPSERVER=0
Server status & connected clients	AT+CIPSTATUS
Set server timeout	AT+CIPSTO=
Show connected clients	AT+CWLIF