IvanV's profile - activity

In a quick look, I see you have not defined any layer in your local costmap. Thus, the costmap will be empty and will no

Sick S3000 ros driver with intensity values Hi, I'm looking for a ROS driver for the Sick S3000 safety laser scanner th

Actually, after updating to a newer version of the package the issue basically disappeared.

@sgermanserrano I'm trying to follow the guide, but I'm unable to download some of the files (headless_setup.yaml), as t

The unfeasible trajectories start at about a dt_ref of 0.5. At 0.3 it doesn't produce unfeasible ones, but the trajector

teb_local_planner: unfeasible trajectories with high dt_ref Hi, I'm trying to use teb_local_planner in a double Ackerma

teb_local_planner: avoid constant path replanning Hello, We are working on a heavy omnidirectional platform using orien

teb_local_planner: avoid constant path replanning Hello, We are working on a heavy omnidirectional platform using orien

Yes, still working on it. There doesn't seem to be any warning being displayed. I've added a small edit with more detail

You need a lot more information for troubleshooting move_base. You should start by attaching your configuration files fo

teb_local_planner: avoid constant path replanning Hello, We are working on a heavy omnidirectional platform using orien

Hi,

We want to use viso2_ros package with a Bumblebee camera to perform visual odometry and feed it to the robot_pose_ekf.

robot_pose_ekf requires covariance matrices to be published in the odometry it receives, giving an error if the input covariance is zero. In the documentation of viso2_ros it says that covariance matrices are not publised, so we are unsure if it will be possible to combine viso2_ros with robot_pose_ekf.

In other answer (answers.ros.org/question/34323/viso2_ros-and-robot_pose_ekf/), it is suggested to use it directly (publishing viso2_ros/odometry to robot_pose_ekf/vo), but according to documentation this shouldn't work, as viso2 doesn't publish covariance matrices and following coments in the answer are not conclusive on the results. We have been unable to test it ourselves yet since we are still setting up everithing.

Before continuing, we would like to know if anyone has used viso2_ros with robot_pose_ekf with success and how have they done it. Also, has anyone estimated the covariances for the viso2_ros process, to insert them manually in the published topic?

Thank you and best regards,

Ivan.

Hello all,

We have a large workspace with plenty packages coming from third party developers. At its moment, dependencies of those packages where solved using rosdep.

However, for documentation purposes we need the complete list of dependencies of all packages.

Is there a way of automatically generate that dependencies list? Something like an option on rosdep to not install anything, but just list all dependencies and output them to console or file.

So far I haven't find such a tool.

Thank you and best regards.

Edit:

Just tested rosdep with --simulate --reinstall options in a new workspace where some source has been placed.

First we run with --simulate:

rosdep install --simulate --from-paths ~/workspaces/project/src --ignore-src
#[apt] Installation commands:
  sudo -H apt-get install ros-indigo-hokuyo-node

It successfully list a ROS package dependency.

If we run also with --reinstall:

rosdep install --simulate --reinstall --from-paths ~/workspaces/project/src --ignore-src
#[apt] Installation commands:
  sudo -H apt-get install ros-indigo-hokuyo-node
  sudo -H apt-get install libeigen3-dev

And it additionally shows an already installed non-ROS dependency.

We now install missing dependencies using rosdep:

rosdep install --from-paths ~/workspaces/project/src --ignore-src

And after that, we run it again with --simulate --reinstall options:

rosdep install --simulate --reinstall --from-paths ~/workspaces/project/src --ignore-src
#[apt] Installation commands:
  sudo -H apt-get install libeigen3-dev

It successfully lists the non-ROS dependency, but doesn't list the ROS dependency.

Running it without --reinstall just gives emply output, as all dependencies are already installed:

rosdep install --simulate --from-paths ~/workspaces/project/src --ignore-src

So its seems that rosdep --reinstall only lists/reinstalls non-ROS packages. Is that the expected --reinstall behaviour?

Ok. So that was a misunderstanding on my part due my light knowledge of ros_control. I guess I was looking for the value

... However, I guess I could use dt to compute the current frequency instead of using it as a parameter. Have to check w

... However, I guess I could use dt to compute the current frequency.

controller_manager update rate I have a controller that uses 2 velocity and 2 position hardware interfaces, and I need t

Thank you. However, in that case update_rate is used to guarantee that the controller makes something at a specific rate

I need to make some computations on the controller that depend on the relation between the controller execution rate and

controller_manager update rate I have a controller that uses 2 velocity and 2 position hardware interfaces, and I need t

Avoiding obstacles is one of the main purposes of the navigation stack. You can either change the planner parameters to

Have you tried using different dynamic parameters? I'm thinking that acc_lim_th: 0.05 is just a too low angular accelera

You don't actually need to modify current steering node. You can just put a "filtering node" in the middle that reads cu

I don't think that feature comes out of the box in ROS. You can always use custom messages or encapsulated messages with

Probably your problem is that you don't have anything beyond the dynamic obstacle, so costmap doesn't get any valid lase

My guess is that costmap is trying to susbscribe to map topic before hector actually creates it, and in my experience to

@akash_p My problem was actually what is mentioned in the first answer: the script had the same name as the package and

I'm building om groovy a catkin package that declares a service and contains a python node that acts as server for the service.

The service is declared in the file usv_comm/srv/sendTwist.srv.

The node script is in the file usv_comm/scripts/usv_comm.py.

The service is listed correctly when I make a rossrv list and rossrv show usv_comm/sendTwist.

The service is imported into the python script by from usv_comm.srv import sendTwist.

However, when I run the node as rosrun usv_comm usv_comm.py, I get the following error:

from usv_comm.srv import sendTwist
ImportError: No module named srv

I have previously declared and used services with rosbuild without problems, but I'm quite new to catkin so I'm basically lost right now.

I have followed the tutorials for creating srv (wiki.ros.org/ROS/Tutorials/CreatingMsgAndSrv) and using services (wiki.ros.org/ROS/Tutorials/WritingServiceClient%28python%29) for catkin and python.

Any insight in this problem will be appreciated.

Configuration files:

setup.py

from distutils.core import setup
from catkin_pkg.python_setup import generate_distutils_setup

d = generate_distutils_setup(
    packages=['usv_comm'],
    package_dir={'': 'scripts'}
)

setup(**d)

CMakeLists.txt

cmake_minimum_required(VERSION 2.8.3)
project(usv_comm)

find_package(catkin REQUIRED COMPONENTS
  rospy
  roscpp
  std_msgs
  geometry_msgs
  message_generation
)

add_service_files(
  DIRECTORY srv
  FILES
  sendTwist.srv
)

generate_messages(
  DEPENDENCIES
  std_msgs
  geometry_msgs
)

catkin_package(
  CATKIN_DEPENDS rospy std_msgs geometry_msgs message_runtime
)

include_directories(
  ${catkin_INCLUDE_DIRS}
)

package.xml

<?xml version="1.0"?>
<package>
  <name>usv_comm</name>
  <version>0.0.0</version>
  <description>The usv_comm package</description>

  <build_depend>message_generation</build_depend> 
  <run_depend>message_runtime</run_depend> 
  <buildtool_depend>catkin</buildtool_depend>
  <build_depend>rospy</build_depend>
  <build_depend>roscpp</build_depend>
  <build_depend>std_msgs</build_depend>
  <build_depend>geometry_msgs</build_depend>
  <run_depend>rospy</run_depend>
  <run_depend>roscpp</run_depend>
  <run_depend>std_msgs</run_depend>
  <run_depend>geometry_msgs</run_depend>

</package>

Thank you and best regards.

Edit 1: Added CMakeLists.txt file.

Edit 2: Added package.xml

Edit 3: Added setup.py