-
Notifications
You must be signed in to change notification settings - Fork 97
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
[Fetch] jsk_fetch_robot/fetcheus/fetch-interface.l :angle-vector, :angle-vector-sequence supports old API #795
[Fetch] jsk_fetch_robot/fetcheus/fetch-interface.l :angle-vector, :angle-vector-sequence supports old API #795
Conversation
@k-okada This is just a question, but |
@knorth55 , I think so, originally we have trouble if we send trajectory startring from current time, and receiver (robot controller) receved that trajectry as a past time (assuming it takes time during data transfer), the controller did not execute the time, that's why we added start-time, may we no longer need that one, for example start-jsk/rtmros_common#1013 :angle-vector
:angle-vector-motion-plan
|
pass start-time to start-offset-time and support :start-time key
@k-okada can you merge this? |
this is rewrited version of #791
related to jsk-ros-pkg/jsk_pr2eus#302, some people like old
:angle-vector
API, likecurrently we have to use