Thread: CRio Connection: Buggy
View Single Post
  #14   Spotlight this post!  
Unread 08-02-2011, 21:54
mswalker mswalker is offline
Mentor
FRC #2583 (Westwood Robotics)
Team Role: Mentor
  
Join Date: Jan 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 26
mswalker is on a distinguished road
Re: CRio Connection: Buggy
We made some progress in identifying this problem.

First, reimaging back to the v25 cRio firmware corrected the problem. There were no blinking status lights and we could deploy code at will.

I then re-imaged using v27 making sure to connect directly from PC to cRio via ethernet. The four blink status light returned. We could not deploy code getting the "failed to connect to Real-time Target" message. We checked to make sure Labview was at 3.1 FRC level.

We had loaded the CAN driver for the Black Jaguar Serial Bridge and had that working under v25. In the cRio Imaging tool I first changed the plugin to "None" leaving "Enable NetConsole" checked. Reimaged at v27 and still had four blink status.

Then I unchecked "Enable NetConsole" and reimaged. That seemed to fix it. cRio booted and I was able to deploy code.

It appears that adding the NetConsole and maybe CAN is consuming memory and putting us over. We have a 2009 cRio. Does this make sense? Are we going to have to avoid CAN? An ideas?
Reply With Quote