Thread: Not able to connect to the cRio
View Single Post
  #5   Spotlight this post!  
Unread 26-02-2014, 08:22
Greg McKaskle Greg McKaskle is online now
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
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: Not able to connect to the cRio
We received code from one team and booted with the serial cable attached. It indicated that the 8-slot cRIO was running out of memory, leading to corruptions, leading the the refusal of the code on the cRIO to abort as requested.

I haven't been able to verify with the team, but I'll know more tomorrow when I see them at the regional. It is relatively easy to modify the list of libraries to load to reclaim additional memory.

So, if you are seeing this on an 8-slot, this may be involved.

Greg McKaskle
Reply With Quote