No connection to Duet-Wifi
-
Hey,
Maybe there is already a thread concerning my problem, well I didn´t find it. In feb. 2017 I ordered a Kossel-XL from a distributor from the Netherlands with a Duet Wifi board (343/500).
Well, first the board did its job very well although the board just was configured for a Kossel-Mini. First I changed this configuration which worked well more or less.
Then I found a config.g in the download space on the page of the printer distributor for the KosselXL / Duet combi.
I made an upload of this config via the web interface on the board. Well, what can I say: what a stupid idea. After that nothing works anymore. No web interface, no connection to pronterface, nothing.
OK, I said to myself, it’s time for a firmware update. The usual procedure doesn’t work cause there was no web interface. Fallback procedure #1 and #2 doesn’t work either for some reason. The Windows-PC didn’t see the Duet board. But… option #3 seems to work. With the SAM-BA 2.16 the PC sees the DuetWifi (Yippeeeeee!).
After sending the fresh downloaded DuetWIFIFirmware.bin (1.18.1) and proceeding the other recommended steps I pressed the Reset bottom at the board followed by the typical “pling-pong” sound when a USB-device is disconnected, also the “Diag-LED” turns off.
Connecting the board via pronterface was still not possible.
After spending quite a couple of nights trying to fix the problem by myself now I´m desperate.
How can I fix the problem, what was my mistake? Is it possible to get back the state of delivering at least?
The distributor in the Netherlands is: http://builda3dprinter.eu/ There you also can find the config.g where the trouble began with.
Greetings from Germany
Nik
-
The original problem may have just been that the config.g file didn't contain the M552 S1 command to turn the WiFi module on.
The new problem may be that you have upgraded to firmware 1.18.1 from an earlier version and have not updated the Windows device driver. Check whether the Duet shows up in Device Manager under the Ports (Com and Lpt) section. If it does, update its device driver from the files in https://github.com/dc42/RepRapFirmware/tree/dev/Driver.
-
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
-
Ok, I see. pcap file is here:
https://sys.gbiloba.org/owncloud/index.php/s/wXQK1JBNIyaoRNm
But I'm now in troubles: I tried to totally erase the firmware, using the erase button, but I'm unable to flash it again! I tried to use bossa, a free linux tool (still waiting from Atmel web site for their soft, but I don't get any notification once registered. When things go wrong…). The strange thing is I still have /dev/ttyACM0 port, but nothing related to bossa.
[2634139.039937] usb 5-1: New USB device found, idVendor=03eb, idProduct=6124
[2634139.039941] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[2634139.043067] cdc_acm 5-1:1.0: ttyACM0: USB ACM deviceBut I'm also unable to send gcodes on this port, so I think there is no more firmware in the flash…
-
Ok, I was able to flash again the firmware using Atmel tool. But it didn't fix the com problem.
I tried to enable telnet and ftp. Only ftp works; telnet does not answer neither.
Strange thing: after the telnet connexion, I initiate a new web connexion, and I got:
12:39:43.153 : New conn on socket 0 for local port 23 <<<<<<<
12:39:43.153 : HTTP connection accepted
12:39:43.155 : Found responder
12:39:43.155 : Received 404 bytes
12:39:43.159 : Sending reply, file = yes
12:39:43.162 : HTTP req, command words { GET / HTTP/1.1 }, parameters { }
12:40:04.388 : Client disconnected on socket 0
12:40:04.388 : Can't send anymorePort number seems to be wrong (I think it is only in debug message).
-
Arrgglll!!!! I made a test with a windows machine, running firefox, and it works!!!
WTF? Why firefox nor chromium does not work from my linux machine???!!???
