ROS navigation package for Pepper

1,645 views
Skip to first unread message

Jason Young

unread,
Aug 22, 2016, 4:27:06 AM8/22/16
to ROS Sig Aldebaran
Hi,
   Does the navigation package work well on Pepper?
   I tried to compile the Navigation package for Pepper with OpenNao, but couldn't fix the lost of dependent libs, such as PCL, VTK, OpenGL(FreeGlut). When I try to compile FreeGlut, it comes out that:  Could NOT find OpenGL (missing: OPENGL_gl_LIBRARY)
   So, can the navigation package be compiled with OpenNao? 
   And can the package work on Pepper?
   Anyone have tried this package?

Surya Ambrose

unread,
Aug 22, 2016, 6:17:56 AM8/22/16
to ros-sig-...@googlegroups.com
Hello,

I never tried the navigation package, so I can't tell if it works with Pepper :/

About compilation, when you say "compile with OpenNao" are you referring to virtual machine ? Because ROS packages are not supposed to compile on OpenNao virtual machine, so I am guessing you probably won't be able to fix all the dependency issues. Most likely, the package needs to be compiled using catkin on your machine with your ROS local installation and run on your desktop (with robot IP as a parameter).

Hope this helps,

Surya

--
You received this message because you are subscribed to the Google Groups "ROS Sig Aldebaran" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.
To post to this group, send email to ros-sig-aldebaran@googlegroups.com.
Visit this group at https://groups.google.com/group/ros-sig-aldebaran.
To view this discussion on the web visit https://groups.google.com/d/msgid/ros-sig-aldebaran/730f0f83-88f4-4888-b43d-0e1080f12248%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


This email and any attachment thereto are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient, please be advised that disclosing, copying, distributing or taking any action in reliance on the contents of this email is strictly prohibited. In such case, please immediately advise the sender, and delete all copies and attachment from your system.
This email shall not be construed and is not tantamount to an offer, an acceptance of offer, or an agreement by SoftBank Robotics Europe on any discussion or contractual document whatsoever. No employee or agent is authorized to represent or bind SoftBank Robotics Europe to third parties by email, or act on behalf of SoftBank Robotics Europe by email, without express written confirmation by SoftBank Robotics Europe’ duly authorized representatives.


Ce message électronique et éventuelles pièces jointes sont confidentiels, et exclusivement destinés à la personne ou l'entité à qui ils sont adressés.
Si vous n'êtes pas le destinataire visé, vous êtes prié de ne pas divulguer, copier, distribuer ou prendre toute décision sur la foi de ce message électronique. Merci d'en aviser immédiatement l'expéditeur et de supprimer toutes les copies et éventuelles pièces jointes de votre système.
Ce message électronique n'équivaut pas à une offre, à une acceptation d’offre, ou à un accord de SoftBank Robotics Europe sur toute discussion ou document contractuel quel qu’il soit, et ne peut être interprété comme tel. Aucun employé ou agent de SoftBank Robotics Europe n'est autorisé à représenter ou à engager la société par email, ou à agir au nom et pour le compte de la société par email, sans qu’une confirmation écrite soit donnée par le représentant légal de SoftBank Robotics Europe ou par toute autre personne ayant reçu délégation de pouvoir appropriée.

Jason Young

unread,
Aug 22, 2016, 8:12:20 AM8/22/16
to ROS Sig Aldebaran
Hi Surya,
Thanks for you reply. I've tried Moveit package on Ubuntu. But Our goal is to install Ros into Pepper directly.
I have succeed in compiling ROS basic core modules on OpenNao virtual machine and installed into pepper successfully.
But I can't compile Navigation package for  lost dependencies such as OpenGL. 

在 2016年8月22日星期一 UTC+8下午6:17:56,Surya Ambrose写道:
Hello,

I never tried the navigation package, so I can't tell if it works with Pepper :/

About compilation, when you say "compile with OpenNao" are you referring to virtual machine ? Because ROS packages are not supposed to compile on OpenNao virtual machine, so I am guessing you probably won't be able to fix all the dependency issues. Most likely, the package needs to be compiled using catkin on your machine with your ROS local installation and run on your desktop (with robot IP as a parameter).

Hope this helps,

Surya
2016-08-22 10:27 GMT+02:00 Jason Young <yangt...@gmail.com>:
Hi,
   Does the navigation package work well on Pepper?
   I tried to compile the Navigation package for Pepper with OpenNao, but couldn't fix the lost of dependent libs, such as PCL, VTK, OpenGL(FreeGlut). When I try to compile FreeGlut, it comes out that:  Could NOT find OpenGL (missing: OPENGL_gl_LIBRARY)
   So, can the navigation package be compiled with OpenNao? 
   And can the package work on Pepper?
   Anyone have tried this package?

--
You received this message because you are subscribed to the Google Groups "ROS Sig Aldebaran" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldeba...@googlegroups.com.
To post to this group, send email to ros-sig-...@googlegroups.com.

Karsten K

unread,
Aug 22, 2016, 11:58:27 AM8/22/16
to ros-sig-...@googlegroups.com
Hi Jason,

it would most likely be overkill to compile the complete ROS navigation stack on the robot. I would recommend to cleanly install a selection of packages where you can handle the dependencies. Move_base and gmapping should compile without any big overhead.

if it helps, I was testing gmapping on my local machine and remotely subscribed to the laser topic. It was more a proof of concept, but I could create a simple map. This would allow you to not cross compile everything.

To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.
To post to this group, send email to ros-sig-aldebaran@googlegroups.com.

Jason Young

unread,
Aug 23, 2016, 12:01:38 AM8/23/16
to ROS Sig Aldebaran
Hi Karsten,
Thanks for your advice.
I have tried gmapping on my remote PC to control Turtle_bot but not implemented with Pepper or Nao.
I think the gmapping module depends on PCL which still need OpenGL. Is there any configure option can be set to compile gmapping without OpenGL? 

在 2016年8月22日星期一 UTC+8下午11:58:27,Karsten Knese写道:

Mikael Arguedas

unread,
Aug 23, 2016, 2:36:49 AM8/23/16
to ros-sig-...@googlegroups.com
Hi Jason,

I don't think that pcl depends on openGL explicitely (c.f. http://www.pointclouds.org/documentation/tutorials/compiling_pcl_posix.php#dependencies).
Although I can't remember the last time I did try to compile it on a machine not supporting OpenGL... but you should be able to compile it on OpenNao if you're VERY patient. The remote solution suggested by Karsten is a good first step to confirm that the map quality produced is suitable for your application before going through the hassle of cross-compiling everything.

Another SLAM package you may want to consider is Cartographer recently release by Google (ros package here). Main advantages being storing only submaps in RAM and the quality of ray-tracing and resulting maps is much better. But It does depend on PCL too.

Cheers,
Mikael

To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.
To post to this group, send email to ros-sig-aldebaran@googlegroups.com.

Jason Yang

unread,
Aug 23, 2016, 2:58:23 AM8/23/16
to ROS Sig Aldebaran
Hi Mikael,
Thanks very much. I'll try it.

在 2016年8月23日星期二 UTC+8下午2:36:49,Mikael Arguedas写道:

Vincent Rabaud

unread,
Aug 23, 2016, 3:38:40 AM8/23/16
to ros-sig-...@googlegroups.com
Hi, I maintain gmapping and it does not depend on PCL.
Navigation does though. But you can use my (not yet merged) PR (and please upvote it too):
so that you can then use the PCL-free navigation:

To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.
To post to this group, send email to ros-sig-aldebaran@googlegroups.com.

Jason Yang

unread,
Aug 23, 2016, 10:03:30 PM8/23/16
to ROS Sig Aldebaran
Hi,
Thanks, I'll try it.

在 2016年8月23日星期二 UTC+8下午3:38:40,Vincent Rabaud写道:
Message has been deleted

Karsten K

unread,
Sep 21, 2016, 2:20:48 AM9/21/16
to ros-sig-...@googlegroups.com
I don't remember the exact quality outcome. But I remember you have to be patient and give it some love :)
Technically speaking, you have to be aware that the laser is rather limited with just a few points. So I would recommend you to move pepper in a slow pace and cross check the map outcome in rviz.

Did you encounter any latency issues?

On Wed, Sep 14, 2016 at 3:02 AM, Jason Yang <yangt...@gmail.com> wrote:
Hi Karsten,
I tested gmapping on my local machine and remotely create map with Pepper.
But the result comes out very inaccurate. Did you get satisfied result map?

在 2016年8月22日星期一 UTC+8下午11:58:27,Karsten Knese写道:
Hi Jason,

--
You received this message because you are subscribed to the Google Groups "ROS Sig Aldebaran" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.
To post to this group, send email to ros-sig-aldebaran@googlegroups.com.
Visit this group at https://groups.google.com/group/ros-sig-aldebaran.

Ronald Cumbal

unread,
Mar 28, 2017, 10:33:52 AM3/28/17
to ROS Sig Aldebaran
Hi everyone,

I've ran slam with Pepper successfully, but the outcome is too noisy. I've tried going at a slow pace, but the map is still not clear enough. Any other recommendations as in how to improve the output map?

adriano...@icar.cnr.it

unread,
Mar 30, 2017, 4:54:53 AM3/30/17
to ROS Sig Aldebaran
Hi Ronald, 

I have the same issue with mapping. To create a decent map, I teleop pepper with a slow movement and trying to give key points at gmapping package since have a high probability to understand where is the position of the robot on the map and add the new information to build the new part of the map.
I adopt the strategy to follow the walls of the rooms, the corners so if there are odometry errors the system adjust the position in the map with the estimate of the known environment.

Giovanni Claudio

unread,
Mar 30, 2017, 5:03:12 AM3/30/17
to ros-sig-...@googlegroups.com
Hi Ronald and Adriano, 

What package are you using to create the map? Which sensors are you using?

In my Pepper, I noticed that there is a problem of distortion from the depth sensor. The surface in the following picture should be flat (Pepper here was facing a wall): 

Immagine incorporata 1Immagine incorporata 2

Is this normal? Also Paco has the same problem.


To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.
To post to this group, send email to ros-sig-aldebaran@googlegroups.com.

Natalia Lyubova

unread,
Mar 30, 2017, 5:08:41 AM3/30/17
to ROS Sig Aldebaran
Hello Giovanni,

right, the distortion is caused by the lenses but not the sensor... Thus, some researchers remove lenses. Please let us know if it is critical for you.

Best regards,
Natalia

Giovanni Claudio

unread,
Mar 30, 2017, 5:17:36 AM3/30/17
to ros-sig-...@googlegroups.com
Hi Natalya, 

Thanks for your answer, I thought it was that. Are you referring to the black lens of the eyes right? Is it easy to remove them?

Giovanni

To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.
To post to this group, send email to ros-sig-aldebaran@googlegroups.com.

Natalia Lyubova

unread,
Mar 30, 2017, 5:50:26 AM3/30/17
to ROS Sig Aldebaran
Right, it is caused by the lenses in the eyes. it is possible to remove those lenses and we can do it.
Please, let me know,

Natalia

adriano...@icar.cnr.it

unread,
Mar 30, 2017, 5:53:55 AM3/30/17
to ROS Sig Aldebaran
HI Giovanni,
I'm using gmapping package with laser sensor. (Topic / pepper_robot / laser from pepper_full.launch).


Adriano


Giovanni Claudio

unread,
Mar 30, 2017, 8:35:08 AM3/30/17
to ROS Sig Aldebaran
Thanks Natalia.

Right now I am not working with SLAM, so it is not a big problem. I will discuss with my colleagues if we need to remove them for future works.

Giovanni

Ronald Cumbal

unread,
Apr 1, 2017, 10:26:26 AM4/1/17
to ros-sig-...@googlegroups.com
Hi Adriano and Giovani!

Thanks for the suggestions. I'm also using gmapping package with laser sensor /pepper_robot/laser from the C++ bring-up.

I have built a map with Pepper, but I had to fix some details manually:

Inline image 2

These are the parameters I'm using in the launch file of Gmapping:

<launch>
    <node pkg="gmapping" type="slam_gmapping" name="slam_gmapping" output="screen">
        <remap from="/scan" to="/pepper_robot/laser"/>
        <param name="map_update_interval" value="0.1"/>
        <param name="maxRange" value="1.2"/>
        <param name="maxUrange" value="1.4"/>
        <param name="minimumScore" value="100.0"/>
        <param name="linearUpdate" value="0.1"/>
        <param name="angularUpdate" value="0.5"/>
        <param name="temporalUpdate" value="0.1"/>
        <param name="resampleThreshold" value="0.5"/>
        <param name="particles" value="100"/>
        <param name="xmin" value="-25.0"/>
        <param name="ymin" value="-25.0"/>
        <param name="xmax" value="25.0"/>
        <param name="ymax" value="25.0"/>
        <param name="delta" value="0.02"/>
    </node>

</launch>

I also checked odometry and laser readings with the suggestions from http://wiki.ros.org/navigation/Tutorials/Navigation%20Tuning%20Guide. I found that translation odometry is correct, but odometry for orientation has a problem with the laser on the left. This is the image I got after performing the test, see that the laser points do not match consistently in the left of the image.

Inline image 3

I also tried running AMCL and move Pepper around the map by using 2D Navigation Goal, but I encounter two problems:
- Pepper starts moving, but stops before reaching the goal without any error reported anywhere.
- Pepper moves toward the goal, but it reaches a different part of the real hallway than the virtual map.

So I'm stuck with the following doubts:

I fixed manually some problem of the map, would this cause problems while navigating?
Is there any way to correct/calibrate laser readings?
The biggest problem I encounter is the lack of features inside the hallway for localization. Any suggestion to improve localization?
My next step is to navigate around the map with different planning algorithms. Any suggestions where  can start?

Thanks for all the help again.





--
You received this message because you are subscribed to a topic in the Google Groups "ROS Sig Aldebaran" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ros-sig-aldebaran/FEtO4Gf9erc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.

To post to this group, send email to ros-sig-aldebaran@googlegroups.com.
Visit this group at https://groups.google.com/group/ros-sig-aldebaran.

For more options, visit https://groups.google.com/d/optout.



--
MSc Candidate in Mechanical Engineering - System and Control 2015-2017
Faculty Mechanical, Maritime and Materials Engineering
Delft University of Technology
Email: ronald.c...@gmail.com
           ronald....@hotmail.com

Paco Dupont

unread,
Apr 5, 2017, 10:08:57 AM4/5/17
to ROS Sig Aldebaran
Hi Ronald,

The robot stop because of the front sonar that is flickering. I've the problem on two Pepper v1.6 here, the sonar regularly return a low range whereas there is no obstacle in front of the robot. The lower module managing velocity cmd on NaoQi then stop the robot to avoid collision and then refuse any incoming forward cmd.

This create a lots of mess with navigation programming ...

--
You received this message because you are subscribed to a topic in the Google Groups "ROS Sig Aldebaran" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ros-sig-aldebaran/FEtO4Gf9erc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ros-sig-aldeba...@googlegroups.com.

To post to this group, send email to ros-sig-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ros-sig-aldebaran.

Paco Dupont

unread,
Apr 6, 2017, 9:15:06 AM4/6/17
to ROS Sig Aldebaran
Hi Natalia,

Can we remove the lenses without warranty void, or we must return Pepper to Aldebaran ?

Best regards,
Paco.

Natalia Lyubova

unread,
Apr 6, 2017, 10:19:59 AM4/6/17
to ROS Sig Aldebaran
Hello Paco,

it is better to ask our support before : https://account.aldebaran.com/support/
I am not sure what happens with warranty then, however we have removed them for some of our partners on their request.


Best regards,
Natalia

Paco Dupont

unread,
Apr 24, 2017, 5:14:41 AM4/24/17
to ROS Sig Aldebaran

Hi Adriano and Ronaldo,

can you share the configuration you used for Pepper with gmapping ? I'm experiencing some strange behavior between the map and the odom frame during the mapping process. My odom frame got some drifting will moving Pepper without gmapping, but nothing unusual.

But when I run gmapping the map and the odom frame are moving from each other (this is due to the odometry correction from gmapping I think but I've some configuration issue so). On this screen the robot run for 3-4 meters and the wall on the left of the robot is the same as the one near the map referencial.




Best regards,
Paco.

Ronald Cumbal

unread,
Apr 24, 2017, 5:25:34 AM4/24/17
to ros-sig-...@googlegroups.com
Hey Paco,

This is the configuration of my launch file:


<launch>
    <node pkg="gmapping" type="slam_gmapping" name="slam_gmapping" output="screen">
        <remap from="/scan" to="/pepper_robot/laser"/>
        <param name="base_frame"            value="base_footprint" />
        <param name="map_frame"             value="map"/>
        <param name="odom_frame"            value="odom"/>
        <param name="map_update_interval"   value="0.1"/>
        <param name="minimumScore"          value="100"/>

        <param name="linearUpdate"          value="0.1"/>
        <param name="angularUpdate"         value="0.1"/>
        <param name="temporalUpdate"        value="-1.0"/>

        <param name="resampleThreshold"     value="0.5"/>
        <param name="particles"             value="100"/>
        <param name="xmin"                  value="-25.0"/>
        <param name="ymin"                  value="-25.0"/>
        <param name="xmax"                  value="25.0"/>
        <param name="ymax"                  value="25.0"/>
        <param name="delta"                 value="0.02"/>
        <param name="maxRange"              value="1.4"/>
        <param name="maxUrange"             value="1.2"/>
    </node>

</launch>

I have notice a big problem with the Rotational Odometry of Pepper. A clear offset error is accumulated with every rotation. Anyone would know how to calibrate this error?



--
You received this message because you are subscribed to a topic in the Google Groups "ROS Sig Aldebaran" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ros-sig-aldebaran/FEtO4Gf9erc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.
To post to this group, send email to ros-sig-aldebaran@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

Paco Dupont

unread,
Apr 24, 2017, 5:51:45 AM4/24/17
to ROS Sig Aldebaran
Thanks a lot Ronald I've got better results with you parameters, I think my minimumScore was too low and my angularUpdate too high.

I'll give a try with AMCL and move_base now.

Thanks again,
Paco.
To unsubscribe from this group and all its topics, send an email to ros-sig-aldeba...@googlegroups.com.

To post to this group, send email to ros-sig-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ros-sig-aldebaran.

adriano...@icar.cnr.it

unread,
Apr 24, 2017, 7:38:02 AM4/24/17
to ROS Sig Aldebaran
Hi Paco and Ronald, 

My configuration parameters are similar, I've been conducted several experiments with different parameters, but I had some problem to understand what are the best parameter set up. 
I wonder if I increment the number of particles (i.e. 300+) I will have better results. 

I would like to have a detailed map because the environment is composed by hallways and rooms similar each other, and the details give a lot of information for the localisation accuracy.



Adriano

To unsubscribe from this group and all its topics, send an email to ros-sig-aldeba...@googlegroups.com.

To post to this group, send email to ros-sig-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ros-sig-aldebaran.

Vincent Rabaud

unread,
Apr 24, 2017, 7:54:23 AM4/24/17
to ros-sig-...@googlegroups.com
Have you guys given a try to Catographer ? https://google-cartographer.readthedocs.io/en/latest/
I just don't want to maintain gmapping anymore :)

To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldebaran+unsubscribe@googlegroups.com.
To post to this group, send email to ros-sig-aldebaran@googlegroups.com.

Paco Dupont

unread,
Apr 24, 2017, 8:11:02 AM4/24/17
to ROS Sig Aldebaran
Hi Vincent,
I tried cartographer last mounth but I was stuck with this Error :

https://groups.google.com/forum/?nomobile=true#!topic/ros-sig-aldebaran/4IfKl35wGX8
> Best regards,
> Paco.
>
>
>
> Le jeudi 30 mars 2017 11:53:55 UTC+2, adriano...@icar.cnr.it a écrit :
> HI Giovanni,
> I'm using gmapping package with laser sensor. (Topic / pepper_robot / laser from pepper_full.launch).
>
>
>
>
>
> Adriano
>
>
>
>
> Il giorno giovedì 30 marzo 2017 11:03:12 UTC+2, Giovanni Claudio ha scritto:
> Hi Ronald and Adriano, 
>
>
> What package are you using to create the map? Which sensors are you using?
>
>
> In my Pepper, I noticed that there is a problem of distortion from the depth sensor. The surface in the following picture should be flat (Pepper here was facing a wall): 
>
>
>
>
>
>
> Is this normal? Also Paco has the same problem.
>
>
>
>
> 2017-03-30 10:54 GMT+02:00 <adriano...@icar.cnr.it>:
>
> Hi Ronald, 
>
>
>
> I have the same issue with mapping. To create a decent map, I teleop pepper with a slow movement and trying to give key points at gmapping package since have a high probability to understand where is the position of the robot on the map and add the new information to build the new part of the map.
> I adopt the strategy to follow the walls of the rooms, the corners so if there are odometry errors the system adjust the position in the map with the estimate of the known environment.
>
>
>
>
>
>
>
>
> Il giorno martedì 28 marzo 2017 16:33:52 UTC+2, Ronald Cumbal ha scritto:
> Hi everyone,
>
> I've ran slam with Pepper successfully, but the outcome is too noisy. I've tried going at a slow pace, but the map is still not clear enough. Any other recommendations as in how to improve the output map?
>
> On Wednesday, September 21, 2016 at 8:20:48 AM UTC+2, Karsten Knese wrote:
> I don't remember the exact quality outcome. But I remember you have to be patient and give it some love :)
> Technically speaking, you have to be aware that the laser is rather limited with just a few points. So I would recommend you to move pepper in a slow pace and cross check the map outcome in rviz.
>
>
> Did you encounter any latency issues?
>
>
> On Wed, Sep 14, 2016 at 3:02 AM, Jason Yang <yangt...@gmail.com> wrote:
>
> Hi Karsten,
> I tested gmapping on my local machine and remotely create map with Pepper.
> But the result comes out very inaccurate. Did you get satisfied result map?
>
> 在 2016年8月22日星期一 UTC+8下午11:58:27,Karsten Knese写道:
> Hi Jason,
>
>
> it would most likely be overkill to compile the complete ROS navigation stack on the robot. I would recommend to cleanly install a selection of packages where you can handle the dependencies. Move_base and gmapping should compile without any big overhead.
>
>
> if it helps, I was testing gmapping on my local machine and remotely subscribed to the laser topic. It was more a proof of concept, but I could create a simple map. This would allow you to not cross compile everything.
>
>
>
>
> On Mon, Aug 22, 2016 at 5:12 AM, Jason Young <yangt...@gmail.com> wrote:
>
>
>
>
> Hi Surya,Thanks for you reply. I've tried Moveit package on Ubuntu. But Our goal is to install Ros into Pepper directly.
> To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldeba...@googlegroups.com.
>
> To post to this group, send email to ros-sig-...@googlegroups.com.
>
> Visit this group at https://groups.google.com/group/ros-sig-aldebaran.
>

Syed Ali Raza

unread,
May 17, 2017, 8:30:58 AM5/17/17
to ROS Sig Aldebaran
Hi,

Has anyone solved the odometry issue?

I am using gmapping with the same configuration like others and using pepper's laserscan.
I moved the robot very carefully and avoided unnecessary rotations. Still, the resulting map is very bad.

Any suggestions? Thanks!

Cheers
Ali

HaSu

unread,
Sep 20, 2018, 1:18:14 PM9/20/18
to ROS Sig Aldebaran
My gmapping attempts were rather poor either so far. I just tried the parameters suggested here and we are finally getting somewhere.
I think it helps to merge all the laser scanners together onto one topic. there are several tools for this, if anyone is interested I can post a link to the one we currently use.

Cartographer was never tested with such little amount of points apparently so I'm not sure if it would work at all - at least that's what I've been told. 
One thing one can do to improve gmapping a bit is to record a bag file and play it back at half the speed, while running gmapping. It usually provides a better map.

Question: What are the experiences so far concerning the range of the laser scanners? I remember reading somewhere that they are usable up to 5m but I am not sure? Does anyone know? Or, with what range are they still usable for navigation?

cheers!
HaSu

luka.fua2

unread,
Sep 20, 2018, 3:49:46 PM9/20/18
to ros-sig-...@googlegroups.com
Back there, when worked with gmapping. Used 3D camera as sensor for building map. Ther is a package for transforming data from camera to point cloud data and you should change in launch file input topic to gmapping.

Luka K.



Poslano s pametnog telefona Samsung Galaxy.

-------- Izvorna poruka --------
Datum: 20.09.2018. 19:18 (GMT+01:00)
To: ROS Sig Aldebaran <ros-sig-...@googlegroups.com>
Naslov: [aldebaran] Re: ROS navigation package for Pepper

--
You received this message because you are subscribed to the Google Groups "ROS Sig Aldebaran" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ros-sig-aldeba...@googlegroups.com.
To post to this group, send email to ros-sig-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ros-sig-aldebaran.

Ronald Cumbal

unread,
Sep 23, 2018, 11:32:35 AM9/23/18
to ros-sig-...@googlegroups.com
I remember that my lasers would work well up to 2 meters. Nevertheless, you can modify this values in the ROS Bridge reading these lasers. The choice given by Luka K. is your best option, although I recall head-motion would introduce a lot of noise. I also used the 3D camera for localization with AMCL and it worked much better. 

These are the parameters I used at the end:
<!--- Start Gmappign node -->
<node pkg="gmapping" type="slam_gmapping" name="slam_gmapping" output="screen" launch-prefix="xterm -e">
<remap from="/scan" to="/pepper_robot/laser"/>
<param name="base_frame" value="base_footprint" />
<param name="map_frame" value="map"/>
<param name="odom_frame" value="odom"/>
<param name="map_update_interval" value="0.1"/>
<param name="minimumScore" value="100"/>
<param name="linearUpdate" value="0.1"/>
<param name="angularUpdate" value="0.1"/>
<param name="temporalUpdate" value="-1.0"/>
<param name="resampleThreshold" value="0.5"/>
<param name="particles" value="1000"/>
<param name="xmin" value="-5.0"/>
<param name="ymin" value="-5.0"/>
<param name="xmax" value="5.0"/>
<param name="ymax" value="5.0"/>
<param name="delta" value="0.02"/>
<param name="maxRange" value="1.4"/>
<param name="maxUrange" value="1.5"/>
</node>
 

Ronald C.


--
You received this message because you are subscribed to a topic in the Google Groups "ROS Sig Aldebaran" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ros-sig-aldebaran/FEtO4Gf9erc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ros-sig-aldeba...@googlegroups.com.


--
Mechanical - Control Engineer
Email: ronald.c...@gmail.com
           ronald....@hotmail.com

Reply all
Reply to author
Forward
0 new messages