Updated The FTC Control System (markdown)
@ -1,9 +1,8 @@
|
||||
### About the _FIRST_ Tech Challenge
|
||||
The _FIRST_ Tech Challenge seeks to inspire youth to become the next generation of STEM leaders and innovators through participation in mentor-guided robotics competition. Teams who participate in the _FIRST_ Tech Challenge must build a robot that performs a variety of tasks. The tasks vary from season to season, and are based on a set of game rules that are published at the start of each season. The more tasks that a robot can complete, the more points a team will earn.
|
||||
|
||||
<img src="https://github.com/FIRST-Tech-Challenge/WikiSupport/blob/master/ftc_app/images/HoustonMatchPlay.jpg" alt="Houston 2017 Match" width="400">
|
||||
<p align="center"><img src="https://github.com/FIRST-Tech-Challenge/WikiSupport/blob/master/ftc_app/images/HoustonMatchPlay.jpg" width="500"><br/>(Photo courtesy of Dan Donovan, ©2017 Dan Donovan / www.dandonovan.com)<p>
|
||||
|
||||
(Photo courtesy of Dan Donovan, ©2017 Dan Donovan / www.dandonovan.com)
|
||||
|
||||
### Autonomous vs. Driver-Controlled
|
||||
A _FIRST_ Tech Challenge match has an _autonomous_ phase and a _driver-controlled_ or _"tele-operated"_ phase. In the autonomous phase of a match the robot operates without any human input or control. In the driver-controlled phase, the robot can receive input from up to two human drivers.
|
||||
@ -11,7 +10,7 @@ A _FIRST_ Tech Challenge match has an _autonomous_ phase and a _driver-controlle
|
||||
### Point-to-Point Control System
|
||||
The _FIRST_ Tech Challenge uses Android phones to control its robots. During a competition, each team has two Android phones.
|
||||
|
||||
<img src="https://github.com/FIRST-Tech-Challenge/WikiSupport/blob/master/ftc_app/images/PointToPointControl.jpg" alt="Point-to-Point" width="500">
|
||||
<p align="center"><img src="https://github.com/FIRST-Tech-Challenge/WikiSupport/blob/master/ftc_app/images/PointToPointControl.jpg" width="500"><p>
|
||||
|
||||
One phone is mounted onto the robot and is called the _Robot Controller_. The Robot Controller acts as the “brains” of the robot. It does all of the thinking for the robot and tells the robot what to do. It consists of an Android device running an FTC Robot Controller app.
|
||||
|
||||
@ -20,7 +19,7 @@ A second phone sits with the team drivers and has one or two gamepads connected.
|
||||
### REV Robotics Expansion Hub
|
||||
The REV Robotics Expansion Hub is the electronic input/output (or “I/O”) module that lets the Robot Controller talk to the robot’s motors, servos, and sensors. The Robot Controller communicates with the Expansion Hub through a USB connection. The Expansion Hub is connected to a 12V battery which is used to power the Expansion Hub, the motors, the servos and sensors. The Robot Controller typically has its own internal battery, which can also be charged through the USB cable connected to the Expansion Hub.
|
||||
|
||||
<img src="https://github.com/FIRST-Tech-Challenge/WikiSupport/blob/master/ftc_app/images/REVExpansionHubLayout.jpg" alt="Expansion Hub Layout" width="400">
|
||||
<p align="center"><img src="https://github.com/FIRST-Tech-Challenge/WikiSupport/blob/master/ftc_app/images/REVExpansionHubLayout.jpg" width="500"><p>
|
||||
|
||||
### What's an Op Mode?
|
||||
|
||||
|
Reference in New Issue
Block a user