Embedded Motion Control 2012 Group 8: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 42: | Line 42: | ||
*** started thinking about the image recognition of the arrows | *** started thinking about the image recognition of the arrows | ||
*** connected to the svn server and successfully shared code | *** connected to the svn server and successfully shared code | ||
* '''Week 2''' | |||
** Have second meeting with tutor on Wednesday (clear some questions about the maze and corridor contest) | |||
** Redo the code based on last discussion (we came up with a new strategy for taking corners) | |||
** Restructure the software's framework for ease of future improvements | |||
** Try to use the messages from the camera with our arrow guiding system |
Revision as of 12:31, 15 May 2012
Group 8
Tutor: Sjoerd van den Dries
Member | |
---|---|
Alexandru Dinu | Alexandru Dinu |
Thomas Theunisse | Thomas Theunisse |
Alejandro Morales | Alejandro Morales |
Ambardeep Das | Ambardeep Das |
Progress
- Week 1
- Installed Ubuntu + ROS + Eclipse
- Working on the tutorials...
- Week 2
- Finished with the tutorials
- Try to find a solution for rviz crashing on one of the computers
- Have the first meeting with the tutor
- Discuss the possible strategies for resolving the maze
- Make a list of the names and structures of relevant topics that can be received from the simulated robot
- Try to practice a bit with subscribing to certain topics from the simulated robot and publish messages to make him navigate around the maze
- Progress
- resolved the issue with rviz
- did testing on the robot and we are now able to make him move, take turns, measure the distance in front of him and take decisions based on that
- made a node that subscribes to the scan topic and publish on /cmd_vel topic
- starting testing code to include the odometry information in our strategy
- started thinking about the image recognition of the arrows
- connected to the svn server and successfully shared code
- Week 2
- Have second meeting with tutor on Wednesday (clear some questions about the maze and corridor contest)
- Redo the code based on last discussion (we came up with a new strategy for taking corners)
- Restructure the software's framework for ease of future improvements
- Try to use the messages from the camera with our arrow guiding system