Edit

Note Viewer


Electrical & Code 2019

Attendance

Note Info

Students
Mentors
Date & Time
Location & Author
  • David S.

  • Shashank H.

  • 1/11/2019

  • 1 hour

  • Aquiferland

  • David S.


Work Completed

All of our time was devoted to figuring out the reason why Atla-Z had such a big delay

  • It's blowing the bandwidth limit
  • Worked smoothly when limelight was unplugged

 

 

Challenges

Nothing much, many of our solutions didn't work to fix Atla-Z. 

Work for Next Meeting

Reduce bandwidth so Atla-Z can run smoothly

Check how many Greyhill encoders we have in inventory!  Need 4 + spare for drivetrains, and I want to order those asap. - Adam

LIMELIGHT VISION: Drive robot towards vision target so the target is in view of limelight; then have robot drive to a specified distance and turn to a specified angle from the vision target (using a calibrated position and the tx & ty from the limelight)

  • Get Rotate_To_Angle_Limelight command working on Atlaz.  PID will need tuning.
  • Continue learning how to use limelight
    • Specifically learn what all of the different values on the network table are and how they can be used
    • Continue to look into the Limelight documentations
  • Go to specified range from target (check case studies on limelight website & documentation)
  • Go to specified range and aim at target (again check case studies)

LINE FOLLOWING:

  • Mount the color sensor to Atlaz. Needs to be only a few centimeters away from floor, pointed at the carpet.
  • Determine what sensor object to use in code to get values from it.  It's an I2C device.
  • Would be used to follow the white tape that is centered coming out from the spots where hatch panels are placed
  • Ultimate question is - Should line following be used instead of limelight vision in some places? Together with limelight vision? Or not at all this year?

OTHER: 

  • Talk to other subteams and drivers to determine what semi-autonomous controls are desired --> need list of everything we wish to accomplish and order of priorities --> this has been started, but more work is definitely needed
    • Will need to finalize these after designs are finalized but should start to get an idea now
    • Then figure out what the best ways are to implement them
    • Encoders? Gyros? Limit Switches? Vision? Line Following? etc. etc.
  • Determine what other electrical components we need for the next season --> probably some motor controllers and such but how many? what type? etc.
  • Begin framework of 2019 robot code, and as soon as drivetrain is decided (ie. 3 mini-CIMs per side & encoders etc.) this code can be written
  • Help other subteams

On Schedule?

Yeah