Using a ESP8266 Wifi Module: Difference between revisions

From STorM32-BGC Wiki
Jump to navigation Jump to search
No edit summary
 
(63 intermediate revisions by the same user not shown)
Line 1: Line 1:
''The information on this page refers to firmware v2.29e and higher.''
''The information on this page refers to firmware v2.61f and higher.''


Since firmware version v2.28e, communication via Wifi using the popular [https://espressif.com/en/products/hardware/esp8266ex/overview ESP8266 Wifi module] is available.
Since firmware version v2.28e, communication via Wifi using the popular [https://espressif.com/en/products/hardware/esp8266ex/overview ESP8266 Wifi module] is supported.


<div class="toclimit-2">__TOC__</div>
<div class="toclimit-2">__TOC__</div>
Line 8: Line 8:


Things to have at minimum:
Things to have at minimum:
* ESP-01 ESP8266 Wifi Module with 1MB (8Mb) flash
* ESP8266 Wifi Module with 1 MB (8 Mb) flash
* USB-to-serial adapter
* USB-to-serial adapter


The need for a ESP8266 Wifi module should be obvious. The USB-to-serial adapter is required for flashing the ESP8266 module with a dedicated firmware and upload other files to the ESP8266. However, you probably have one anyhow, since it's also needed for upgrading STorM32 v1.x main boards.
The ESP8266 Wifi module in the list is obvious. A USB-to-serial adapter is needed in addition. It is required for flashing the ESP8266 module with a dedicated firmware and upload other files to the ESP8266. However, you probably have one anyhow.


It is important to get the correct ESP8266 module. Quite many different versions are available, see e.g. [http://www.esp8266.com/wiki/doku.php?id=esp8266-module-family]. You need a module with '''''1MB (8Mb)''''' flash, since the STorM32's ESP firmware is made for that flash size.  
It is important to get the correct ESP8266 module. Quite many different versions are available, see e.g. [http://www.esp8266.com/wiki/doku.php?id=esp8266-module-family]. You need a module with '''''1 MB (8 Mb)''''' flash, since the STorM32's ESP firmware is made for that flash size.  


With proper cabling any ESP8266 module with said flash size can be used. The STorM32 v3.x boards are however prepared for hosting a ESP-01 module. The original ESP-01 module has only 512KB (4Mb) flash and is thus '''''not''''' suitable. You need a "new" ESP-01 module, which nowadays are in fact mostly sold. These are typically black instead of blue, and come with a label '''''"AI-Cloud inside"''''', or as '''''ESP-01s "s series"'''''. However, as always with this Asian stuff, one can't be absolutely sure, so buy with care.
In principle, any ESP8266 module with said flash size can be used. The original ESP-01 module has only 512 KB (4 Mb) flash and is thus '''''not''''' suitable. You need a "new" ESP-01 module, which nowadays are in fact mostly sold. These are typically black instead of blue, and come with a label '''''"AI-Cloud inside"''''', or as '''''ESP-01s "s series"'''''. However, as always with this Asian stuff, one can't be absolutely sure, so buy with care.


:[[File:Esp8266-esp01-modules.jpg|360px]]
:[[File:Esp8266-esp01-modules.jpg|360px]]


== Installation ==
== Power Supply ==


The installation consists of four steps: flashing the ESP8266 module with the dedicated firmware, uploading some data files to the ESP8266 module, connecting the ESP8266 module to the STorM32 controller, and configuring the STorM32 controller.
The ESP8266 requires 3.3 V, but is quite power hungry and attention needs to be paid to the power scheme. The average power consumption is not critical, the ESP8266 however consumes the power in burst of up to several 100 mA, and the power supply must be able to handle that. Therefore, the ESP8266 module must not be powered from the 3.3 V rail on the STorM32 boards.  


=== Flashing the ESP8266 ===
== Setup ==


Before the ESP8266 module can be used with the STorM32, it needs to be flashed with a dedicated firmware, and some data files need to be uploaded.


=== Uploading of Data Files to the ESP8266 ===
In the following steps you will flash the ESP8266 module with the dedicated firmware, upload some data files to the ESP8266 module, and connect the ESP8266 module to the STorM32 controller.


# '''''Connecting the ESP8266 to the USB-TTL Adapter:''''' For flashing, the USB-TTL adapter needs to be connected to the ESP, the GPIO0 pin connected with Gnd, and the ESP module be reset. These steps are explained in countless posts on the web, so please choose the one of your liking ([https://www.google.de/search?q=ESP8266+ESP-01+flashing&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&ei=wkhwWcq6GafVXqrsm1A google]).
# '''''Flashing the ESP8266:''''' Bring the ESP module into flash mode as described in step (1). Open a file explorer and browse to the directory 'o323BgcEspWebApp' in your STorM32 firmware folder. Hit cmd-here.bat, which should open a DOS box. Enter 'uploadInoBin.bat COM??' (without quotation marks), where COM?? should be the correct COM port the USB-TTL adapter is assigned to, and hit enter. The flashing should start now.
# '''''Uploading of Data Files to the ESP8266:''''' Bring the ESP module again into flash mode as described in step (1). In the DOS box enter now 'uploadDataToFs.bat COM??' (without quotation marks), where COM?? should be the COM port of the USB-TTL adapter as before, and hit enter. The data upload should start now.
# '''''Connecting the ESP8266 to the STorM32:''''' The ESP module needs to be connected to the UART port on the STorM32 controller.


=== Connecting the ESP8266 ===
{{COMMENT|{{WARNING|The ESP module is quite power hungry, it needs up to ca. 250 mA. Do '''not''' connect it to the 3.3 V supply on the STorM32 board. Power it by a separate 3.3 V BEC. Do '''not''' apply voltages larger than 3.3 V to the ESP module, this will destroy it immediately.}}}}


== ESP8266 Operation Modes ==
The ESP can be run in different operation modes. You can set and configure the mode by corresponding entries in the storm32web.cfg file, which is located in the data file folder, and which you just uploaded together with some other files in that folder. In the following, we will use the default configuration, which is the '''''AP Bridge''''' mode. The ESP provides then an access point, with these credentials:
* SSID = STorM32 ESP
* password = thisisgreat
* url = 192.168.4.1
* port = 80
When powered up, you should find an entry 'STorM32 ESP' in the WLAN list. For using it you will of course have to connect to it.
:[[File:Esp8266-apbridge-wlanlist-connected.jpg|200px]]
The '''''AP Bridge''''' mode provides Wifi access the STorM32 via both the GUI or the STorM32 Web App, but not both at the same time. Also, once the STorM32 Web App has been called, a connection to the GUI via Wifi is not possible anymore (using first the GUI, and then the STorM32 Web App works fine, but not vice versa). In order to get Wifi access again via the GUI, you have to reset the STorM32 controller (or enter '192.168.4.1/apbridge' in the browser).
{{COMMENT|This is so because for connecting with the GUI the ESP is switched internally to work as a bridge while for running the STorM32 Web App the ESP is switched internally to act as a web server. It is possible to switch from bridge to web server operation, but not back.}}
== GUI ==
Using the Wifi connection with the GUI is trivial. When your WLAN is connected to the access point 'STorM32 ESP', an entry 'ESP (STorM32 ESP)' should show up in the drop down list of the {{GUIFIELD|Port}} field. Select it, that's it. All GUI functions should work as normal.
:[[File:Esp8266-apbridge-gui-port.jpg|380px]]
{{COMMENT|It may happen that the connection hangs for few seconds at the first connection. This is because Windows has enumerated the access point, which lets the 'ESP (STorM32 ESP)' entry appear in the list, but is not yet really ready, as also indicated by the mouse cursor.}}
<!--
== Ordering Information ==
Things to have at minimum:
* ESP8266 Wifi Module with 1 MB (8 Mb) flash
* USB-to-serial adapter or v3.x STorM32 board
The ESP8266 Wifi module in the list is obvious. If you are using a v1.x STorM32 board, when a USB-to-serial adapter is needed in addition. It is required for flashing the ESP8266 module with a dedicated firmware and upload other files to the ESP8266. However, you probably have one anyhow. For STorM32 v3.x boards a USB-TTL adapter is not needed.


=== STorM32 Configuration ===
It is important to get the correct ESP8266 module. Quite many different versions are available, see e.g. [http://www.esp8266.com/wiki/doku.php?id=esp8266-module-family]. You need a module with '''''1 MB (8 Mb)''''' flash, since the STorM32's ESP firmware is made for that flash size.
 
In principle, any ESP8266 module with said flash size can be used. For the STorM32 v3.x boards adapter PCBs for hosting a ESP-01 module are available. The original ESP-01 module has only 512 KB (4 Mb) flash and is thus '''''not''''' suitable. You need a "new" ESP-01 module, which nowadays are in fact mostly sold. These are typically black instead of blue, and come with a label '''''"AI-Cloud inside"''''', or as '''''ESP-01s "s series"'''''. However, as always with this Asian stuff, one can't be absolutely sure, so buy with care.
 
:[[File:Esp8266-esp01-modules.jpg|360px]]
 
== Power Supply ==
 
The ESP8266 requires 3.3 V, but is quite power hungry and attention needs to be paid to the power scheme. The average power consumption is not critical, the ESP8266 however consumes the power in burst of up to several 100 mA, and the power supply must be able to handle that. Therefore, the ESP8266 module must not be powered from the 3.3 V rail on the STorM32 boards.
 
The v3.3x STorM32 board provides a ESP8266 port, which exposes the 5 V power rail. The ESP8266 can be powered from this using a 3.3 V voltage regulator with sufficient capacitance. A dedicated ESP8266 adapter board has been designed:
 
::[[File:Esp8266-adapter.jpg|480px]]
 
== Setup ==
 
Before the ESP8266 module can be used with the STorM32, it needs to be flashed with a dedicated firmware, and some data files need to be uploaded. Also, the ESP8266 support needs to be enabled in the GUI. The procedure is different for the v1.x and v3.x STorM32 boards.
 
=== v3.x STorM32 Boards ===
 
For v3.x STorM32 boards, the configuration of the ESP8266 module can be conveniently achieved by using the {{GUI|ESP Configure Tool}}, which is accessible from the {{GUI|Tools}} menu in the GUI. Just go through these steps.
 
# Connect the STorM32 controller via its USB port to a PC. Note: The STorM32 controller must be connected via its USB port, and not via any of the UART ports.
# Select the USB COM port of the STorM32 controller.
# Select the UART port the ESP8266 module is connected to. For v3.x STorM32 boards this would normally be {{PARAMVALUE|uart2}}.  This setting will be written into the parameter {{PARAMNAME|Esp Configuration}}.
# Flash the ESP8266 with the proper firmware by hitting the {{GUI|Upload .Bin}} button. This brings up a DOS box. Please wait until it has finished, and then press any key to close it.
# Upload the data files to the ESP8266 by hitting the {{GUI|Upload Data Files}} button. This brings up a DOS box. Please wait until it has finished, and then press any key to close it.
# Repower both the STorM32 and ESP8266 boards. Note: You must repower both, resetting only the STorM32 board is not sufficient.
 
:[[File:Esp8266-v3x-gui-configuration.jpg|360px]]
 
=== v1.x STorM32 Boards ===
 
In the following steps you will flash the ESP8266 module with the dedicated firmware, upload some data files to the ESP8266 module, connect the ESP8266 module to the STorM32 controller, and configure the ESP support in the GUI.
 
# '''''Connecting the ESP8266 to the USB-TTL Adapter:''''' For flashing, the USB-TTL adapter needs to be connected to the ESP, the GPIO0 pin connected with Gnd, and the ESP module be reset. These steps are explained in countless posts on the web, so please choose the one of your liking ([https://www.google.de/search?q=ESP8266+ESP-01+flashing&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&ei=wkhwWcq6GafVXqrsm1A google]).
# '''''Flashing the ESP8266:''''' Bring the ESP module into flash mode as described in step (1). Open a file explorer and browse to the directory 'o323BgcEspWebApp' in your STorM32 firmware folder. Hit cmd-here.bat, which should open a DOS box. Enter 'uploadInoBin.bat COM??' (without quotation marks), where COM?? should be the correct COM port the USB-TTL adapter is assigned to, and hit enter. The flashing should start now.
# '''''Uploading of Data Files to the ESP8266:''''' Bring the ESP module again into flash mode as described in step (1). In the DOS box enter now 'uploadDataToFs.bat COM??' (without quotation marks), where COM?? should be the COM port of the USB-TTL adapter as before, and hit enter. The data upload should start now.
# '''''Connecting the ESP8266 to the STorM32:''''' The ESP module needs to be connected to the UART port on the STorM32 controller.
# '''''Configuring the ESP support in the GUI:''''' Connect the STorM32 board via one of the serial ports to your PC, select the correct port in the {{GUIFIELD|Port}} field, and hit {{GUIFIELD|Connect}} (do '''''not''''' use the Wifi connection, but a standard serial connection). Then browse to the {{GUI|Setup}} tab, and set the parameter {{PARAMNAME|Esp Configuration}} to {{PARAMVALUE|uart}}. Write+Store the settings to the board, and repower. You must repower both the STorM32 and ESP boards; resetting only the STorM32 board is not sufficient.
:[[File:Storm32-wiki-esp8266-gui-configuration-2.jpg|360px]]
 
{{COMMENT|{{WARNING|The ESP module is quite power hungry, it needs up to ca. 250 mA. Do '''not''' connect it to the 3.3 V supply on the STorM32 board. Power it by a separate 3.3 V BEC. Do '''not''' apply voltages larger than 3.3 V to the ESP module, this will destroy it immediately.}}}}
 
=== What is the parameter {{PARAMNAME|Esp Configuration}} for? ===
 
The ESP8266 Wifi module has the nasty property that it sends out junk on its UART at startup. In order to avoid that this junk data upsets the STorM32 controller, the UART port to which the ESP8266 is connected to needs a special handling. This special handling is enabled by the {{PARAMNAME|Esp Configuration}} parameter.
 
Enabling the special handling implies that the respective UART port doesn't work normally. For instance, using it to connect to the GUI via a USB-TTL adapter won't work as expected.
 
It is not strictly mandatory to use the special handling, i.e., setting {{PARAMNAME|Esp Configuration}} to {{PARAMVALUE|off}} is possible. However, doing so implies to count on ones luck that the ESP8266 startup junk doesn't upset the STorM32 controller.


== ESP8266 Operation Modes ==
== ESP8266 Operation Modes ==


The ESP can be put into different operation modes. You can set and configure the mode by a corresponding entries in the storm32web.cfg file, which is located in the data file folder, and which you just uploaded together with some other files in that folder. However, in the following, we will use the default configuration, which is the '''''AP Bridge''''' mode (for further details see below). The ESP provides then an access point, with these credentials:
The ESP can be run in different operation modes. You can set and configure the mode by corresponding entries in the storm32web.cfg file, which is located in the data file folder, and which you just uploaded together with some other files in that folder. In the following, we will use the default configuration, which is the '''''AP Bridge''''' mode. The ESP provides then an access point, with these credentials:


* SSID = STorM32 ESP
* SSID = STorM32 ESP
Line 43: Line 131:
* port = 80
* port = 80


When powered up, you should find an entry 'STorM32 ESP' in the wlan list. For using it you will of course have to connect to it.
When powered up, you should find an entry 'STorM32 ESP' in the WLAN list. For using it you will of course have to connect to it.


:[[File:Esp8266-apbridge-wlanlist.jpg|200px]] : [[File:Esp8266-apbridge-wlanlist-connected.jpg|210px]]
:[[File:Esp8266-apbridge-wlanlist-connected.jpg|200px]]


The '''''AP Bridge''''' mode allows us to access the STorM32 via both the GUI or the STorM32 Web App, but not both at the same time. Also, once the STorM32 Web App has been called, a connection to the GUI is not possible anymore (using first the GUI, and then the STorM32 Web App works fine, but not vice versa). In order to get again access via the GUI, you have to reset the STorM32 controller (or enter '192.168.4.1/bridge' in the browser).  
The '''''AP Bridge''''' mode provides Wifi access the STorM32 via both the GUI or the STorM32 Web App, but not both at the same time. Also, once the STorM32 Web App has been called, a connection to the GUI via Wifi is not possible anymore (using first the GUI, and then the STorM32 Web App works fine, but not vice versa). In order to get Wifi access again via the GUI, you have to reset the STorM32 controller (or enter '192.168.4.1/apbridge' in the browser).  


{{COMMENT|This is so because for connecting with the GUI the ESP is switched internally to work as a bridge while for running the STorM32 Web App the ESP is switched internally to act as a web server. It is possible to switch from bridge to web server operation, but back.}}
{{COMMENT|This is so because for connecting with the GUI the ESP is switched internally to work as a bridge while for running the STorM32 Web App the ESP is switched internally to act as a web server. It is possible to switch from bridge to web server operation, but not back.}}


== GUI ==
== GUI ==
Using the Wifi connection with the GUI is trivial. When your WLAN is connected to the access point 'STorM32 ESP', an entry 'ESP (STorM32 ESP)' should show up in the drop down list of the {{GUIFIELD|Port}} field. Select it, that's it. All GUI functions should work as normal.


:[[File:Esp8266-apbridge-gui-port.jpg|380px]]
:[[File:Esp8266-apbridge-gui-port.jpg|380px]]


== STorM32 Web App ==
{{COMMENT|It may happen that the connection hangs for few seconds at the first connection. This is because Windows has enumerated the access point, which lets the 'ESP (STorM32 ESP)' entry appear in the list, but is not yet really ready, as also indicated by the mouse cursor.}}
 
== Web Browser: STorM32 Web App ==
 
The STorM32 Web App is an attempt to provide platform independent configuration of the STorM32 controller, for mobiles and desktops.
 
It works as follows: The ESP module runs a web server, at the URL given in the chapter [[#ESP8266_Operation_Modes|ESP8266 Operation Modes]]. Thus, with your device (mobile or desktop) you just need to establish a Wifi connection to the ESP module, start a web browser, and browser to the said URL. The ESP isn't very fast, so the loading of the web page takes a couple of seconds.
 
Currently, the STorM32 Web App provides only very basic configuration possibilities; all parameters can be read, modified and written and stored.
 
:[[File:Esp8266-webapp-dashboard.jpg|440px]]
 
 
==== Call for Contributions ====
 
I'm not an experienced web page programmer, and I'm especially weak on web design. In short, any contribution in that regard would be most appreciated. You are greatly encouraged to create your own styles, and improve the javascript file.
 
This is made very easy, I think, by the STorM32's ESP firmware. The modified .js and .css (and even . htm) files just need to be uploaded to the ESP, as described before in the chapter [[#Installation|Installation]]. Even better for development, one can set options in the storm32web.cfg file such that the .js and .css files are fetched from your private web space, which makes the development cycle very fast. See storm32web.cfg for details.
 
 
 
-->
 
 
 




== Brief ==


brief instructions for using the ESP8266 wifi support


0) you need a black ESP-01 (i.e. a ESP-01 with 1M instead of 0.5M)(typically they come with a label "AI-Cloud inside", or as ESP-01s "s series").


1) you need to flash the firmware onto the ESP
- connect the ESP to a usb-ttl adapter and connect the pins to bring it into bootloader mode, exactly as explained on one of the many instructions on the web
- browse to the o323BgcEspWebApp directory in the STorM32 firmware folder
- double click cmd-here.bat
- enter uploadInoBin COM??, where COM?? stands for the com port (e.g. COM23), and hit enter


2) you need to upload the files in the data subfolder to the SPIFFS file system
- connect the ESP to a usb-ttl adapter and connect the pins to bring it into bootloader mode, exactly as explained on one of the many instructions on the web
- browse to the o323BgcEspWebApp directory in the StorM32 firmware folder
- double click cmd-here.bat
- enter uploadDataToFs COM??, where COM?? stands for the com port (e.g. COM23), and hit enter


3) Connect the ESP to the STorM32 board
- connect the ESP's Tx and Rx pins to the STorM32's UART Rx and Tx pins
- provide 3.3V power to the ESP (do NOT use the STorM32's 3.3V pins, they are too weak)(do NOT use voltages larger than 3.3V)


4) Configure ESP in STorM32 GUI
- set the parameter "Esp Configuration" in the Expert tab to "Uart"


5) Connect Wifi
By default the ESP is configured as access point with ssid "STorM32 ESP" and password "thisisgreat". So, connect to it, start the browser, and go to 192.168.4.1. Alternative, start the GUI and choose "ESP" in teh Port field.




You are greatly encouraged to improve the javascript and css files. This is made very easy. The ESP just provides a very rudimentary HTML skeleton, everything essential is filled in by the js and css scripst, and these are stored in the ESP's filesystem. In order to use your own js and css, you just have to upload them to the EPS's filesystem (step 3). You also can provide links to js and css files on your own webspace, which makes development most easy. See storm32web.cfg for details.
<!--
3). You also can provide links to js and css files on your own webspace, which makes development most easy.  




Line 101: Line 196:


* '''''AP Bridge''''': This mode is activated by an entry 'mode = AP Bridge' in the storm32web.cfg file. In this mode the ESP is configured as access point. That means, after startup you will find a new access point with the SSID and password as set in the storm32web.cfg file (parameters 'AP bridge ssid' and 'AP bridge password'). Per default the SSID is 'STorM32 ESP' and the password 'thisisgreat'. In this mode, the STorM32 can be accessed via the STorM32 Web App, but not the GUI. The STorM32 Web App is started by browsing to the url 192.168.4.1.
* '''''AP Bridge''''': This mode is activated by an entry 'mode = AP Bridge' in the storm32web.cfg file. In this mode the ESP is configured as access point. That means, after startup you will find a new access point with the SSID and password as set in the storm32web.cfg file (parameters 'AP bridge ssid' and 'AP bridge password'). Per default the SSID is 'STorM32 ESP' and the password 'thisisgreat'. In this mode, the STorM32 can be accessed via the STorM32 Web App, but not the GUI. The STorM32 Web App is started by browsing to the url 192.168.4.1.
-->

Latest revision as of 07:25, 23 July 2022

The information on this page refers to firmware v2.61f and higher.

Since firmware version v2.28e, communication via Wifi using the popular ESP8266 Wifi module is supported.

Ordering Information

Things to have at minimum:

  • ESP8266 Wifi Module with 1 MB (8 Mb) flash
  • USB-to-serial adapter

The ESP8266 Wifi module in the list is obvious. A USB-to-serial adapter is needed in addition. It is required for flashing the ESP8266 module with a dedicated firmware and upload other files to the ESP8266. However, you probably have one anyhow.

It is important to get the correct ESP8266 module. Quite many different versions are available, see e.g. [1]. You need a module with 1 MB (8 Mb) flash, since the STorM32's ESP firmware is made for that flash size.

In principle, any ESP8266 module with said flash size can be used. The original ESP-01 module has only 512 KB (4 Mb) flash and is thus not suitable. You need a "new" ESP-01 module, which nowadays are in fact mostly sold. These are typically black instead of blue, and come with a label "AI-Cloud inside", or as ESP-01s "s series". However, as always with this Asian stuff, one can't be absolutely sure, so buy with care.

Esp8266-esp01-modules.jpg

Power Supply

The ESP8266 requires 3.3 V, but is quite power hungry and attention needs to be paid to the power scheme. The average power consumption is not critical, the ESP8266 however consumes the power in burst of up to several 100 mA, and the power supply must be able to handle that. Therefore, the ESP8266 module must not be powered from the 3.3 V rail on the STorM32 boards.

Setup

Before the ESP8266 module can be used with the STorM32, it needs to be flashed with a dedicated firmware, and some data files need to be uploaded.

In the following steps you will flash the ESP8266 module with the dedicated firmware, upload some data files to the ESP8266 module, and connect the ESP8266 module to the STorM32 controller.

  1. Connecting the ESP8266 to the USB-TTL Adapter: For flashing, the USB-TTL adapter needs to be connected to the ESP, the GPIO0 pin connected with Gnd, and the ESP module be reset. These steps are explained in countless posts on the web, so please choose the one of your liking (google).
  2. Flashing the ESP8266: Bring the ESP module into flash mode as described in step (1). Open a file explorer and browse to the directory 'o323BgcEspWebApp' in your STorM32 firmware folder. Hit cmd-here.bat, which should open a DOS box. Enter 'uploadInoBin.bat COM??' (without quotation marks), where COM?? should be the correct COM port the USB-TTL adapter is assigned to, and hit enter. The flashing should start now.
  3. Uploading of Data Files to the ESP8266: Bring the ESP module again into flash mode as described in step (1). In the DOS box enter now 'uploadDataToFs.bat COM??' (without quotation marks), where COM?? should be the COM port of the USB-TTL adapter as before, and hit enter. The data upload should start now.
  4. Connecting the ESP8266 to the STorM32: The ESP module needs to be connected to the UART port on the STorM32 controller.

Comment: The ESP module is quite power hungry, it needs up to ca. 250 mA. Do not connect it to the 3.3 V supply on the STorM32 board. Power it by a separate 3.3 V BEC. Do not apply voltages larger than 3.3 V to the ESP module, this will destroy it immediately.

ESP8266 Operation Modes

The ESP can be run in different operation modes. You can set and configure the mode by corresponding entries in the storm32web.cfg file, which is located in the data file folder, and which you just uploaded together with some other files in that folder. In the following, we will use the default configuration, which is the AP Bridge mode. The ESP provides then an access point, with these credentials:

  • SSID = STorM32 ESP
  • password = thisisgreat
  • url = 192.168.4.1
  • port = 80

When powered up, you should find an entry 'STorM32 ESP' in the WLAN list. For using it you will of course have to connect to it.

Esp8266-apbridge-wlanlist-connected.jpg

The AP Bridge mode provides Wifi access the STorM32 via both the GUI or the STorM32 Web App, but not both at the same time. Also, once the STorM32 Web App has been called, a connection to the GUI via Wifi is not possible anymore (using first the GUI, and then the STorM32 Web App works fine, but not vice versa). In order to get Wifi access again via the GUI, you have to reset the STorM32 controller (or enter '192.168.4.1/apbridge' in the browser).

Comment: This is so because for connecting with the GUI the ESP is switched internally to work as a bridge while for running the STorM32 Web App the ESP is switched internally to act as a web server. It is possible to switch from bridge to web server operation, but not back.

GUI

Using the Wifi connection with the GUI is trivial. When your WLAN is connected to the access point 'STorM32 ESP', an entry 'ESP (STorM32 ESP)' should show up in the drop down list of the [Port] field. Select it, that's it. All GUI functions should work as normal.

Esp8266-apbridge-gui-port.jpg

Comment: It may happen that the connection hangs for few seconds at the first connection. This is because Windows has enumerated the access point, which lets the 'ESP (STorM32 ESP)' entry appear in the list, but is not yet really ready, as also indicated by the mouse cursor.