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.

Sign up for GitHub

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

Jump to bottom

Integrate easy_profiler to diagnose the procedure #164

Open

1 task

Chunting opened this issue May 17, 2018 · 0 comments

Open

1 task

Integrate easy_profiler to diagnose the procedure #164

Chunting opened this issue May 17, 2018 · 0 comments

Collaborator

Chunting commented May 17, 2018 •

edited

Loading

Integrate easy_profiler into grl to analyze the performance.
The robot won't execute the command till after 31 seconds.

After start the program, we can hear "CLICK" sound immediately, which means robot receives connection request and release the joint;
EXCELLENT signal shows up in SmartPad;
The command sent to robot is printed in Terminator;

However, the robot won't move till after 31 seconds.
In JAVA mode, this problem doesn't exist.

Write a shell to install easy_profiler.

Use easy_profiler to diagnose the procedure, also need to check the java part if it sucks there.

Sample of prof file, open it in easy_profiler
2018_05_04_20_19_50.prof.zip

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