The notes you list are good, but but additionally, make sure that the no networks are enabled, including virtual ones, and simplify the network connection as much as possible, no switches or routers during imaging the cRIO.
Do you have a null modem serial cable available? If so, can you toggle the Console Out dip switch, connect a serial cable to your PC, and save the output you get on your PC? (You can use Window’s built-in hyperterminal, baud 9600). Posting that output may help us diagnose the problem.
There was a situation during beta where severely corrupted cRIOs were resulting in this error message being displayed. The solution in that scenario is to toggle the Safe Mode dip switch on, reboot, then run the imaging tool. You should get a dialogue that the tool has detected the cRIO is in safe mode asking if you want to reformat the device. Select the reformat option, and when it is done, toggle off safe mode, reboot, and run the imaging tool again to image the target normally.
Hey guys, we had the exact same problem as the op.
It was also originally done on a laptop that had leftovers of old software on it. Once we switched to a new computer it worked, so this seems to be the working solution.
We are having this exact problem without any resolution. All setting are correct (10.23.33.2/255.0.0.0 and 10.23.33.6/255.0.0.0). We communicate with the cRIO with both a crossover and straight through. The imaging process starts and then gives the error “The specified address is unreachable. Ensure IP address is on the correct subnet.”
Also, during the connection process it disconnects and reconnects the laptop to the cRIO. Then the error message pops.
We removed Labview and all of its components and reinstalled everything including all updates. We really could use some help as we are trying to get the camera working.