Embedded Motion Control 2014 Group 8: Difference between revisions
Line 13: | Line 13: | ||
2. approximately 250 degrees of measurement direction <br> | 2. approximately 250 degrees of measurement direction <br> | ||
3. The datapoint at the left (930), front (540) and right (150) <br> | 3. The datapoint at the left (930), front (540) and right (150) <br> | ||
4. The maximum distance measurement is 30 meters <br> | |||
5. | |||
<br><br> | |||
The figure on the right shows the location of the laser (distance) measurement points | |||
== First test == | == First test == |
Revision as of 09:42, 21 May 2014
Harm van Deursen
Lex Hoefsloot
Paul Verhoekx
Teun Melief
Robin Smit
PICO Knowns
1. 1080 laser points for distance measurement
2. approximately 250 degrees of measurement direction
3. The datapoint at the left (930), front (540) and right (150)
4. The maximum distance measurement is 30 meters
5.
The figure on the right shows the location of the laser (distance) measurement points
First test
Corridor test
second test
Approach
Two approaches are investigated. The basis of both is to drive safe. Save driving is interpretated as "not hitting the walls". This is implemented as follows: if the laser scans a wall... TODO.
Now the robot does not hit any walls, the first approach can be implemented. This approach is "time-based": Pico drives between the walls. If the lasers scan a gap at the right or the left the program measures the time. Meanwhile, pico is still driving forward and is still measuring the opening. If the lasers scan a wall again, pico measures the time again. Now the time to drive from the beginning of the opening to the end of the opening is known, so also the time to drive to the middle of the opening is known. This is exactly the time pico needs to drive backwards. Now pico is driving sidewards for a specific amount of time (this time needs to be tuned). Now the robot is in the "new" corridor. The last action is to turn 90 degrees. This is done by driving a specific amount of time (dependent of the turningvelocity).
SCHEME NEEDS TO BE INCLUDED
The second approach...
Role division
driving, arrow detection, trajectory planning...
It's a new world
How to load the T-junction:
- Open Terminator
- Run:
gazebo maze/placearrow_Tjunc.world
when in the maze folder - In another terminal
- Run:
rosrun maze spawn_Tjunc
- and run:
roslaunch pico_gazebo pico.launch
to load Pico - Now you can run Rviz:
rosrun pico_visualization rviz