DIGITAL TECHNOLOGIES

COMPETITION IN INDUSTRY
PROJECT DETAIL REPORT
TEMPLATE
Team Name:
Team ID:
Application ID:

1
Table of contents
1. REPORT SUMMARY (10 POINTS)..........................................................3
2. TEAM CHART (5 POINTS).....................................................................3
3. PROJECT CURRENT STATUS ASSESSMENT (5 POINTS)........................3
4. VEHICLE DESIGN (40 POINTS).............................................................3
4.1. System Design (10 Points).........................................................................................3
4.2. Mechanical Design of the Vehicle..............................................................................3
4.2.1. Mechanical Design Process (3 Points)...................................................................3
4.2.2. Ingredients (3 Points)..............................................................................................4
4.2.3. Production Methods (2 Points)................................................................................4
4.2.4. Physical Characteristics (2 Points).........................................................................4
4.3. Electronic Design, Algorithm and Software Design....................................................4
4.3.1. Electronic Design Process (3 Points)......................................................................4
4.3.2. Algorithm Design Process (3 Points)......................................................................4
4.3.3. Software Design Process (4 Points).......................................................................4
4.4. External Interfaces (10 Points)...................................................................................5
5. SECURITY (10 POINTS)........................................................................5
6. TEST (5 POINTS).................................................................................5
7. EXPERIENCE (5 POINTS)......................................................................5
8. TIME, BUDGET AND RISK PLANNING (5 POINTS).................................5
9. ORIGINALITY AND LOCALITY (5 POINTS).............................................5
10. COMMERCIALIZATION POTENTIAL (5 POINTS).....................................6
11. BIBLIOGRAPHY (5 Points)....................................................................6

1. REPORT SUMMARY (10 POINTS)----(Ehtesham)

2
 {This section provides a summary of the activities carried out within the scope
of the project}

2. TEAM CHART (5 POINTS)-----(Jareer)

2.1. Team Members
{This section provides information about the team members and the
advisor, if any. (Do not include your name, surname, school and class
information. Just write down the chapter you are reading and your role
in the team.)}

2.2. Organizational Chart and Distribution of Tasks

{This section provides information about the distribution of tasks and
team organization.}

3. PROJECT CURRENT STATUS ASSESSMENT (5

POINTS)----(Ehtesham and Hassaan)
{In this section, the Technical Qualification Form is evaluated. Material and
algorithm changes, if any, made after the Technical Qualification Form and
why the changes were made are explained. In the Technical Qualification
Form, a comparison is made between the planned budget and the final
budget.}

4. VEHICLE DESIGN (40 POINTS)

4.1. System Design (10 Points)------(Sajid and Abdullah J)
{In this section, the block diagram containing the final design of the
vehicle is given in detail.}

4.2. Mechanical Design of the Vehicle

4.2.1. Mechanical Design Process (3 Points)------(Hassaan)

{This section describes the mechanical design processes of the vehicle
step by step. Visuals (technical drawings, prototype photos, etc.) of the
designs made until the final design of the vehicle are included. Explain
why the final design was chosen. Details of the final design are given.
Technical drawing of the final design of the vehicle and post-production
photographs are included.}

4.2.2. Ingredients (3 Points)-----(Ehtesham)

3
 {Describes the materials used in the manufacture of the vehicle
(engines, the frame of the vehicle, etc.), the properties of the materials,
and why they were chosen. Pre-purchased and/or developed/designed
sub-components are specified}

4.2.3. Production Methods (2 Points)------(Ehtesham and

Hassaan)
{Describes the methods used during the production of the vehicle and
why these methods were chosen.}

4.2.4. Physical Characteristics (2 Points)-------(Ehtesham)

{Features of the vehicle, such as dimensions and weight, are included.}

4.3. Electronic Design, Algorithm and Software Design

4.3.1. Electronic Design Process (3 Points)-----(Hassaan)

{This section describes the electronic design processes of the vehicle.
Explain why the final design was chosen. Visuals (block diagram,
technical drawing, prototype photos, etc.) of the designs made until the
final design of the vehicle are included. Information is given about the
materials used (sensors, cameras, cables, motherboard, motor drivers,
power boards, etc.) and explains why it was chosen or how it was
designed. The properties of the materials and why they were chosen
are explained.}

4.3.2. Algorithm Design Process (3 Points)----(Saad)

{ Control/Navigation/Guidance Algorithm Processes:

We have used the PD controller for Line following, an obstacle-

detection method using IR sensors, a Load Cell to monitor the weight of
the load, a QR Code Scanner for QR code scanning and an internally
installed voltmeter to monitor the battery health of the robot throughout
the run. These methods are discussed in details below.

The QTR Analogue sensors send emissions and read their

reflections from the black line forming a numerical way to judge the
current position of the robot. This position is compared to the aimed
position and, depending on how for it is from the aimed position, an
error is calculated. The bigger the error, the larger the gap between the
current and aimed position will be and the robot will adjust the speeds
of its motors and will change them to achieve the desired position. How
fast the robot moves to achieve its desired position is determined by the

4
P-Component of the code which is a constant. The error calculated is
multiplied with this number and then an update is made to the motor
speeds. So, the greater the error, the robot will move towards the line
with a faster speed.
Also, as the robot nears the line its speed begins to decrease to
avoid overshoot and of course unbalanced movements. This uses a
derivative method to check how fast the robot is moving towards the
line and how far it is to the line. This is done by continuously by
calculating the change in the error (Error – Last Error).
This is then multiplied to the D-component of the code and it
contributes to the changing adjustments in the motor speeds as the
robot smoothly steers back on the line perfectly.
We have used this method as it is the single-best way of precise
and accurate way of line following as it can manipulate to run the robot
over almost any line after a 5-seconds calibration. Moreover, it is also
extremely smooth and does not make those typical ‘oscillations’ like the
robots do when using digital data and a few ‘IF Statements’.
This algorithm is however bypassed at times when the robot
detects an obstacle ahead. We have used Sharp IR Sensors in front of
the robot. These are always sending and receiving signals to determine
how close the robot is to the object it’s approaching. When it reaches
the fed distance, the microcontroller commands the motors to apply
brakes. The robot then checks the QR Code and decides whether to lift
or leave the load. Once the required task is done, the robot then steers
away from the obstacle, still keeping distance using the Sharp IR
Sensors, and moves back on to the black line before re-enters the PD
and begins to follow the line as before.
Then, for keeping a check on the weight of the load, we have a
bending load cell. The load cell bends on the side where the load is
applied while the other side remains fixed in one place, generating
resistance which is then converted to digital values and is stored in the
computer as the weight. This way, continuously monitors the weight of
any load and gives an over-load warning once the weight exceeds
125kg..
Also, to keep a check on the battery level, we have installed an
internal voltmeter that continuously measures the battery and keeps
giving the readings to the controller which then compares it with the
given readings. As soon as the reading is lower than 80(in our case),
the robot’s other functions are interrupted and robot is commanded to
go to the charging area and get charged. The battery level is still under
monitoring and as soon as it is full, the robot resumes its primary tasks.
Similarly, whether a load has to be lifted from a particular place or not is
decided by the QR Code on which the robot will scan using a QR Code

5
Scanner. The code will be checked for verification and the required task
will be performed.
So, we have chosen all these algorithms as they seemed to us
the most convenient and powerful. Also, these are the ways used
worldwide in different technological sectors for similar purposes. For
example the load cell can measure thousands of kilograms efficiently
correct to decimal places. The PD controller is the most sophisticated
line following method used in industries where robot are trained to carry
items to-and-fro. A good example could be of Amazon.}

4.3.3. Software Design Process (4 Points)-----(Saad)

{ To configure the Software aspects of our robot, C programming
language was used to code our Algorithm Design structure. Choosing
C language was the result of the many demands of our Software
requirements. It has high speed execution and, more importantly, can
make use of special machine-dependent instructions that is vital
when coding embedded systems like our Industrial Robot. For the GUI
commnication, we have the softeare DGUS which too uses the C
Language. Furthermore the diverse range of libraries available for an
even wider scope of electronic components makes it suitable for our
technical specifications.

The Atmega2560 Microcontroller will be coded in C language to

interact and control with the peripheral units through the Arduino Mega
software for serial communication as outlined in the Algorithm Design
Process (above).

6
 In the Program the following libraries have been used in the sub-
program routines

1) Touch-screen Display library <DWIN.h>

2) XBEE serial wireless communication <XBee.h>
3) Initializing serial communication on digital pins of Arduino
<SoftwareSerial.h> (For Maikrt QR code sensor)
4) Sensor Library <QTRsensors.h>
}

4.4. External Interfaces (10 Points)--------(Jarreer)

{The external interfaces of the vehicle, the sub-components used in
these interfaces, and the message interfaces are described. Information
is given about the interfaces used in the control of the vehicle, the
software used in places such as image and data transfer, and the
selected software languages.}

5. SECURITY (10 POINTS)----(Zakariya)

{In this section, the measures taken to meet the security needs specified in the
competition specifications and the solution methods are explained. Materials
used for safety precautions are indicated.}

6. TEST (5 POINTS)-----(Saad)
{The team has not conducted any physical tasks on the robot so far for testing
it for all of its required capabilities. However, we suerly plan to carry out these
tests very soon in the future as they essential and very helpful to asses
whether the robot requires any furhter work done on it. So here’s our plan for
these tests:

Types of tests Plan

7
 We plan to test different parts of the robot by
putting them under certain harsh conditions to
Robot’s durability test test whether it can withstand heavy loads and
hard collisions(In case they take place).

We plan to check all the sensors that we’ll be

using for their correct values. We’ll do this by
Sensor Working test connecting them to a computer and check their
values in some IDE from a code.

We have planned to thoroughly test the

communicating devices as these are very
Testing communication crucial for the task to run smoothly. So we plan
devices to regularly test these devices by connecting to
our computers

Test

7. EXPERIENCE (5 POINTS)----(Hassaan)
{In this section, information is given about the accidents experienced during
the design, production and testing stages of the vehicle, the mistakes made
and how they were overcome, and the experiences gained.}

8. TIME, BUDGET AND RISK PLANNING (5

POINTS)-----(Zakariya)
{In this section, a time planning, final budget planning and risk planning are
made including the critical design, production and testing processes of the
vehicle.}

9. ORIGINALITY AND LOCALITY (5 POINTS)------

(Jarrer)
{In this section, the original and local aspects of the project/vehicle should be
explained.}

10. COMMERCIALIZATION POTENTIAL (5

POINTS)------(Zakariya)

8
 {In this section, you are expected to make a study for one of the original parts
of the project/vehicle or for the entire project/vehicle according to the headings
below.

 Market Analysis: A detailed analysis of the size, growth potential, and

segmentation of the targeted market.
 Competitor Analysis: Analysis of existing competitors in the market and
evaluation of the competitive environment.
 Marketing Strategy: The marketing strategy of the product or service,
how to reach the target audience, and marketing channels.}

11. BIBLIOGRAPHY (5 Points)-----(Jarreer)

{This section should include the sources used in the report. The layout of the
report will be evaluated together with the bibliography.}

9
 NOTE ON THE REPORT TEMPLATE:

(This page will not be included in the reports.)

 Project Detail Report; It will be a minimum of 15 pages and a maximum of

60 pages, including the Cover, Table of Contents, Bibliography and
Appendices (if any) pages.
 All reports should be written in accordance with academic report
standards.
 Each report should contain 3 separate pages for "Cover, Table of
Contents and Bibliography" headings.
 Font: Arial, Font size: 12, Title font: Arial Black, Title Font: 14, Line
Spacing: 1.15, Justified, Page margins: top-bottom-right-left should be 2.5 .
 The sentences in the report should not be identical and repetitive.
 -Reports pages should be numbered consecutively.
 There is no project introduction video at this stage.
 References in the bibliography can be stated as follows. References used
should be shown in the text. It is recommended to use square brackets in
in-text notation. (e.g. [1], [4,7,21], [5-11])
Digital/Web Reference: Authors' surname, initials of their names, title of the
article, date of the article, access date, access address.
Academic Reference: Authors' Surname, Initial Letter of Their Names,
(Publication Date) Title of the Article, Name of the Journal in which it was
published (if any), Number of the journal (if any), Page number, DOI.
 Project Detail Reports that do not comply with the report template will not be
evaluated.

10