[Python] Update() replies with incorrect simulation time about robodk-api HOT 3 CLOSED

It looks like there is around 10% discrepancy... This does not look normal.
Do you have the RDK file to reproduce this issue?
Can you try calling Update twice?

from robodk-api.

Using Update() twice does not help. rdk file is enclosed

demo_0801.zip

from robodk-api.

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.

demo_0801 v2.zip

    # Define the start point of the robot before simulating or updating the program 
    # (for example, the last target in case we run this program in a loop)
    # Indicate that this target is a Cartesian target 
    # (this recalculates the joint values of the target)
    home.setAsCartesianTarget()

    # Retrieve the calculated joints
    startjoints = home.Joints()

    # Set the robot to that location and update to retrieve estimated cycle time
    robot.setJoints(startjoints)
    update_result = prog.Update(check_collisions)

from robodk-api.