Embedded Motion Control 2015 Group 1: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Embedded Motion Control]] (EMC) Group 1 is a multidisciplinar and | [[Embedded Motion Control]] (EMC) Group 1 is a multidisciplinar and multilingual project group working on the 'A-MAZE-ING PICO'. This wikipedia page consists of the weelky progress presented in the journal, the written report and some other practical or useful stuff. | ||
The report focussus on the individual components of the software architecture, this includes mathematical analyses and software implementation. | |||
= Journal = | |||
= | The proces of developing a software architecuter and the implementation requires great coordination and collaboration. This journal will be updated to track the progress of the group. This includes weekly progress, countered problems and divided tasks and argumentation of tasks and dicisions. | ||
The proces of developing a software architecuter and the implementation requires great coordination and collaboration. This journal will be updated to track the progress of the group. This includes | |||
== Meetings == | == Meetings == | ||
Revision as of 11:53, 17 May 2015
Embedded Motion Control (EMC) Group 1 is a multidisciplinar and multilingual project group working on the 'A-MAZE-ING PICO'. This wikipedia page consists of the weelky progress presented in the journal, the written report and some other practical or useful stuff.
The report focussus on the individual components of the software architecture, this includes mathematical analyses and software implementation.
Journal
The proces of developing a software architecuter and the implementation requires great coordination and collaboration. This journal will be updated to track the progress of the group. This includes weekly progress, countered problems and divided tasks and argumentation of tasks and dicisions.
Meetings
1. Thursday 23: 12:45 - 13:30 in OGO19
2. Wednesday 29: 10:15-11:00 in OGO17
3. Friday 1 May: ?-? in ?
Design Architecture
The design architecture is based on the 5 C's decomposition and is best shown using a representative figure.
Potential Field
Report-like explanation of the potential field: the working principle, the underlying mathematics and, the implementation.
Lower Level Skills
Explanation of the decision making algorithm and the low level skills used to drive the robot.
Corridor Challenge
Preparation of the Embedded Motion Control #Corridor Competition and the results shown in a short movie.
Appendix
Group Members
Group 1 consists of the following members:
| Name | Student nr | |
|---|---|---|
| Maurice Poot | 0782270 | m.m.poot@student.tue.nl |
| Timo Ravensbergen | 0782767 | t.ravensbergen@student.tue.nl |
| Bart Linssen | 0786201 | a.j.m.linssen@student.tue.nl |
| Rinus Hoogesteger | 0757249 | m.m.hoogesteger@student.tue.nl |
| Nitish Rao | 0927795 | n.rao@student.tue.nl |
| Aakash Amul | 0923321 | a.v.h.amul@student.tue.nl |
| Ignacio Vazquez | 0871475 | i.s.vazquez.rodarte@student.tue.nl |
Qt from terminal
If Qt Creator is not run from the terminal, the programs inside cannot connect to the ROS master. To be able to run Qt Creator from the desktop without any problems, follow a similar procedure to the one that is used in the Customizing Ubuntu tutorial for the Terminator file:
Edit
~/.local/share/applications/QtProject-qtcreator.desktop
and change the third line to:
Exec=bash -i -c /home/rinus/qtcreator-3.3.2/bin/qtcreator
This will run QtCreator from a terminal even if the desktop icon is used.