You may add code to your program to display values for your sensors and actuators while the robot is in Test mode. This can be selected from the Driver Station whenever the robot is not on the field. The code to display these values is automatically generated by RobotBuilder and is described in the next article. Test mode is designed to verify the correct operation of the sensors and actuators on a robot. In addition it can be used for obtaining setpoints from sensors such as potentiometers and for tuning PID loops in your code.

This document details the basics of connecting your Classmate Computer to a cRIO.

This document outlines the procedure to image an E12 Classmate PC using the USB Stick provided in the 2014 Rookie Kit of Parts if necessary. Veteran teams may not need to image their machines, but should see the section on Image Download if they wish to do so.'

Note that the Rookie Classmates are provided with a Windows 7 image installed and do not necessarily need to be imaged with the provided USB stick. If you are experiencing an issue with the Drive account or with activating Windows please see below.

After the E12 Rookie machines were imaged and USB sticks were created an error was discovered that prevents the Driver Station from launching properly on the Driver Account. Teams can either follow the instructions located here to download and install one of the online images or follow the instructions below to fix the Driver account after imaging with the provided USB key.

This guide will show you how to use the 2013 FRC Bridge Configuration Tool software to configure your robot's wireless bridge for use outside of FRC events.

Before you begin using the software:

1. Disable WiFi connections on your computer, as it may prevent the configuration utility from properly communicating with the bridge
2. Make sure no devices are connected to your computer via ethernet, other than the wireless bridge.

The Identifying the Targets section explains a theoretical approach to locating the Vision Targets on the 2014 FRC Field. This document will cover the details of C++ and Java examples which implement this theoretical approach. Note that in addition to the typical differences between the C++ and Java WPILib code, there are also a few additional differences prompted by the way the NIVision functions are accessed from the Java code. Through the syntax may differ slightly the general approaches are similar enough that this document will walk through the C++ code which should provide sufficient insight into the function for both C++ and Java teams.