Embedded Motion Control 2014 Group 9: Difference between revisions
| Line 66: | Line 66: | ||
==Summary meeting week 2== | ==Summary meeting week 2== | ||
-progress and format was discussed. Tasks were divided. For the corridor competition we need a set of four functions, all with input the laser data,(first increment starts at the left), output and type given, extra output possible for future extensions (as separate function) | -progress and format was discussed. Tasks were divided. For the corridor competition we need a set of four functions, all with input the laser data,(first increment starts at the left), output and type given, extra output possible for future extensions (as separate function) | ||
---- | |||
Corridor detection: CL, CR (type bool) true if a corridor is at ~90deg left/right of pico | Corridor detection: CL, CR (type bool) true if a corridor is at ~90deg left/right of pico | ||
-> Jordi | -> Jordi | ||
---- | |||
Driving: Vx, Vy, Vz (etc) -> straight, safe, and aligned driving. Also steering towards corners/endstops | Driving: Vx, Vy, Vz (etc) -> straight, safe, and aligned driving. Also steering towards corners/endstops | ||
-> Koos | -> Koos | ||
Result: library implemented, have not been able to test yet. 2 function created for area reconnaisance. One for translating laser data into coordinates, another to relate that data to straight driving objective of pico | |||
---- | |||
Corner: Vx, Vy, Vz (etc), override -> action when CL or CR is true, overrides driving function | Corner: Vx, Vy, Vz (etc), override -> action when CL or CR is true, overrides driving function | ||
-> Rene | -> Rene | ||
---- | |||
end: Vx, Vy, Vz (etc), exit -> for stopping after finish | end: Vx, Vy, Vz (etc), exit -> for stopping after finish | ||
-> Jasper | -> Jasper | ||
---- | |||
Combining in main() | Combining in main() | ||
-> Joost | -> Joost | ||
Revision as of 17:36, 10 May 2014
Team members
| Name | Student # | Remark | |
| Koos Elferink | k.elferink@student.tue.nl | 0716494 | |
| Joost Potma | j.potma@student.tue.nl | 0864146 | |
| Jasper Spanjaards | j.j.a.spanjaards@student.tue.nl | 0746039 | |
| Jordi van Dijk | j.v.dijk@student.tue.nl | 0805981 | |
| René Bruintjes | r.f.bruintjes@student.tue.nl | 0877139 |
Planning
Week 1
- Installing Ubuntu
- Installing ROS
- Installing SVN
- Follow tutorial C++
Week 2
- Install Qt-creator (IDE)
- Group meeting to make a start on the project
- Test robot with standard script
- Test robot with added self made script parts
Week 3
- Group meeting (goal: finish corridor script)
- Second test on robot (test script)
- Corridor contest (16 May)
Future
- 20 June: Maze contest
Summary meeting week 2
-progress and format was discussed. Tasks were divided. For the corridor competition we need a set of four functions, all with input the laser data,(first increment starts at the left), output and type given, extra output possible for future extensions (as separate function)
Corridor detection: CL, CR (type bool) true if a corridor is at ~90deg left/right of pico -> Jordi
Driving: Vx, Vy, Vz (etc) -> straight, safe, and aligned driving. Also steering towards corners/endstops -> Koos
Result: library implemented, have not been able to test yet. 2 function created for area reconnaisance. One for translating laser data into coordinates, another to relate that data to straight driving objective of pico
Corner: Vx, Vy, Vz (etc), override -> action when CL or CR is true, overrides driving function -> Rene
end: Vx, Vy, Vz (etc), exit -> for stopping after finish -> Jasper
Combining in main() -> Joost