Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for all iiwa_msgs? #4

Closed
ahundt opened this issue Mar 3, 2016 · 5 comments
Closed

Support for all iiwa_msgs? #4

ahundt opened this issue Mar 3, 2016 · 5 comments
Labels

Comments

@ahundt
Copy link

ahundt commented Mar 3, 2016

Can this send/receive any messages besides JointPosition?

The readme said the app can "iiwa_ros_java: the ROSJava interface to use on SunriseApplications - it allows to send and receive messages defined in iiwa_msgs", however reading the actual ROSSmartServo code perhaps there are some changes implementing that functionality not publically available yet?

@SalvoVirga
Copy link
Member

Indeed it "can" send/receive any iiwa_msgs right away.
The ROSSmartServo applications was born as an exemplary application, it shows how to send and receive JointPosition messages. It contains instances of iiwaPublisher and iiwaSubscriber and they do the job, for example at line 135 subscriber.getJointPosition() it will give you the last commanded JointPosition. iiwaSubscriber has all the interfaces necessary to obtain any iiwa_msgs and do what you need to do with them. The method publish() of iiwaPublisher, will just publish any iiwa_msgs previously set (but only if a subscriber is listening).

In general, once you get a clear idea of the stack in the master branch I would suggest you to use the development one. There, ROSSmartServo already publishes the complete state of the robot and it allows robot control both with JointPosition and CartesianPosition (actually, iiwa_msgs is also different there), with a seamless transition between the two.
That branch has a lot of bug fixes and better functionalities than master, the downside is the nothing is documented in the wiki, but with some knowledge on ROS and the KUKA APIs it should be easy to use.

@SalvoVirga
Copy link
Member

More on that, we will probably merge the devel branch into master this week.

@marcoesposito1988
Copy link
Collaborator

In the master branch it was possible to command the robot only in joint position mode. In development we added cartesian control, and we also switched back to standard ROS messages when a custom type is not necessary.

We will specify the possible control modes after merging development into master. Thank you for asking!

@SalvoVirga
Copy link
Member

New version of the framework is now in the master branch.
Also updated readme and wiki, hopefully they are more complete and clear now.

@ahundt
Copy link
Author

ahundt commented Mar 14, 2016

Interesting, thanks for the updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants