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

Unable to launch op3_manager on ROBOTIS OP3 #60

Closed
VasilyevGeorgy opened this issue Mar 14, 2019 · 4 comments
Closed

Unable to launch op3_manager on ROBOTIS OP3 #60

VasilyevGeorgy opened this issue Mar 14, 2019 · 4 comments
Assignees
Labels

Comments

@VasilyevGeorgy
Copy link

VasilyevGeorgy commented Mar 14, 2019

Hi!
After packages upgrade on the real OP3 the robot doesn't take initial position.
When I try to launch op3_manager in console there appears an error:

Unable to launch [op3_manager-2]. 
If it is a script, you may be missing a '#!' declaration at the top.
The traceback for the exception was written to the log file

Regards
George

P.S.: buttons on back also stopped to work.

@kaym9n
Copy link
Member

kaym9n commented Mar 15, 2019

Hi

Could you tell me how to upgrade to OP3
and tell me more about the error message?

Regards,
Kayman

@VasilyevGeorgy
Copy link
Author

OP3 terminates with an error
GDB log:

terminate called after throwing an instance of 'std::runtime_error'
  what():  Duration is out of dual 32-bit range

Thread 13 "op3_manager" received signal SIGABRT, Aborted.

@VasilyevGeorgy
Copy link
Author

Kinetic sync seemed to have introduced an ABI break. A complete, clean rebuild of the workspace was required, not just compiling again. Now it works fine

@kaym9n
Copy link
Member

kaym9n commented Mar 18, 2019

I am glad to be well.
If you have any other questions, please open the issue.
Thanks

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