-
Notifications
You must be signed in to change notification settings - Fork 73
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
Position Control using ROS #152
Comments
It is possible to control joint positions over FRI with GRL, and we've been able to command positions. Do you need specific instructions on activating FRI with GRL? Have you been able to install the driver on Sunrise and command the arm with GRL? If so activating the FRI API should be fairly simple and we can go from there. Please note the FRI feature is still a work in progress but we are happy to work with you on it. Regarding the force and torque sensors in the arm, there are known issues with the iiwa LBR and the readings are very inaccurate. A solution to this problem has recently been published, and we'd love to support integration of it into GRL. See https://www.disneyresearch.com/publication/toward-torque-control-of-a-kuka-lbr-iiwa/ for details, the paper itself can also be downloaded at that link. Note that this would be a substantial undertaking, and if you'd like a quick-fix solution I recommend simply purchasing a force torque sensor such as those provided by robotiq or other firms and attaching it to your end effector. |
I have installed the driver on the Sunrise controller so a brief how-to on how to use FRI with grl and which Java APIs and cpp files work together would be most useful. I am currently using an external force sensor attached to the end eff for this project, so will be sticking with the simple option for now. |
Be very careful the first time you run things with the big read button handy at all times. The robot should start straight up with all joints at 0 for this test. So you followed the following steps? Once those steps are all done, starting up the driver is just selecting GRL_Driver from the kuka teach pendant's application list, ensuring autonomous mode is enabled and hit play. It will sit an wait there until grl connects to it. If you would like to test the ROS driver, you just launch the driver executable Then run the kuka_ros_test_command.sh to make it move, just one joint should rotate a few degrees. You can play around and modify the script to send a variety of joint positions.
We also have a fully integrated ROS setup that works with the kuka and integrates with https://github.com/IFL-CAMP/iiwa_stack/ at: |
Do you have any other questions? |
Sorry, I've had to work on other things instead recently. |
you need to use ccmake and set Alternately, you can see how it is done with cmake parameters in: Don't forget to put the FRI zip in the data folder or the driver won't build. |
I'm still having issues with |
which version of grl and sunrise are you using? |
I am using the latest version of grl on the master branch. Sunrise version is 1.10.0.8 |
Ah we have 1.11, and I think that might be the source of the problem. Is there any chance it might not be too difficult to upgrade? |
I managed to get Sunrise 1.11 which solved the issues with the TransformationProviderApp folders. |
It seems like you need to update your flatbuffers version as well. The current release is https://github.com/google/flatbuffers/tree/v1.8.0 |
It was 1.8 that I had but reinstalled it from that link and still got the same problem. |
sorry can you run with |
|
very strange, && is being inserted between... The command should be something more like:
The flatc command generates code that helps with sending messages to the robot. Which version of grl are you on, master or 4.1? |
I'm using the master branch version |
I'm unable to reproduce the error, things seem to compile ok for me, including flatc. What version of cmake are you using? Here is mine:
|
CMake version is 3.5.1 |
Updated to 3.10.2 but still getting the same result. When I run the |
Probably too late, but I ran into the same errors (flatc one and sphinx one) and after some tries, I managed to correctly compile the code:
I also had to change two files due to another error with spdlog:
I had to add at the top of both of them this include line: Otherwise I got the following error several times in different parts of the mentioned files:
|
thanks! Sorry that I had not seen these posts until now |
Some of these items might be fixed in #166 as well |
@ahundt did you use the iiwa_ros_java on the KUKA workbench project when you integrate the iiwa_stack? |
I’m trying to recall the details, I think I ran the GRL Java driver on the
robot but integrated the models from iiwa stack and possibly a couple of
rod messages. There is a small ros program built into GRL which converts
everything to ros messages. You might have to check the cmake settings and
dependencies to enable it.
On Sat, Aug 24, 2019 at 5:09 AM Jack Liu ***@***.***> wrote:
@ahundt <https://github.com/ahundt> did you use the iiwa_ros_java
<https://github.com/IFL-CAMP/iiwa_stack/tree/master/iiwa_ros_java> on the
KUKA workbench project when you integrate the iiwa_stack
<https://github.com/IFL-CAMP/iiwa_stack>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#152?email_source=notifications&email_token=AAANTQE4FVDAAG2SMINALUDQGECHPA5CNFSM4EHHYDZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5B5FVY#issuecomment-524538583>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAANTQAJV2F72V7EWPZBWRDQGECHPANCNFSM4EHHYDZA>
.
--
Cheers!
Andrew Hundt
|
I am working on a project where I need to directly command Cartesian or joint positions to a KUKA iiwa LBR 14 using ROS. These positions are calculated in C++ from force sensor readings at either 500 or 1000Hz. I have previously tried this using DirectServo and SmartServo without using a FRI connection but the movements were performed too slowly.
Is there functionality in your toolkit that allows for this?
Thanks.
The text was updated successfully, but these errors were encountered: