cRIO Imaging Tool Wrong IP

[RufflesRidge]

When the Imaging Tool detects the cRIO, check the IP of the cRIO in the top box. Then set your computer to the same subnet (match the first 3 octets). After your computer IP is set, then try imaging the cRIO. The imaging may or may not complete, but it should be able to set the IP of the cRIO. If the imaging does not complete, change the IP of the computer back to your team subnet, then try imaging again.

[Alan Anderson]

Look at the "Advanced" settings for the network adapter. Make sure there isn't a second IP address configured.

Be absolutely certain that all firewalls (including those associated with anti-malware software) are disabled.

Try switching the subnet mask between 255.255.255.0 and 255.0.0.0 temporarily.

You are using the D-Link between the computer and the cRIO, right?

[alicerao]

Thank you all for your advice.

WHAT WORKED : We were indeed able to re-image our cRIO and reestablish communications with the robot through the Driver Station after switching to WiFi imaging through the D-Link (thank you, Alan!). Everything worked exactly as we expected: 10.50.26.5 as the IP, 255.255.255.0 as the subnet mask, all cRIO modules shown, etc. We are not, however, sure why this worked when Ethernet didn't, as WiFi has usually been the least consistent method for us.

WHAT DIDN'T : Before using WiFi, we tried setting the computer IP to the (incorrect) IP given in the imaging tool; this led us to an error message saying the tool couldn't find the cRIO at all.

When we ran the National Instruments MAX program (Measurement and Automation Explorer) it found the cRIO but said it had the error "Inconsistent IP Address." Creating a report with this program gave us an IP address for the cRIO which had 255.255.0.0 for a subnet mask.

NOT TESTED: We did not end up having to run the program from a different computer, so we don't know if this would have helped.

Again, thanks to everyone for their suggestions!

[FrankJ]

We just fixed the apparently the same problem as the OP's We ended up using the dlink, wired. Setting the computer id one digit off in the last octet the imagining tool showed for the cRio (xx.xx.xn) We used n-1. subnet mask was either 255.255.255.0 or 255.0.0.0 (we flipped several times I am not sure which one we using when it final took.) Reimaging the cRio with our team number successfully reset the IP & then errored out from not being able to reach the cRio which is normal when resetting a device's IP to one a different subnet. We then reset the IP on the computer to the normal IP (10.xx.xx.05 with a subnet of 255.255.255.0) & formatted the cRio with the formatting tool.