ROBOT C CHALLENGE DESIGN DOCUMENT TEAM NAME (SELECT TEAM NAME TO NAVIGATE TO THE TEAM S DESIGN DOCUMENT) Sample Design Document Bolt EVA Lightning RoboGirls Cloud9 Femmebots
SAMPLE ROBOT C DESIGN DOCUMENT ONE ELEMENT_74 Robot C Design Document Specifications: Robot Dimensions: (must be less than 12 x12 x12 ) Length: 10 Width: 9 Height: 10 Pictures of Robot: Main Components: 2 motors (B and C) to drive 1 motor (A) to turn ultrasonic sensor 1 ultrasonic sensor 1 light sensor 2 medium tires with rough tread 1 small grey wheel on back
Programming: Our program directs the robot to follow the following course and end the course with a 360 spin. Note, each square represents a motor time of 1 second. Pseudocode and Code: Pseudocode should be typed up following correct Robot-C procedures (//). Code may be screen shot and pasted in, but should be free from grammar and syntax errors. //start motor a,, //run both for 5.5 s //stop motor a //run motor b for 1.5 s.. Our code and pseudocode in RobotC. Be sure to capture your motor and sensor setup in the image.
FlowChart: Flow charts can be done using any program (lucidchart in google drive recommended) but should follow all rules of flowchart symbols.
Testing: Students will explain the testing of their robot and what modifications they made to improve its speed, accuracy, or attack (BattleBots). This should include physical changes to the robot such as changing the wheels, modifications to the missile/attack arm or even redesigning the robot. It should also include specific changes to the programming. Students should include a data table showing the results of different trials. Trial Time Adjustments 1 17.2 s First successful completion of the course. 2 15.7 s Increased the distance between the sensors to 14cm. 3 14.2 s Decreased the distance between the sensors to 12cm. 4 12.4 s Increased the power on the motors to 80% 5 10.2 s Increased the power on the motors to 90% END SAMPLE
Team Name: BOLT Robot C Design Document Template Specifications: Robot Dimensions: Length:5.5 Height: 5.5 Pictures of Robot: Width:5.5
Main Components: -2 Motors (A AND B) to Drive - 2 medium tires with rough tread - 1 ball and socket -Touch Sensor -Robot C brain start Spin 360+/ End
Brick
Testing So first we did Our 1 st attempt by trying to test If our robot could go straight... turns out our robot went to the right a lot. To Improve this, we simply just changed the track and added wheels instead. This made our robot finally goes straight. For the robot to go to the brick and back up we had to remodel the robot which helped our robot with speed also. Another problem we resolved was that our robot could not turn, so we added more time with the turn. The result of that modification helped made our spin turn right.
Attempt # Result Modifications 1 Went to the right a lot Changed power of left 2 Got to the end of Put wheels instead of tracks straight way 3 Got to brick and backed Change the whole model up 4 Didn t turn Added more time to the turn 5 Got the corner Made it turn right spin
Team: EVA RobotC Design Document: Specifications: Robot Dimensions: (must be less than 12 x12 x12 ) Length: 5 1/2 Width: 6 1/2 Height: 6 Pictures of Robot: Main Components: 2 motors (B and A) to drive 1 light sensor 2 medium tires with rough tread 1 small grey wheel on back Programming: Our program directs the robot to follow the following course and end the course with a 360 spin.
Note, each square represents a motor time of 1 second. Pseudocode and Code: Pseudocode should be typed up following correct Robot-C procedures (//). Code may be screen shot and pasted in, but should be free from grammar and syntax errors. //start motor a,, //run both for 5s //stop motor a //stop motor b //start motor a //turn right //run both for 3s //stop motor a //stop motor b //start motor a //turn right //run both for 1s //stop motor a //stop motor b //start motor a //turn right //run both for 5s //stop motor a //stop motor b //start motor a // turn right // run both for 3s // stop motor a //stop motor b Our code and pseudocode in RobotC. Be sure to capture your motor and sensor setup in the image.
Flowchart: Flow charts can be done using any program (lucid chart in google drive recommended) but should follow all rules of flowchart symbols.
Testing: Students will explain the testing of their robot and what modifications they made to improve its speed, accuracy, or attack (BattleBots). This should include physical changes to the robot such as changing the wheels, modifications to the missile/attack arm or even redesigning the robot. It should also include specific changes to the programming. Students should include a data table showing the results of different trials. Trial Time Adjustments 1 14.5s First successful completion of the course. 2 10.8s Increased the distance between the sensors to 14cm. 3 14.2 s Decreased the distance between the sensors to 12cm. 4 12.4 s Increased the power on the motors to 80% 5 10.2 s Increased the power on the motors to 90%
Team: Lightning Robot C Design Document Specifications: Robot Dimensions: (must be less than 12 x12 x12 ) Length: 7.5 Width: 5 Height: 6in Pictures of Robot: Main Components: 2 motors (B and C) to drive 1 touch sensor (1) 2 medium tires with rough tread 1 small grey wheel on back Programming:
Note, each square represents a motor time of 1 second. First, we will program the robot to move 5 second then turn right. Now start the motor and move for 3 seconds and turn to the left and take 1 second. Then you start the motor again and move to the right and take 5 seconds. Start the motor, turn left and take 3 seconds. Pseudocode and Code: Pseudocode should be typed up following correct Robot-C procedures (//). Code may be screen shot and pasted in, but should be free from grammar and syntax errors. //start motor c, //run both 5 seconds //stop motor b //start motor c for left turn //run motor c 1 second //stop motor b //start motor c //run both for 5 seconds //stop motor b //start motor c for left turn //start motor c,
FlowChart: Testing: Trial Time Adjustments 1 2 3 4 5
Team: Robogirls Robot C Design Document Specifications: Robot Dimensions: (must be less than 12 x12 x12 ) Length:9in Width:7.5 Height:7 Pictures of Robot: Main Components: 2 motors (C and A) to drive 1 motor (B) to open and close the claw 2 medium wheels Programming: The program makes the robot move. It sets the robot's speed. It also tells the robot when to shut off a motor.
Note, each square represents a motor time of 1 second. Pseudocode and Code: //start motor a //run both for 5.5s //stop motor a //run for 1.5s //start motor a //run both for 4s //start motor a //stop motor b //run for 1.5s //start motor a //run both for 3s //stop motor a //run for 1.5s //start motor a //run both for 5.5s //start motor a //run both for 3.5s Our code and pseudocode in RobotC. Commented [AT1]: Use the snipping tool to take a picture of the code you wrote on robotc for the maze above.
FlowChart: Testing: Trial Time Adjustments 1 2 3 4 5
Team: Cloud9 RobotC Design Document: Specifications: Robot Dimensions: (must be less than 12 x12 x12 ) Length: 8 Width: 7 Height: 5 Pictures of Robot: Main Components: 2 motors (B and C) to drive 1 bump sensor 2 large tires with rough tread 1 small grey ball on back Programming: The name of the program is Robot C and we have to insert every program ourselves to make our robot move. We have to program each motor with a certain name as well as type in the exact milliseconds that we want it to move with. Basically our program directs the robot to complete the following course and end the course with a 360 spin.
The robot must complete this course and do a 360 at the end. Pseudocode and Code: Pseudocode should be typed up following correct RobotC procedures (//). Code may be screen shot and pasted in, but should be free from grammar and syntax errors. Our code and pseudocode in RobotC. Be sure to capture your motor and sensor setup in the image.
//start motor c //run both for 3.5 seconds //stop motor b //stop motor c //run both for 2 seconds //stop motor c //run both for 1.5 seconds //start motor c //run both for 5 seconds //repeat until touch //stop motor c //run both for 1.5 seconds //start motor c //run both for 4 seconds //stop motor c //run both for 4 seconds
Flowchart: Testing: Trial Complete/Fai Adjustments l Course 1 Fail First attempt of the course with startup code 2 Fail Decreased right motor to 97 as it kept swerving 3 Fail Changed rotation time to 500 milliseconds to reach the turn 4 Complete First completion of course with 360 5 Complete Double checked my programming to make sure it worked The first time I attempted the course, I failed because my code was way off on turning left and right. So, the second time I corrected the code and I decreased the right motor speed to 97 because the robot was swerving more to the right and I still failed due to the rotation of the robot when turning around the corner. So, I changed the rotation time to 500 milliseconds and this seemed to solve the problem. This change allowed me to reach the end and do a 360 degree spin. The final time I wanted to see if my program worked or if it was just luck. Depending on my placement of my robot it worked when I started the course to the left which made up for the rotation going to the right.
Team: FemmeBots Running Blind: FemmeBots Robot C Design Document Specifications: Robot Dimensions: (must be less than 12 x12 x12 ) Length: 7.5 Width: 5 Height: 7.5 Pictures of Robot: Main Components: 2 motors (B and C) to drive 1 light sensor 2 medium tires with rough tread 1 small grey wheel on back Programming: We did not get to complete the course through Robot C programming.
Pseudocode and Code:, //start motor c, //run both for 2 s //stop motor b //stop motor c //stop for 2 s //run motor b for 1.5 s //run motor b //start motor c //run both for 5.5 seconds //stop motor b //stop motor c
FlowChart: Testing: This is our first time creating a robot and our first time programming. Initially, we worked with some of the boys doing battlebots and they suggested a few designs, but they weren t very helpful ideas to go through a course. We decided to use the instruction manual to create a basic robot structure and added the light sensor. We tried using the program with the buttons, the NXT remote program, and were able to program some basic movements and commands with the robot after watching the tutorials. We attempted a basic course, and were able to complete it in 20.8 seconds after several trials and errors. We found out were actually supposed to use the RobotC program, but didn t know how to use the program. Our teacher helped us learned how to do some basic code, and we were able to connect to the robot and do some basic maneuvers, but were unable to complete a course because we were still struggling with using the RobotC program. We are still working through issues with this and hopefully will be better before the competition. We also ran into an issue with both our controller and one of the motors. One of the motors continued to run even after we turned off the controller and the B and C ports were not communicating with the motors. Trial Time Adjustments 1 20.8 s First successful completion of the course. 2 18.4 s Increased the power on motors to 80% 3 19.7 s Changed programs. 4 Incomplete Rewrote some of the program