-
Notifications
You must be signed in to change notification settings - Fork 115
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
[Python] Update() replies with incorrect simulation time #39
Comments
It looks like there is around 10% discrepancy... This does not look normal. |
Using Update() twice does not help. rdk file is enclosed |
I believe the main problem is that the start point is undefined. You'll get different cycle times depending on where the robot is coming from (last point where the robot was left). To avoid confusion with the API I recommend you to impose the robot position to the last known position of the robot. For example, the last point of your program if you are planning to run your program in a loop. I also recommend you to check if the path is feasible before relying on the cycle time. I changed the TCP of your simulation to make sure the programs that you are automatically generating are feasible. Another detail: I recommend you to make the first move of a program joint move. This will make sure the robot joints are defined as you expected for the program. See attached RDK file.
|
Using the next snippet, that generates a program with different targets and speed, the update func is used to know the estimated simulation time.
Unfortunately, it replies correctly only for the first program call.
To obtain the right simulation time, I have to uncomment this code (and this not wanted in my case....):
python program I used:
wrong results without RunProgram():
wrong_results.txt
good results with RunProgram():
good_results.txt
The text was updated successfully, but these errors were encountered: