-
Notifications
You must be signed in to change notification settings - Fork 304
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
Duration is out of dual 32-bit range #247
Comments
I try to add debug mode like this:
I modify the launch file like this:
Do I made something wrong? Edit: I modify the argument with : I get that error:
Edit 2:
|
Same issue here, also seems to be random. ROS noetic on Ubuntu 20.04 (in a docker), libfranka 0.9.0-2focal.20220328.144759. |
We also have the same issue. Any update on this, please? |
There is an issue for the same problem in libfranka. You can try out the "solution" that was mentioned there, but I doubt that it will really fix your problem. Honestly, there is not much I can do for you as I cannot reproduce it 😕 |
@marcbone Are my debug logs enough. Do you need other trace ? I can generated it for you. |
We also have had this error for some months:
Scenario
What the problem could berhaschke stated in #232 (and a few days ago checked that the error was still there) that when the start of a controller actually failed, the ControllerManager thinks that controller switching succeeded. Maybe our switch is not successful and we don't know it. But he also mentioned that this raises a ROS error, so I'm not sure if we would see this. Any comments on our thoughts or ideas of what to try are welcome. |
@HumbertoE I try a 'solution' since o,e week. I found on Ros forum that moveit Can create that keep of problem if the package is not updated. So I update Moveit and ROS and it seems to solve my trouve. |
@xav12358 could you share the ROS forum question or issue if you still have it open? We can try this, thanks. I will comment here if this solves the issue for us |
@xav12358 what version of Moveit are you using? Or if installed from source, what commit of the Moveit repository are you at? We are installing it from source and are in commit 7949bd6ea776e1268b8ff9e2015cad5cb695b829 that was done on August 16 (one week before you started testing I think) and we still got the error. I will update moveit to the latest state in the master branch and test in the robot in a couple of days and inform if this solves the issue for us. |
@HumbertoE in fact I use the Ubuntu 20.04 Moveit package. Why do you need to install moveit from source package ? |
So the release 1.1.5 maybe? I will try that one then and see if the duration error disappears. Thank you We had to do some custom changes to one package moveit depends on for our application. The changes are not fixes, so we didn't make any pull request. I will also check that this package is compatible to that release |
We changed to the 1.1.5 release version on Moveit and we still have the same error. We also changed to libfranka version 0.9.2 and franka ros 0.9.1 (before we had both at 0.9.0) and still we get the duration error. In some point we also got another error of the controller not executing commands even when the controller manager said it was ok and running. I manually changed to another controller and then back to the position_joint_trajectory_controller and then it worked. My theory is that when we change controllers, it fails but the controller manager reports it doesn't or it reports it was successful before it finishes (the controller switch service returns success after between 5 and 7 ms) and then when it receives some commands for the controller that is reported as loaded, it fails. The problem here of the failure in changing controllers could be in our implementation, but if the controller switch is reported as successful when it is not, it is very hard to debug. |
Now the problem seems to be solved for us. It hasn't appeared in more than a month, even when we try to provoke it. We were running the ROS core in one computer and the ROS control node in another one with a different version of ROS. Now we have the same version of ROS and this solved the problem. |
It seems to be unrelated to franka_ros but is caused by ABI incompability in the workspace/installed packages. See:
I will close it for now. |
Hello,
I use ROS noetic on ubuntu 20.04.
I run that launch file :
After one or two moveit execution, I get that error:
Unfortunatly there is no franka_control-3.log file. Is there a way to get it?
And then, I don't really no where the problem comes. Can someone help me to solve this?
The text was updated successfully, but these errors were encountered: