Web Interface straight from computer establishing problem

Hello

I have connected the Duet straight into my laptop's ethernet port.

I have flashed DC42 firmware on my Duet and replaced the SD files accordingly with the included ones. In the config.g file I changed the IP address into the same as my laptop's IP, as well as the netmask (that was already matching by default). I did not touch the Gateway, since there is no visible one in my coputer's network settings. Now when trying to connect the web interface to the Duet there is no connection. I use Firefox, and both the green and orange led are lit in the ethernet connector of the Duet, that is powered with 12V.

What else is there to do, or what have I misunderstood?

Thanks in advance!

Edited 2 time(s). Last edit at 10/19/2015 08:39AM by PropellerHat.

The IP address must not be the same as the laptop IP address. Change the last digit of the printer's IP address - the easiest is to either increase or decrease it by one, but ensure that the new number is not 0 or 255. Netmask should be 255.255.255.0

The IP addresses must have the first three numbers the same as your laptop (to show they are on the same physical network), but each device must have a different address. Think of it like sending a letter to your next-door neighbour. The first three IP address numbers are like the country, county and street, and so will be the same as your address. The last number is however like your house number, and if you address it to your own house number it will not reach your neighbour.

Dave

Edited 1 time(s). Last edit at 10/19/2015 11:09AM by dmould.

Thanks, Dave! Makes a lot sense. I'll give it another try.

Thanks, Dave! Makes a lot of sense. Mainly I was confused if the IP in the Duet SD refers to what machine to "get involved with" or the way you explained. I'll give it another try.

Edited 1 time(s). Last edit at 10/19/2015 11:12AM by PropellerHat.

Well, I changed the printer's IP into 169.254.78.185 while the computer is 169.254.78.180. The subnet mask is put 255.255.255.0, but in the network settings of my macbook it is 255.255.0.0 and I tried also to put it same as in the Duet, 255.255.255.0. No connection. Looks like my problem is elsewhere in the end.

Edited 1 time(s). Last edit at 10/19/2015 11:33AM by PropellerHat.

The subnet mask will be OK either way in this setup, and the gateway address doesn't matter - the first thing to do to test the connection is to see if you can ping the printer (i.e. ping 169.254.78.185). Just to make sure the laptop IP is correct you can also try pinging 169.254.78.180 - i.e. pinging itself. If you don't get a reply then the laptop IP address is not what you think it is!

Be aware that many laptops have 2 different IP addresses, one for the WiFi interface and one for the wired Ethernet port.

Dave

Quote
dmould
Be aware that many laptops have 2 different IP addresses, one for the WiFi interface and one for the wired Ethernet port.

Good point. Please also make sure that both connections do not use the same IP-address or even the same subnet. So only one IP-address starting with 169.254.78.*** is allowed (if you use the subnet 255.255.255.0). Otherwise the PC does not know which connection it should use. The best way would be to deactivate WLAN.

---

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.

Alternatively, bridge the WLAN and Ethernet connections. To do this on a Windows machine go to Network Connections, select both adapters, right click, and choose Bridge.

---

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].

Pinging the printer gave a negative result (Request timeout for icmp_seq). I pinget that same IP as is put in the SD card's sys/config.g, so what do I do wrong? The Duet is on, and the SD is in it's slot, ethernet cable nicely connected and leds lit.

Pinging the computer itself gets results like this: 64 bytes from 169.254.78.180: icmp_seq=0 ttl=255 time=0.067 ms.

Run a command prompt (maybe administrative priviliges are needed) and run the command "ipconfig" without quotation marks. post the output here. Post your config.g here.

---

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.

Ipconfig run results:

Propellerhats-MacBook-Pro:~ Propeller$ ipconfig
usage: ipconfig
where is one of waitall, getifaddr, ifcount, getoption, getpacket, getv6packet, set, setverbose
Propellerhats-MacBook-Pro:~ Propeller$

Doesn't look helpful...

Config.g from the SD card;

; RepRapPro Ormerod
; Standard configuration G Codes
M550 POrmerod; Set the machine's name
M551 Preprap; Set the password
M552 P169.254.78.185; Set the IP address
M553 P255.255.255.0; Set netmask
M554 P192.168.1.1; Set the gateway
M555 P2; Emulate Marlin USB output
M92 E420; Set extruder steps/mm
G21 ; Work in mm
G90 ; Absolute positioning
M83 ; Extrusions relative
M558 P1 ; Turn Z Probe on
G31 Z0.5 P500 ; Set Z probe height and threshold
M906 X800 Y800 Z800 E800 ; Motor currents (mA)
T0 ; Select extruder 0

This the first time I setup any another kind of connection than logging into a wifi so bare with me

Please post the output of "ipconfig getifaddr" instead, this will hopefully provide the information we need. I'm still a bit reluctant to believe that your configured IP address works, but I'll provide an alternative suggestion once I see which IP addresses are used by your MacBook.

Quote
PropellerHat
Ipconfig run results:

Propellerhats-MacBook-Pro:~ Propeller$ ipconfig
usage: ipconfig
where is one of waitall, getifaddr, ifcount, getoption, getpacket, getv6packet, set, setverbose
Propellerhats-MacBook-Pro:~ Propeller$

Doesn't look helpful...

Config.g from the SD card;

; RepRapPro Ormerod
; Standard configuration G Codes
M550 POrmerod; Set the machine's name
M551 Preprap; Set the password
M552 P169.254.78.185; Set the IP address
M553 P255.255.255.0; Set netmask
M554 P192.168.1.1; Set the gateway
M555 P2; Emulate Marlin USB output
M92 E420; Set extruder steps/mm
G21 ; Work in mm
G90 ; Absolute positioning
M83 ; Extrusions relative
M558 P1 ; Turn Z Probe on
G31 Z0.5 P500 ; Set Z probe height and threshold
M906 X800 Y800 Z800 E800 ; Motor currents (mA)
T0 ; Select extruder 0

This the first time I setup any another kind of connection than logging into a wifi so bare with me

Try setting the Gateway in your M554 line to be the same as your Router or MacBook (If you are directly connecting to it). The way you have it now it is trying to send everything to a totally different subnet.

Now I am no IP Network expert but do reckon that has a big part to play in your problems it may be that you can comment that line out but I am not to certain on that.

HTH

Doug

The wrong Gateway should not be a problem. The GW will only be used if you request an IP from another subnet. As long as you stay inside the same SN in this case 169.254.78.0 there is no problem. Okay if I am a bad boy I would say that I do not know if Apple follows this standard regulation.
The GW should not be a problem. But I also believe that the IP-configuration of the PC is wrong and thanks to ZPL we know now the corrct command for Apple to get this information.

---

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.

In my laptop's network settings I can't see any gateway - it is blank. Laptop's IP is 169.254.78.180.

Please post the output of "ipconfig getifaddr"

Dave

Quote
dmould
Please post the output of "ipconfig getifaddr"

Dave

I totally agree. If you want further support we need this output. Otherwise we are not able to assist you any further.

---

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.

PropellrhatsMBP:~ Propeller$ ipconfig getifaddr
usage: ipconfig getifaddr
PropellrhatsMBP:~ Propeller$

I am no expert of Apple but it seems that the normal Linux/UNIX command works.
Please post the output of "ifconfig" instead.

---

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.

All right, this looks more informatic:

PropellrhatsMBP:~ Propeller$ ifconfig
lo0: flags=8049 mtu 16384
options=3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1
gif0: flags=8010 mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863 mtu 1500
options=10b
ether c8:2a:14:06:7d:91
nd6 options=1
media: autoselect (none)
status: inactive
en1: flags=8863 mtu 1500
ether e0:f8:47:3f:61:12
inet6 fe80::e2f8:47ff:fe3f:6112%en1 prefixlen 64 scopeid 0x5
inet 192.168.1.12 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=1
media: autoselect
status: active
fw0: flags=8863 mtu 4078
lladdr c8:2a:14:ff:fe:6e:33:36
nd6 options=1
media: autoselect
status: inactive
en2: flags=8963 mtu 1500
options=60
ether d2:00:16:e3:33:60
media: autoselect
status: inactive
p2p0: flags=8843 mtu 2304
ether 02:f8:47:3f:61:12
media: autoselect
status: inactive
bridge0: flags=8863 mtu 1500
options=63
ether ca:2a:14:60:46:00
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en2 flags=3
ifmaxaddr 0 port 7 priority 0 path cost 0
nd6 options=1
media:
status: inactive
PropellrhatsMBP:~ Propeller$

The Duet is NOT connected now since it is at my workshop.

Edited 1 time(s). Last edit at 10/23/2015 02:12AM by PropellerHat.

Sorry, but you have to connect the Duet for two reasons:

1. Your WLAN needs to be connected to your homenetwork so we can see what IP-address you get inside your WLAN.
2. The Duet needs to be connected. The interface detects if a cable is connected. If not it is disabled and deactivated so we cannot see your setup and that is the interesting thing at all. I assume that there is some problem with your configuration.

---

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.

OK, in an hour or so I'll post the outcome when connected

Here we go:

Propellerhats-MacBook-Pro:~ Propeller$ ifconfig
lo0: flags=8049 mtu 16384
options=3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1
gif0: flags=8010 mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863 mtu 1500
options=10b
ether c8:2a:14:06:7d:91
inet6 fe80::ca2a:14ff:fe06:7d91%en0 prefixlen 64 scopeid 0x4
inet 169.254.78.180 netmask 0xffffff00 broadcast 169.254.78.255
nd6 options=1
media: autoselect (100baseTX )
status: active
en1: flags=8863 mtu 1500
ether e0:f8:47:3f:61:12
inet6 fe80::e2f8:47ff:fe3f:6112%en1 prefixlen 64 scopeid 0x5
inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=1
media: autoselect
status: active
fw0: flags=8863 mtu 4078
lladdr c8:2a:14:ff:fe:6e:33:36
nd6 options=1
media: autoselect
status: inactive
en2: flags=8963 mtu 1500
options=60
ether d2:00:16:e3:33:60
media: autoselect
status: inactive
p2p0: flags=8843 mtu 2304
ether 02:f8:47:3f:61:12
media: autoselect
status: inactive
bridge0: flags=8863 mtu 1500
options=63
ether ca:2a:14:60:46:00
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en2 flags=3
ifmaxaddr 0 port 7 priority 0 path cost 0
nd6 options=1
media:
status: inactive
Propellerhats-MacBook-Pro:~ Propeller$

Thanks for that ifconfig output, it looks quite useful. So here is my proposal for an alternative configuration:

1) Configure your MacBook's LAN (ethernet) adapter in this way:
- IP address: 192.168.2.10
- Subnet mask: 255.255.255.0

2) Change the network configuration of your printer to:

M552 P192.168.2.20; Set the IP address
M553 P255.255.255.0; Set netmask
M554 P192.168.2.10; Set the gateway (optional)

3) Restart your printer with the new configuration and try to connect to [192.168.2.20]

I did that, but:

Propellerhats-MacBook-Pro:~ Propeller$ ping 192.168.2.20
PING 192.168.2.20 (192.168.2.20): 56 data bytes
Request timeout for icmp_seq 0

There appears to be 2 different network adaptors, one with a MAC address of c8:2a:14:06:7d:91 and the other has a MAC of e0:f8:47:3f:61:12 - probably one is the WiFi and the other the Ethernet port. The IP address allocated to the first is 169.254.78.180 and the other is 192.168.1.51

You have had no luck with the first LAN range, so try setting the Duet to an address in the range of the other adaptor (say 192.168.1.60) and see if you can ping that.

Dave

I did that and equally negative result. I suppose I forget this web UI until I get somebody in flesh to set it for me - probably there is something very simple wrong that you guys would roll your eyes on, that is supposed to be right but is not. Thanks for the help anyway!

I am afraid that the next step would be using Pronterface with an USB-connection. Reading a log from there. Are you sure you copied the folder www completely to the SD-card and replaced the files? Did you accidentally put the contents to the root directory or did you copy the folder www to the www folder so that you have a www folder inside your www folder?

---

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.

One quick thing to check - when you plug the Ethernet cable into the Duet (with the Duet powered on), you should notice that the "link" LED lights up on the connector. Unplug and it should go out. If that is not happening you have a fundamental connection issue (probably wrong type of cable).

Dave

I did not manipulate the WWW-folder, instead all the changes have been done in config.g file in the SYS one.