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

Message queue not served @ controller rate = 100 Hz #46

Closed
pattacini opened this issue Jun 24, 2016 · 2 comments
Closed

Message queue not served @ controller rate = 100 Hz #46

pattacini opened this issue Jun 24, 2016 · 2 comments
Labels

Comments

@pattacini
Copy link
Member

pattacini commented Jun 24, 2016

We have experienced big problems while controlling reaching with a rate of 100 Hz (i.e. sample period Ts = 0.01 s). What happened was that the internal messages queue got increasing and, as result, the movements got delayed of significant amount of time.

By changing Ts = 0.1 s, we improved the situation, even though a rate of 10 Hz is way low...

cc @randaz81 @barbalberto @ale-git

@pattacini pattacini added the bug label Jun 24, 2016
@barbalberto
Copy link

barbalberto commented Jun 26, 2016

This was related to issue #45, and thus solved by 2d5ecd0.

In general case, we see this problem when a positionMove or setPosition are called on tripodMotionControl at "high" rate.
As a rule of thumb, if this error happens again on CER robot, then verify that the code is not calling a loop over single joint for tripod device or position command are not sent at too high frequency.

@pattacini
Copy link
Member Author

I deem we can close it for now.

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

No branches or pull requests

2 participants