G.A. vd. Hoorn

@ivareri: re: cartesian: my apologies, somehow I interpreted your OP as implying that the external axes would be controlled using a Cartesian interface.

You still appear to be using MoveIt to plan trajectories for you. In essence, you are using it to generate very short plans, very rapidly. You then publish those trajectories...

@EricMarcil: @harumo11 is using #215, which extends the driver with a streaming interface. This allows users to produce `JointTrajectoryPoint`s at a suitable rate, while the driver essentially executes an "infinite"...

@MarqRazz: could I please ask you to calm down a little? Your phrasing and choice of words make your comments sound somewhat antagonistic. You may not intend it that way,...

Additionally: @MarqRazz: could you confirm whether you are using the standard driver or with #215 merged? If you don't have #215 merged, this issue is not the place to post...

> Sorry @tanimfresh and @harumo11 for dirtying up your issue thread! I would be happy to remove my comments from here if you would like me to clean it up....

There is now support for [substitution args](http://wiki.ros.org/roslaunch/XML/rosparam) in the `roslaunch` `rosparam` tag. That would make what @mikepurvis suggests possible without resorting to template expansion.

@shaun-edwards: note the comment by @jim-rees: > (not including the cartesian jogging)

@chrisgilmerproj reported difficulties running the (new) driver in `AUTO` mode and also provided some comments on how to configure the/his controller to get this to work. Ref: https://github.com/gavanderhoorn/fanuc_driver_exp/issues/2#issuecomment-294232058.

@marip8 wrote: > Add support for multi-group I/O reading/writing what is this exactly @marip8 ? Reading/writing bytes and words, or getting everything to work in both the single and multi-motion...