Note Viewer

Pneumatics (Comp Bot):

• Connected tubes to disk brake on cargo arm
• Compressor works!
• When testing for the first time, we found many leaks, most of which have been fixed
• Replaced regulator --> we don't know if we have it set correctly...

Pneumatics (Practice Bot):

• Put basics components on practice bot
• I think they connected them with tubes as well
• Made mounts for the air tanks on the back of the robot too
• Mounted solenoid block I believe

Electronics (Comp Bot):

• CAN Bus (long CAN wires work but are a pain)
• Wired climbers with huge wire sleeve things (thanks Chris!)
• Wired cargo arm motor
• Wired hatch arm motor
• Mounted and wired cargo arm potentiometer
• Attemped to make it look prettier --> still needs a lot of work
• Battery connector (black cable connected to PDP) had severed since it was wired poorly so that was fixed...

Electronics (Practice Bot):

• Mounted and wired climber limit switches
• Mounted electronics board (and drilled holes through it potentially for wires and tubes??)

Code & Testing:

• Got rid of some issues using the simulator
• Everything worked well on the simulator I thought
• Then we ran it on the actual robot...
• Created IDs for CAN Bus on Phoenix Tuner thing
• Didn't crash but buttons didn't do what we were expecting
  • Cargo arm worked
  • Hatch motion worked in 1 direction, but not the other
  • Drivetrain worked --> motor controllers need to be calibrated
  • Did not test climber at all
  • Hatch pistons (beak & moving the entire plate) and the cargo intake/outake were mapped to different buttons than the code specified --> issue with constants? issue with xbox controller class? idk something to figure out tomorrow

Other:

• I think Sam made a list of IDs on the robot but idk where it went
• LEDs began to get mounted which is fun and our frosted polycarb came in which is also fun

• PNEUMATIC LEAKS ARE ANNOYING AF also remember to plug the solenoid block since I forgot to
• So many wires, so little space
• Missing one stupid paranthese on code caused some set back since I couldn't figure that out for a while

1. Pneumatics (comp bot) --> Fix leak on hatch piston
2. Electrical System (comp bot), wire & mount...
   • climber drive motor
   • wire cargo limit switch
   • check if encoders are working, check if cargo pot is working, etc.
   • the ultrasonic sensors
   • (and find a home for) the arduino
   • light sensors
   • string pot on hatch
   • LEDs :)))
3. Robot Code!!!
   • Talk to Marlow & Sam about buttons and controls for the robot (as of now climber and drivetrain is on 1; hatch and cargo is on 2
   • Figure out this issue with buttons or constants bc it is perplexing
     • Check CAN Bus IDs for PCMs
     • Check all constants
   • Integrate ultrasonic sensors
   • Add code for limelight to drive to the hatch
   • Integrate line sensors to hatch pid
   • Single climber command
   • Cargo set points
4. Wire electrical system & pneumatics of practice bot
   • MAKE SURE THE IDs ARE THE SAME ON BOTH ROBOTS
5. Continue the schematic for the electrical system using the schematic software stuff --> talk to Malia & Caden about this if you are interested 
6. Line Followers & Arduino -> someone (who is not Bryn and is going to both competitions) needs to understand this and know how to debug it...
7. Vision
   • Now that the gyro is working again, this should be worked on some more...
   • 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 Poly again.  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)

I mean no but that's alright