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

RobotRob's profile - activity

2019-05-20 01:12:38 -0500 marked best answer dynamixel_workbench: message fields for single_manger to multi_port

I am running ROS kinetic on Ubuntu 16.04.3 LTS (and kernal name 4.13.0-32-generic). I am working with the dynamixel_workbench stack. Specifically, I have a MX-106, an MX-64, and another MX-64 daisy-chained.

I want to get a rough estimate of torque output of motors over time. The message published to the topic /dynamixel/MX when I run single_manager.launch contains Present_Load, Present_Voltage, and Present_Temperature. I am interested in knowing these values when I run 3 motors.

When I run roslaunch my_dynamixel_workbench_tutorial multi_port.launch to control my 3 motors, the message published to /dynamixel_state does not contain those same fields I am interested in.

Is there a straightforward way to have the voltage/load/temperature fields published for multi_port (ideally without delving through the source code and creating my own custom overlay)?

2019-04-13 12:21:28 -0500 received badge  Famous Question (source)
2019-02-28 11:49:17 -0500 commented question Moveit! interactive marker is not appearing

I did not figure out a solution.

2019-02-06 20:16:40 -0500 received badge  Famous Question (source)
2018-10-28 08:02:48 -0500 received badge  Famous Question (source)
2018-06-18 05:34:34 -0500 received badge  Famous Question (source)
2018-05-08 12:17:00 -0500 received badge  Notable Question (source)
2018-05-08 07:21:21 -0500 received badge  Popular Question (source)
2018-05-07 14:24:03 -0500 asked a question Daisy-chained motors' publish rate is slow: dynamixel_workbench

Daisy-chained motors' publish rate is slow: dynamixel_workbench I am running ROS kinetic on Ubuntu 16.04.3 LTS (and kern

2018-05-03 17:51:06 -0500 received badge  Notable Question (source)
2018-04-05 07:58:01 -0500 received badge  Notable Question (source)
2018-04-01 20:59:07 -0500 commented answer dynamixel_workbench: message fields for single_manger to multi_port

just to clarify, adding dynamixel_state[cnt].Present_Load =dxl_wb_[port_cnt]->itemRead(dxl_id_[port_cnt][index

2018-04-01 20:46:54 -0500 received badge  Popular Question (source)
2018-03-30 16:16:33 -0500 asked a question dynamixel_workbench: message fields for single_manger to multi_port

dynamixel_workbench: message fields for single_manger to multi_port I am running ROS kinetic on Ubuntu 16.04.3 LTS (and

2018-03-28 15:33:39 -0500 commented question pan_tilt_port: No motors found.

did you end up resolving this?

2018-03-28 07:55:32 -0500 received badge  Supporter (source)
2018-03-28 07:50:39 -0500 received badge  Enthusiast
2018-03-27 21:39:17 -0500 received badge  Popular Question (source)
2018-03-27 13:15:03 -0500 commented question Moveit! interactive marker is not appearing

Didn't press save on the update, oops. Now it's up.

2018-03-27 13:14:26 -0500 edited question Moveit! interactive marker is not appearing

Moveit! interactive marker is not appearing I am running ROS kinetic using rviz version 1.12.15 on Ubuntu 16.04.3 LTS (a

2018-03-27 11:47:51 -0500 commented question Moveit! interactive marker is not appearing

I added the console output for the simpler URDF package generation (from stephen zuccaro's youtube tutorial) to my initi

2018-03-27 10:05:06 -0500 asked a question Moveit! interactive marker is not appearing

Moveit! interactive marker is not appearing I am running ROS kinetic using rviz version 1.12.15 on Ubuntu 16.04.3 LTS (a

2018-03-21 13:03:00 -0500 commented question rqt_plot error from incomplete joint state data

I am having a similar issue with several servo motors publishing in array format. Did you end up resolving this?

2018-03-19 12:08:45 -0500 received badge  Notable Question (source)
2018-03-19 08:32:00 -0500 commented question dynamixel_controllers tutorial issue: Waiting for joint trajectory action

I changed the line self.jta = actionlib.SimpleActionClient('/'+self.name+'_controller/follow_joint_trajectory', FollowJo

2018-03-19 04:15:23 -0500 received badge  Popular Question (source)
2018-03-10 17:39:59 -0500 commented question dynamixel_controllers tutorial issue: Waiting for joint trajectory action

I figured it out. It turns out that removing _controller from the self.jta = actionlib.SimpleActionClient call in the py

2018-03-09 16:27:01 -0500 asked a question dynamixel_controllers tutorial issue: Waiting for joint trajectory action

dynamixel_controllers tutorial issue: Waiting for joint trajectory action Hello, I am fairly new to ROS and have recentl