Thread: cRIO not being found by imaging tool
View Single Post
  #4   Spotlight this post!  
Unread 17-01-2014, 16:39
Hugh Meyer's Avatar
Hugh Meyer Hugh Meyer is offline
Registered User
FRC #1741 (Red Alert Robotics)
Team Role: Mentor
  
Join Date: Feb 2009
Rookie Year: 2008
Location: Greenwood Indiana
Posts: 158
Hugh Meyer has much to be proud ofHugh Meyer has much to be proud ofHugh Meyer has much to be proud ofHugh Meyer has much to be proud ofHugh Meyer has much to be proud ofHugh Meyer has much to be proud ofHugh Meyer has much to be proud ofHugh Meyer has much to be proud of
Re: cRIO not being found by imaging tool
Drew,

It can take a long time.... besides what you have done I would suggest you make certain the wireless is turned off on the laptop. If you are familiar with the IP stack you could try turning off everything except the IP 4 wired port part. We have had the same problem on a few of our computers and we think it is having a hard time deciding which network interface to use. The newer systems like win8 seem to have lots of places network code can look. Another option would be to try a different computer.

One of our systems we let search all night, but it had found the CRIO when we arrived the next morning. We never will really know how long it took.

Be sure the mask on the computer is 255.255.255.0 not 255.0.0.0 which is the standard operating mode for the robot network except for imaging. This is covered in the instructions but is easy to miss.

You also might try just talking to the CRIO with the driver station to confirm you really have a path to the device....that just depends what is on the CRIO now.

-Hugh