CoppeliaSim forums

You can also use the web-based CoppeliaSim front-end...

Cheers

Hello, when controlling a robot from an external application, best would be to have all the IK calculations remain in CoppeliaSim, and the external application only provide e.g. the desired pose of the end-effector. This way also you'd have the exact same behaviour as from within CoppeliaSim. If fro...

Hello, not sure I understand what you mean... In CoppeliaSim, you are not supposed to generate thousands of objects in each simulation pass (e.g. like rain drops), otherwise things will get pretty slow. Best would probably be to use drawing objects just for visualy, then use simple geometric calcula...

Hello, if you use the MuJoCo engine in CoppeliaSim, you can link 2 or more joints via a linear equation. In the joint properties dialog , select Dependent mode for the joint, then edit the dependency equation . One of the joints needs to be in dynamic mode . Have a look at the demo scene scenes/gear...

I highly recommend to use the ZeroMQ remote API, instead of the legacy remote API: the ZeroMQ remote API is much more flexible, easier to use, and faster. Additionally, it covers all API functions you'd also use from within CoppeliaSim.

Cheers

Hello, that is unfortunately too much code to review for us. However take note of following few points: The IRB360 robot is a PKM. As such, it doesn't work out of the box with simIK.findConfigs The IRB360 robot is not redundant. Thus, for each target position, there is either 1 or 0 solution. You ca...

Hello, I tried adding the additional joint to the set and checking what would happen, but I realized that this should not be the procedure to follow Why? You can see the linear guide just as another joint, at the base of the robot. e.g.: guideBase --> prismatic joint --> robotBase --> robotJoint1 --...

You need to run CoppeliaSim V4.6, at least. Then you need to load the plugin from within your script, e.g.: --lua function sysCall_init() sim = require 'sim' simCHAI3D = require 'simCHAI3D' device = 0 toolRadius = 0.01 workspaceRadius = 0.2 simCHAI3D.start(device, toolRadius, workspaceRadius) end Th...

Hello,

you can get some inspiration by looking at the demo scene scenes/vision/objectTracking.ttt

Cheers

Hello, yes, that is right. The sim.pauseSimulation API command actually only makes sense if there is some interaction with the user afterwards, otherwise there is no need/reason to pause a simulation: instead, simply do not step anymore and the result is the same. However, try to add function sysCal...