Difference between revisions of "Stronghold Meeting - 18-Jan-2016"

From DEW Robotics
Jump to: navigation, search
(Programming)
 
(4 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
<big>[[Stronghold Meeting - 17-Jan-2016 | << PREVIOUS]] -- [[Stronghold Meeting - 19-Jan-2016 | NEXT>>]]</big>
 +
 
=='''Competition Season Meeting'''==
 
=='''Competition Season Meeting'''==
  
Line 11: Line 13:
 
|}
 
|}
 
==CAD & Design==
 
==CAD & Design==
 +
 +
-Intake Crayola CAD continues. We should have it ready within the next couple of days.
  
 
==Mechanical==
 
==Mechanical==
 +
 +
-An adjustable launch angle catapult was developed from the original prototype, allowing for more accurate testing.
 +
 +
-The AM14U2 kitbot revision 2 was completed and driven over the defenses. We were unable to achieve a conclusive result, however, due to the chains continuing to pop off and the width of the drivebase is almost as large as the platform width, making initial alignment and maintaining alignment difficult. The wheelbase needs to be shortened for adequate testing.
  
 
==Programming==
 
==Programming==
  
- We developed a new system for selecting the drive type.
+
- We started with investigating the memory problem of GRIP.  
 
 
:-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.  
+
:-Fist, we watched to see if there was a memory leak. It did not appear to be so. If there was one, it was unnoticeable.  
  
:-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 deployed the GRIP program, watching the RAM before and after. The GRIP program used almost 50 mb of RAM.  
  
- 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.  
+
:-For now, it seems that GRIP only causes memory issues occasionally during deploys.
  
:-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.
+
:-Since this did not cause a serious problem, we decided to wait for a GRIP update to address this issue.
  
 
==Strategy==
 
==Strategy==
  
 
==Field Elements==
 
==Field Elements==
 +
 +
-The ramparts were completed and the seesaw remains under construction. Construction also began on the portcullis and tower.
  
 
==Other==
 
==Other==
Line 49: Line 57:
 
|<br /><br />
 
|<br /><br />
 
|}
 
|}
 +
 +
<big>[[Stronghold Meeting - 17-Jan-2016 | << PREVIOUS]] -- [[Stronghold Meeting - 19-Jan-2016 | NEXT>>]]</big>
 +
 
----
 
----
 
[[Category:DEWBOT XII]][[Category:Engineering]]
 
[[Category:DEWBOT XII]][[Category:Engineering]]

Latest revision as of 17:09, 28 January 2016

<< PREVIOUS -- NEXT>>

Competition Season Meeting

Meeting Date Meeting Time Location Attendees
TCHS Brandywine

CAD & Design

-Intake Crayola CAD continues. We should have it ready within the next couple of days.

Mechanical

-An adjustable launch angle catapult was developed from the original prototype, allowing for more accurate testing.

-The AM14U2 kitbot revision 2 was completed and driven over the defenses. We were unable to achieve a conclusive result, however, due to the chains continuing to pop off and the width of the drivebase is almost as large as the platform width, making initial alignment and maintaining alignment difficult. The wheelbase needs to be shortened for adequate testing.

Programming

- We started with investigating the memory problem of GRIP.

-Fist, we watched to see if there was a memory leak. It did not appear to be so. If there was one, it was unnoticeable.
-We deployed the GRIP program, watching the RAM before and after. The GRIP program used almost 50 mb of RAM.
-For now, it seems that GRIP only causes memory issues occasionally during deploys.
-Since this did not cause a serious problem, we decided to wait for a GRIP update to address this issue.

Strategy

Field Elements

-The ramparts were completed and the seesaw remains under construction. Construction also began on the portcullis and tower.

Other



Recorded by: Date: Journal Editor: Date:








<< PREVIOUS -- NEXT>>