-
Notifications
You must be signed in to change notification settings - Fork 272
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
Feature Request: Continuous Servoing #1
Comments
Hi, Nice to hear that you enjoy python-urx. Concerning 1 I did try to find a solution last year but did made it. both I you do a test with all the available commands movel, movep, speedl, Olivier On 4 August 2014 07:20, Kel Guerin notifications@github.com wrote:
|
Hi Oliver, I would love to see that sample code. I think your second point makes the most sense, sending a socked listener to the robot. I will look into this and make changes to my fork. Cheers, |
Hello! I have been using URX for a while and it is really great code. I really appreciate the clean interface to the robot, as opposed to some other wrappers interacting with universal robots.
I was wondering if it is possible to continuously servo the robot to a pose using URX. I have tried sending a sequence of movel commands using urx, but it seems that the rate is limited by how long it takes to upload the program to the robot. Is there a better way of commanding the robot at say, 50-100Hz? I have an application where I would like to have the robot follow the pose of a Razer Hydra, and with the method I mentioned above I seem to only get about 4Hz communication rate to the robot. I would not be surprised if I am doing it wrong, but I figured I would ask.
I have seen other (bad) implementations that load a program to the robot and communicate with that program over a socket to rapidly send a sequence of movel commands, but it seems that URX was written in sort of a one-program-per-command paradigm (which I like and which makes sense for discrete commands).
If there is no way to do this with the current implementation, I would be happy to contribute this feature, I just wanted to make sure that I wasn't missing something first.
Thanks for the help and the great software!
Cheers,
Kel
The text was updated successfully, but these errors were encountered: