Embedded Motion Control 2015
Guide towards the assignment
'A-MAZE-ING PICO'
Introduction
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.
Course Schedule and Lecture Slides
Lectures will be given on Wednesdays from 8.45 - 10.30 in Gem-Z 3A-12. The course schedule is as follows:
| April 22 | Introduction | |
| April 29 | Composition pattern part I by Herman Bruyninckx | Tooling and Infrastructure by Sjoerd van den Dries |
| May 6 | First presentation of the design by groups: 6-minute presentation about the group's design in the context of the task-skill-motion system architecture and the composition pattern. | |
| May 13 | Corridor competition | |
| May 20 | Composition Pattern part II by Herman Bruyninckx | |
| May 27 | Second presentation of the design by groups | |
| June 3 | Communication patterns | |
| June 10 | Presentation of final design by groups | |
| June 17 | Final competition | |
Assignment
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.
Corridor Competition
An intermediate review will be held on May 13th, 8.45h at the RoboCup soccer field. During this challenge, called the corridor competition the students have to let the robot drive through a corridor and then take the first exit. The precise location of this exit will not be given in advance. Some facts:
- Set-up
- Make sure your software is easy to set-up, i.e:
- Your software can be updated with one easy command, e.g. 'git pull'
- Your software can be compiled using 'cmake' and 'make'
- To start your software, only one executable has to be called
- If your set-up deviates from this method, let us know as soon as possible!
- The software of all groups will be updated on the robot before the challenge starts
- This way, teams starting the challenge have as much time as teams that do the challenge at the end
- Make sure your software is easy to set-up, i.e:
- The corridor:
- The exit can be either left or right
- It is not known beforehand how far the exit is located from the start (somewhere between 1 and 10 meters)
- The opposing end wall (on the far end) will be open
- The walls are approximately parallel to each other
- Note: the walls might not be perfectly straight
- The distance between the walls is not known in advance, but will be reasonable (somewhere between 0.5 and 1.5 meters).
- The distance between the walls will be fairly constant throughout the corridor, 'fairly' meaning that we build the corridor by hand, and the distance may change a little along the corridor.
- At the exit, the finish line is located approximately 30 cm from the side of the corridor (Notice: approximately, so don't just drive forward for 30 cm!). The walls that can be used to align PICO will be a little bit longer.
- Start, goal and limits:
- PICO will start with its laser range finder between the walls
- PICO will be approximately facing the end of the corridor. (Notice: approximately, so don't just drive forward for n seconds!)
- You have finished the assignment if PICO did not drive into walls, took the correct turn and the entire rear wheel is across the finish line.
- Maximum speed (is limited in PICO): 0.5 m/s translational, 1.2 rad/s rotational. By the way, that's pretty fast (compared to last year's 0.2 m/s), so be careful! You don't have to drive that fast!
- Scoring:
- Try not to touch the wall! Slightly touching is OK, however, bumping (i.e., driving head-on into a wall) is not allowed! If PICO hits the wall, we decide whether it counts as bumping. If PICO bumps into the wall, that trial ends immediately.
- Every team has two trials (= max one restart). A trial ends if:
- PICO bumps into the wall
- PICO has not moved or has not made sensible movements (as judged by the tutors) for 30 seconds
- The total time limit of 5 minutes per group is reached
- The group requests a restart (on the first trial)
- restart means:
- PICO restarts at the beginning of the corridor
- CORRIDOR time (= time used for scoring) is reset, BUT
- TOTAL time keeps running
- Every team has a total of 5 minutes
- There will be no second attempt if first attempt was successful
Next you can see an example of a corridor:
Getting Started
To get started, please do the tutorials on the Tutorial Page. Please note:
- Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later. If something is not working as expected, make sure you correctly did all previous steps.
- Of course, things may still go wrong. If so, do not hesitate to contact us.
- See Using Pico for a quick overview of how to use Pico.
FAQ
Here you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.
Group Wiki Pages
Group 1 - visit wiki - Tutor: Luis Ferreira
Group 2 - visit wiki - Tutor: Luis Ferreira
Group 3 - visit wiki - Tutor: Sjoerd van den Dries
Group 4 - visit wiki - Tutor: Sjoerd van den Dries
Group 5 - visit wiki - Tutor: Yanick Douven
Group 6 - visit wiki - Tutor: René van de Molengraft
Group 7 - visit wiki - Tutor: Yanick Douven
Group 8 - visit wiki - Tutor: René van de Molengraft
Group 9 - visit wiki - Tutor: René van de Molengraft
Group 10 - visit wiki - Tutor: Yanick Douven
Pico test schedule
In order to test your software on the Pico robot, each group has one one hour time slot a week available. You can reserve your test slot in the table below.
Please charge the robots whenever possible so there is no down time due to empty batteries.
| Date | Time | Group |
|---|---|---|
| 07-05-2015 | 8:30 - 9:30 | |
| 07-05-2015 | 9:40 - 10:40 | |
| 07-05-2015 | 10:50 - 11:50 | 9 |
| 08-05-2015 | 8:30 - 9:30 | 8 |
| 08-05-2015 | 9:40 - 10:40 | 3, DIBBS! |
| 08-05-2015 | 10:50 - 11:50 | 5 |
| 08-05-2015 | 14:10 - 15:10 | 7 |
| 08-05-2015 | 15:20 - 16:20 | 10 |
| Date | Time | Group |
|---|---|---|
| 11-05-2015 | 8:30 - 9:30 | 4 |
| 11-05-2015 | 9:40 - 10:40 | 1 |
| 11-05-2015 | 10:50 - 11:50 | 2 |
| 11-05-2015 | 13:00 - 14:00 | 5 |
| 11-05-2015 | 14:10 - 15:10 | 10 |
| 11-05-2015 | 15:20 - 16:20 | 4 |
| 12-05-2015 | 8:30 - 9:30 | 7 |
| 12-05-2015 | 9:40 - 10:40 | 2 |
| 12-05-2015 | 10:50 - 11:50 | 6 |
| 12-05-2015 | 13:00 - 14:00 | 6 |
| 12-05-2015 | 14:10 - 15:10 | 8 |
| 12-05-2015 | 15:20 - 16:20 | 9 |
| 12-05-2015 | 16:30 - 17:30 | 3, DIBBS! |
Group Final Presentations
To be added...
Contact Details
In case of questions related to working with the real PICO robot, please contact Yanick. For questions regarding the simulator or Git, please contact Sjoerd.
Tutors
Sjoerd van den Dries - S dot v dot d dot Dries at tue dot nl
Luis Ferreira - L dot F dot Bento dot Ferreira at tue dot nl
Yanick Douven - y dot g dot m dot douven at tue dot nl
...