Embedded Motion Control 2015 Group 5: Difference between revisions
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
<tr> | <tr> | ||
<td>Joost Franssen</td> | <td>Joost Franssen</td> | ||
<td> | <td>0824821</td> | ||
<tr> | <tr> | ||
<tr> | <tr> | ||
| Line 31: | Line 31: | ||
<td>Marjon 't Klooster<b></b></td> | <td>Marjon 't Klooster<b></b></td> | ||
<td> | <td>0819200</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Revision as of 12:35, 29 April 2015
Group Members
| Name: | Student id: |
| Bart van Willigen | 0770142 |
| Joost Peters | 0747630 |
| Robin Loose | 0771575 |
| Koen Bos | 0763939 |
| Joost Franssen | 0824821 |
| Lotte de Koning | 0655209 |
| Marjon 't Klooster | 0819200 |
Requirements
Functions
Components
Specifications
Interfaces
After a first succesful brainstorm, the first draft of the system interface is determined. In this schematic the different contexts are presented. The goal to solve the maze is monitored by the Task monitor. Based on the observed environment and the maze solving algorithm, a set of skills is selected. Task control feedforward is used when no deterministic choice can be made. These skills are based on the robot's basic functions.
