Embedded Motion Control 2014 Group 10: Difference between revisions
Jump to navigation
Jump to search
Line 41: | Line 41: | ||
* Write corridor navigation | * Write corridor navigation | ||
* Test the written code on Pico | * Test the written code on Pico | ||
* Corridor challenge ([http://youtu.be/z8PHiTTVJhs | * Corridor challenge ([http://youtu.be/z8PHiTTVJhs Recorded performance]) | ||
<br> | <br> | ||
Revision as of 12:29, 17 May 2014
Members of group 10
Bas Houben | 0651942 |
Marouschka Majoor | 0660462 |
Eric de Mooi | 0734166 |
Nico de Mooij | 0716343 |
Planning
Week 1
- Introduction
- Install Ubuntu
Week 2
- Determine the course goals
- Brainstorm about the robot control architecture
- Start with the tutorials
Week 3
- Continue with the tutorials
- Install ROS/QT
- Finish robot control architecture
- Brainstorm about collision principle
- Brainstorm about navigation
Week 4
- Meet with the tutor
- Finish installation
- Finish tutorials
- Write collision detection
- Write corridor navigation
- Test the written code on Pico
- Corridor challenge (Recorded performance)
Concepts
Robot program architecture
The idea of our architecture is to create different process layers. By splitting the incoming signals and combining them later, the tasks can be divided and the different processes can run in parallel. An image will be added later.
Corridor test wall detector
The wall detector determines whether the robot is close to a wall or not by determining the unblocked distances at its two sides. When either side is too close (within 30cm) it turns parallel to that side, taking a distance of 30cm from the wall.