Difference between revisions of "Stronghold Meeting - 17-Jan-2016"
From DEW Robotics
(→CAD & Design) |
MaiKangWei (talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | <big>[[Stronghold Meeting - 16-Jan-2016 | << PREVIOUS]] -- [[Stronghold Meeting - 18-Jan-2016 | NEXT>>]]</big> | ||
| + | |||
=='''Competition Season Meeting'''== | =='''Competition Season Meeting'''== | ||
| Line 46: | Line 48: | ||
|<br /><br /> | |<br /><br /> | ||
|} | |} | ||
| + | |||
| + | <big>[[Stronghold Meeting - 16-Jan-2016 | << PREVIOUS]] -- [[Stronghold Meeting - 18-Jan-2016 | NEXT>>]]</big> | ||
| + | |||
---- | ---- | ||
[[Category:DEWBOT XII]][[Category:Engineering]] | [[Category:DEWBOT XII]][[Category:Engineering]] | ||
Revision as of 12:52, 27 January 2016
Competition Season Meeting
| Meeting Date | Meeting Time | Location | Attendees |
|---|---|---|---|
| TCHS Brandywine |
CAD & Design
Designs submitted and created for track drivetrain
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.
Field Elements
| Recorded by: | Date: | Journal Editor: | Date: |
|---|---|---|---|
