Imaging Tool not finding Crio

[nydnh01]

As the title states, the FRC Crio imaging tool is not finding the Crio connected to the computer. With all the IP address and Subnet address correct the Imaging tool still does not find it. When I open the Driver Station the Crio shows communication with the DS. Right now it is configured for Labview but I need the Crio to be imaged for JAVA.

[Jared]

Make sure you're connected with an ethernet cable instead of wireless.

Also, try going to network and sharing center, adapter settings, and disable all network adapters that aren't your ethernet adapter.

[nydnh01]

Originally Posted by Jared

Make sure you're connected with an ethernet cable instead of wireless.

Also, try going to network and sharing center, adapter settings, and disable all network adapters that aren't your ethernet adapter.

I am connected via an ethernet cable. I have disabled all the adapters except the LAN adapter and still the same results.

[Jared]

Weird.

What is the IP address and subnet mask of the computer?

If you go to adapter settings, right click on adapter, properties, IPv4, properties, advanced, do you have multiple ip addresses assigned to the computer? For some reason, I've seen teams have random issues caused by this.

Is your firewall configured to allow imaging tool to connect?

[nydnh01]

Originally Posted by Jared

Weird.

What is the IP address and subnet mask of the computer?

If you go to adapter settings, right click on adapter, properties, IPv4, properties, advanced, do you have multiple ip addresses assigned to the computer? For some reason, I've seen teams have random issues caused by this.

Is your firewall configured to allow imaging tool to connect?

The IP address is 10.16.1.5 and the subnet is 255.255.255.0. I do not have multiple IP addresses on the adapter. My firewall is turned off.

[Jim Wilks]

Can you ping the CRIO?

[nydnh01]

Originally Posted by Jim Wilks

Can you ping the CRIO?

Yes, I am able to ping the Crio.

[nydnh01]

I was able to reimage after leaving the program running to search for the crio for 45 minutes.

[Jared]

Originally Posted by nydnh01

I was able to reimage after leaving the program running to search for the crio for 45 minutes.

Have you tried imaging with the classmate laptop? A while ago, I remember a team having a similar issue (using an HP laptop), which they think was caused by the method of scanning not playing well with a specific network adapter.

A solution can be to reset the IP address of the cRIO before reimaging. I find that the cRIO is found much quicker if it has the default IP address than our team address.

I know we can't image well with my laptop because the network adapter doesn't reconnect properly between cRIO reboots, so the connection times out.

[cgmv123]

I've had success imaging with a crossover cable running straight from a laptop to the cRIO.

[Greg McKaskle]

The problem I've seen with HP laptops tends to be that they bring down the ethernet interface eagerly, such as when an attached cRIO is rebooting. Then they are slow to bring it back up. This is often improved if the cRIO and laptop are both plugged into a switch such as the DLink.

Greg McKaskle