No connection to Duet-Wifi
-
Oh wow, this was it! Thank you so much. After updating the driver everything works well.
-
Hi!
I just received my DuetWifi (still waiting for the Duex5, as the supplier sent me a PanelDue instead :o/ ). I set up the wifi, and it connects correctly, but then, I'm unable to access the web interface (no answer).
I'm using linux, and nmap shows that port 80 is open. What can be the problem? I'm using the pre-installed firmware, which is 1.18.1 (according to infos sent over usb).
I noticed that the wifi re-connects every minute or two; is that normal? Do I need to power up the board through Vin, or is USB 5V enough for proper wifi com.?
Thanks,
-
Which browser are you using? Try Chrome or FireFox if you are using something else.
Otherwise, please run M552 from USB, check that it reports the Duet is connected to your access point, and see what version of DuetWiFiServer it reports (it should be 1.03ch). If that passes, try re-installing the web interface into the wifi module by sending M997 S2.
-
I'm using chromium. I tried Firefox, without success.
The DuetWifi is connected, as I can ping it. Server version is 1.03 ch. I tried to re-install firmware in esp module, but it didn't improve things.
No answer from web nor telnet.
-
BTW, when it restarts wifi, it says Vcc 3.01V or Vcc 3.03V…
-
Strange! Can you run Wireshark on your PC and get a trace of a connection attempt?
-
Ok, I'll do that.
BTW, I made a quick test, yesterday, with a power supply connected to Vin: no success (I still need to check if the wifi re-connect every minute, like when powerd up through usb).
Another question: I saw in the wifi status that it uses ip 192.168.1.14 (not sure of the ip, but not 1.1), but really connected to 192.168.0.169 (address given by my dhcp server). What does it mean?
-
I think you mean that the IP address was set to 192.168.1.14 in the M552 command in config.g. That parameter is ignored on the Duet WiFi. With 1.18 and earlier firmware it always uses DHCP. With 1.19 series beta firmware, you have the option of setting a static IP address.
-
Ok!
-
Which format do you want? Where do I send it to you?
-
I just noticed, when the wifi restarts, it says: 'reset reason: Exception'…
-
@fma:
I just noticed, when the wifi restarts, it says: 'reset reason: Exception'…
That explains it! In that case I suggest you try the 1.19beta series firmware. See https://duet3d.com/wiki/DuetWiFiFirmware_1.19beta.
-
I get en error when I try to execute the SetNetwork macro:
M98 PSetNetwork
<<< 20:37:39.937 : Can't open 0:/sys/0 to read, error code 4What can be the problem?
-
Ok, I gave the gcode manually.
This time, when I try to connect on the web interface, I see:
20:46:54.363 : New conn on socket 0 for local port 0
20:46:54.363 : HTTP connection accepted
20:46:54.366 : Found responder
20:46:54.366 : Received 383 bytes
20:46:54.370 : Sending reply, file = yes
20:46:54.372 : HTTP req, command words { GET / HTTP/1.1 }, parameters { }
20:46:54.372 : New conn on socket 1 for local port 0
20:46:54.372 : HTTP connection accepted
20:46:54.374 : Found responderBut still no answer :o(((
-
@fma:
I get en error when I try to execute the SetNetwork macro:
M98 PSetNetwork
<<< 20:37:39.937 : Can't open 0:/sys/0 to read, error code 4What can be the problem?
I don't know, the M98 command works fine for me, whether I provide name of a file that is present, or the name of a file that isn't (I get an error message which includes the name of the file I asked for). But if you created SetNetwork in the /macros folder, you need to send M98 P/macros/SetNetwork to run it.
Or perhaps you have something strange in tur SetNetwork macro file?
-
@fma:
Ok, I gave the gcode manually.
This time, when I try to connect on the web interface, I see:
20:46:54.363 : New conn on socket 0 for local port 0
20:46:54.363 : HTTP connection accepted
20:46:54.366 : Found responder
20:46:54.366 : Received 383 bytes
20:46:54.370 : Sending reply, file = yes
20:46:54.372 : HTTP req, command words { GET / HTTP/1.1 }, parameters { }
20:46:54.372 : New conn on socket 1 for local port 0
20:46:54.372 : HTTP connection accepted
20:46:54.374 : Found responderBut still no answer :o(((
That debug info looks correct except that it should say port 80 not port 0. If it is sending the reply to port 0, that would explain the problem. But if the request really was addressed to port 0, the HTTP responder should not have accepted it, unless you told it that you were using port 0 in a M586 command.
Can you run Wireshark on the PC and get a trace of the connection attempt? Filter the Wireshark display by the IP address of the Duet.
-
I don't know, the M98 command works fine for me, whether I provide name of a file that is present, or the name of a file that isn't (I get an error message which includes the name of the file I asked for). But if you created SetNetwork in the /macros folder, you need to send M98 P/macros/SetNetwork to run it.
Or perhaps you have something strange in tur SetNetwork macro file?
The content is correct, I triple checked. And it gives the same result with the complete path.
-
Can you run Wireshark on the PC and get a trace of the connection attempt? Filter the Wireshark display by the IP address of the Duet.
I did; just tell me the format you want, and where to send the trace. I can send you a pcap file, or a pure ascii trace…
-
I made a new test, and this time I get:
09:15:28.941 : New conn on socket 0 for local port 80
09:15:28.943 : HTTP connection accepted
09:15:28.943 : Found responder
09:15:28.943 : Received 404 bytes
09:15:28.947 : Sending reply, file = yes
09:15:28.949 : HTTP req, command words { GET / HTTP/1.1 }, parameters { }but still no answer… Looks like the debug info was messy.
Could it be a hardware problem? I ask because firmware 1.18.1 was crashing... And the fact I can't load a file with M98 (I check the SD card, which is not corrupted).
BTW, if the SD card can't be read, it could also explain why it does not answer... But firmware was correctly loaded from card! I'm puzzled.
-
To check that the SD card can be read, run M503.
You can also use M98 to run other macros, e.g. M98 Phomeall.g
If the Wireshark trace is short, post it here as ascii. Otherwise put the .pcap file on a file sharing site and post a link to it.
We know that the pre-1.19 WiFi module firmware used to crash repeatedly for a very small number of users. The same Duet would work perfectly when attached to one network but crash when connected to a different network. We never tracked this down because we couldn't reproduce it. The version 1.19 WiFi firmware is largely rewritten, uses very little of the ESP8266 Arduino core, and shifts most of the server functionality to the main processor of the Duet where we can track down any issues much more easily.
HTH David