cRIO Imaging Tool trouble

[Mark McLeod]

Some laptops don't handle the cRIO IP changes/reboot well.

It often helps to connect your laptop to the cRIO through a network switch rather than directly. The network switch remembers the connection to the cRIO longer before aging it out, lasting through a reboot, while some laptops see the cRIO disappear immediately and break off the connection right away.

[Wildcat Robotic]

Thanks! About how much would a network switch probably be, and where could I find one? I'm not too savvy with networking stuff.

[Joe Ross]

You have one in the kit.

[Wildcat Robotic]

Ah. I feel silly. Thanks so much!

[linuxboy]

Originally Posted by Mark McLeod

Some laptops don't handle the cRIO IP changes/reboot well.

It often helps to connect your laptop to the cRIO through a network switch rather than directly. The network switch remembers the connection to the cRIO longer before aging it out, lasting through a reboot, while some laptops see the cRIO disappear immediately and break off the connection right away.

Just wondering, since I like to know the details of what is actually going on, is the ARP table time to live on switches higher than on computers? Does windows just clear the ARP table when a cable is unplugged? Or am I misinterpreting the switch remembering the cRIO as an ARP thing when it really isn't?

Oliver

[Alan Anderson]

If you keep getting timeout errors, go through the usual checklist of network settings. DISABLE all firewalls. DISABLE all network interfaces other than the one actually connecting to the cRIO. Don't just disconnect them, or just turn off the WiFi. Make sure, of course, that your computer's IP address is compatible with your team number.

[Mark McLeod]

Originally Posted by linuxboy

Just wondering, since I like to know the details of what is actually going on, is the ARP table time to live on switches higher than on computers? Does windows just clear the ARP table when a cable is unplugged? Or am I misinterpreting the switch remembering the cRIO as an ARP thing when it really isn't?

As you know, a network switch maintains an ARP and ages out connections gracefully for efficency's sake. Switches, routers, gateways, access points all have to be much more forgiving that a computer's NIC, because they must deal with more simultaneous connections, and momentary (or longer) communication glitches are much more common. Devices connect and disconnect all the time, and switches also keep track of which network hops are likely to lead to twice-removed machines.

An individual computer's NIC typically only talks directly to or through one other device, while a switch must maintain connections to dozens. The timeout on a switch or NIC depends on the manufacturer's attitude towards who they consider their market, so some timeout quickly, while others are more forgiving and take longer.
Part of the reason for the quick-to-drop attitude may be the evolving nature of mobile devices that must be on the lookout to change APs rapidly to maintain the strongest network connection. Switches don't roam as much as laptops do (except for those on our robots maybe).

[kgzak]

We are having the same problem and can't get it to work. Any other ideas?

[Alan Anderson]

Originally Posted by kgzak

We are having the same problem and can't get it to work. Any other ideas?

Only the ones already posted. Have you turned off the Windows firewall? Have you gone into the network configuration and disabled extra network adapters?

[kgzak]

Originally Posted by Alan Anderson

Only the ones already posted. Have you turned off the Windows firewall? Have you gone into the network configuration and disabled extra network adapters?

Tried all that. Still didn't work. Switched to my computer and it worked. Must have been something about my dad's computer