DuetWifi not serving Web pages
-
Hello,
I am trying to commission my kossel - migrating from a Duet 0.8.5 to a DuetWifi and I am having issues to make things work: I can connect to the wifi and receive an IP.When connecting to the IP however, the browser connects, and then waits… and waits... no page load is occurring.
Pinging the IP address shows some strange behavior: ping times vary from 50% replies within 2-4ms and others being between 100-800ms reply, with sometimes a timeout.
Any ideas what could make this happen? I have flashed already the latest firmware (DuetWiFiFirmware-1.15e.bin, DuetWiFiServer-1.02.bin and DuetWebControl-1.12.bin). Connecting through pronterface seems to work just fine.
-
How good is the WiFi signal where the Duet is? If you send M552 S0 from Pronterface turn off WiFi and then M552 S1 to turn it back on, what signal strength does it report when it reconnects?
-
thanks for the quick reply. The router is in the next room: it reports -59db
-
Checking further, I still don't see any pattern or success:
- Laptops indicate full WIFI strength (full bars in Windows) when sitting on the printer bed
- I changed the network SSID (believing that maybe special characters could confuse the Duet - no success
- Also moved the printer to a different room - right next to the router - with no success.
I still see erratic response times, including time outs when pinging. Also when entering the address in the browser, it doesn't time out or indicates "not reachable" but just "waiting for…" endlessly.
Do you see anything else I can try to isolate the issue?
The Board itself works fine (when used through USB, or PanelDue) to move the printer (homing, probing), could the wifi chip have an issue (or the firmware on it - despite flashing the firmware anew)?
-
My gut feeling is that -59db is a rather weak signal, especially if there are a lot of WiFi networks in the area. What is the signal strength with the Duet in the same room as the router? Bear in mind that cordless telephones and microwave ovens use the same 2.4GHz spectrum.
Can you provide a Wireshark trace of the communication with the printer when the problems occur? You could also try pressing control-shift-J to see if any errors are reported in the browser debug console.
-
Continuing the search, and getting quite frustrating…
Have moved the printer right next to the original access point: no change
Did a try with a new access point: no changeThis is what I get from Pronterface:
WiFi server starting up
DuetWiFiServer version 1.02
Flash size 4194304, free RAM 31504 bytes, WiFi Vcc 3.28V, host name: duetwifi, reset reason: Turned on by main processor
WiFi server connected to access point ing0001_2.4G, IP=192.168.0.11, signal strength=-58dBmThis is what wireshark is showing:
https://drive.google.com/open?id=0B__AzxizPXtAU0E1bnl6b3ZuTjgCan provide the full wireshark dump if that helps, but as you can see the browser finds the duetwifi, and it replies once with a 0 length packet to the get request.
These are the only traces I get when requesting 192.168.0.11 (DuetWifi)
Also to note that the original page (when you need to select the wifi AP and password) takes quite long (10sec) to load consistently.
As browser I am using two different laptops (Windows with IE or Chrome) and one android tablet - with identical results.Especially worried about the signal strength: I've not seen it move below -57dBm, even when the router is literally touching the antenna!
Not sure also if it is relevant, but the Diag LED is constantly red… is that to say anything (as I read that it was not functional in pre-series boards)?
-
I had to put my Duet WiFi on a separate wifi network from all my other devices to make it work reasonably reliably.
-
Continuing the search, and getting quite frustrating…
Have moved the printer right next to the original access point: no change
Did a try with a new access point: no changeThis is what I get from Pronterface:
WiFi server starting up
DuetWiFiServer version 1.02
Flash size 4194304, free RAM 31504 bytes, WiFi Vcc 3.28V, host name: duetwifi, reset reason: Turned on by main processor
WiFi server connected to access point ing0001_2.4G, IP=192.168.0.11, signal strength=-58dBmThis is what wireshark is showing:
https://drive.google.com/open?id=0B__AzxizPXtAU0E1bnl6b3ZuTjgCan provide the full wireshark dump if that helps, but as you can see the browser finds the duetwifi, and it replies once with a 0 length packet to the get request.
These are the only traces I get when requesting 192.168.0.11 (DuetWifi)
Also to note that the original page (when you need to select the wifi AP and password) takes quite long (10sec) to load consistently.
As browser I am using two different laptops (Windows with IE or Chrome) and one android tablet - with identical results.Especially worried about the signal strength: I've not seen it move below -57dBm, even when the router is literally touching the antenna!
Not sure also if it is relevant, but the Diag LED is constantly red… is that to say anything (as I read that it was not functional in pre-series boards)?
That -58dBm doesn't look right at all. I suspect a faulty WiFi module. Time to replace your board I think - please contact your supplier.
It's normal for the diag LED to be illuminated if you have a type 1 Z probe configured in your M558 command. The diag LED shares a port pin with the Z probe command/modulation signal.
-
Hi David
Seams I have same problem. I was able to do initial configuration and even upload new FW. But after 1.5 months I cannot connect to the board any more.
This is what I get when WiFi starts:
< 21:15:21: DuetWiFiServer version 1.03 (ch fork)
< 21:15:21: Flash size 4194304, free RAM 32840 bytes, WiFi Vcc 3.07V, host name: kossel, reset reason: Turned on by main processor
< 21:15:21: WiFi server connected to access point UPC0051808, IP=192.168.200.40, signal strength=-55dBmMy router is 5m away from the board and I can see that IP was assigned. However, when pinging the IP of the board all packages are dropped.
I order board from Duet3d.com webpage.
Best regards, Marjan
-
Here is another thread regarding a similar issue, unfortunately unsolved:
https://www.duet3d.com/forum/thread.php?id=124&p=3But pinging should usually work nevertheless. This is quite strange.
-
Thank you. Will take a look..