If you URSim is running on a Virtual Machine, RoboDK will consider it as an external device you can connect on.
If both your PC and the VM are connected to the same network, the connection should be achievable the same way you generally connect to a real robot.
Maybe a little more detailed description of the problems.
The first question is: If I run the simulation only in RoboDK (command: RUN), then the simulation runs smoothly. If I run the simulation in both RoboDK and the URSim environment (command: RUN ON ROBOT), the robot does not move smoothly in RoboDK environment - configuration changes appear. Why does this happen?
The second question is: If I use the command: RUN ON ROBOT, then the simulation is performed in both RoboDK and URSim - applies to the moveL command. How can I then similarly execute the moveP command - so that the simulation runs in both RoboDK and URSim at the same time and uses the moveP move command.
So far I've managed to use the moveP command, just by using the option: Send program to robot - but in this case the simulation runs only in URSim environment, but not in RoboDK. Is there any solution for this?
I hope I have explained the problem clearly enough.
02-26-2020, 06:52 AM (This post was last modified: 02-26-2020, 06:52 AM by Mitja GOLOB.)
If I understand correctly, it is possible to run the simulation at the same time in the RoboDK environment as URSim only using the commands: moveJ, moveL, moveC. In this case we use 'Run on robot'.
When using the moveP command, we need to select the appropriate postprocessor (in our case we use: Universal Robots MoveP) and then the 'Send program to robot' command. In this case, we also cannot run simulations in RoboDK and URSim simultaneously.