View Single Post
  #16   Spotlight this post!  
Unread 29-01-2011, 18:22
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,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: wireless communication sparatic/dangerous

On the other issues.

Sorry for using the acronym -- DS. That stands for driver station. People also use it to refer to the computer and HW elements that the driver station application runs on.

The default NI code had game autonomous added to it at the last minute, and the digital inputs for the IR sensors are used in autonomous independent VI, but are not opened and stored in Begin. If the errors refer to that, you can correct it by opening and storing using the same names. An update will be released shortly to fix some issues not found in WPILib and in in the framework template code.

As for how to check the CPU usage on VXWorks if not running LV -- you can use the netConsole or serial connection via null-modem cable and look at the commands at this URL http://touro.ligo-la.caltech.edu/~cp..._commands.html. I don't have the WindRiver tools with me, but it may be that "i" gives you the info I was thinking of. If not, ask on the WindRiver forum or google a bit.

Greg McKaskle

Greg McKaskle
Reply With Quote