Embedded Motion Control/Hospital Competition 2018: Difference between revisions
Jump to navigation
Jump to search
(Created page with 'thumb|right|800px|Scheme of a possible Hospital, with measurements, but not up to scale! '''Challenge Specifications''' * You have finished the assignment …') |
No edit summary |
||
Line 1: | Line 1: | ||
[[File:EMC2018C2.png|thumb|right| | [[File:EMC2018C2.png|thumb|right|700px|Scheme of a possible Hospital, with measurements, but not up to scale!]] | ||
'''Challenge Specifications''' | '''Challenge Specifications''' | ||
* You have finished the assignment if PICO did not bump into walls and the entire rear wheel is across the finish line. | * You have finished the assignment if PICO did not bump into walls and the entire rear wheel is across the finish line. |
Revision as of 11:36, 14 February 2018
Challenge Specifications
- You have finished the assignment if PICO did not bump into walls and the entire rear wheel is across the finish line.
- Do not touch the walls! Slightly touching is allowed, 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.
- 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 defined start position
- The trail time (= the time graded) is reset, but
- the total time keeps running
- Maximum speed (is limited in PICO): 0.5 m/s translational, 1.2 rad/s rotational.
- There will be no second attempt if first attempt was successful
On the right you can find one example of a Escape Room Challenge.
Environment Specifications
Robot Software
- 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 your tutor know 1 week before the challenge!
- 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