ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

ryanoldja's profile - activity

2021-08-10 10:34:52 -0500 received badge  Good Question (source)
2021-02-27 00:29:54 -0500 received badge  Nice Question (source)
2019-09-18 15:15:48 -0500 received badge  Famous Question (source)
2019-05-20 02:12:33 -0500 marked best answer dynamixel_motor support for protocol 2.0

Has anyone transitioned from protocol 1.0 to 2.0 following recent firmware upgrades? I'm currently using MX-64T's with the dynamixel_motor stack, but I'm trying to understand what upgrading to protocol 2.0 would entail. Is this as simple as updating the control table addresses in dynamixel_const.py? Or would it be best to incorporate the official Robotis DynamixelSDK package in place of the dynamixel_driver package?

Any advice is appreciated!

2018-10-11 08:28:28 -0500 received badge  Famous Question (source)
2018-09-14 18:09:50 -0500 received badge  Famous Question (source)
2018-02-23 06:25:03 -0500 received badge  Notable Question (source)
2018-02-02 09:44:27 -0500 received badge  Famous Question (source)
2018-01-24 19:20:29 -0500 received badge  Notable Question (source)
2017-12-01 22:58:34 -0500 received badge  Popular Question (source)
2017-11-30 10:42:44 -0500 marked best answer Failed to create the global_planner/GlobalPlanner planner

Setup: ROS Kinetic, Ubuntu 16.04

on the TurtleBot platform, when launching the move_base node configured for the global_planner/GlobalPlanner, I receive the following error:

Failed to create the global_planner/GlobalPlanner planner, are you sure it is properly registered and that the containing library is built? Exception: According to the loaded plugin descriptions the class global_planner/GlobalPlanner with base class type nav_core::BaseGlobalPlanner does not exist. Declared types are navfn/NavfnROS

I load move_base_params.yaml within move_base as follows:

<node pkg="move_base" type="move_base" respawn="false" name="move_base" output="screen" > <rosparam file="$(find robust_navigation)/param/move_base_params.yaml" command="load" />

where the base_global_planner param is defined in move_base_params.yaml as follows: base_global_planner: "global_planner/GlobalPlanner"

I've re-installed the nav stack and re-built my workspace to no avail.

2017-11-30 10:32:45 -0500 commented question Failed to create the global_planner/GlobalPlanner planner

very sorry, the problem seems to have been caused by sourcing conflicting workspace. this is resolved. thanks!

2017-11-29 22:54:19 -0500 asked a question Failed to create the global_planner/GlobalPlanner planner

Failed to create the global_planner/GlobalPlanner planner Setup: ROS Kinetic, Ubuntu 16.04 on the TurtleBot platform, w

2017-10-26 23:32:17 -0500 received badge  Famous Question (source)
2017-10-11 20:47:24 -0500 received badge  Notable Question (source)
2017-10-06 16:19:11 -0500 received badge  Notable Question (source)
2017-10-05 03:59:44 -0500 received badge  Popular Question (source)
2017-08-18 17:48:57 -0500 received badge  Popular Question (source)
2017-08-08 11:10:21 -0500 marked best answer tf2 reversing coordinate frame tree

The tf2 documentation suggests that the implementation somewhat breaks down in cases where coordinate frames require re-parenting. Is there a reasonable solution for completely reversing the child-parent tree?

A simple example: a serial manipulator has 3 joints, 'joint1', 'joint2', 'joint3', and the tf2 tree is configured to reflect this (joint1 --> joint2 --> joint3). At any point, I'd like to reverse the configuration such that the 'joint3' frame is now effectively treated as the 'joint1' frame (i.e. joint3 --> joint2 --> joint1).

A thought: Would a potential solution be to modify the frame_id for each joint? For instance, before reversing, the frame_ids 'joint1', 'joint2', and 'joint3' would correspond to the physical joint1, joint2, and joint3, respectively. Then, could I simply overwrite the frame_ids linked to the physical joints such that the physical joint1 is represented by frame_id 'joint3', etc. ?

2017-08-08 11:09:43 -0500 received badge  Famous Question (source)
2017-08-08 11:08:56 -0500 asked a question Semi-constrained end-effector goal orientation

Semi-constrained end-effector goal orientation I'm using MoveIt! with TRAC-IK to do motion planning for a 6-DOF robotic

2017-08-06 07:22:11 -0500 received badge  Student (source)
2017-08-05 14:23:22 -0500 asked a question dynamixel_motor support for protocol 2.0

dynamixel_motor support for protocol 2.0 Has anyone transitioned from protocol 1.0 to 2.0 following recent firmware upgr

2017-07-28 08:33:50 -0500 received badge  Notable Question (source)
2017-07-28 08:33:50 -0500 received badge  Popular Question (source)
2017-06-26 14:07:32 -0500 received badge  Enthusiast
2017-06-23 19:02:30 -0500 received badge  Notable Question (source)
2017-06-23 16:09:40 -0500 received badge  Supporter (source)
2017-06-23 16:09:14 -0500 marked best answer Guide for managing a ros project with Git

I've been searching around through the documentation/forum posts and haven't really found a good walk-through explaining how to set up version control of a ros project using Git. I'll explain what I have and what I'm hoping to do (it's very possible that what I have in mind is not necessarily the most efficient way of maintaining our source code, so feel free to point me towards something more in-line with current convention or best practices). I am fairly inexperienced with ROS and Git.

Just for a very simple example, I have a catkin workspace ros_ws/ and three packages ros_ws/src/my_pkg_1, ros_ws/src/my_pkg_2 and ros_ws/src/other_pkg.

ros_ws/src/my_pkg_1 & ros_ws/src/my_pkg_2 are packages written and maintained solely be me. ros_ws/src/other_pkg is an external repository that I've cloned into my workspace.

I'd like to have version control for my_pkg_1 & my_pkg_2 within my personal repository and be able to pull and update other_pkg as it is maintained externally. Additionally, I don't want to maintain build/ or devel/ (I typically have seen these directories in the .gitignore in other examples as well). In the end, I want to be able to clone this entire project onto a new machine.

Thanks for any guidance or advice! We want to be sure we're starting off with good organization, as I'd imagine it can be painful to try to reorganize later on ...

2017-06-23 16:09:14 -0500 received badge  Scholar (source)
2017-06-23 11:41:34 -0500 received badge  Popular Question (source)
2017-06-23 11:14:29 -0500 commented answer Guide for managing a ros project with Git

thanks for the example ... so in this instance, is https://github.com/googlecartographer/cartographer.git or https://git

2017-06-23 10:19:54 -0500 asked a question Guide for managing a ros project with Git

Guide for managing a ros project with Git I've been searching around through the documentation/forum posts and haven't r

2017-06-20 08:46:50 -0500 received badge  Popular Question (source)
2017-06-13 11:56:50 -0500 edited question ros kinetic install fails to resolve dependencies (qtbase5-dev)

ros kinetic install fails to resolve dependencies (qtbase5-dev) We are operating on a Raspberry Pi 3 Model B, with Debia

2017-06-13 10:28:42 -0500 asked a question ros kinetic install fails to resolve dependencies (qtbase5-dev)

ros kinetic install fails to resolve dependencies (qtbase5-dev) We are operating on a Raspberry Pi 3 Model B, with Debia