View Single Post
  #1   Spotlight this post!  
Unread 13-03-2012, 17:06
kjohnson's Avatar
kjohnson kjohnson is offline
Insert Clever Title Here
AKA: Kyle J.
FRC #1610 (BOT)
Team Role: Mentor
 
Join Date: Jan 2004
Rookie Year: 2004
Location: Virginia
Posts: 575
kjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond repute
Team Update - 2012-03-13

Nothing game changing, just a warning about CPU usage on the cRIO and Driver's Station.

Quote:
GAME
Caution about CPU Usage

During the first two weeks we have observed a substantial number of teams with communications issues caused by CPU saturation. Saturating the CPU on either your cRIO or Driver’s Station computer can compromise your communications and cause your robot response to lag or drop completely. cRIO CPU usage can be monitored via the Driver’s Station Charts tab or the Driver Station Log File Viewer, more information on this utility is available on the Driver Station Kit of Parts page. Driver’s Station CPU usage can be viewed using the Task Manager by pressing Ctrl+Shift+Esc.

As a reminder, wireless control of robots in the pits is prohibited per section 4.3.1 of the Administrative manual. Additionally, we would highly recommend teams to connect to their DAP 1522 Robot Radio via Ethernet when tethering in the pits and leave the cRIO to Robot Radio connection in place.

Good luck in Week 3!
Reply With Quote