[eliasmontini]

Hi RoboDK community,

I'm working on a project that analyses robot motion times across multiple robot configurations and orientations. Specifically, I'm computing both point-to-point motion times and path traversal times for various scenarios.
I've encountered a significant performance bottleneck: as I scale up the number of points or test different orientations, the simulation time increases substantially. To address this, I attempted to use RDK.Render(False) and     RDK.setSimulationSpeed() in Python to disable rendering, but this solution doesn't seem to work.

I am using RoboDK with Python API

• Testing multiple robot configurations
  
• Analyzing various point orientations
  
• Calculating both P2P and path traversal times
  

I'd appreciate guidance on the following:

• Alternative methods to get point2point motion times
  
• Best practices for batch processing multiple configurations
  
• Whether other rendering/visualization settings could help
  

[Albert]

For the simulation of the movement commands to go faster you just need to increase the simulation speed by using setSimulationSpeed. For example:

Code:

RDK.setSimulationSpeed(1000)

You can find more information about setting the simulation speed using the API here:
https://robodk.com/doc/en/PythonAPI/robo...ationSpeed

You can also evaluate your robot movement commands without simulating the actual robot movements by setting the run mode to be a quick validation. Example:

Code:

RDK.setRunMode(RUNMODE_QUICKVALIDATE)

You can find more information about setting the run mode here:
https://robodk.com/doc/en/PythonAPI/robo...setRunMode

[eliasmontini]

Thanks! I will try asap with these commands.