Thread: cRIO imaging issue
View Single Post
  #9   Spotlight this post!  
Unread 13-01-2013, 19:56
jcbc's Avatar
jcbc jcbc is offline
Registered User
AKA: Julie
no team
  
Join Date: Aug 2010
Rookie Year: 2011
Location: PA
Posts: 53
jcbc is a jewel in the roughjcbc is a jewel in the roughjcbc is a jewel in the roughjcbc is a jewel in the rough
Re: cRIO imaging issue
Quote:
Originally Posted by Tom Line View Post
Generally speaking, any newer computer knows when to crossover and when not to, so that shouldn't be the problem (but it might!).
Looking at NI's documentation for the regular non-FRC version of the cRIO II (cRIO-9075/9076, page 12), it says: "use an Ethernet crossover cable to connect the chassis directly to a computer". I don't know if it is the issue that some teams are having, but I thought I would mention it since it was in last year's documentation.

Quote:
Originally Posted by Tom Line View Post
We actually got stuck at the rebooting point, and I'd never seen it before. We found a couple things. First, the battery was nearly dead. Next, the cRio wasn't being powered from the 24V on the power distribution board. Fixing those allowed a reimage (wierd huh?).
We were trying something out today and discovered that all of the indicator lights on the cRIO can be on but if the battery doesn't have enough power, LabVIEW won't be able to connect to the cRIO to deploy code to it. The cRIO is picky about having enough power.