Michael Ripperger

I'm running into a similar issue on the [current kinetic-devel branch](https://github.com/ros-industrial/motoman/tree/7860ff545106d98ed6a3fa0121f2fb60891f69bd) of this repository. I have a robot+rail system (i.e. 2 motion groups) with a DX100. When I call the...

I was previously using a modified version of #179, but had updated to the kinetic-devel branch to utilize the `motoman_es_support` package and found that the driver seemed to work as...

I meant I/O support for bytes/strings/etc. I just changed the wording above

I ran into a similar issue on a project where I was using a rail-mounted ES200RN robot. We weren't doing any sort of high speed operation, but one of the...

All our trajectories started from a zero-velocity state. I'm not entirely sure what you mean by inflating the `time_from_start` field of the initial point. Are you wanting to *insert* the...

Sorry for the delay in addressing this issue, but I have a few suggestions: 1. Try building the workspace without the additional catkin build arguments (i.e. just run `catkin build`)....

I'm okay with merging the optimization changes. I don't think the tool is needed; it's pretty specific to a single use-case and there is already an example (possibly the same...

> I know a while a go some work was done to refactor things into industrial_calibration, but not sure what the status is. Hasn't progressed much; I'm okay with adding...

We should move forward with the changes to `rct_optimizations` and `rct_image_tools` sooner rather than later. Our current development efforts may make it difficult to reconcile those packages (at least `rct_optimizations`)...

I think we could move the data and target loading functions into `rct_image_tools` since they primarily deal with loading targets and images. I believe `yaml-cpp` and `xmlrpcpp` are both ROS-independent...