Process: -Our team went to kickoff. We saw the challenge of velocity vortex. To us it seems like an easier game than res-q. Only time will tell if we can accomplish more than last year. Our feelings: -We were so pumped after the introduction. We debated a design for the this year's competition before we even got back.
September 15, 2016 (Thursday meeting)
Tasks; -Read the Game Manual to understand all rules
Process: -Gave a good reading of the game manual -We discussed on what to aim for our robot (especially beacons autonomous)
September 19, 2016 (Monday meeting)
Tasks: -Start the web designing the website on weebly
Process: -Started setting up the class websites using weebly. Made it open for both groups to add information. Also, the site was broken up into three pages
September 22, 2016 (Thursday Morning meeting)
Tasks: -Take bio pictures -Think of what to do the next week -Do bios for engineering notebook -Plan and approve a design for the robot
Process: -As a team, we all worked on the bios for the engineering notebook. Then we made a plan for the next week
September 23, 2016 (Friday meeting)
Tasks: -Start a shooter prototype
Process: -We plan to have two wheels spinning rapidly to shoot the balls. We got the wheels attached to gears today
September 27, 2016 (Thursday meeting)
Tasks: -Attaching the wheels
Process: -We attach omni-directional wheels to front of the robot to aid turning as well as normal wheels to the back of the robot. Attached gears to the back two wheels in preparation for the motors we will attach -We built a functional shooter, however it seems like we need more speed. We are planning to increase the gear ratio to increase the RPM
September 30, 2016 (Friday meeting)
Tasks: -Increase the gear ratio
Reflection: -To make the launcher better we must increase the gear ratio. However, how do we do that without spending $27.95 on another set of gears? Solution we 3D print. Using our school's MakerBot 3D printer we are in the process of printing another set of 120 tooth gears. Currently, it takes 13 hours to print one gear. Patience is a virtue
October 5, 2016 (Wednesday meeting)
Tasks: -Transfer robot partsfrom pushbot to main robot -Set up all images for image tracking -Experiment 3D printing smaller gears
Reflection: -We transplanted the Core Power Distribution modules and motor controllers from the pushbot to this year's chassis. (Improvement on wiring is necessary) Modules are stacked by standoffs to save space in the center -Also with our 3D printer we experimented a thingiverse file that reduced the speed of the motor hoping to reverse engineer it to make it go ALOT faster. However SketchUp is hard deal with
October 6, 2016 (Thursday meeting)
Tasks: -Add an intake
Reflections: -Added an intake to collect balls and maybe in the future will collect balls into a storage area. Then on the press of a button will launch the particles
October 3, 4, 6, 10, 2016 (Shooter build)
Tasks: -Prototype Launcher
Reflections: -When we had built our first launcher we came to the realization the rotation speed wasn't fast enough for the task we needed. So, we had to come up with a way to increase the speed. Therefore, for the past few meetings I was working on a prototype multi-gear ball launcher that we could incorporate into our robot. This launcher would increase the rotation speed by connecting multiple large gears to smaller gears
October 17, 18, 2016
Tasks: -Attaching launcher to the body
Reflections; -For the past few days we have been working on a way to attach the ball launcher to the chassis. There were multiply factors we had to take into account such as: the acceptable height, the acceptable width, and the correct angle
November 14, 2016
Tasks: -Add the ability to press buttons on beacons
Programming Log
September 21, 2016 (Wednesday meeting)
Tasks: -Work on the color sensor
Reflections: -We programmed the color sensor to detect the color of the beacon. -Using the help from this video: http;//www.youtube.com/watch?v=eC-sFRIa-Ls
September 28, 2016 (Wednesday meeting)
Tasks: -Check out Vuforia -Try to implement this video's code: http://www.youtube.com/watch?v=FLNnNbS5VJA from Swerve Robotics
Reflections: -Looked up how to use Vuforia Navigation. Got it working but have no idea what the telemetry numbers are. Looks cool and I want to implement it on our school
October 5, 2016 (Wednesday meeting)
Tasks: -Add all the images to Vuforia -Try to implement this video's code: http://www.youtube.com/watch?v=2z-o9Ts8XoE from FIXIT3451
Reflections: -In the linear OP mode we added the capability to track multiple images to detect the different images on the field
October 12, 2016 (Wednesday meeting)
Tasks: -Using what I learned in the two tutorial videos, create your own opcode using conceptVuforia program given. -Add a joystick control and Autonomous to the Vuforia tracker
Reflections: -In the linear OP mode we copied the original into 2 programs one for autonomous and one for teleop -In the whileOpmodisactive method added motor inputs and puts them to the motors -In the autonomous program we put a while loop to run motors until the distance is less than 600 mm from the target
November 4, 2016 (Monday meeting)
Tasks: -Finish working with vuforia
Reflections: -Today I have finished my gold master vuforia code. I feel very protective of this code so I won't provide images but basically it adds 4 image tracking objects and sets them up to the corresponding images. Also, I am able to get there variables from Vuforia: robotX shows the distance from image, robotY shows the sideways distance from the center, and robotAngle shows the angle relative to the beacon. With these variables given by Vuforia we hope to gain an accurate autonomous
November 5, 2016
Tasks: -Work on the autonomous
Reflections: -Our harware angineers added a SUPER ADVANCED bar that aligns to the height of the beacons. My challenge is to program the robot to hit the right beacon by learning to the correct color first then ramming it to hit the correct button
November 8, 2016
Tasks: -Work on the autonomous
Reflections: -We plan to drive using encoders. Below is a method that drives using encoders -Basically we input Inches and then it uses variables to convert it to encoder ticks. Then we move the motors to the wanted position by adding the wanted position to the current location