View Single Post
  #1   Spotlight this post!  
Unread 05-02-2014, 21:42
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,113
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: cRIO imaging timeout error

What is the IP address of your computer? It should be 10.47.73.xx, where xx is 5 (if you're going to run the Driver Station on that computer) or 6 (if you're just doing development on it) or something greater than 15 (if you have another computer at the .6 address). The subnet mask should be 255.0.0.0 in any case. Check the Advanced settings for IPv4 and make sure that only one IP address is set on the adapter. Delete any extra ones.

You should not be trying to image the cRIO over a wireless connection. You should have only the wired network interface enabled on your computer, with every other interface disabled. The computer's ethernet jack should be wired to one of the D-Link router's connections, and the cRIO should be wired to another connection on the cRIO. You can wire directly from the computer to the cRIO, but some computers take a long time to deal with the cRIO's dropping off the network during part of the reimaging process and that has been known to disrupt communication at a crucial time.

Do you have any antivirus or firewall software running on your computer? They should all be turned off when you're trying to load a cRIO image.
Reply With Quote