Web-Page examples for ESP8266 and R4

Official Hardware Classic UNO R4 WiFi
1

On ESP8266 I've made webserver sketches based on the given examples. They have dynamic items with values updating. The R4 examples only update when you press F5 or click on a link.

The ESP code uses server.on (various functions) and has values sent both ways (ws.textAll). The R4 has a text conversation with the web-page using client.read and client.print and can only redraw the whole page.

The ESP web-pages seem more useful. Is the difference necessary or can the R4 deliver web-pages like the ESP ones. Does it depend on which libraries are included? Are the libraries hardware dependent? The R4 has an ESP32 so can that run the ESP8266 code?

Any enlightenment appreciated.

ESP

#include <Arduino.h>
#include <ESPAsyncTCP.h>
#include <ESPAsyncWebServer.h>
#include <AsyncElegantOTA.h>
#include <WiFiUdp.h>

R4

#include <SPI.h>
#include <WiFiS3.h> 
#include <ArduinoOTA.h>
2

there was an attempt to port esp webservers to other Arduinos

3

You say "attempt" so I assume unsuccessful. I wouldn't know how to copy things to another hardware if they don't link and work straight away. For the R4 I don't understand if my code is running on ESP32 or Renasas, and I don't want to brick it.

I've copied some css from ESP example, that worked. Next going to try Javascript. Then there's websocket comms between server and web-page - is that available? I guess not.

I'm thinking that Javascript could regularly send a "get" to the server, and that can redraw the page. When the page redraws there is no flicker. Good, surprising. I remember some simple Arduino web-pages a few years ago that had very bad flicker.

4

the libraries work but they predate the Uno R4 and the WiFiS3 library so no support. a WebSocket library is there too.

5

I've made Javascript do a regular "Get" to refresh the page. Yes it works, but not ideal. On Firefox it doesn't flicker, but on Chrome (PC and phone), on MS Edge, and on iPad there is a very annoying flicker.

The R4 sketch also has a running pattern on the led matrix. I noticed it stopped when the R4 updated the web-pages. It stops when the sketch is doing all the client.prints. I added more bytes or more prints to see the time for each. Each print takes 4 mS, and each 10 bytes takes 1 mS. The prints could be combined to make that less significant. 10 bytes/mS is about 0.1 Mbits/Sec. Typical low WiFi is 3 Mbps. So why so slow?

This client.print is new to me. Documentation says print to the server, but for us the R4 is the server and we are printing to the web-page which is the client. Seems the wrong way round. Anyway, I'm wondering what options there are for speeding up or only sending the new values to the web-page. Others asked similar and this may do what I want.

6

Serial for the WiFiS3 communication with the fw in the esp32s2 is at 115200 baud

7

fw? 115200 baud agrees with my measured 0.1Mbps.

8

firmware. this one GitHub - arduino/uno-r4-wifi-usb-bridge

1 Like