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!
