|
Re: cRIO imaging issue
Ok, we are starting to see the same problems. Never saw this in beta.
Directly connecting to the cRIO was not working. The imaging tool would take an extremely long time to find the cRIO. It was not identifying the modules at all: they remained blank on the cRIO picture on the imaging tool.
Attempted imaging resulted in getting stuck at the Rebooting..... point, requiring a trip to the task manager to stop the imaging. After this, when restarting the reimaging tool the image would show as 'not known'.
We rebooted the robot a number of times, tried with and without the gaming adapter in place, and tried two different computers. Then, suddenly, it 'just worked'. I can't point to anything that fixed the problem.
|