PRE2017 4 Groep6: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
(Created page with 'The patent on remote control systems granted to Mitsubishi Electric Crop. By the US government. This document is a thorough description of how remote control systems work, if we …')
 
No edit summary
Line 1: Line 1:
== Group members ==
* David van den Beld, 1001770
* Gerben Erens, 0997906
* Luc Kleinman, 1008097
* Maikel Morren, 1002099
* Adine van Wier, 0999813
== Project ==
=== Project Statement ===
=== Planning ===
Below follows the planning for the project for the upcoming 9 weeks constituting the course 0LAUK0 Project: Robots Everywhere
{| class="wikitable" style="text-align: left; color: black"
|+ '''Table 1: Preliminary planning for the project'''
! Week number
! Task
! Person<sup>*</sup>
|-
| 1
|
|
|-
|
| Choose definitive subject
| Collaborative effort of all members
|-
|
| Define problem statement and objectives
| David
|-
|
| Define users
| Adine
|-
|
| Obtain user requirements
| Gerben
|-
|
| Work out typical use cases
| Luc
|-
|
| Define the milestones and deliverables
| Maikel
|-
|
| Define the approach of the problem
| Collaborative effort of all members
|-
|
| Search for relevant state-of-the-art (SotA) sources, categories: <br>
1. Modularity <br>
2. (Semi-) Autonomous cars <br>
3. Sensors for prospecting/evaluating ground <br>
4. Drilling/plowing/seeding mechanism <br>
5. Current Forestation combat methods <br>
| All divided into the subcategories: <br>
1. Maikel <br>
2. David <br>
3. Luc <br>
4. Gerben <br>
5. Adine <br>
|-
|
| Make project planning
| Collaborative effort of all members
|-
| 2
|
|
|-
|
| Review user requirements and use cases
| Collaborative effort of all members
|-
|
| Finish collecting SotA articles and write SotA section
| Each member for their respective subcategory
|-
|
| Compile list of potential robot designs
| Collaborative effort of all members
|-
|
| Make some concept design sketches
| Maikel
|-
|
| Make a preliminary list of required parts
| Gerben
|-
|
| Define embedded software environment
| Luc
|-
|
| Preliminary elimination session for designs based on user requirements
| Adine
|-
|
| Start compiling list of design preferences/requirements/constraints
| David
|-
| 3
|
|
|-
|
| Finish list of preferences/requirements/constraints
| Adine
|-
|
| Further eliminate designs due to constraints
| Collaborative effort of all members
|-
|
| Rank remaining designs and select a winner
| Collaborative effort of all members
|-
|
| Develop a building plan/schemata for the winner design
| Gerben, Luc
|-
|
| Start acquiring physical quantities for modelling design
| Maikel, David
|-
|
| Start with a simple model of some system parameters
| Maikel, David
|-
| 4
|
|
|-
|
| Commence robot assembly according to highest priority of building schemata
| Gerben, David
|-
|
| Continue modelling/simulating
| Maikel
|-
|
| Start coding robot functionalities
| Luc
|-
|
| Catch up on documenting the wiki
| Adine
|-
| 5
|
|
|-
|
| Continue robot assembly and coding
| Gerben, David, Luc
|-
|
| Continue modelling/simulating
| Maikel
|-
|
| Catch up on documenting the wiki
| Collaborative effort of all members
|-
| 6
|
|
|-
|
| Continue robot assembly and coding
| Gerben, Luc
|-
|
| Test the first (few) finished sub-system(s) of the robot.
| Collaborative effort of all members
|-
|
| Finish modelling/simulating
| Maikel, David
|-
|
| Finish catching up on documenting the wiki
| Collaborative effort of all members
|-
| 7
|
|
|-
|
| Finish robot assembly
| Gerben
|-
|
| Make concept designs for possible modules
| Luc
|-
|
| Make a draft for final presentation
| Maikel, David, Adine
|-
|
| Test the first (few) finished sub-system(s) of the robot.
| Collaborative effort of all members
|-
| 8
|
|
|-
|
| Buffer time
| Collaborative effort of all members
|-
|
| Finish final presentation
| Maikel, David, Adine
|-
|
| Complete wiki
| Gerben, Luc
|}
<sup>*</sup> The current division of task is a rough estimate for the next 7 weeks. New tasks may pop up or task division may be rotated, and is hence subject to change during the progress of the course.
=== Approach ===
The problem will be approached by a design question. What is the best design for a robot to combat deforestation which will be build modular so that it can be implemented for other purposes with minor changes. The first 2 weeks the approach will primarily be sequential, as user analysis, use cases and requirements/preferences/constraints need to be done sequentially before the rest of the project can start. Once this is over, the project will run in a parallel fashion where building and modelling will happen simultaneously.
=== Milestones and Deliverables ===
{| class="wikitable"
|+ '''Table 2: Milestones'''
|-
! Date
! Accomplished
|-
| 30-04-2018
| SotA research done
|-
| 03-05-2018
| User analysis/use cases done
|-
| 07-05-2018
| Have a partially eliminated list of designs
|-
| 10-05-2018
| Pick final “winner” design
|-
| 21-05-2018
| Have the first working subsystem
|-
| 25-05-2018
| Finish modelling
|-
| 31-05-2018
| Have an operational prototype running <br> with at least 2 subsystems
|-
| 07-06-2018
| Made several concepts for modules
|-
| 11-06-2018
| Presentation is finished
|-
| 14-06-2018
| Wiki is completely updated
|}
== Literature Review ==
The patent on remote control systems granted to Mitsubishi Electric Crop. By the US government. This document is a thorough description of how remote control systems work, if we decide to make our vehicle remote controlled all the info we need is in here. But it is incredibly lengthy and written in a way that is not pleasant to read, so use it as a last resort. https://patentimages.storage.googleapis.com/eb/4b/ce/ba560b94ae5c1a/US5554980.pdf  
The patent on remote control systems granted to Mitsubishi Electric Crop. By the US government. This document is a thorough description of how remote control systems work, if we decide to make our vehicle remote controlled all the info we need is in here. But it is incredibly lengthy and written in a way that is not pleasant to read, so use it as a last resort. https://patentimages.storage.googleapis.com/eb/4b/ce/ba560b94ae5c1a/US5554980.pdf  


Revision as of 12:44, 28 April 2018

Group members

  • David van den Beld, 1001770
  • Gerben Erens, 0997906
  • Luc Kleinman, 1008097
  • Maikel Morren, 1002099
  • Adine van Wier, 0999813

Project

Project Statement

Planning

Below follows the planning for the project for the upcoming 9 weeks constituting the course 0LAUK0 Project: Robots Everywhere

Table 1: Preliminary planning for the project
Week number Task Person*
1
Choose definitive subject Collaborative effort of all members
Define problem statement and objectives David
Define users Adine
Obtain user requirements Gerben
Work out typical use cases Luc
Define the milestones and deliverables Maikel
Define the approach of the problem Collaborative effort of all members
Search for relevant state-of-the-art (SotA) sources, categories:

1. Modularity
2. (Semi-) Autonomous cars
3. Sensors for prospecting/evaluating ground
4. Drilling/plowing/seeding mechanism
5. Current Forestation combat methods

All divided into the subcategories:

1. Maikel
2. David
3. Luc
4. Gerben
5. Adine

Make project planning Collaborative effort of all members
2
Review user requirements and use cases Collaborative effort of all members
Finish collecting SotA articles and write SotA section Each member for their respective subcategory
Compile list of potential robot designs Collaborative effort of all members
Make some concept design sketches Maikel
Make a preliminary list of required parts Gerben
Define embedded software environment Luc
Preliminary elimination session for designs based on user requirements Adine
Start compiling list of design preferences/requirements/constraints David
3
Finish list of preferences/requirements/constraints Adine
Further eliminate designs due to constraints Collaborative effort of all members
Rank remaining designs and select a winner Collaborative effort of all members
Develop a building plan/schemata for the winner design Gerben, Luc
Start acquiring physical quantities for modelling design Maikel, David
Start with a simple model of some system parameters Maikel, David
4
Commence robot assembly according to highest priority of building schemata Gerben, David
Continue modelling/simulating Maikel
Start coding robot functionalities Luc
Catch up on documenting the wiki Adine
5
Continue robot assembly and coding Gerben, David, Luc
Continue modelling/simulating Maikel
Catch up on documenting the wiki Collaborative effort of all members
6
Continue robot assembly and coding Gerben, Luc
Test the first (few) finished sub-system(s) of the robot. Collaborative effort of all members
Finish modelling/simulating Maikel, David
Finish catching up on documenting the wiki Collaborative effort of all members
7
Finish robot assembly Gerben
Make concept designs for possible modules Luc
Make a draft for final presentation Maikel, David, Adine
Test the first (few) finished sub-system(s) of the robot. Collaborative effort of all members
8
Buffer time Collaborative effort of all members
Finish final presentation Maikel, David, Adine
Complete wiki Gerben, Luc

* The current division of task is a rough estimate for the next 7 weeks. New tasks may pop up or task division may be rotated, and is hence subject to change during the progress of the course.

Approach

The problem will be approached by a design question. What is the best design for a robot to combat deforestation which will be build modular so that it can be implemented for other purposes with minor changes. The first 2 weeks the approach will primarily be sequential, as user analysis, use cases and requirements/preferences/constraints need to be done sequentially before the rest of the project can start. Once this is over, the project will run in a parallel fashion where building and modelling will happen simultaneously.

Milestones and Deliverables

Table 2: Milestones
Date Accomplished
30-04-2018 SotA research done
03-05-2018 User analysis/use cases done
07-05-2018 Have a partially eliminated list of designs
10-05-2018 Pick final “winner” design
21-05-2018 Have the first working subsystem
25-05-2018 Finish modelling
31-05-2018 Have an operational prototype running
with at least 2 subsystems
07-06-2018 Made several concepts for modules
11-06-2018 Presentation is finished
14-06-2018 Wiki is completely updated

Literature Review

The patent on remote control systems granted to Mitsubishi Electric Crop. By the US government. This document is a thorough description of how remote control systems work, if we decide to make our vehicle remote controlled all the info we need is in here. But it is incredibly lengthy and written in a way that is not pleasant to read, so use it as a last resort. https://patentimages.storage.googleapis.com/eb/4b/ce/ba560b94ae5c1a/US5554980.pdf

This 2 page article is a statement from Elon Musk, CEO of Tesla, about his predictions for autonomous cars in the near future. It shows his vision, which is directly linked to his companies (one of the biggest on this market) vision. http://www.oharas.com/ET/elonmusk.pdf

To get our car driving smoothly, we will probably utilize a remote control, meaning that it will be very closely related to a remote controlled toy car, to which this doc. is the current active patent. It shows the state of the art radio controlled toy car technology currently available. https://patents.google.com/patent/US4457101A/en

A guide to help us control a servo motor with our computer, as a servo motor is the most likely option if we want our car to drive without outside help. http://www.instructables.com/id/How-to-Dynamically-control-a-servo-or-motor-throug/

A short article on the workings of servo motors, the main two interesting reads are the control of the servo and the different types, as we will have to chose one if we opt to use servo’s to drive our car around. https://www.jameco.com/jameco/workshop/howitworks/how-servo-motors-work.html

Even though this site is a webshop, and not a scientific article, it shows what technology we can buy within a respectable price range and thus shows what we do not need to make ourselves. Before we start thinking about how to make a part of our robot, lets first check what this shop has got. https://www.tinytronics.nl/shop/nl

Retrieved from "https://cstwiki.wtb.tue.nl/index.php?title=PRE2017_4_Groep6&oldid=55093"