ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2018-02-20 20:53:24 -0500 | received badge | ● Nice Question (source) |
2017-05-17 09:18:33 -0500 | received badge | ● Famous Question (source) |
2017-03-08 07:55:40 -0500 | received badge | ● Famous Question (source) |
2017-03-08 07:55:40 -0500 | received badge | ● Notable Question (source) |
2017-02-02 10:12:33 -0500 | received badge | ● Popular Question (source) |
2017-02-02 09:55:51 -0500 | commented answer | ROS Kinetic Eigen using EIGEN3 in the DEPENDS resolved the porblem! |
2017-02-02 05:47:52 -0500 | asked a question | ROS Kinetic Eigen Since migrating from Indigo to Kinetic, i am receiving the following CMake warning:
Unfortunately I am unable to resolve this issue. The corresponding package.xml: Any suggestion on what is going wrong? |
2016-12-04 10:03:39 -0500 | received badge | ● Notable Question (source) |
2016-12-03 08:55:16 -0500 | commented answer | Temporarily changing of joint limits in RobotState @gvdhoorn I only require the end-effector to be "in front" of the robot. Without limiting the joints the Ik solution derived by TRAC-IK is some weirdly looking "behind the shoulder" grasp. The planning procedure may actually utilize the full joint space. Are you aware of a more elegant solution ? |
2016-12-02 09:18:09 -0500 | answered a question | Temporarily changing of joint limits in RobotState I found that by using the service, it is possible to specify individual moveit_msgs::JointConstraint . First tests yield promising results. |
2016-12-02 09:15:49 -0500 | received badge | ● Popular Question (source) |
2016-12-02 07:55:47 -0500 | received badge | ● Famous Question (source) |
2016-12-02 02:05:24 -0500 | received badge | ● Supporter (source) |
2016-12-02 02:05:20 -0500 | received badge | ● Scholar (source) |
2016-12-02 02:05:17 -0500 | received badge | ● Famous Question (source) |
2016-12-02 02:04:41 -0500 | asked a question | Temporarily changing of joint limits in RobotState I am calculating the IK for my robot setup using: Now on certain occasions, I do have to restrict the joint limits in one of the joints further than required for the default case. Is there any method that allows one to change the joint limits used within the RobotState IK framework? I have seen that the allows one to modify the joint limits. However I do see no way of accessing this method from the RobotState API. Does anyone know of a method or way on how to approach my issue? |
2016-10-26 08:02:04 -0500 | commented question | Image from Raspberry Pi 2, with indigo in Raspbian Jessie The download link you provide requires installing a browser extension. Moreover my download canceled as I exeeded my daily "free download quota". Thank you for your efforts but I consider this type of download platform a major nono! |
2016-10-24 08:00:01 -0500 | received badge | ● Notable Question (source) |
2016-10-21 11:40:17 -0500 | received badge | ● Student (source) |
2016-10-10 13:11:09 -0500 | received badge | ● Enthusiast |
2016-10-09 15:18:49 -0500 | received badge | ● Popular Question (source) |
2016-10-09 05:08:33 -0500 | asked a question | Troubles installing ROS Kinetic on Linux Mint Sarah 18 I am currently trying to install ROS Kinetic on my Linux Mint 18 running laptop. As far as I am aware of, Sarah 18 is based on Linux kernel 4.4 and an Ubuntu 16.04 package base. Following the wiki installation manual, I am running into the following errors (when calling Is this problem related to the fact that I am not using Ubuntu? Are there any methods of installing ROS on Linux Mint Sarah 18? |
2015-11-20 13:41:05 -0500 | received badge | ● Notable Question (source) |
2015-10-28 07:43:58 -0500 | received badge | ● Popular Question (source) |
2015-10-28 07:42:26 -0500 | answered a question | Initial joint configuration using using MoveIt! and Rviz I found out that the initial values need to be set for the joint_state_publishers, as described in the documentation. |
2015-10-27 11:23:46 -0500 | asked a question | Initial joint configuration using using MoveIt! and Rviz I am currently trying to plan and visualize a robot using MoveIt! and Rviz. Having finished the robot URDF, I started the MoveIt! setup assistant and created the MoveIt! configuration package. From what I know, a fake joint controller publishes the robot's joint states which are then visualized in Rviz. Is there any way to set the initial joint configuration of the robot, such that the robot is not placed at the center of origin ? |