Embedded Motion Control 2017 Group 3 / Corridor Challenge: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This page is part of the Embedded Motion Control [[Embedded_Motion_Control_2017_Group_3 | Group 3]] of 2017. | This page is part of the Embedded Motion Control [[Embedded_Motion_Control_2017_Group_3 | Group 3]] of 2017. | ||
[[File:EMC17-G3_CC_Corridor.png|thumb|250px|right|Initial Control Hierarchy]] | |||
This page is about the design made from the initial design up to the moment of the the Corridor Challenge. For this challenge is PICO should drive itself through a corridor which is constructed with parallel walls, detect the first exit and take a turn. First the design steps are described, followed by notable algorithms used and there software implementation and concluding with the functioning of the code in the simulation. | This page is about the design made from the initial design up to the moment of the the Corridor Challenge. For this challenge is PICO should drive itself through a corridor which is constructed with parallel walls, detect the first exit and take a turn. First the design steps are described, followed by notable algorithms used and there software implementation and concluding with the functioning of the code in the simulation. | ||
Revision as of 11:53, 21 June 2017
This page is part of the Embedded Motion Control Group 3 of 2017.
This page is about the design made from the initial design up to the moment of the the Corridor Challenge. For this challenge is PICO should drive itself through a corridor which is constructed with parallel walls, detect the first exit and take a turn. First the design steps are described, followed by notable algorithms used and there software implementation and concluding with the functioning of the code in the simulation.