Recent Updates

  • Updated on: Jan 20, 2023

    Setting the default autonomous command

    Since a command is simply one or more actions (behaviors) that the robot performs, it makes sense to describe the autonomous operation of a robot as a command. While it could be a single command, it is more likely going to be a command group (a group of commands that happen together).

    Manual RobotBuilder

  • Updated on: Jan 20, 2023

    Connecting the operator interface to a command

    Commands handle the behaviors for your robot. The command starts a subsystem to some operating mode like raising and elevator and continues running until it reaches some setpoint or timeout. The command then handles waiting for the subsystem to finish. That way commands can run in sequence to develop more complex behaviors.

    RobotBuilder will also generate code to schedule a command to run whenever a button on your operator interface is pressed. You can also write code to run a command when a particular trigger condition has happened.

    Manual RobotBuilder
    Command Operator interface

  • Updated on: Jan 20, 2023

    Producing a wiring diagram for your robot

    Once all the subsystems are defined and filled with sensors and actuators you can produce a wiring diagram that will help the team wiring the robot to make sure that the electrical connections between the components and the cRIO robot controller are correct.

    Manual RobotBuilder

  • Updated on: Jan 20, 2023

    Creating a command

    Commands are classes you create that provide behaviors or actions for your subsystems. The subsystem class should set the operation of the subsystem, like ElevatorUp to start the elevator moving up, or ElevatorToSetPoint to set the elevator's PID setpoint. The commands initiate the subystem operation and keep track of when it is finished.

    Manual RobotBuilder
    Command

  • Updated on: Jan 20, 2023

    Creating a subsystem

    Subsystems are classes that encapsulate (or contain) all the data and code that make a subsystem on your robot operate. The first step in creating a robot program with the RobotBuilder is to identify and create all the subsystems on the robot. Examples of subsystems are grippers, ball collectors, the drive base, elevators, arms, etc. Each subsystem contains all the sensors and actuators that are used to make it work. For example, an elevator might have a Jaguar speed controller and a potentiometer to provide feedback of the robot position.

    Manual RobotBuilder
    Subsystem

  • Updated on: Jan 20, 2023

    Setting up the robot project

    The RobotBuilder program has some default properties that need to be set up so the generated program and other generated files work properly. This setup information is stored in the properties for robot description (the first line).

    Manual RobotBuilder

  • Updated on: Jan 31, 2019

    LabVIEW Resources

    To learn more about programming in LabVIEW and specifically programming FRC robots in LabVIEW, check out the following resources.

    Manual Getting Started With LabView

  • Updated on: Oct 03, 2017

    Detailed Hardware Documents

    Manual Getting Started With the 2014 Control System

  • Updated on: Jan 30, 2014

    Using limit switches to control behavior

    Manual WPILib programming