|
Explore TEAMS!
|
Student /
Group3consecutivecommandsTo go back click here --> Lab1GarciaMeslerVuWebster Why is this linked into the Drive Direct Command?? Exceeds two page limit. Why not group data into one table to save space? Please use a leading zero before a decimal, e.g., 1/4 = 0.25, not .25. changes have been made, see below Consecutive Commands And Their SpeedsPurpose: The purpose of this experiment is to calculate the accuracy between consecutive commands. Hypothesis: The create will take 16/64 (0.25) seconds to process consecutive commands. Materials
Procedure:
*152 14 155 5 145 0 200 0 200 155 5 145 0 0 0 0
Results: Time Create Waited-----------------------Time Create Drove (Programed to drive 5 seconds)---Entire Script-----------------------Reaction Time
Calculations and Conclusions: Averages:
-Using all of the averages from above, we can now do our calculations. The number of seconds the entire script took minus the reaction time should equal the number of seconds of the wait time minus the reaction time plus the number of seconds of driving time minus the reaction time. (It is important to subtract the reaction time so that there is as little experimental error as possible.) In numbers: (10.3913-.2083)=(5.2666-.2083)+(5.261-.2083) 10.183=10.1104 Difference in seconds: .0726 In conclusion, the create takes approximately 0.0726 seconds to process consecutive commands. However, this number might be slightly lower due to my reaction times. The create robot is very efficient when processing consecutive commands. Special thanks to -> http://www.online-stopwatch.com/ |