Webserver won't start
-
Didn´t help...
-
@droftarts During my initial setup everything seemed to work nicely - duet got an IP and dwc was working. Then I unplugged everything - put it into the printer/attached cables and when I powered it up, it didnt work anymore. After that I got rid of the WR802N and connected it directly with my router and also I did downgrade from 3.01RC5 to RRF3.0 and now 2.05.
-
I'm a little curious why mine said "No SD card detected" at boot but yours didn't.
Can you also run M503 and M20 before anything else when starting up just for good measure?
-
@bearer Sure.
Downgrading to 2.04 didnt help neither
-
Now with M503 and M20:
-
Well, that proves there isn't any conflicting config despite the lacking message about missing SD card*. I'm at the end of the line unless you can capture the traffic with wireshark as outlined above. (also, you can skip the M111 command, it doesn't seem to produce any relevent debug info in this scenario)
*) never mind I see now the version information isn't from the boot message, but from M115 - so any messages about missing SD cards were above that; and a moot point in any case now.
-
@Haffwalker I appreciate this is frustrating. Could you please test it with a different ethernet cable. Perhaps the one that connects the Duet to the TL-WR802N, if it's long enough, as this cable has been proven to work with the Duet.
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
I downgraded to 2.01 - I think that was the firmware which was on the board when i bought it - still no change...
-
@droftarts I unconnected everything to get it to my router and I used the cable which already was working, but still nothing changes in the behavior...
-
@bearer About the wireshark traffic...do you have any source of explanation, which steps I have to take like a youtube video or something?
-
@Haffwalker said in Webserver won't start:
@bearer About the wireshark traffic...do you have any source of explanation, which steps I have to take like a youtube video or something?
its mostly down to equipment; a modern switched network won't send the packets to your computer unless they're adressed to your computer ... so to monitor traffic between your Duet and your router you'd need some fancy managed gear.
Although, if you have a basic switch and can be bothered to set up a DHCP server on your computer that would work to diagnose the issue. A relatively simple DHCP server for windows is tfptd32 (or 64 whatever floats your boat).
(you need the switch because you need to configure the computers interface with a static IP and start the DHCP server before connecting the Duet, and a such a direct connection won't work even though you're just connecting the computer and the duet to a basic switch)
-
@Haffwalker Yes, I don't think this is a firmware issue. Thanks for trying the different ethernet lead. I'm just looking at the Duet 2 Ethernet I have here, particularly how easy it is to dislodge the ethernet module. It isn't!
Ian
-
This may sound stupid but have you tried taking it back out of the printer and trying it again on the bench just to see if it could be a short somewhere?
It's a long shot mind but it is all I can think of now.
-
..its not stupid when everything else doesnt work:)
-
@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.18I 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 msI 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.19Not 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.
