MariaKrgr's profile - activity

Hello, I use nav2d in a real robot with kinect. But when I call /StartMapping, there is an error:

ERROR: Is the robot out of the map?

Here is a print screen of the costmap and my costmap.yaml.

Any ideas about what's wrong?

(when i had a similar problem with navigation_stack I remember that I moved the origin_x and origin_y of the costmap, but I think nav2d does not have such parameters)

Just for the record, package documentation was rebuild and updated within 3 days.

thank you for the advices! I will be waiting for three days to see any rebuild in doc jobs..

Hello to everyone.

I have successfully added my package to rosdistro for indigo and kinetic. I renamed the directory name to match the package name I gave to it..

Should I do something more, so that the ros documentation status in ros wiki link to be updated?
Because it's still says

"Cannot load information on name: muse_bldc_motor_drive, distro: indigo, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index."

Here is my repository https://bitbucket.org/muserobotics/mu... Here is the documentation link I have already wrote http://wiki.ros.org/muse_bldc_motor_d...

update ros wiki link to my package after renaming it Hello to everyone. I have successfully added my package to rosdist

update ros wiki link to my package after renaming it Hello to everyone. I have successfully added my package to rosdistr

Hello there. I use navigation stack to perform autonomous navigation in known map. I got help from this tutorial http://wiki.ros.org/navigation/Tutori... but, as you can see in the picture below, global costmap is rotated compared to the map. The degrees are not fixed, other times it's 90 degrees, other times 180, or ~40 compared to the map. Everything else (goal pose, local path, global path) is working right according to generated costmaps. Any thoughts?

Hello there, I just performed SLAM with navigation_stack and V-REP simulator. As I know for know, we should give initial position of the robot so that AMCL performs localization and costmaps are generated properly.

My question is: Is there a way to skip the procedure of the user giving the initial position?

After a long search I found out that there is an ABI incompatibility between ROS Indigo and later ROS distros in libroscpp.so library.

Hello there,

I built a ROS package in Ubuntu 14.04 LTS and ROS Indigo and now I test these executables that I built in different Linux and ROS distributions. Giving an example, when I setup a VM with Ubuntu 12.04 LTS and ROS Hydro everything worked fine.

Now I am trying to run my package in Ubuntu 16.04 LTS and ROS Kinetic and I am getting this error:

maria@maria-VirtualBox:~/devel/lib/execDir$ ./executableName 
./executableName: symbol lookup error: ./executableName: undefined symbol: _ZN3ros4initERiPPcRKSsj

and when I filter the symbol:

maria@maria-VirtualBox:~/devel/lib/execDir$ echo _ZN3ros4initERiPPcRKSsj|c++filt
ros::init(int&, char**, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned int)

Also If i search for this symbol in libroscpp.so in ROS Indigo I can find it, but in Kinetic I do not!

Any ideas?

I uploaded a

.gif

it does a similar thing even in the simulation, where I take odometry from V-REP simulator..

The basic map in /map topic is correct, so I guess it's not an odometry issue, but a parameter in costmap.yaml maybe or in another .yaml file...

Hello, I use nav2d package for SLAM on a real robot. All of a sudden costmap building has an issue while updating.. I have uploaded a .gif because it's difficult to describe it:

via GIPHY

It's like the costmap is correct in a small square around the robot, and beyond that square the costmap goes bad.

The weird thing is that I didn't have that issue before some days, and I cannot find which of the things that I changed broke the costmap! I guess it's a parameter but I cannot detect it.

Ok today updating parameters works for some magic reason.. Thank you for your time