Hi Brian, 
thank you for your helpfulness!
Fortunately, I resolved the problem a couple of hours before!
Anyway, you're right! I made a mistake similar (but not the same!) that I
made with amcl! In few words, I built a "tf publisher" node, but the "odom"
tf frame made reference to wrong coordinate frame, so all odometry data was
wrong: the gmapping was able to receive messages and frames as well, but the
algorithm failed.
Now I fixed my code and everything works fine!!
(I knew that there was a bug in my code, but I didn't able to understand
where).
For this reason, no drop warning messages or similar on rosconsole output! 

By the way, next step in my work could be to build a map using sonar sensors
instead laser (low cost solution), and when try to integrate both sensors:
do you know if anybody already tried to do this in ROS? If I understood
well, the gmapping would be ok for this goal (but not the gmapping wrapper
in ros, right?)
If not, what do you suggest to start this work?

Greetings!
Enea
-- 
View this message in context: http://ros-users.122217.n3.nabble.com/slam-gmapping-messages-problem-tp676863p746122.html
Sent from the ROS-Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
ros-users mailing list
ros-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ros-users