DUET Ethernet connect problem

alvgarvel

I get this from the ipconfig, it's in Spanish but it's the same as yours

Sufijo DNS específico para la conexión. . : home
Vínculo: dirección IPv6 local. . . : fe80::219f:d0f0:172c:b884%14
Dirección IPv4. . . . . . . . . . . . . . : 192.168.1.22
Máscara de subred . . . . . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada . . . . . : 192.168.1.1

PaulHew

connect to the USB port and type
M552
Note the reply from the board, then type
M552 S1
again note the reply from the board.

alvgarvel

m552
Network is enabled, configured IP address: 192.168.1.43, actual IP address: 192.168.1.43
ok
m552 S1
ok

I don't know why I don't recieve anything with M552 S1

PaulHew

Are you connected to the DWC now?

alvgarvel

I can't connect the DWC, when I connect the DUET via Ethernet and I type the IP direction, the browser can't find the page and type the ERR_ADDRESS_UNREACHABLE

PaulHew

Where the ethernet cable plugs into the duet, is there any activity on the lights?

alvgarvel

The LEDs in the DUET are always on, and the LEDs in the Ethernet module, the orange light is always on and the green light is blinking. But the two reds and the green from the DUET don't do anything different

alvgarvel

If I do a Windows problem diagnosis it says that my Ethernet connection has not a valid IP configuration

PaulHew

Reboot PC, make sure you can access internet from that computer.
From a command prompt type ping 192.168.1.1 and see if you get a response.
You should see something like this.
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Try the ping again with 192.168.1.43

If all seems good, on the Duet try
M552 P0.0.0.0
This will tell it to get an ip address from your router.

alvgarvel

Hi Paul!
I've made all the things you suggested my with this results:

Ping my local ethernet connection, all correct.

Haciendo ping a 192.168.1.1 con 32 bytes de datos:
Respuesta desde 192.168.1.1: bytes=32 tiempo=8ms TTL=64
Respuesta desde 192.168.1.1: bytes=32 tiempo=14ms TTL=64
Respuesta desde 192.168.1.1: bytes=32 tiempo=23ms TTL=64
Respuesta desde 192.168.1.1: bytes=32 tiempo=15ms TTL=64

Estadísticas de ping para 192.168.1.1:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 8ms, Máximo = 23ms, Media = 15ms

I've changed the Ethernet wire to the Duet and make ipconfig.

Sufijo DNS específico para la conexión. . :
Vínculo: dirección IPv6 local. . . : fe80::219f:d0f0:172c:b884%14
Dirección IPv4 de configuración automática: 169.254.184.132
Máscara de subred . . . . . . . . . . . . : 255.255.0.0
Puerta de enlace predeterminada . . . . . :

I've changed the IP to the 192.168.1.10 with M552 P192.168.1.10 S1
I've made ipconfig and I've recieved the same information.
Ping 169.254.184.132, good results.

Haciendo ping a 169.254.184.132 con 32 bytes de datos:
Respuesta desde 169.254.184.132: bytes=32 tiempo<1m TTL=128
Respuesta desde 169.254.184.132: bytes=32 tiempo<1m TTL=128
Respuesta desde 169.254.184.132: bytes=32 tiempo<1m TTL=128
Respuesta desde 169.254.184.132: bytes=32 tiempo<1m TTL=128

Estadísticas de ping para 169.254.184.132:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 0ms, Máximo = 0ms, Media = 0ms

Ping the IP assigned to the Duet 192.168.1.10, no signal. 100% packages lost.

I'm starting to think that my Ethernet module is broken, becouse it does't act like the other people posting things about it.

Thank you for your help

PaulHew

I think it could be, but i do not know everything.
Hopefully someone else with more Duet technical knowledge could assist?

Dougal1957

are you connecting the Duet to your Router or directly to the PC?

alvgarvel

Directly to the PC

Phaedrux

@alvgarvel said in DUET Ethernet connect problem:

Directly to the PC

In that case, if you have no router to issue DHCP addresses you would need to manually assign your own IP address to both the PC and the Duet.

It would be much easier to just connect both the PC and Duet to a router.

dc42

When connecting the Duet directly to a PC:

You may need to use a crossover cable, depending on the PC.
You need to set static IP addresses on both the PC and the Duet. For example:

PC : 192.168.1.1
Duet: 192.168.1.10

On both, set the netmask to 255.255.255.0. The default gateway doesn't matter because there isn't one, but if you need to enter one then I suggest 192.168.1.254.

With these addresses set up, on the PC run this to ping the Duet:

ping 192.168.1.10

to check the connection.

alvgarvel

Thank you guys,
I understand what my failure was, I follow your instructions and now my Duet works correctly.

Thank you of all you four your help!