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

Implement additional motor/axis yarp::dev interfaces #55

Open
jgvictores opened this issue Dec 22, 2017 · 3 comments
Open

Implement additional motor/axis yarp::dev interfaces #55

jgvictores opened this issue Dec 22, 2017 · 3 comments

Comments

@jgvictores
Copy link
Member

Think about implementing additional motor/axis yarp::dev interfaces:

@PeterBowman
Copy link
Member

http://www.yarp.it/classyarp_1_1dev_1_1IAxisInfo.html

Might be blocked by roboticslab-uc3m/teo-main#44 (renaming joints).

@jgvictores jgvictores pinned this issue Nov 19, 2019
@jgvictores jgvictores changed the title Think about implementing additional motor/axis yarp::dev interfaces Implement additional motor/axis yarp::dev interfaces Nov 19, 2019
@jgvictores
Copy link
Member Author

http://www.yarp.it/classyarp_1_1dev_1_1IAxisInfo.html

Done at 571abb9

Might be blocked by roboticslab-uc3m/teo-main#44 (renaming joints).

Thanks to roboticslab-uc3m/teo-openrave-models#35 for roboticslab-uc3m/teo-main#44, we actually have the pretty names. ^^

Screenshot from 2019-11-19 15-07-49

@jgvictores jgvictores unpinned this issue Dec 3, 2019
@PeterBowman
Copy link
Member

Besides, we are missing an implementation for IPositionControl::getRefAcceleration and IEncoders::getEncoderAcceleration (at least a dummy one which simply returns zero and true). It is causing trouble in:

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

No branches or pull requests

2 participants