Embedded Motion Control 2019 Group 8: Difference between revisions
Jump to navigation
Jump to search
Line 85: | Line 85: | ||
== Escape Room Execution == | == Escape Room Execution == | ||
For the escape room all the functions and components described above are programmed into C++. Several aspects are already done and working. Since the most robust solution is to follow a wall, this is chosen to be programmed first. This gives good results in 2 random maps shown below. | For the escape room all the functions and components described above are programmed into C++. Several aspects are already done and working. Since the most robust solution is to follow a wall, this is chosen to be programmed first. This gives good results in 2 random maps shown below. | ||
[[File:EscapeRoom1.gif]] | [[File:EscapeRoom1.gif]] [[File:EscapeRoom2.gif]] |
Revision as of 14:07, 12 May 2019
Group Members
Names: | Student id: |
---|---|
Stan den Hartog | 0953184 |
Elise Verhees | 0950109 |
Rob Dorussen | 0968849 |
Gosse Bijlenga | 0950642 |
Max van Haren | 0953564 |
Design
Design Document
Requirements
- Autonomously complete the 'Escape Room'.
- Must not bump into the wall.
- Must not tip over.
- Make sensible movements/progress each 30 seconds.
- Software must be easy to set up.
- Robot must function robustly.
Specifications
- Rear wheel must cross the finish line.
- The robot should finish within 5 minutes.
- The robot should finish within 2 trials.
- Distance between the wall and the robot must be 0,05 meter.
- The maximum translational speed is 0,5 meter per second.
- The maximum rotational speed is 1.2 radians per second.
- The robot must have a maximum speed/stop before changing direction.
- The maximum inclination angle is around 5 degrees.
- The software must have 1 command to update
- The software should be able to compile (cmake/make)
- The software should start by calling upon one executable.
- The status must be reported at least each 30 seconds.
- The functions must be scalable.
- Definition of data ownership must be explicit.
- Switch states only to advance the strategy plan.
Functions
- Detect if the robot is over the finish line
- Drive forward (keeping the speed specifications in mind)
- Rotate
- Collision detection
- (Update World Model)
- Print status
- Scan environment for exit
- State function/ Life Cycle State Machine (LCSM)
- Wall hugging
Components
- Room
- Walls
- Finish line
- Exit tunnel
- (Obstacles)
- Robot
- Actuators
- Sensors
- Body
- Hardware
- Software
- World Model
- Interfaces
- Plan
- Actuator control
- Monitoring
- Preception
- Mediation
- Life Cycle State Machine (LCSM)
Escape Room Execution
For the escape room all the functions and components described above are programmed into C++. Several aspects are already done and working. Since the most robust solution is to follow a wall, this is chosen to be programmed first. This gives good results in 2 random maps shown below.