Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    DUET Ethernet connect problem

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    5
    18
    2.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • PaulHewundefined
      PaulHew
      last edited by

      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.

      RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
      Voron 2.4 disassembled..... Waiting for the RailCore Mini....

      1 Reply Last reply Reply Quote 0
      • alvgarvelundefined
        alvgarvel
        last edited by

        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

        1 Reply Last reply Reply Quote 0
        • PaulHewundefined
          PaulHew
          last edited by

          Are you connected to the DWC now?

          RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
          Voron 2.4 disassembled..... Waiting for the RailCore Mini....

          1 Reply Last reply Reply Quote 0
          • alvgarvelundefined
            alvgarvel
            last edited by

            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

            1 Reply Last reply Reply Quote 0
            • PaulHewundefined
              PaulHew
              last edited by

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

              RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
              Voron 2.4 disassembled..... Waiting for the RailCore Mini....

              1 Reply Last reply Reply Quote 0
              • alvgarvelundefined
                alvgarvel
                last edited by

                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

                1 Reply Last reply Reply Quote 0
                • alvgarvelundefined
                  alvgarvel
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • PaulHewundefined
                    PaulHew
                    last edited by

                    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.

                    RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                    Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                    1 Reply Last reply Reply Quote 0
                    • alvgarvelundefined
                      alvgarvel
                      last edited by

                      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

                      1 Reply Last reply Reply Quote 0
                      • PaulHewundefined
                        PaulHew
                        last edited by

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

                        RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                        Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                        1 Reply Last reply Reply Quote 0
                        • Dougal1957undefined
                          Dougal1957
                          last edited by

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

                          1 Reply Last reply Reply Quote 0
                          • alvgarvelundefined
                            alvgarvel
                            last edited by

                            Directly to the PC

                            Phaedruxundefined 1 Reply Last reply Reply Quote 0
                            • Phaedruxundefined
                              Phaedrux Moderator @alvgarvel
                              last edited by

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

                              Z-Bot CoreXY Build | Thingiverse Profile

                              1 Reply Last reply Reply Quote 0
                              • dc42undefined
                                dc42 administrators
                                last edited by

                                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.

                                Duet WiFi hardware designer and firmware engineer
                                Please do not ask me for Duet support via PM or email, use the forum
                                http://www.escher3d.com, https://miscsolutions.wordpress.com

                                1 Reply Last reply Reply Quote 0
                                • alvgarvelundefined
                                  alvgarvel
                                  last edited by

                                  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!

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post
                                  Unless otherwise noted, all forum content is licensed under CC-BY-SA