Hi!
Yesterday we began trying to install player in Pio. We first noticed a lot of packages were missing so we decided to add repositories. When doing so, we realized that, due to the fact that Pio's Ubuntu version is quite old (7.04), the repositories aren't available anymore. We tried to upgrade the version to 7.10 but weren't able to do so. The solution we thought of was installing a more recent version of Ubuntu (8.04, 8.10 or 9.04), however, due to the architecture of the robot (128 Mb of ram and Pentium 3) it is not possible,
What we did today was download old versions of Player (1.4 first and then 1.5). We did the ./configure, make and make install but weren't installed successfully. We will continue working on that issue tomorrow, we think we can find a way to do so or maybe download the missing packages individually.
Concerning the Playernav task, we know how to complete it in Carlos's computer (his installation of Player was different). In my computer, however, I have been having some troubles when running the application. It does it succesfully, however, the terminal shows me several warnings and one of the robots won't execute the planned route in the world file.
We have researched in blogs and apparently, one of the warnings has to do with the way in which I installed Player.
We hope to receive some suggestions, concerning particularly the issue of Player installation in Pio.
Regards!!
Showing posts with label playernav. Show all posts
Showing posts with label playernav. Show all posts
Tuesday, June 30, 2009
Sunday, June 21, 2009
Playernav execution, drivers research
Hi!
On Thursday and Friday Arturo, Carlos G. and I began working on the execute the Playernav task.
1.- When trying to execute playernav for the first time we got the following error message:
bash: playernav: command not found
The reason for this error message was that the libgnomecanvas 2-0 was missing so we used the synaptic package manager to install it and the configured it in order to allow its compilation like so:
pkg-config --cflags --libs libgnomecanvas-2.0
We then compiled it in the playernav directory player/utils/playernav with make.
2.- We then opened the wavefront.cfg file and executed ./playernav. We started manipulating the tools provided to draw trayectories and saw that the two main devices used in this tool are localize and planner which we will analyze with more detail later on.
Here is a screenshot of playernav being executed in wavefront.cfg which in fact uses the simple.world

3. The next step was to compare the wavefront.cfg and simple.cfg files in order to find out why isn't playernav executed properly in the latter.
We saw that wavefront cfg has three additional drivers.
5. We will also be working on the create map for Player/Stage task tomorrow. We have already completed the first step and we are now getting familiarized with the amcl and similar drivers so we have an idea on how to complete the second step. However we really need Carlos L. to give us back Pio's HD in order to complete the third step.
Regards!!
On Thursday and Friday Arturo, Carlos G. and I began working on the execute the Playernav task.
1.- When trying to execute playernav for the first time we got the following error message:
bash: playernav: command not found
The reason for this error message was that the libgnomecanvas 2-0 was missing so we used the synaptic package manager to install it and the configured it in order to allow its compilation like so:
pkg-config --cflags --libs libgnomecanvas-2.0
We then compiled it in the playernav directory player/utils/playernav with make.
2.- We then opened the wavefront.cfg file and executed ./playernav. We started manipulating the tools provided to draw trayectories and saw that the two main devices used in this tool are localize and planner which we will analyze with more detail later on.
Here is a screenshot of playernav being executed in wavefront.cfg which in fact uses the simple.world

3. The next step was to compare the wavefront.cfg and simple.cfg files in order to find out why isn't playernav executed properly in the latter.
We saw that wavefront cfg has three additional drivers.
- The amcl driver localizes the poses of a robot using data from several sensors. It does it using a filter of particle which increase according to the uncertaainty of the localization.
- The nd driver makes collision avoidance adjusted to non punctual robots in reduced spaces by using several devices like position2d, laser or sonar.
- The wavefront driver creates paths according to the data provided by the devices localize and planner. It also uses very commonly the vfh driver.
- The vfh driver provides both obstacle avoidance and path following capabilities
5. We will also be working on the create map for Player/Stage task tomorrow. We have already completed the first step and we are now getting familiarized with the amcl and similar drivers so we have an idea on how to complete the second step. However we really need Carlos L. to give us back Pio's HD in order to complete the third step.
Regards!!
Subscribe to:
Posts (Atom)