No Connection to Web-Interface

Hello again,

after three weeks not having printed, I wanted to do it today.

Switched On the PSU, and tried to connect. Nothing happened. I can ping at the setted IP-Adress, and get a respond. Chrome doesn't load the interface at all, Firefox loads the interface (but it's all ripped apart) but can not connect. After having tried to connect via the web interface, the ping would not work anymore. It is just possible again after turning the PSU off an on.

Help me please :-(

Do you have the Duet configured to use a fixed IP address? If so, perhaps your router has assigned that address to another device during that 3 weeks.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

I connected it direct to the computer. The computer still has the same ip adress as before, and the printer too.

Is the computer also connected to a network using WiFi? If so, did you tell the operating system to bridge the network connections?

It could also be something simple like a dodgy cable.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

I already changed the cable.

After I bridged my WiFi and the LAN connection (to the printer), I can not even ping the printer anymore. So this would not be the issue, I think... :-(

Quote
kizashi
I already changed the cable.

After I bridged my WiFi and the LAN connection (to the printer), I can not even ping the printer anymore. So this would not be the issue, I think... :-(

So is the IP address of the Ormerod on the same subnet as your PC and router? For example, if your router has address 192.168.1.254 then the Ormerod needs to be 192.168.1.something. Or you can set it to 0.0.0.0 then the Ormerod will as the router for an IP address, and you can access it by typeing ormerod/ (or whatever you have your machine name set to in config.g) into the address bar.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Please provide your config.g. Please also start a command prompt (maybe administrator privileges are needed) and give us the output of ipconfig (Windows) or ifconfig (Linux and I think Apple, too).

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

Printer IP: 192.168.1.14
Computer IP: 192.168.1.100

IPCONFIG:
________________________________________________________
Ethernet-Adapter Ethernet:

Verbindungsspezifisches DNS-Suffix:
IPv4-Adresse . . . . . . . . . . : 192.168.1.100
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . :

Drahtlos-LAN-Adapter WiFi:

Verbindungsspezifisches DNS-Suffix: fritz.box
Verbindungslokale IPv6-Adresse . : fe80::1807:9926:68d5:1c71%10
IPv4-Adresse . . . . . . . . . . : 192.168.178.20
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.178.1
________________________________________________________


my config.g:
________________________________________________________
M111 S0 ; Debug off
M550 PMy RepRapPro Ormerod 1 ; Machine name (can be anything you like). With DHCP enabled connect to (example) [reprapproormerod1] (machine name with no spaces).
M551 Preprap ; Machine password (currently not used)
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
;M552 P0.0.0.0 ; Un-comment for DHCP
M552 P192.168.1.14 ; IP address, comment for DHCP
M553 P255.255.255.0 ; Netmask
M554 P192.168.1.1 ; Gateway, comment for DHCP
M555 P2 ; Set output to look like Marlin
G21 ; Work in millimetres
G90 ; Send absolute corrdinates...
M83 ; ...but relative extruder moves
M906 X800 Y1000 Z800 E800 ; Set motor currents (mA)
;M305 P0 R4700 ; Set the heated bed thermistor series resistor to 4K7
;M305 P1 R4700 ; Set the hot end thermistor series resistor to 4K7
M569 P0 S1 ; Set X axis direction
M92 E433 ; Set extruder steps per mm
M558 P1 ; Use an unmodulated Z probe (change to P2 if you update to the modulated probe)
G31 Z2.8 P662 ; Set the probe height and threshold (deliberately too high to avoid bed crashes on initial setup)
M556 S78 X0 Y0 Z0 ; Put your axis compensation here
M201 X800 Y800 Z15 E1000 ; Accelerations (mm/s^2)
M203 X15000 Y15000 Z100 E3600 ; Maximum speeds (mm/min)
M566 X200 Y200 Z30 E20 ; Minimum speeds mm/minute
M563 P1 D0 H1 ; Define tool 1
G10 P1 S-273 R-273 ; Set tool 1 operating and standby temperatures
____________________________________________

thanks!

So your Wifi uses subnet 192.168.178.xxx. That explains why you couldn't ping the Duet when you bridged the network connections. You would need to set the Duet IP address to e.g. 192.168.178.80 to use bridging, then you would be able to access the Duet from anywhere on the network (e.g. your smartphone).

However, your existing config looks OK to me for access from the connected PC only, assuming you are typing 192.168.1.14 into the address bar of your browser.

Edited 2 time(s). Last edit at 11/20/2015 01:32PM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Yes, I am typing 192.168.1.14 and only want to access the printer via ethernet cable at my desk.
Can not figure out the problem :-(

Which firmware and web interface versions are you trying to use?

Firmware 1.09 and 1.06 web interface.

It all worked a few weeks ago, I did not change anything..

On Windows I guess? Maybe a Windows update has messed up your TCP/IP stack, so try resetting it once: [support.microsoft.com]

If that doesn't help, could you make a Wireshark dump so I get an idea what's going on?

Yes Windows. I didn't have success with the reset.

So here we go: [workupload.com]

I'm sorry, but there is no communication between your PC and the Duet in it. Can you make another one while trying to load the web interface?

I saw this same behavior on mine. It was related to my Google Chrome browser. I had to clear the cache of any history that went to the printer. For me this was only a day or so back. I did not clear my saved passwords or other stuff just the browser history. Once I did this it came up in Chrome as it would normally. I chalked this up to my computer but now that I have seen it a second time maybe there is something in the web interface that we need to check? If Kizashi can clear his browser and let us know if this works we might have something more to go on or rule out?

Thanks to all your answers!
Cleaning chromes history did not work either.
I think that there is a hardware problem. Sometimes pinging the printer works, sometimes not.

I changed the laptops IP adress to *.55, just to test it. Did not change anything.

Here is another log, where you can see the ping & answer, and trying to connect to the web interface.

[workupload.com]

I think I forgot to mention that I upgraded from Win8.1 to Win10... Maybe this is the issue?! Unfortunately I don't have another computer to test the connection.

W10 works fine for me, but I know it kills Antivirus software for example. Maybe your Firewall settings are wrong?

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

Hmm, you have a couple of TCP retransmissions at the end of that dump, but they are sent from the Duet to your PC while your PC doesn't reply. My guess is that this is somehow related to your PC, maybe your firewall/anti-virus or faulty network drivers. It's fairly possible that this is related to your Windows upgrade too.

You can also try out my latest firmware (and web interface) from here and check if that resolves your problem.

I figured it out..

My Avira AntiVirus Browser Protection blocked the connection to the ormerod. After setting an exception for the ip-adress, it worked again.

Thank you so much for your support!!