DUET V0.8.5 ethernet connect problem



  • Hello,
    i have two board RepRap DUET V0.8.5 but only one board RepRap DUET V0.8.5 is connected to the network,on both boards this software is loaded.
    First i connect the first board DUET,this from my config

    M552 P192.168.2.7 ;
    M553 P255.255.255.0 ;
    M554 P192.168.1.255 ;

    open the chrome browser and i type "192.168.2.7" and loads the page duet web control.

    Then disconnect this board and i connect the second duet board with the same files inside the sd card and the same archive "config"

    M552 P192.168.2.7 ;
    M553 P255.255.255.0 ;
    M554 P192.168.1.255 ;

    open the chrome browser and i type "192.168.2.7" but it doesn't load the page duet web control.

    Why doesn't the second DUET board connect?I need to change something?
    The DUET board is connectet to the router,i try the two boards individually,i don't have them both connected at the same time.



  • I know this sounds a bit silly, but have you tried turning the second board off and back on a few times and try to connect between each power on?

    I have (4) Duet 0.8.5 boards each with unique MAC addresses and IP Addresses, and every so often when I turn them on they don't respond on the network properly. In my case, I shutoff the machine, give it a second, and then turn it on again and try to connect. Sometimes it takes 2-4 attempts before the boards respond on the network. No idea why it works, no idea why it doesn't sometimes. I have found its more frequently an issue when a machine goes un-powered for a longer period of time which means it could be some capacitor issue in the 0.8.5 design is discharging over time causing the issue and the repetitive turning it on and off recharges it enough to behave.

    I also found it happens less frequently when I changed my config lines for M552 to include the S1 parameter, but I still see this happen every so often.



  • I have that same issue with the v0.6 and v0.8.5 boards not connecting. I wonder if it is related to the MDNS (machinename.local address rather than IP address in browser) problem that dc42 mentioned in the thread I recently raised about the. Local addressing.



  • When i connect the duet the green light of ethernet flashes.
    I did "ping 192.168.1.14" (the IP address you set in config.g)but i didn't get any answer.
    The problem is in hardware or software?What else can i do to see where the problem is?



  • Is there any particular case for needing to use the same IP address on both boards?

    After you have accessed the first board your local computer will remember the ip address to mac address mapping for something like 2-5 minutes and in that time if you try to access the second board your computer will send the data to the correct ip address but the wrong mac address, and the duet will never respond.



  • @doctrucker said in DUET V0.8.5 ethernet connect problem:

    I have that same issue with the v0.6 and v0.8.5 boards not connecting. I wonder if it is related to the MDNS (machinename.local address rather than IP address in browser) problem that dc42 mentioned in the thread I recently raised about the. Local addressing.

    shouldn't affect addressing the board directly by ip address.



  • @john_1 said in DUET V0.8.5 ethernet connect problem:

    I did "ping 192.168.1.14" (the IP address you set in config.g)but i didn't get any answer.

    Thats not the IP address you have in the config you showed? Furthermore your Duet IP address and gateway are on separate subnets, 192.168.1.0/24 vs 192.168.2.0/24 - which network is your computer on?



  • @bearer said in DUET V0.8.5 ethernet connect problem:

    @john_1 said in DUET V0.8.5 ethernet connect problem:

    I did "ping 192.168.1.14" (the IP address you set in config.g)but i didn't get any answer.

    Thats not the IP address you have in the config you showed? Furthermore your Duet IP address and gateway are on separate subnets, 192.168.1.0/24 vs 192.168.2.0/24 - which network is your computer on?

    Bearer i tried with default archives.The computer is on the network 192.168.2.0/24.



  • Then 192.168.1.14 is not going to work in any case; even if both your router and computer knows how to get the packages to 192.168.1.0/24 the Duet will have no idea on how to return it. You'd do yourself a favour by keeping both in the same subnet.


Log in to reply