Difference between revisions of "Stronghold Meeting - 18-Jan-2016"
From DEW Robotics
(Created page with '=='''Competition Season Meeting'''== <!-- This is the meeting information table --> {|border=1 cellpadding="10" !Meeting Date !!Meeting Time !!Location !!Attendees |- | | | TC...') |
(→Programming) |
||
| Line 15: | Line 15: | ||
==Programming== | ==Programming== | ||
| + | |||
| + | - We developed a new system for selecting the drive type. | ||
| + | |||
| + | :-This year, arcade/tank, gyro correction, auto aim, and (if necessary) anti-tip will all be supported. | ||
| + | |||
| + | :-At any time, all of these may be turned on. We needed a way to allow for different features to be prioritized. For example, anti tip takes priority over the vision auto aim. | ||
| + | |||
| + | :-We decided to store the priority in an integer. Each bit of the integer would be if each feature was on / off. The highest bit would be the highest priority. This code became much more streamlined and robust than simply using if statements for every feature. Adding a feature becomes very easy. | ||
| + | |||
| + | - We also worked on having our code start GRIP instead of manually. This way the drivers would not have to start it before each match. | ||
| + | |||
| + | :-After trying many different things, we were finally able to get the program to run GRIP. However, we then noticed that GRIP was eating up quite a bit of RAM. | ||
==Strategy== | ==Strategy== | ||
Revision as of 07:56, 24 January 2016
Contents
Competition Season Meeting
| Meeting Date | Meeting Time | Location | Attendees |
|---|---|---|---|
| TCHS Brandywine |
CAD & Design
Mechanical
Programming
- We developed a new system for selecting the drive type.
- -This year, arcade/tank, gyro correction, auto aim, and (if necessary) anti-tip will all be supported.
- -At any time, all of these may be turned on. We needed a way to allow for different features to be prioritized. For example, anti tip takes priority over the vision auto aim.
- -We decided to store the priority in an integer. Each bit of the integer would be if each feature was on / off. The highest bit would be the highest priority. This code became much more streamlined and robust than simply using if statements for every feature. Adding a feature becomes very easy.
- We also worked on having our code start GRIP instead of manually. This way the drivers would not have to start it before each match.
- -After trying many different things, we were finally able to get the program to run GRIP. However, we then noticed that GRIP was eating up quite a bit of RAM.
Strategy
Field Elements
Other
| Recorded by: | Date: | Journal Editor: | Date: |
|---|---|---|---|
