Embedded Motion Control 2013/Goal: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
* the robot can be actuated by sending information to the '''base controller''' | * the robot can be actuated by sending information to the '''base controller''' | ||
* during the final contest, it is highly imperative that the PICO robot refrains from colliding with the walls in the maze. '''Colliding with the walls will result in severe time-penalties.''' | * during the final contest, it is highly imperative that the PICO robot refrains from colliding with the walls in the maze. '''Colliding with the walls will result in severe time-penalties.''' | ||
* the walls of the maze will contain several types of pointers to the exit, which can potentially help PICO to speed up execution of the task | * the walls of the maze will contain several types of pointers to the exit, which can potentially help PICO to speed up execution of the task. | ||
An intermediate review will be held on September | <!-- | ||
[http://cstwiki.wtb.tue.nl/images/Arrow.pdf Click here for a pdf file containing the arrow we will use]. Also, we have uploaded a [http://cstwiki.wtb.tue.nl/images/Arrows_emc.zip zip file] with multiple images of these arrows captured on the real PICO robot. Furthemore, we captured PICO's camera topics in a [https://amigo.wtb.tue.nl/svn/amigo/data/recorded/bags/pico_camera_arrow.bag bag file] while the robot was looking at the arrow. You can play this bag file as follows:<pre>rosbag play pico_camera_arrow.bag</pre> The topics ''/robot/body/head/camera/camera_info'' and ''/robot/body/head/camera/image_raw'' should then become available. For example, while playing the bag file, use <pre>rosrun image_view image_view image:=/robot/body/head/camera/image_raw</pre> to view the camera images. | |||
--> | |||
An intermediate review will be held on September 25th, during the corridor competition. During this challenge 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. | |||
During the final contest, the groups are expected to give a short (5 minute) presentation about their progress and design decisions. | During the final contest, the groups are expected to give a short (5 minute) presentation about their progress and design decisions. | ||
Revision as of 09:35, 4 September 2013
The goal of the assignment is to get the real-time concepts in embedded software design operational.
The concrete task that has to be solved is to let the PICO robot find his way out of a maze. The final demonstration by each participating group of 4-5 students will be performed during a contest, the winner of which is the group that exits the maze in the shortest amount of time. To prepare for this competition the following guidelines have to be considered:
- to test with PICO and to prepare for the final contest, a simulator will be made available that mimics the in and outputs to the real robot. Specifics of this simulator will be presented in the first lecture on September 4th
- the maze of the final competition will be constructed just before the competition. The maze presented in the simulator is therefore different from the real one used in the final contest.
- both on the real and simulated PICO robot, three sources of sensor information will be available to perceive the environment and to derive the state of the robot:
- laserdata provided by the forward pointing laser scanner,
- images captured by the monocular camera,
- odometry provided by the base controller
- the robot can be actuated by sending information to the base controller
- during the final contest, it is highly imperative that the PICO robot refrains from colliding with the walls in the maze. Colliding with the walls will result in severe time-penalties.
- the walls of the maze will contain several types of pointers to the exit, which can potentially help PICO to speed up execution of the task.
An intermediate review will be held on September 25th, during the corridor competition. During this challenge 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.
During the final contest, the groups are expected to give a short (5 minute) presentation about their progress and design decisions.