Hi Gordon
I try to use the new UDP/Broadcast feature. First to receive UDP packages/messages.

Here is the code on the serverside, nodejs on linux. It sends a small JSON string every 10 seconds:
Please replace "BROADCAST_ADDR" with yours.

var PORT = 7077;
var BROADCAST_ADDR = "192.168.68.255";
var dgram = require('dgram');
var server = dgram.createSocket("udp4");

server.bind(function() {
    server.setBroadcast(true);
    setInterval(broadcastNew, 10000);
});

function broadcastNew() {
    var msg=JSON.stringify({ type: "SYS", name : "_M", cfg: 187 });
    var message = new Buffer(msg);
    server.send(message, 0, message.length, PORT, BROADCAST_ADDR, function() {
        console.log("Sent '" + message + "'");
    });
}

Please start it with node:

node test.js

And now, this is the code running on EspruinoWiFi. Please replace your WLAN SSID and PW:

/*
ESPRUINO WIFI
*/
var WIFI_NAME = "Paradise";
var WIFI_OPTIONS = { password : "XYZ" };
var PORT = 7077;
var wifi = require("EspruinoWiFi");
var dgram = require('dgram');
var client = dgram.createSocket("udp4");

wifi.connect(WIFI_NAME, WIFI_OPTIONS, function (err) {
    if (err) {
        console.log("Connection error: " + err);
    }
    wifi.getIP(function (f, ip) {
        console.log("Connected: " + ip.ip);

        // UDP Broadcast

        client.on('listening', function () {
            var address = client.address();
            console.log('UDP Client listening on ' + address.address + ":" + address.port);
            client.setBroadcast(true);
        });

        client.on('message', function (message, rinfo) {
            console.log('UDP Msg: ' + rinfo.address + ':' + rinfo.port +' - ' + message);
            try {
                var u = JSON.parse(message);
                console.log('OK:'+u.cfg);
            }
            catch(err) {
                console.log('ERR: UPD packet not JSON, ignore');
            }
        });
        client.bind(PORT);
    });
});

Please type "save" on the EspruinoWiFi.

Espruino receives packets. They are often corrupt, not complete or even from a wrong IP Address ??
It's a question of time, then the espruino is crashing.

____                 _
|  __|___ ___ ___ _ _|_|___ ___
|  __|_ -| . |  _| | | |   | . |
|____|___|  _|_| |___|_|_|_|___|
         |_| espruino.com
 1v96 (c) 2017 G.Williams
>
=undefined
>save();
=undefined
Compacting Flash...
Calculating Size...
Writing..
Compressed 114368 bytes to 27188
Connected: 192.168.68.158
UDP Msg: 192.168.68.13:39242 - {"type":"SYS","name":"_M","cfg":187}
OK:187
UDP Msg: 77.34.44.34:26211 - :187}
ERR: UPD packet not JSON, ignore
UDP Msg: 192.168.68.13:39242 - {"type":"SYS","name":"_M","cfg":187}
OK:187
UDP Msg: 192.168.68.13:39242 - {"type":"SYS","name":"_M","cfg":18
ERR: UPD packet not JSON, ignore
>

Thanks for your help.

Sacha

Ups. Hmmm. Have several EspruinoWifi's will check it again with a differnt one.
Will also reflash the 1v95.

Hi Gordon
Thanks for your answer. I tested it with two different types of relayboards:

https://www.aliexpress.com/item/Relay-module-for-arduino-uno/32400577838.html?spm=a2g0s.9042311.0.0.oem8mW

https://www.aliexpress.com/item/Free-shipping-10Pcs-5V-30A-1-Channel-Relay-Module-Optocoupler-H-L-Level-Triger/32691375337.html?traffic_analysisId=recommend_3035_null_null_null&scm=1007.13338.80878.000000000000000&pvid=6d6fabc7-6c62-4899-91c8-ea18cd519179&tpp=1

Sacha

Hi Gordon

• Espruino Wifi is powered by VUSB and GND Pin, 5v (Not USB)
  
• Wifi is connected
  
• Relay is connected to the same powersource, 5v, trigger on A5 (Nothing connected to the relay on the load side)
  
• A6 is monitored by setWatch, nothing connected to A6
  
  

SetWatch:

pinMode(A6, "input_pulldown");
setWatch(function(e) { do something }

Relay:

When i switch the relay width "digitalWrite(A5,1)" on, relay will be triggered as expected.

Sometimes the A6 setWatch is triggered in the same moment as the relay is triggered. Not allways, it is reproduceable out of 25 on/off switches of the relay.

I was not able to reproduce it when i have the setWatch on A1.
I was also not able to reproduce it then i powered the EspruinoWifi by USB.

Is this becuase A5 and A6 are neighbors ?

Thanks
Sacha

You are always helpfull Gordon. This is the reason why i like to be a patreon.

Sacha

Dear Gordon

Besides the udp send/receive functions i have another wish for 1.95 ;-).
Could you please implement the ping function in the wifi library as well.

Is there a way to get the default gateway address received by the dhcp protocoll ?

Thanks

Sacha

Thanks Gorden for the answer.
It could be a button with bounces.

Sacha

Hi Gordon

I noticed that i get from time to time the following error in the console on the EspruinoWifi:

"New interpreter error: FIFO_FULL"

It happens, when i send socket data (small junk of JSON data) after a setWatch of a button is triggered.

It is very difficult to reproduce.

• process.memory shows more than 3500 free mem after the error
  
• I think it never happens when i send data triggered by setTimeout or setInterval
  
• It happens very rarely
  
• It seams to be that it happens only after powerup, triggered by one of the first setWatches but well after the board is wifi connected.
  
• After the error, everything is working as expected with additional setWatches and socket transfers.
  
  

I use the following pins with setWatch:

A1, A5, A6, A7, B9, B8, B4

I think it's not dedicated to a special pin i used.

Greetings

Sacha

Thanks Gordon
I will wait until 1.95 in the hope it will include udp support.
Thanks
Sacha

Hi There

Is it possible to broadcast with the EspruinoWifi ?

A simple example sending / receiving would be nice.

Sacha

Jup 1v94

Hi Gordon

I would like to share my first experiences with the EspruinoWifi.

For testing i have two Espruinos, both as a socket server and client. In the last 24h i connected every 7 second to the other Espruino and catched some data.

More than 12'000 times without any error or glitches. Most important, memory usage is stable too.

Very nice.

Sacha

Many thanks Gorden.
I was confused regarding the Wifi documentation here:

https://www.espruino.com/Reference#l_Wifi_connected

Hi There
I just received a few espruino.wifi boards. Nice work!

I try to detect the connected or disconnected event without success. I did not get any of this two events. No connected event on connect and no disconnect event when i switch off my wifi AP.

Code:

var wifi = require("EspruinoWiFi");
var WIFI_NAME = "XYZ";
var WIFI_OPTIONS = { password : "PW" };

console.log('Starting...');

wifi.on('connected', function(data) {
    console.log("> connected "+data);
});
wifi.on('disconnected', function(data) {
    console.log("> disconnected "+data);
});

wifi.connect(WIFI_NAME, WIFI_OPTIONS, function(err) {
    if (err) {
        console.log("Connection error: "+err);

        return;
    }
    wifi.getIP(function(f,ip) {
        console.log("Connected: ", ip);
    });
});

The console output is:

_____                 _
|   __|___ ___ ___ _ _|_|___ ___
|   __|_ -| . |  _| | | |   | . |
|_____|___|  _|_| |___|_|_|_|___|
          |_| http://espruino.com
 1v94 Copyright 2016 G.Williams
>Starting...
=undefined
Connected:  {
  "ip": "192.168.68.175",
  "mac": "5c:cf:7f:c0:14:c8"
 }
>

Thanks. As far a i know the xbee modules only supprts HW flow control.
@Gordon: What about HW flowcontrol ?

Dear Espruinos

I use several picos with an xbee modul to communicate to each other.
I only connected power and rx/tx. So there is no flow control used.

Maybe as a result, when i communicate faster than 2400bps i have data losses.

I would like to test it with flowcontrol. Do the pico support HW flowcontrol ?

Thanks for your advise

Sacha

That's cool. Include this in your homeautomation. Google will be listening what you are saying and is able to control your home....

@allObjects
Thanks, i know about onInit. I didn't know that the watchdog function has to be called/restarted after a reset while other internal functions like Intervals/Timers for example not.

Dear Gordon
I've done some tests with the new watchdog function. My testcode is the following (right side):

doreset=false;
setInterval(function() { if(doreset===false) { console.log('kick'); E.kickWatchdog(); } },20000);
E.enableWatchdog(25,false);
save();

You will see in the console every 20 seconds 'kick'. E.kickWatchdog is called.
Then please set the var doreset to true:

doreset=true;

After a few seconds the pico will reset. Then please reconnect to the console.
You will see the output of 'kick' again.

Please give the variable doreset again the value of true.

doreset=true;

On the console 'kick' messages are gone. E.kickWatchdog is not called anymore.

But the pico does not reset after more that 25 seconds. Please see the attached screenshot.

Do I understand something wrong ? It only resets once ?

Thanks

Sacha

Gordon. Please include this command in the reference page of setInterval/Timeout.
"print(global["\xff"].timers);". This will help others debugging those functions.
Thanks
Sacha

Many thanks for your help Gordon. I think i found the problem. It was self made. In a special situation i called clearTimeout() with an undefined var. This cleared all intervals.

Sacha

Worked this is the output while setInterval is not anymore called:

test();
LSEON 0
LSERDY 0
LSION 1
LSIRDY 2
LSI

I have the problems also when not using setTime..... E.kickWatchdog is realy not ideal.
Is there a way to debug, display registered or pending setInterval's / setTimeout's ?

Gordon
Tried to run your code by copy it into the left side. Got:

>test();
Uncaught ReferenceError: "R" is not defined
 at line 1 col 40
console.log("LSEON",peek32(RCC.a.BDCR)&R­CC.f.BDCR.LSEON);
                                       ^
in function "test" called from line 1 col 6
test();

I'm feeling like a ghost hunter! After an hour or so, my setInterval is not called anymore. Also when I don't use setTime. The theory about setTime() could be wrong again.