Arduino UNO Wi-Fi

I have 3 x uno wi-fi boards, have upgraded all 3 to use WiFiLink library.
Using ESPRecovery & putting the board into Bootloader mode.

Upgraded the firmware with:-

sudo python esptool.py -p /dev/tty.usbmodemFA121 -b 9600 write_flash -ff 80m -fm qio -fs 32m 0x000000 ArduinoFirmwareWiFiLink-UNO_WIFI_DEV_ED-1.0.0.bin 0x300000 ArduinoFirmwareWiFiLink-WEB_PANEL-1.0.0.bin

I’m running a modified sketch, WiFiUdpNtpClient, although the actual problem has nothing to do with this or any other sketch.

I have noticed that I do not get connected to my internal wifi network, possibly 8 out of 10 times that I try running the program after a power on or a reset. Resetting the ESP8266 makes no difference either.

The symptoms are that the ESP8266 on board indicator led does not ‘flash’ and when I run the program the connection fails. Whenever it succeeds the ESP8266 led is flashing, this indicates to me that the ESP8266 is not running or no bridge exists between the uno and the ESP8266.

When I do connect to my internal wifi, the led is flashing and the sketch runs and connects fine, as expected.

The question I am asking is how to resolve this condition? Another firmware version perhaps?

WiFi Link firmware check.

Firmware version installed: 1.0.0
Firmware version required : 1.0.0

Check result: PASSED

Library: WiFiLink by Arduino ver1.0.1

#include <WiFiLink.h>
#include <WiFiUdp.h>

WiFiUDP Udp;

int status = WL_IDLE_STATUS;
char ssid = “MYSSID”; // your network SSID (name)
char pass = “my password”; // your network password
int keyIndex = 0; // your network key Index number (needed only for WEP)

unsigned int localPort = 2390; // local port to listen for UDP packets

IPAddress timeServer(129, 6, 15, 28); // time.nist.gov NTP server

const int NTP_PACKET_SIZE = 48; // NTP time stamp is in the first 48 bytes of the message

byte packetBuffer[ NTP_PACKET_SIZE]; //buffer to hold incoming and outgoing packets

// A UDP instance to let us send and receive packets over UDP

void setup()
{
// Open serial communications and wait for port to open:
Serial.begin(115200);
while (!Serial) {
; // wait for serial port to connect. Needed for native USB port only
}

//Check if communication with wifi module has been established
if (WiFi.status() == WL_NO_WIFI_MODULE_COMM) {
Serial.println(“Communication with WiFi module not established.”);
while (true); // don’t continue:
}

// attempt to connect to Wifi network:
while ( status != WL_CONNECTED) {
Serial.print("Attempting to connect to SSID: ");
Serial.println(ssid);
// Connect to WPA/WPA2 network. Change this line if using open or WEP network:
status = WiFi.begin(ssid, pass);

// wait 10 seconds for connection:
delay(1000);
}

Serial.println(“Connected to wifi”);
printWifiStatus();

Serial.println("\nStarting connection to server…");
Udp.begin(localPort);
}

void loop()
{
sendNTPpacket(timeServer); // send an NTP packet to a time server
// wait to see if a reply is available
delay(1000);
if ( Udp.parsePacket() ) {
Serial.println(“packet received”);
// We’ve received a packet, read the data from it
Udp.read(packetBuffer, NTP_PACKET_SIZE); // read the packet into the buffer

//the timestamp starts at byte 40 of the received packet and is four bytes,
// or two words, long. First, esxtract the two words:

unsigned long highWord = word(packetBuffer[40], packetBuffer[41]);
unsigned long lowWord = word(packetBuffer[42], packetBuffer[43]);
// combine the four bytes (two words) into a long integer
// this is NTP time (seconds since Jan 1 1900):
unsigned long secsSince1900 = highWord << 16 | lowWord;
Serial.print("Seconds since Jan 1 1900 = " );
Serial.println(secsSince1900);

// now convert NTP time into everyday time:
Serial.print("Unix time = ");
// Unix time starts on Jan 1 1970. In seconds, that’s 2208988800:
const unsigned long seventyYears = 2208988800UL;
// subtract seventy years:
unsigned long epoch = secsSince1900 - seventyYears;
// print Unix time:
Serial.println(epoch);

// print the hour, minute and second:
Serial.print("The UTC time is "); // UTC is the time at Greenwich Meridian (GMT)
Serial.print((epoch % 86400L) / 3600); // print the hour (86400 equals secs per day)
Serial.print(’:’);
if ( ((epoch % 3600) / 60) < 10 ) {
// In the first 10 minutes of each hour, we’ll want a leading ‘0’
Serial.print(‘0’);
}
Serial.print((epoch % 3600) / 60); // print the minute (3600 equals secs per minute)
Serial.print(’:’);
if ( (epoch % 60) < 10 ) {
// In the first 10 seconds of each minute, we’ll want a leading ‘0’
Serial.print(‘0’);
}
Serial.println(epoch % 60); // print the second
}
// wait ten seconds before asking for the time again
delay(10000);
}

// send an NTP request to the time server at the given address
unsigned long sendNTPpacket(IPAddress& address)
{
//Serial.println(“1”);
// set all bytes in the buffer to 0
memset(packetBuffer, 0, NTP_PACKET_SIZE);
// Initialize values needed to form NTP request
// (see URL above for details on the packets)
//Serial.println(“2”);
packetBuffer[0] = 0b11100011; // LI, Version, Mode
packetBuffer[1] = 0; // Stratum, or type of clock
packetBuffer[2] = 6; // Polling Interval
packetBuffer[3] = 0xEC; // Peer Clock Precision
// 8 bytes of zero for Root Delay & Root Dispersion
packetBuffer[12] = 49;
packetBuffer[13] = 0x4E;
packetBuffer[14] = 49;
packetBuffer[15] = 52;

//Serial.println(“3”);

// all NTP fields have been given values, now
// you can send a packet requesting a timestamp:
Udp.beginPacket(address, 123); //NTP requests are to port 123
//Serial.println(“4”);
Udp.write(packetBuffer, NTP_PACKET_SIZE);
//Serial.println(“5”);
Udp.endPacket();
//Serial.println(“6”);
}

void printWifiStatus() {
// print the SSID of the network you’re attached to:
Serial.print("SSID: ");
Serial.println(WiFi.SSID());

// print your WiFi shield’s IP address:
IPAddress ip = WiFi.localIP();
Serial.print("IP Address: ");
Serial.println(ip);

// print the received signal strength:
long rssi = WiFi.RSSI();
Serial.print(“signal strength (RSSI):”);
Serial.print(rssi);
Serial.println(" dBm");
}

I noticed this behavior too. I think the esp8266 doesn't like network requests while initializing.

thanks Juraj - good to know I'm not alone - anyone want 3 x Arduino Wi-Fi boards, seriously they are no good to me, if they cannot at least initialise correctly. Maybe I should get a refund !!.
Maybe anyone from the Arduino camp would like to respond?
Anyone know of a decent alternative? I need I\O , wi-fi, and PWM in a very similar form factor or smaller?

Alan

I think it is an esp8266 flaw. I think there isn't a better alternative. Similar combined boards are not better.
For me the Uno WiFi does a good job. WiFi Link has many small bugs, but I found out there isn't a better alternative for Arduino and esp8266. WiFiEsp library (with AT firmware in esp) is worse.

you wait only 1 sec after WiFi.begin

Alan, try building the WiFi Link firmware with esp8266 core 2.4 RC2.