We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A group of users is wondering if it makes sense to change checkEncoders so that it accepts arbitrary pose.
checkEncoders
Currently with checkEncoders the joints movement happen here I suppose:
self.rh_svc.initializeJointAngle(jname, option)
Looks like we need to change hrpsys if we want to achieve this change?
The text was updated successfully, but these errors were encountered:
checkEncoders is hard coded in libiob.so, so we have to ask them for it's possibility, also we do not know what initializeJiontAngle do, actually.
◉ Kei Okada
On Fri, Apr 24, 2015 at 3:29 AM, Isaac I.Y. Saito [email protected] wrote:
A group of users is wondering if it makes sense to change checkEncoders so that it accepts arbitrary pose. Currently with checkEncoders the joints movement happen here rtmros_hironx/hironx_ros_bridge/src/hironx_ros_bridge/hironx_client.py Line 647 in 330175f self.rh_svc.initializeJointAngle(jname, option) I suppose: self.rh_svc.initializeJointAngle(jname, option) Looks like we need to change hrpsys if we want to achieve this change? — Reply to this email directly or view it on GitHub #359.
Currently with checkEncoders the joints movement happen here
rtmros_hironx/hironx_ros_bridge/src/hironx_ros_bridge/hironx_client.py
Line 647 in 330175f
— Reply to this email directly or view it on GitHub #359.
Sorry, something went wrong.
No branches or pull requests
A group of users is wondering if it makes sense to change
checkEncoders
so that it accepts arbitrary pose.Currently with checkEncoders the joints movement happen here I suppose:
Looks like we need to change hrpsys if we want to achieve this change?
The text was updated successfully, but these errors were encountered: