Fix for issue #42: driver was checking for wrong comm type to send reply message

ros-industrial / abb

ROS-Industrial ABB support (http://wiki.ros.org/abb)

146 stars 154 forks source link

Fix for issue #42: driver was checking for wrong comm type to send reply message #62

Closed Levi-Armstrong closed 9 years ago

Levi-Armstrong commented 9 years ago

After a trajectory stop command was sent to the abb driver the user was unable to send any new trajectories to the abb driver. The issue was that trajectoryStop function within ROS was waiting for a reply message that the abb driver never sent because it was looking for the wrong comm type to send a reply message.

The comm type required to send a reply message was changed from ROS_COM_TYPE_SRV_REPLY to ROS_COM_TYPE_SRV_REQ fixing the issue.

shaun-edwards commented 9 years ago

+1...Thanks for the contribution.