Recent Changes - Search:

TEAMS Academy Wiki

Explore TEAMS!
for visiting sophomores & juniors

Robotics

EnvBioTech

Bat Design

Assistive Tech


Students


Instructors

TEAMS Forum

TEAMS Calendar

TEAMS Web Site

Wiki Info

edit Student.SideBar

Group3consecutivecommands

To 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 Speeds

Purpose:

 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

  • Create Robot
  • Real Term
  • Connection cables
  • Number converter
  • Stopwatch

Procedure:

  1. Using Real Term, make a script command, have the create wait for five seconds, drive (drive direct) for five seconds, and stop.
   *152 14 155 5 145 0 200 0 200 155 5 145 0 0 0 0 
  1. Using the Stop watch, time how long it takes for the robot to start. Repeat this and take the average time it took for the robot to start.
  2. Repeat above but this time use the stopwatch to time the robot's driving time. Again, take the average time.
  3. This time, use the stopwatch to time the entire script and average the times.
  4. Now test your accuracy with the stop watch. Stop the stopwatch when it reaches 5 seconds and record the amount you were off. Once more, take the average error.

Results:

Time Create Waited-----------------------Time Create Drove (Programed to drive 5 seconds)---Entire Script-----------------------Reaction Time

TrialSeconds TrailSeconds TrialSeconds TrialSeconds
15.150-----14.703----------110.150-----10.320
24.891-----25.156----------210.940-----20.156
36.049-----35.780----------310.110-----3-0.985
45.109-----45.109----------410.940-----40.187
55.359-----55.780----------510.630-----50.188
65.468-----65.150----------610.125-----60.172
754.953-----75.109----------710.109-----70.940
85.250-----85.157----------810.160-----80.790
95.203-----95.047----------910.780-----90.310
105.234-----105.630----------109.969-----100.000
           
Total52.666 Total52.61 Total103.913 ------
Average5.266 Average5.261 Average10.391 Average0.2083

Calculations and Conclusions:

  Averages:
  • Entire script: 10.3913
  • Driving time: 5.261
  • Wait time: 5.2666
  • Reaction time: 0.2083

-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/

Edit - History - Print - Recent Changes - Search
Page last modified on October 07, 2007, at 03:00 PM