DUET Ethernet connect problem



  • Hi everyone!
    I've just bougth the Duet 2 Ethernet and I'm facing an issue trying to connect with the Duet Web Control.
    I've been following the Getting connected guide from https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7, and I get a trouble when I connect the Duet via Ethernet with my computer and I put the IP adress assigned by the Duet.
    I get a problem like this: 0_1554913989858_error.JPG
    I have no problem connecting via USB. When I write M552 I get: Network is enabled, configured IP address: 192.168.1.74, actual IP address: 192.168.1.74 and when I write M552 S1 I recieve: ok
    I don't know what's going wrong, I've followed the guide step by step but I get this problem, probably it's becouse I'm new with this, but any help will be amazing!

    PD: I think it will be usefull to attach the M122 status:
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet Ethernet 1.02 or later
    Board ID: 08DGM-917DA-G4MS4-6J1DL-3S86N-TBYMA
    Used output buffers: 1 of 20 (1 max)
    === RTOS ===
    Static ram: 25524
    Dynamic ram: 98176 of which 0 recycled
    Exception stack ram used: 256
    Never used ram: 7116
    Tasks: NETWORK(ready,1968) HEAT(blocked,1232) MAIN(running,3868) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:03:47 ago, cause: power up
    Last software reset details not available
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 19.3, current 25.2, max 25.4
    Supply voltage: min 0.5, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
    Driver 0: ok, SG min/max not available
    Driver 1: ok, SG min/max not available
    Driver 2: ok, SG min/max not available
    Driver 3: ok, SG min/max not available
    Driver 4: ok, SG min/max not available
    Date/time: 1970-01-01 00:00:00
    Cache data hit count 424100908
    Slowest loop: 0.17ms; fastest: 0.06ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    Movement lock held by null
    http is idle in state(s) 0
    telnet is idle in state(s) 0
    file is idle in state(s) 0
    serial is ready with "M122" in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 0.17ms; fastest: 0.01ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 0 of 8
    Interface state 2, link down



    1. What address is your PC?
    2. What is your router address?

    This from my config
    M552 P192.168.0.8 S1 ; Enable network and set IP address
    M553 P255.255.255.0 ; Set netmask
    M554 P192.168.0.1 ; Set gateway
    M586 P0 S1 ; Enable HTTP

    If you are running windows, open a command prompt, and type ipconfig
    It should give you these details.
    Connection-specific DNS Suffix . :
    IPv4 Address. . . . . . . . . . . : 192.168.0.51
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.0.1



  • 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



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



  • 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



  • Are you connected to the DWC now?



  • 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



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



  • 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



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



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



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

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

    1. 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 . . . . . :

    1. I've changed the IP to the 192.168.1.10 with M552 P192.168.1.10 S1
    2. I've made ipconfig and I've recieved the same information.
    3. 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

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



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



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



  • Directly to the PC



  • @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.


  • administrators

    When connecting the Duet directly to a PC:

    1. You may need to use a crossover cable, depending on the PC.

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



  • 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!


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.