Embedded Motion Control 2014 Group 5: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
<td width="120px"><b>Student id:</b></td> | <td width="120px"><b>Student id:</b></td> | ||
<td width="170px"><b>Email:</b></td> | <td width="170px"><b>Email:</b></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Geert van Kollenburg/td> | <td>Geert van Kollenburg/td> | ||
<td> </td> | <td> </td> | ||
<td>[ | <td>[ ]</td> | ||
</tr> | </tr> | ||
<tr>Paul Blatter</td> | <tr>Paul Blatter</td> | ||
| Line 24: | Line 21: | ||
<td>Kevin van Doremalen</td> | <td>Kevin van Doremalen</td> | ||
<td>0797642</td> | <td>0797642</td> | ||
<td>[ | <td>[k.p.j.v.doremalen@student.tue.nl]</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 34: | Line 31: | ||
<td>Robin Franssen</td> | <td>Robin Franssen</td> | ||
<td> </td> | <td> </td> | ||
<td>[ ]</td> | <td>[ ]</td> | ||
</tr> | </tr> | ||
Revision as of 08:41, 13 May 2014
Group 5
Paul Blatter| Name: | Student id: | Email: |
| Geert van Kollenburg/td> | [ ] | |
| [] | ||
| Kevin van Doremalen | 0797642 | [k.p.j.v.doremalen@student.tue.nl] |
| Niek Wolma | [ ] | |
| Robin Franssen | [ ] |
Planning
Week 1
- Instal Ubuntu
- Instal ROS
- Setup SVN
- Tutorials
Week 2
- Continu tutorials
- Setting up program for first test
Week 3
- Finishing tutorials
- Continu on program first test
- First test robot
- Program architecture
Week 4
- Setting up program for corridor
- Second test robot
- Corridor challenge
Week 5
Week 6
Week 7
Week 8
Week 9
- Maze challenge
Introduction
The goal of this course is to implement (embedded) software design (with C++ and ROS) to let a humanoid robot navigate autonomously. The humanoid robot Pico is programmed to find its way through a maze, without user intervention.
This wiki page contains the approach and choices that were made by group 5.
Corridor Challenge
Program Architecture
Laser data
The robot contains a laser, which has a view of 270 degrees.
Odometry
Odometry is the use of data of the angular positions of the robot wheels. This data is used to estimate the position of the robot relative to a starting point. The angular positions are converted into Carthesian coordinates (x-, y- and theta-direction). This data is never fully accurate, inter alia due to wheel slip.