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

Joint trajectory is executed immediately even if its time stamp is in future #1048

Open
pazeshun opened this issue Jul 9, 2018 · 6 comments · May be fixed by #1052
Open

Joint trajectory is executed immediately even if its time stamp is in future #1048

pazeshun opened this issue Jul 9, 2018 · 6 comments · May be fixed by #1052

Comments

@pazeshun
Copy link
Collaborator

pazeshun commented Jul 9, 2018

(send *ri* :angle-vector (send *robot* :angle-vector) 1000 nil 10) immediately starts and completes in 1 sec, but it's wrong behaviour.
angle-vector execution should start at 10 secs after commanding because start-time is set as 10 secs.

@YoheiKakiuchi
Copy link
Member

HrpsysSeqStateROSBridge ignores start-time.
(It's not only for roseus but also other ros interface. )

@pazeshun
Copy link
Collaborator Author

pazeshun commented Jul 9, 2018

HrpsysSeqStateROSBridge ignores start-time.

Is there any reason for this?
I think the simplest solution is to add sleep in action client callback when start-time is enabled, but does this solution harm something?

@pazeshun
Copy link
Collaborator Author

the simplest solution is to add sleep in action client callback when start-time is enabled

I found this solution is harmful because joint_states stops while sleeping...

@emijah
Copy link
Contributor

emijah commented Jul 10, 2018 via email

@pazeshun
Copy link
Collaborator Author

Do you think you can add a countdown feature somewhere?

Maybe countdown feature can be added to execution loop.

@emijah
Copy link
Contributor

emijah commented Jul 10, 2018 via email

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

Successfully merging a pull request may close this issue.

3 participants