Macro for setting up your network

Phaedrux

Thanks for the macro. I edited your post to put it in a code block so that it displays correctly.

Macgyver

@Phaedrux thank you for the assist,

I am working on a couple of things so you may see more coming in the future if they have a cool factor I am aiming for

stuartofmt

I'm curious about the assertion that dual band networks will not work. Is this precautionary? The reason I ask is that, from memory (I'm now using SBC), I've routinely used Duet2 on dual band SSID. In theory (and in practice with many other devices) the WIFI will connect using whatever frequency is available to the client (typically with 5GHz preferred if the client supports both). In the case of a Duet2 this would be 2.4GHz.
Of course, my memory could be very fallible

Phaedrux

@stuartofmt I think what seems to happen sometimes with dual band networks is that the router erroneously steers the Duet to the 5ghz network even though the Duet can't use it. I'm not sure if that's ever been definitively confirmed though.

stuartofmt

@Phaedrux said in Macro for setting up your network:

@stuartofmt I think what seems to happen sometimes with dual band networks is that the router erroneously steers the Duet to the 5ghz network even though the Duet can't use it. I'm not sure if that's ever been definitively confirmed though.

I suspect that some different network issue(s) may have been explained away as such. Unless the client was sitting "right on top of the router antenna" - it should not be possible for a 2.4GHz client to even "see" a 5Ghz signal. Still ... stranger things have happened.

I'm just a bit leery of pointing people towards what might be an unnecessary complication (i.e. splitting SSIDs into separate frequency bands).

OwenD

@Macgyver
It's a pity M587.2 doesn't have an option to return an array with just SSID names.
Then you could cut out incorrect entries.

Unfortunately it only gives a text output full of unnecessary information (for a macro) or a json return

oliof

@stuartofmt it's been a problem 2008-2012ish in some networks I've been on, but I can say its never been a problem for a Duet2Wifi, Duet3mini, or any of the ESP8266/ESP32 modules for the STM port.

mrehorstdmd

Is there any possibility that the browser being used to access the web server has some effect on reliability of the connection?

I have had a lot of trouble keeping a Duet2 WiFi board connected to my mixed 2.4/5GHz network for the last few years. About a year ago I switched to a mesh network with no change in the connection behavior. The mesh router has a dedicated 2.4 GHz IOT network that I use for the Duet and things like light bulbs, appliances, etc. The Chrome browser in my laptop would connect and I could access the control panel for between 30 seconds and maybe 2 minutes at a time, then the connection would fail. It got a bit better when I shut off the VPN (even though I had local network sharing enabled) on the laptop, but still not what anyone would call reliable. I gave up on ever getting it to work reliably.

I recently tried the Mullvad browser that is based on Firefox (I think) and Duet board miraculously stays connected for up to an hour, maybe more, at a time, so it seems the browser used plays a part in the reliability of the connection.

Or am I completely wrong?

jay_s_uk

@mrehorstdmd I think this is to do we the number of AJAX tries etc

dc42

@mrehorstdmd if you have a PanelDue In your machine, is the network connection more reliable if you leave it on the Setup page?

mrehorstdmd

@dc42 There's no Panel Due. This particular controller is in the sand table.

I have gone through all the posts on wifi problems and played with ajax retries, it didn't seem to do much good. I also shut off the VPN when I am connecting to the table. The Mullvad browser just seems to work about 10x more reliably than Chrome.

Phaedrux

@mrehorstdmd

When you're unable to connect, are you still able to ping the Duet IP?

Does the chrome dev console show any errors?

mrehorstdmd

@Phaedrux I don't have access to the table right now- it's over at my brother's distillery tasting room and I don't know when it will be back.