Revision as of 14:09, 19 January 2014

Programming Sub-pages and Links

1.15.14

PROGRAMMING MEETING:

Discussed staying with the standard C++ programming method, or changing to Command Base.
We decided to stay with the standard method, and save Command Base for next pre-season.
We will be using GIT(?) to update and archive the programs.
OnSunday, January 19th, we will be holding a meeting right after Lunch to discuss the primary code layouts for our subteams.
- Please know your subteams needs for the meeting.

1.19.14

PROGRAMMING MEETINGS:

Decided to create 3 main subsystems: Intake, Drive, Kicker
- Intake subsumes the roller and lift/cradle mechanism
- Drive is the drivetrain
- Kicker is only the motors and sensors associated with moving the kicker "leg"
Like in previous years, we have Auto, Controls, Lights classes
No camera class yet, until we use a rotating camera
Relegated utility classes and functions to "./util/" folder.
Using references/stack allocation for classes
Using git. Code is on laptop 3 and cloned in Manuel's data realm.
Need to decide where to host: svn.penfieldrobotics.com/git/ is possible, but needs a config change; github/google code/etc. possible

IMPORTANT: Include ThunderDrive.h & ThunderDrive.cpp while integrating
- Use #include "ThunderDrive.h"
ThunderDrive is an object type that allows you to use the comands...
- Teleop
  - .TankDrive (float left, float right, bool turbo, bool slow)
    - Inputs
      - left (float, -1 to +1)
        left stick Y position
      - right (float, -1 to +1)
        right stick Y position
      - turbo (bool)
        status of the turbo button
      - slow (bool)
        status of the slow button
    - Allows you to drive using tank controls
  - .DoDebug
    - Inputs
      - left (float, -1 to +1)
        left stick Y position
      - right (float, -1 to +1)
        right stick Y position
      - turbo (bool)
        status of the turbo button
      - slow (bool)
        status of the slow button
    - Shows you current motor power
    - Prints into net console for CRIO(? What part is caps)
- Auto
  - .AutonomousDrive(float distance_IN, float maxPower)
    - disance_IN (float)
      - how far you plan to go in inches
    - maxPower (float)
      - maximum power to be used wilst going to the position
  - .AutonomousTurn(float distance_IN, float maxPower)
    - degrees (float)
      - how far you plan to turn in degrees

@@ Line 6: / Line 6: @@
 *[[Jaguar Firmware Notes]]
 *[[2014:Robot IO Map]]
 .15.14
@@ Line 20: / Line 16: @@
 *On<u>'''Sunday, January <span data-scaytid="6" data-scayt_word="19th">19th</span>'''</u>, we will be holding a meeting right after Lunch to discuss the primary code layouts for our <span data-scaytid="20" data-scayt_word="subteams">subteams</span>.
 **Please know your <span data-scaytid="23" data-scayt_word="subteams">subteams</span> needs for the meeting.
+.19.14
+PROGRAMMING MEETINGS:
+*Decided to create 3 main subsystems: Intake, Drive, Kicker
+** Intake subsumes the roller and lift/cradle mechanism
+** Drive is the drivetrain
+** Kicker is only the motors and sensors associated with moving the kicker "leg"
+* Like in previous years, we have Auto, Controls, Lights classes
+* No camera class yet, until we use a rotating camera
+* Relegated utility classes and functions to "./util/" folder.
+* Using references/stack allocation for classes
+* Using git. Code is on laptop 3 and cloned in Manuel's data realm.
+* Need to decide where to host: svn.penfieldrobotics.com/git/ is possible, but needs a config change; github/google code/etc. possible
 = DRIVETRAIN =