Webserver won't start
-
@bearer It isn't to me either but I k now how frustrating these things can be and the simplest thing gets overlooked. It is certainly the approach I would take now
-
Just put everything back together on the bench how it already worked once, but it didn't help...still not working.
-
I got the router which was provided by my provider, but I only use it for the internet connection + the 4 ethernet ports in the back...for wifi I have an Ubiquiti Nano - maybe that thing has some precious logging funcionality...
-
Doubt it, but it would probably be a setting in the vicinity of vlans or mirror settings.
Depending on the router you might be able to capture a DHCP discover request or some ARP traffic without any special setup, but it'd be a bit half hearted.
-
@Haffwalker I set up the Duet Ethernet I've got here. Connected to a TP-Link AV500 TL-WPA4220 powerline adapter (wifi and Ethernet), which connects to a TL-PA4010 at the other end, then into a Virgin Media Super Hub 2ac. From first power on, no SD card, I get:
Connecting... RepRapFirmware for Duet 2 WiFi/Ethernet Version 2.02(RTOS) dated 2018-12-24b1 No SD card present Network disabled. RepRapFirmware for Duet 2 WiFi/Ethernet is up and running. ok B:2000.0 /0.0 Printer is now online. ok B:2000.0 /0.0 >>>M552 SENDING:M552 Network is disabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0 >>>M552 P0.0.0.0 S1 SENDING:M552 P0.0.0.0 S1 ok B:2000.0 /0.0 >>>M552 SENDING:M552 Network is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0 Network running, IP address = 192.168.0.18 >>>M552 SENDING:M552 Network is enabled, configured IP address: 0.0.0.0, actual IP address: 192.168.0.18
I get a solid orange light on the Ethernet socket on the Duet, and flashing green light.
I can also ping it:
Ians-MacBook-Pro:~ Ian$ ping 192.168.0.18 PING 192.168.0.18 (192.168.0.18): 56 data bytes 64 bytes from 192.168.0.18: icmp_seq=0 ttl=128 time=22.335 ms 64 bytes from 192.168.0.18: icmp_seq=1 ttl=128 time=2.999 ms 64 bytes from 192.168.0.18: icmp_seq=2 ttl=128 time=3.411 ms 64 bytes from 192.168.0.18: icmp_seq=3 ttl=128 time=2.110 ms 64 bytes from 192.168.0.18: icmp_seq=4 ttl=128 time=1.592 ms 64 bytes from 192.168.0.18: icmp_seq=5 ttl=128 time=1.542 ms 64 bytes from 192.168.0.18: icmp_seq=6 ttl=128 time=1.395 ms
I put the original SD card back in and reset the board. I could connect to it via USB, but not to the IP address it was using, but then realised that the SD card has a static IP address set, of 192.168.1.14. I turned off networking, then turned it back on with a DHCP set IP address, and was then able to connect to DWC. Log:
Connecting... Network running, IP address = 192.168.1.14 Error: Temperature reading fault on heater 1: sensor open circuit Printer is now online. >>>M552 SENDING:M552 Network is enabled, configured IP address: 192.168.1.14, actual IP address: 192.168.1.14 >>>M20 P"/www" SENDING:M20 P"/www" Begin file list favicon.ico.gz html404.htm language.xml.gz reprap.htm.gz css fonts js dwc.json End file list >>>M552 S0 SENDING:M552 S0 Network stopped >>>M552 P0.0.0.0 S1 SENDING:M552 P0.0.0.0 S1 Network running, IP address = 192.168.0.19
Not sure if any of this is useful for diagnosing your problem, though!
Ian
-
Wireshark gives me this:
so it should recieve 192.168.137.22 as ip adress, but i cant ping it nor is it in listed in arp -a.
-
is this with just the computer and the duet on a switch? can you save and upload the .pcap file somewhere? gofile.io or similar?
(at a glance it looks like the duet isn't sending its mac address as part of the dhcp discovery)
-
This is what I get when I connect the Ethernet cable directly to my pc and the duet.
I can't find the Duet's Mac Address anywhere in Wireshark...
I also got a DSO0138 if that helps troubleshooting....I think, that the ethernet module is broken.
-
as laid out earlier, a direct connection isn't the best option as windows takes a while from the link status goes up until its ready with a static ip to start logging and/or serving dhcp.
anyways, still like to have a peak at the whole .pcap for any arp or mdns traffic etc, as well as looking as the ethernet source for the packets etc. but for now it would appear the ethernet module is the culprit, given the firmware isn't corrupted - which is unlikely given the downgrades
-
@bearer I try to upload to gofile.io, but it doesnt work...I zipped my pcap file into an rar archive and added .txt to the end, to be able to upload it directly...so simply remove .txt and you should have an rar archive.duetethernet.rar.txt
I hope this is allowed (and works).
-
@Haffwalker I’m still puzzled by why you got an IP address initially. But does increasingly look like a failure of the Ethernet module. How long ago, and where did you buy it? Warranty is 6 months.
Ian
-
Right, I'm guessing you haven't put a static IP address on your computer and the DHCP requests are from the local machine.
The only thing the log actually tells me is that there isn't a single frame that isn't from your computer, i.e no traffic from the Duet. Two possible explanations, either it didn't get a DHCP response before window was ready and stopped trying, or it never started trying. This is why the switch is needed so windows and wireshark is up to speed before the Duet establishes a link status.
-
I got the Duet Ethernet back in January 2019 for a different project (I did optimize a Deltatower RTA420, because the owner wasn't happy with it's performance, which he now is), but went for the Duet Wifi instead, so the ethernet was sitting under my workbench for over a year now...so no warranty anymore...Well then i probably blow this one up with a bunch of fireworks and get a Duet Wifi instead.
Thanks everyone for your time and help!!!PS: I currently run three Duet 2 Wifi boards...but wanted to use the Ethernet and get a Maestro as well, to have the full set ^^
PPS: Will also get Duet 3 as soon as I start building a CNC machine...
-
@Haffwalker You can get just the Ethernet module, if you want. https://www.duet3d.com/DuetEthernet_Module
Ian
-
@droftarts I bought it from makerdise
-
Just found an old switch...will try tomorrow! Not sure about how to set everything including tftpd up, but will find out eventually.
-
its been a while but from memory
- connect computer to switch
- set a static ip for your wired network https://www.google.com/search?q=window+static+ip
- ip 10.10.10.1
- netmask 255.255.255.0
- configure tfpd64 by clicking the setup button (bottom center of the window)
- open the global tab and make sure dhcp is ticked
- open the dhcp tab and fill in
- ip pool start address 10.10.10.10
- size of pool 10
- mask 255.255.255.0
- bind dhcp to this address 10.10.10.1
- close settings and restart tftpd64.
- start wireshark and begin capture
- plug in network cable for the duet
- power up the duet.
- enable the network on the duet with either config file on sd card or by sending M552 S1
- pray
you can use whatever private address you like, using 10 is faster to type imho, but techincally its a little dirty to use that netmask with that class of network but hopefully we don't have to go off topic on that any more than i just did...
-
I did all of the steps provided, now the green led is blinking less frequently, but still doesn't work.
-
and presumably no packets shown if you enter bootp as a display filter, some arp traffic likely, but doubt its relevant
-
neither bootp nor dhcp show up anything.