Difference between revisions of "Product Evaluation (Sensors)"

From EG1003 Lab Manual
Jump to: navigation, search
 
(34 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Objectives =
= Objectives =
A robot, which has already been designed for this lab using an EV3 robotics kit,  will be evaluated for accuracy and precision by utilizing two different sets of code, the first without the use of sensors and the second with sensors. The robot will be tested on one of the three provided mini-courses. The data from the product evaluation of both sets of code will determine if the robot should or should not use sensors.
A pre-built robot will be evaluated for accuracy and precision by utilizing two different sets of code, the first without the use of sensors and the second with sensors. The robot will be tested on one of the three provided mini-courses. The data from the product evaluation of both sets of code will determine if the robot should or should not use sensors in navigating the mini-course.


== Product Evaluation ==
== Product Evaluation ==
Line 62: Line 62:


Changes will be implemented after testing the initial code.
Changes will be implemented after testing the initial code.
== Reverse Engineering ==
Reverse engineering software involves reversing a program's machine code to obtain the original source code or determine the file structures the program uses. This  is done when source code is lost or is not available. For example, when a project is reactivated after being dormant for years to add new features to a product, the original design documentation may have been lost. Also, when companies are writing a program that must interface with a second company's software, the second company may not have any incentive to cooperate by describing how the data in the files they use are organized, forcing the first company to deduce it on their own. Sometimes, this process is  used to improve the performance of a program, to fix a bug, or to find a virus. When the source code is obtained in this way for any of these reasons, it is legal and necessary. Reverse engineering software  to copy it constitutes a copy¬right violation and is illegal.<ref name="two">''What Is ''website. TechTarget Network. Retrieved July 29th, 2003.</ref>
Hardware reverse engineering involves taking apart a device to see how it works. If a processor manufacturer wants to see how a competitor's processor works, the company can purchase the processor, disassemble it, and then make a new processor similar to it. In some countries, this process is illegal. Hardware reverse engineering is quite expensive and requires an expert in the field.<ref name="two"></ref>
= Design Considerations =
Carefully consider the lab objectives and what needs to be done to achieve them:
* What made or will make the results, inaccurate or imprecise?
* If the robot failed a test, why did it fail?
== Center of Gravity ==
'''Center of Gravity''' is the place in a system or body (such as a robot) where the weight is evenly distributed and all sides are in balance. An example of the center of gravity is the middle of a seesaw when it is balanced.
You can think of a robot’s center of gravity as the “center position” of all the weight on the robot. Because Center of Gravity uses both weight and position, heavier objects have a greater effect than lighter ones in determining where the center of gravity is. For example, if your robot can collect, hold, and/or manipulate objects, those objects change the center of gravity as they are being manipulated because they add weight.
[[Image:CofG.PNG|frame|center|Figure 2: Change of Center of Gravity because of change of weight of the robot.]]
Likewise, pieces that are farther out have a greater effect than pieces that are near the middle of the robot. So, if your robot has an arm that lifts and/or reaches, its center of gravity changes with that movement.
[[Image:DynamicCG.PNG|frame|center|Figure 3: Change of Center of Gravity because of dynamic parts.]]
== Drivetrain Design ==
The most basic, multi-functional competition robot Drivetrain design consists of:
* A rectangular '''Chassis''' (the structure of a mobile robot that holds wheels, motors, and/or any other hardware used to make up a '''Drivetrain''')
* Two Motors
* Four Wheels
* Gears transmitting Power from the Motors to all Wheels
Drivetrains can come in all shapes and sizes - some don’t provide power to all wheels, use different types of wheels, or are not even a rectangular shape! Whatever the details of your Drivetrain, you should always be aware of a property known as '''Turning Scrub'''.
'''Turning Scrub''' is the friction that resists turning. This friction is created from the wheels dragging sideways on the ground as a robot (or another mobile vehicle) turns. The greater the '''Turning Scrub''' in a '''Drivetrain''', the harder it is for a robot to turn. '''Turning Scrub''' in a basic '''Drivetrain''' can be easily managed and minimized in two ways:
# Make sure that the '''Wheelbase''' (distance between '''Drivetrain''' wheels) is wider (side-to-side) than it is long (front-to-back):
[[Image:Wheelbase.PNG|frame|center|Figure 4: Wheelbase Example.]]
# Use different wheel and/or tire types to reduce the friction of Turning Scrub:
[[Image:Wheels.PNG|frame|center|Figure 5: Different Wheels Example.]]


= EV3 Sensors =
= EV3 Sensors =
Line 149: Line 108:


== Problem Statement ==
== Problem Statement ==
Evaluate two types of code for a robot by creating a line of code without the use of sensors and then a separate line of code using sensors. For each trial, record the distance from the wall and angle of deviation from the center line. Test the first code by running four trials of Section 1 of the mini-course as marked on the physical course. Create a second line of code using switches and loops that incorporate the types of sensors found on the robot and features on the mini-course. Test the robot again with four trials of Section 1. This part of the procedure will have a total of 8 trials. Download the pre-made [[Media:EG_Lab_3_data.xlsx|Datasheet]] and fill in the data for each trial.
Evaluate two types of code for a robot by creating a line of code without the use of sensors, and then a separate line of code using sensors. For each trial, record the distance from the wall and angle of deviation from the center line. Test the first code by running four trials of Section 1 of the mini-course as marked on the physical course. Create a second line of code using switches and loops that incorporate the types of sensors found on the robot and features on the mini-course. Test the robot again with four trials of Section 1. This part of the procedure will have a total of 8 trials. Download the pre-made [[Media:EG_Lab_3_data.xlsx|Datasheet]] and fill in the data for each trial.


== Course Breakdown ==
== Course Breakdown ==
Line 155: Line 114:
[[Image:Course_diagram.PNG|thumb|center|400px|Figure 12: Mini-course.]]
[[Image:Course_diagram.PNG|thumb|center|400px|Figure 12: Mini-course.]]


== Part 1: Reverse Engineering ==
== Part 1: Hardcoding ==
Upon receiving the pre-built robot, selected by the TA, analyze the design and performance of the robot by both physical inspection and basic testing (i.e. '''run the robot at least once to see how it works'''). Run the robot once on the ramp and once on the flat surface in Section 1. There are 5 basic problems in the pre-built robots. The problems are listed below:
Based off of your observations, make design changes to the robot in order to run trials on the first section (Section 1) of the mini-course.
 
# The Center of Gravity of the robot is too high. This will be observed when the robot is tested over the ramp. The high center of gravity does not allow the robot to traverse the hill.
# The incorrect Drivetrain is installed. The tires on the rear wheels of the robot cause excessive traction.
# The Light Sensor is positioned incorrectly. The Light sensor is more than 2 cm above the ground.
# The Gyro Sensor is installed in the incorrect orientation. It has been installed vertically which hinders the functioning of the Gyro.
# The Ultrasonic Sensor is also oriented incorrectly. The Ultrasonic sensor is installed in the z-axis orientation whereas the robot will need the sensor to record data in the x-axis.
 
The fixes for these problems are listed below:
 
# The Connectors connecting the EV3 Brick and the chassis can be shortened to lower the robot.
## Disconnect the Gyro Sensor
## Next remove the angled connectors marked in the picture below:
[[Image:Before.PNG|thumb|center|400px|Figure 13: Robot before modifications.]]
## Next remove the angled connectors marked in the picture below:
[[Image:Before.PNG|thumb|center|400px|Figure 13: Robot before modifications.]]
## Remove the right-angled connectors shown below:
[[Image:Before.PNG|thumb|center|400px|Figure 13: Robot before modifications.]]
## Connect a 7-hole connector to the square frame labelled in the picture below using the blue arrow:
[[Image:Before.PNG|thumb|center|400px|Figure 13: Robot before modifications.]]
## Connect the right-angled lego pieces as shown in the picture above using red arrows.
# The Tires can be attached to the rear wheels which will provide enough traction for a proper turn.
# The Light Sensor can be moved to a different mounting position to make it closer to the ground.
# The Gyro Sensor can be flipped to make it horizontal.
## Connect it as shown in the picture below:
[[Image:Before.PNG|thumb|center|400px|Figure 13: Robot before modifications.]]
# The Ultrasonic Sensor can be oriented so that it’s horizontal instead of diagonal. This will be achieved when the Center of Gravity is brought down.
 
[[Image:After_side_view.PNG|thumb|center|400px|Figure 14: Robot side view after modifications.]]
 
[[Image:After_front_view.PNG|thumb|center|400px|Figure 15: Robot front view after modifications.]]
 
== Part 2: Hardcoding ==


'''Every run, unless the robot goes off the course, counts as a trial. There is only one test run allowed after which all runs will be recorded as trials.'''
'''When troubleshooting the code, please cross check the port number on the code and the port the sensor/motor is connected to before anything else.'''
=== Product Evaluation ===
=== Product Evaluation ===
Using the modified design, conduct four trials of the robot using a code without sensors to travel in a straight line across the first four tiles, turn 90 degrees to the right, and stop 5 cm from the wall. '''The values used in the sections of code below are only examples - the actual values must be determined through experimentation.'''
Using the modified design, conduct four trials of the robot using a code without sensors to travel in a straight line across the first four tiles, turn 90 degrees to the right, and stop 5 cm from the wall. '''The values used in the sections of code below are only examples - the actual values must be determined through experimentation.'''
   
   
# Start the '''Mindstorms EV3''' software
# Start the '''Mindstorms EV3''' software.
# Click on the '''+''' in the top left corner to open up a blank program
# Download the [[Media:Lab_3_Product_Evaluation.zip|zipped folder]] containing the Mindstorms program.
#: [[Image:Lab evalimprov ev3 2.png|thumb|center|500px|Figure 16: Mindstorms screen.]]
# The hardcoding program should look like the one pictured below: [[Image:Hardcode_2018.png|thumb|center|700px|Figure 17: Part 1 Code]]
# The screen is shown in Figure 9. The program begins with the '''Start''' block
# Please read the comments before running the program.
#: [[Image:Lab evalimprov ev3 3.png|thumb|center|500px|Figure 17: Start block.]]
# Change the ports to the configuration on your robot.
# Place a '''Steering''' block from the '''Action''' palette next to the '''Start''' block (Figure 10). Set the '''Port''' to reflect both motors plugged into the brick; '''both ports have to be correct'''
# Run a sample trial to understand the code.
#: [[Image:Steering_block.PNG|thumb|center|640px|Figure 18: Steering block.]]
# Evaluate the number of rotations by measuring the total distance that the robot has to move for a certain block of code and divide that by the perimeter of the wheel.
# Along the bottom of the Steering block, there are four options. On the left, there is a Mode Selector button followed by three values for the input parameters picture above the value from left to right, Power, Rotations, and Brake at End
# Change the values to the evaluated numbers.
#: [[Image:Steering_options.PNG|thumb|center|640px|Figure 19: Steering block mode.]]
# Try to stop 5cm before the wall.
# Change the type of the '''Steering''' block to '''On for Seconds'''. This will change the '''Rotations''' input parameter to '''Seconds'''
# Run the program for four trials. For each trial, record the distance and angle using pre-made markings on the sides of the tile.
#: [[Image:Steering_seconds.PNG|thumb|center|640px|Figure 20: Steering block rotations' menu.]]
# Distance is measured as the distance from the wall for which the ruler on the side of the tile can be used. (Denote it as y)
# Add a '''Steering''' or '''Tank''' block to turn the robot to the right 90 degrees. Then add another ''Steering'' block to travel straight until it is 5 cm away from the wall.  
# Angle of deviation is calculated in the following way:
#: [[Image:Harcode_straight_turn.PNG|thumb|center|640px|Figure 21: Final code for hardcoded trials.]]
## Measure deviation from the center of the wall. (Denote it as x)
# Test different values of '''Power''' and '''Seconds''' to find the best settings to travel the first four tiles of the course, turn to the right, and stop five '''cm''' from the wall. When the optimal settings are found, alert the TA and run the program. Run the program for four trials. For each trial, record the distance and angle using the pre-made markings on the sides of the tile. Distance is measured as distance from the wall and angle of deviation is calculated from measuring deviation from the center of the wall and distance from the edge of the tile opposite from the wall. '''If you are confused as to how to calculate angle of deviation, ask your TA for help.'''
## tan^-1 (x/y)
## '''If you are confused as to how to calculate the angle of deviation, ask your TA for help.'''


== Part 3: Sensors ==
== Part 2: Sensors ==
'''Every run, unless the robot goes off the course, counts as a trial. There is only one test run allowed after which all runs will be recorded as trials.'''
'''When troubleshooting the code, please cross check the port number on the code and the port the sensor/motor is connected to before anything else.'''
=== Quality Improvement ===
=== Quality Improvement ===
Using the results of the original robot, incorporate the use of sensors in the robot's code. The following steps outline how to build a line-following code for the robot to stay on track. '''The values used in the sections of code below are only examples; the actual values must be determined through experimentation.'''
Using the results of the original robot, incorporate the use of sensors in the robot's code. The following steps outline how to build a line-following code for the robot to stay on track. '''The values used in the sections of code below are only examples; the actual values must be determined through experimentation.'''
# Click on the '''+''' in the top left corner to open up a blank program.
# Move to the Software Trials tab
# Insert a blank '''Loop'''. Insert a '''Switch''' within the loop.
# The program should look like this: [[Image:Sensors_Code_2018.png|thumb|center|800px|Figure 18: Software Trials Code]]
#: [[Image: Loop_switch.PNG|thumb|center|640px|Figure 22: Code for light sensor.]]
# Please read the comments before running the program
# Set the input of the switch to a '''Light Sensor''' and the type to '''Reflected Light Intensity'''. Set the comparison to the “greater than” symbol and use '''Port View''' on the EV3 brick to measure the light intensity of the line. Set the value of the light intensity to the value displayed by '''Port View''' (not the value seen in the image below)
# Change the ports to the configuration on your robot
#: [[Image: Port_view.PNG|thumb|center|640px|Figure 23: Light sensor output.]]
# Run a sample trial to understand the code
# In the top half of the switch, insert two Move Motor blocks. Set one to stop and one to continuously moving. Duplicate this in the bottom half, but switch the ports. This way one wheel will move while the other is stationary, which will make the robot wiggle along the line
# Using the port view shown below, set the readings on the Mindstorms code for the light sensors and the gyro sensors blocks to the appropriate values. Adjust Rotations as done in the previous part. '''Ask a TA for assistance if you don't know what values to use.''' [[Image: Port_view.PNG|thumb|center|640px|Figure 19: Port view]]
#: [[Image:Lab_sensorsev3_26.png|thumb|center|640px|Figure 24: Move motor code.]]
# Take the same measurements as for Part 1: Harcoding
# Each time the '''Gyro Sensor''' is used, it has to be reset in order to set the direction the robot is facing before turning as zero. Insert a '''Gyro Sensor''' block and set it to reset:
# Tabulate results neatly in the Datasheet
#: [[Image:Gyro_sensor_reset.PNG|thumb|640px|center|Figure 25: Gyro Sensor Reset]]
# Insert a '''Wait''' block right after the gyro reset. Set it to 2 seconds.
#: [[Image:Gyro_wait.PNG|thumb|640px|center|Figure 26: Wait Block]]
# In order for the robot to continue turning until 90 degrees is reached, a '''Loop''' must be used to constantly run the robot until the gyro sensor reads 90 degrees. Insert a loop after the wait block and set the end condition to be activated by the gyro sensor using '''Measure''' and '''Angle'''. Change the comparison to '''Greater Than''' and the value of the angle to '''90''' degrees.
#: [[Image:Gyro_code_1_revised.PNG|thumb|640px|center|Figure 27: Gyro Sensor as End Statement]]
# Insert a '''Motor''' block into the loop. Select the port that when activated will turn the robot to the right. Change the '''Motor''' type to '''Rotations''' and '''.05''' rotations. This translates to the robot moving in .05 rotation increments until the gyro sensor reads 90 degrees:
#: [[Image:Lab3_gyroturn_revised.PNG|thumb|640px|center|Figure 28: Turning Program]]
# Add the gyro code to the end of the line following code. Insert a new loop and '''Steering''' block inside the loop for the robot to travel straight. Use either rotations or time to move the robot. Set the loop's end statement to be controlled by the ultrasonic sensor
#: [[Image:Gyro_code_complete_revised.PNG|thumb|640px|center|Figure 29: Turning Program Continued]]
# Use the '''Ultrasonic Sensor''' to make the robot stop '''five cm away from the first wall'''. Set the end statement of the loop to be controlled by the '''Ultrasonic Sensor''' and set the type to '''Distance Centimeters''' for five cm. The completed code for the first section should look like the code below
#: [[Image:Loop_options.PNG|thumb|center|500px|Figure 30aa: Ultrasonic sensor options]]
#: [[Image:Final_code.png|thumb|center|800px|Figure 30b: Final code for Section 1]]
# Take the same measurements as for Part 1: Hardcoding and tabulate results neatly in the Datasheet.


== Tabulation of Results ==
== Tabulation of Results ==
Line 252: Line 171:
|}
|}


== Part 4: Robot Competition ==
== Part 3: Robot Competition ==
The robot competition consists of a single trial of the entire course to travel the most tiles as possible. '''Again, the values used in the sections of code below are only examples - the actual values must be determined through experimentation.''' The averages from the best type of coding (Part 1 vs Part 2) are also used to calculate the competition ratio.
The robot competition consists of a single trial of the entire course to travel the most tiles as possible. '''Again, the values used in the sections of code below are only examples - the actual values must be determined through experimentation.''' The averages from the best type of coding (Part 1 vs Part 2) are also used to calculate the competition ratio.
=== Procedure ===
=== Procedure ===
Line 258: Line 177:


# Recreate the line following code to allow the robot to travel up the ramp. Test different values of power to overcome the ramp. The end statement should cause the robot to stop '''10 cm''' away from the wall.
# Recreate the line following code to allow the robot to travel up the ramp. Test different values of power to overcome the ramp. The end statement should cause the robot to stop '''10 cm''' away from the wall.
#: [[Image:Section_2_complete_revised.PNG|thumb|640px|center|Figure 31: Full Competition Code]]
# Notice that everything until the second loop is a replica of the Software Trial code. You only have to add the last loop. '''Ask a TA for assistance if you don't know how to do it.'''
#: [[Image:Section_2_complete_revised.PNG|thumb|640px|center|Figure 20: Full Competition Code]]


===Competition Rules===
===Competition Rules===
Line 280: Line 200:
* Discuss product evaluation and the need for it
* Discuss product evaluation and the need for it
* Discuss quality improvement and its importance
* Discuss quality improvement and its importance
* Explain why reverse engineering is important
* Include examples of product evaluation and quality improvement
* Include examples of product evaluation, quality improvement, and reverse engineering
* Discuss a standard, an average, accuracy, and precision
* Discuss a standard, an average, accuracy, and precision
* Discuss Different Design Considerations
* Describe the importance of Center of Gravity and Drivetrain
* Describe loops and switches and how they are useful in coding
* Describe loops and switches and how they are useful in coding
* Describe the light sensor, gyro sensor, and ultrasonic sensor used in the lab and their optimal position
* Describe the light sensor, gyro sensor, and ultrasonic sensor used in the lab and their optimal position
* Discuss the importance of tolerance and %Acc in determining product quality
* Discuss the importance of tolerance and percent accuracy in determining product quality
* Discuss the EV3 kit and software used
* Discuss the EV3 kit and software used
* Describe Mindstorms programming for '''only the sensors coding portion'''
* Describe Mindstorms programming for '''only the sensors coding portion'''
* Describe all robot modifications
* Compare the final code with sensors and final code without sensors; determine which is better. * * Substantiate the decision with data, observations, and other facts collected
* Compare the final code with sensors and final code without sensors; determine which is better. * * Substantiate the decision with data, observations, and other facts collected
* Make a final evaluation of the product: should it go into production? Describe its accuracy and precision
* Make a final evaluation of the product: should it go into production? Describe its accuracy and precision

Latest revision as of 17:22, 24 August 2019

Objectives

A pre-built robot will be evaluated for accuracy and precision by utilizing two different sets of code, the first without the use of sensors and the second with sensors. The robot will be tested on one of the three provided mini-courses. The data from the product evaluation of both sets of code will determine if the robot should or should not use sensors in navigating the mini-course.

Product Evaluation

Product evaluation is a common task for an engineer and for companies. Sometimes the product evaluated will be a company's product, and sometimes companies will be evaluating a competitor's design. In either case, this evaluation will use a standard (an accepted value), determine an average, and calculate accuracy and precision. [1]

Professional engineers must be sure of standards. For the purpose of this lab, the EG1003 standard will be 80% precision and accuracy. This means that the product has to achieve a percent accuracy of 80% and meet a tolerance of 1cm for distance and 10 degrees for angle. [1]

When taking measurements, the first step is to determine an average (Equation 1).

Equation 1: Average.

In this equation, Ap is the average, P1, P2, P3, ..., Pn are the results of the tests, and N is the number of tests performed.

The average is compared to the standard. Accuracy is a variable the must always be considered. The degree of accuracy required will allow the results to be verified. Engineers often work on projects that affect people's safety so it is critical that the solutions to the problems solved by technical professionals are accurate.

The comparison of the average to the standard is called accuracy, defined as Acc in Equation 2.

Equation 2: Accuracy.

In Equation 2, Ps is the standard value, and Ap is the value measured. Accuracy is always a positive number, so use the absolute value in case Ps is less than Ap.

Precision is the repeatability of a result, or how close the results are to each other, defined as Prec in Equation 3.

Equation 3: Precision.

In Equation 3, Prec is precision, Phigh is the highest data value and Plow is the lowest data value. Like accuracy, precision is always a positive number, so use an absolute value here as well.

A product can be accurate but imprecise, or precise but inaccurate (Figure 1). The goal is to achieve a combination of the highest accuracy and precision. In order for engineers to make a recommendation based on experimental test data, it is important to determine how a product compares to a standard. Engineers need these benchmarks to determine the quality of a product.

Figure 1: Accuracy and precision.

By determining the percent accuracy of an experiment, and comparing this percentage to a standard, it can be determined, based on experimental evidence, if the product has passed or failed. The equation for percent accuracy is:

Equation 4: Percent accuracy.

In Equation 4, %Acc is the percent accuracy, Ps is the standard value, and Ap is the value measured.

Precision shows how precise a product is compared to the standard.

Adequate precision is determined by an acceptable tolerance, set by the manufacturer. In this lab, the precision of the robot must be compared to the tolerance allowed:

Distance Test:
Angle of Deviation Test:

Calculating percent accuracy and precision and then comparing those results to a standard determines the quality of the product.

Quality Improvement

Quality improvement is a process of analyzing a design and testing it through physical modeling, computer simulation, or mathematical modeling. Quality improvement ensures that a product will perform as expected and allows improvements to be made to the design.

When deciding how to improve the design in this lab, keep these questions in mind:

  • Does the robot perform to standard?
    • If no, what can be done to improve its functionality?
    • If yes, what can be done to improve its performance beyond the standard?

Changes will be implemented after testing the initial code.

EV3 Sensors

Sensor Basics

A sensor is a device that measures a specific value and is used as an input. Different properties can be measured by the EV3 sensors, such as light intensity, angle, or distance. The three sensors used in this lab are the light sensor, gyro sensor, and an ultrasonic sensor.

Light Sensor

The light sensor or color sensor (Figure 6) can measure reflected light intensity, color, and ambient light, and is useful when the robot has the option to follow a line or use differences in color to perform different actions, such as stopping when detecting a different color. If measuring color, the sensor outputs a value (0-7) that corresponds to a specific color. Measuring reflected light outputs a value (0-100) depending on the intensity of the light that is reflected. The ambient light works the same way as the reflected light, except it measures only the surrounding light. The light sensor, as well as all other sensors, can be found in the yellow category the Mindstorms software. The light sensor should be placed so that it is 2 cm, at max, away from whatever it trying to record.

Figure 6: Light sensor.

The type of value the sensor can measure can be changed by clicking the small box on the bottom left of the block (Figure 7).

Figure 7: Light sensor, value input.

Gyro Sensor

The gyro sensor can measure the degrees it turns or the rate at which it is turning. For example, if the robot is set to turn 90º using the gyro, the robot will keep trying to turn until 90º is reached, regardless of any bumps in its way (Figure 8). The gyro sensor should be placed parallel to the plane of the EV3 Brick.

Figure 8: Gyro sensor.


Ultrasonic Sensor

The ultrasonic sensor measures the distance between the robot and the closest object to it. It can measure distance in both centimeters and inches; the recommended range is 1 cm to 250 cm (Figure 9).

Figure 9: Ultrasonic sensor.

Switches and Loops

Switches and loops are used to tell the robot what actions to perform depending on the inputs from its surroundings, measured by the sensors.

Switch

A switch is an “if-else” statement: if the initial condition is true, the top action will occur, if false, the bottom action will occur. This block is used when the robot has to perform different actions depending on the input from the sensors (Figure 10).

Figure 10: Switch.

Loop

A switch will only run the code once, so if repeated action is desired, a loop must be used to repeat the switch’s statement. A loop continuously runs the code until the end statement occurs. The end statement can be determined with a sensor or hard-coded to a specific duration or rotations. Figure 11 shows an infinite loop.

Figure 11: Loop.

Materials and Equipment

  • A Mindstorms kit with pre-made robot
  • A computer with Mindstorms software
  • A mini-course with accuracy markings

Procedure

Problem Statement

Evaluate two types of code for a robot by creating a line of code without the use of sensors, and then a separate line of code using sensors. For each trial, record the distance from the wall and angle of deviation from the center line. Test the first code by running four trials of Section 1 of the mini-course as marked on the physical course. Create a second line of code using switches and loops that incorporate the types of sensors found on the robot and features on the mini-course. Test the robot again with four trials of Section 1. This part of the procedure will have a total of 8 trials. Download the pre-made Datasheet and fill in the data for each trial.

Course Breakdown

The mini-course (Figure 12) has a designated Section 1 to complete the eight trials of the lab: one flat straight section of four tiles and a right turn with a wall at the end. The competitive trial will utilize the entire course. In Figure 8, Section 1 is marked in red.

Figure 12: Mini-course.

Part 1: Hardcoding

Based off of your observations, make design changes to the robot in order to run trials on the first section (Section 1) of the mini-course.

Every run, unless the robot goes off the course, counts as a trial. There is only one test run allowed after which all runs will be recorded as trials. When troubleshooting the code, please cross check the port number on the code and the port the sensor/motor is connected to before anything else.

Product Evaluation

Using the modified design, conduct four trials of the robot using a code without sensors to travel in a straight line across the first four tiles, turn 90 degrees to the right, and stop 5 cm from the wall. The values used in the sections of code below are only examples - the actual values must be determined through experimentation.

  1. Start the Mindstorms EV3 software.
  2. Download the zipped folder containing the Mindstorms program.
  3. The hardcoding program should look like the one pictured below:
    Figure 17: Part 1 Code
  4. Please read the comments before running the program.
  5. Change the ports to the configuration on your robot.
  6. Run a sample trial to understand the code.
  7. Evaluate the number of rotations by measuring the total distance that the robot has to move for a certain block of code and divide that by the perimeter of the wheel.
  8. Change the values to the evaluated numbers.
  9. Try to stop 5cm before the wall.
  10. Run the program for four trials. For each trial, record the distance and angle using pre-made markings on the sides of the tile.
  11. Distance is measured as the distance from the wall for which the ruler on the side of the tile can be used. (Denote it as y)
  12. Angle of deviation is calculated in the following way:
    1. Measure deviation from the center of the wall. (Denote it as x)
    2. tan^-1 (x/y)
    3. If you are confused as to how to calculate the angle of deviation, ask your TA for help.

Part 2: Sensors

Every run, unless the robot goes off the course, counts as a trial. There is only one test run allowed after which all runs will be recorded as trials. When troubleshooting the code, please cross check the port number on the code and the port the sensor/motor is connected to before anything else.

Quality Improvement

Using the results of the original robot, incorporate the use of sensors in the robot's code. The following steps outline how to build a line-following code for the robot to stay on track. The values used in the sections of code below are only examples; the actual values must be determined through experimentation.

  1. Move to the Software Trials tab
  2. The program should look like this:
    Figure 18: Software Trials Code
  3. Please read the comments before running the program
  4. Change the ports to the configuration on your robot
  5. Run a sample trial to understand the code
  6. Using the port view shown below, set the readings on the Mindstorms code for the light sensors and the gyro sensors blocks to the appropriate values. Adjust Rotations as done in the previous part. Ask a TA for assistance if you don't know what values to use.
    Figure 19: Port view
  7. Take the same measurements as for Part 1: Harcoding
  8. Tabulate results neatly in the Datasheet

Tabulation of Results

All data must be inputted into the Datasheet. From the datasheet, determine if the EG standards were met for accuracy and precision; recorded precision must be divided by 2 to get the corresponding tolerance:

Hardcode Accuracy %Acc Pass/Fail Precision Tolerance Pass/Fail
Distance Test
Angle of Deviation Test


Sensors Code Accuracy %Acc Pass/Fail Precision Tolerance Pass/Fail
Distance Test
Angle of Deviation Test

Part 3: Robot Competition

The robot competition consists of a single trial of the entire course to travel the most tiles as possible. Again, the values used in the sections of code below are only examples - the actual values must be determined through experimentation. The averages from the best type of coding (Part 1 vs Part 2) are also used to calculate the competition ratio.

Procedure

The robot competition consists of attempting to travel the most amount of tiles possible in a single run. Only one trial counts as valid and must verbally be declared before the run starts.

  1. Recreate the line following code to allow the robot to travel up the ramp. Test different values of power to overcome the ramp. The end statement should cause the robot to stop 10 cm away from the wall.
  2. Notice that everything until the second loop is a replica of the Software Trial code. You only have to add the last loop. Ask a TA for assistance if you don't know how to do it.
    Figure 20: Full Competition Code

Competition Rules

  1. Only parts provided in the EV3 kits are allowed (no regular Lego's)
  2. No changes in physical robot design
  3. No "re-tests"
  4. The trial used for the competition must be declared before the robot runs and cannot be disputed
  5. A robot counts as clearing a tile if it stops on the tile with at least 50% of the robot on the tile

Competition Ratio

The team with the highest competition ratio wins the competition. Adistance is the robot's average distance from the wall for four trials, Aangle is the robot's average angle of deviation for four trials, and Ntiles is the number of tiles cleared during the single competition run:

The lab work is now complete. Please clean up the workstation. Return all unused materials to the TA. Refer to the Assignment section for the instructions needed to prepare the lab report.

Assignment

Individual Lab Report

Follow the lab report guidelines laid out in the page called Specifications for Writing Your Lab Reports in the Technical Communication section of this manual. The following points should be addressed in the appropriate section of the lab report.

  • Discuss product evaluation and the need for it
  • Discuss quality improvement and its importance
  • Include examples of product evaluation and quality improvement
  • Discuss a standard, an average, accuracy, and precision
  • Describe loops and switches and how they are useful in coding
  • Describe the light sensor, gyro sensor, and ultrasonic sensor used in the lab and their optimal position
  • Discuss the importance of tolerance and percent accuracy in determining product quality
  • Discuss the EV3 kit and software used
  • Describe Mindstorms programming for only the sensors coding portion
  • Compare the final code with sensors and final code without sensors; determine which is better. * * Substantiate the decision with data, observations, and other facts collected
  • Make a final evaluation of the product: should it go into production? Describe its accuracy and precision
  • Assess the techniques used in the testing process
  • Discuss better testing methods for the robot design
  • Recommend if any design improvements should be made

Remember: Lab notes must be taken. Experimental details are easily forgotten unless written down. EG1003 Lab Notes Paper can be downloaded and printed from the EG1003 Website. Use the lab notes to write the Procedure section of the lab report. At the end of each lab, a TA will scan the lab notes and upload them to the Lab Documents section of the EG1003 Website. One point of extra credit is awarded if the lab notes are attached at the end of the lab report. Keeping careful notes is an essential component of all scientific practice.

Team PowerPoint Presentation

Follow the presentation guidelines laid out in the page called EG1003 Lab Presentation Format in the Introduction to Technical Presentations section of this manual. When preparing the presentation, consider the following points:

  • Based on the test results, what is the product's marketability?
  • If determinations were that the robot(s) did not meet the standard, what improvements could be made?
  • Why is product evaluation important?
  • Discuss why quality improvement is important
  • Discuss the importance of utilizing sensors
  1. ^ a b Oakes, W.C., L.L. Leone, and C.G. Gunn, Engineering Your Future, MI: Great Lakes Press, 2002.