View Single Post
  #5   Spotlight this post!  
Unread 10-02-2013, 12:24
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,750
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Robot Not Enabling

For some reason, reimaging the cRIO always seems easier than debugging and fixing the issue, but it is rarely the cause of the issue unless SW is out of date. And because of the IP addresses, it actually isn't that easy or foolproof to reimage.

Focus on reimaging the cRIO back to where you had it. You will need to put the computer and cRIO on the same subnet and ensure that other network options such as wireless are disabled and ensure that the wired ethernet doesn't have more than one IP address set.

Then we can resume debugging the original issue.
Greg McKaskle
Reply With Quote