Recent Updates

  • Updated on: Mar 24, 2015

    Troubleshooting Dashboard Connectivity

    We have received a number of reports of Dashboard connectivity issues from events. This document will help explain how to recognize if the Dashboard is not connected to your robot, steps to troubleshoot this condition and a code modification you can make

  • The 2015 convention for using the Axis camera uses mDNS with the camera name set to axis-camera.local At home this works fine as there is only one camera on the network. At official events, this works fine as each team is on their own VLAN and therefore doesn't have visibility to another team's camera. At an offseason using a single network, this will cause an issue where all teams will connect to whichever team's camera "wins" and becomes "axis-camera", the other cameras will see that the name is taken and use an alternative name. This article describes how to modify the Dashboard and/or robot code to use a different mDNS name to separate the camera streams.

  • Updated on: Feb 09, 2015

    RobotBuilder created code

    Manual RobotBuilder
  • Updated on: Feb 06, 2015

    Analog inputs

    The roboRIO Analog to Digital module has a number of features not available on simpler controllers. It will automatically sample the analog channels in a round robin fashion, providing a combined sample rate of 500 ks/s (500,000 samples / second). These channels can be optionally oversampled and averaged to provide the value that is used by the program. There are raw integer and floating point voltage outputs available in addition to the averaged values. The diagram below outlines this process.

  • The default LabVIEW Dashboard utilizes Network Tables to pass values and is therefore compatible with C++ and Java robot programs. This article covers the keys and value ranges to use to work with the Dashboard.

  • Updated on: Jan 20, 2015

    FRC Java WPILib API Documentation

  • Updated on: Jan 20, 2015

    Using the Microsoft Lifecam HD-3000

    The Microsoft Lifecam HD-3000 is a USB webcam that was tested with the roboRIO as part of the Beta testing and software development effort. While other USB webcams may work with the roboRIO, this camera has been tested to be compatible with the provided software.

  • Counter objects are extremely flexible elements that can count input from either a digital input signal or an analog trigger.

  • RoboRealm is a vision processing application that runs on a Windows PC connected to the robot via a network connection. It can read the camera stream, process images and send results back to the robot. It is often desirable to see the results of the image processing on your driver station laptop, but screen real estate is at a premium. You can display images from RoboRealm on the SmartDashboard by using it's internal web server as shown in this article.

  • There are two ways of running programs onto the roboRIO. You can

    1. Attach to the roboRIO and run the program using the debugger from your development system OR
    2. Load it onto the roboRIO flash drive so it will run on reboot.

    For tournaments you should always download the program so that it will be there when the robot is restarted and the match is played. This article will cover loading the program onto the roboRIO to run on reboot. The next article will cover the debugger.