CoppeliaSim forums

json args( json_array_arg ); args.push_back("1"); first arg passed to function args.push_back("2"); second arg passed to function args.push_back("3"); int nScriptHandle = sim.getScript( sim.scripttype_customization, "Script_GUI" ); argsRet = sim.callScriptFun...

Yes you can change the velocity afterwards.

To command the conveyor externally or from another script, simply do:

Remote API is documented here:

https://manual.coppeliarobotics.com/en/ ... erview.htm

Legacy remote API is deprecated. ZMQ Remote API should be used instead.

Hi, the manual is your friend. It is true there aren't many tutorials around to do specific things. This is mainly because once you got the basic concepts, it is very easy to create more complex behavior by composing simpler things. Make sure to have a look at the included example scenes and also st...

Older versions are found here:

https://coppeliarobotics.com/previousVersions

V3.5.0 is probably too old.
Newer versions should maintain backwards compatibility to some extent, you might try one of those.

You will be measuring everything attached to the force sensor, including the gripper itself. The force sensor will be measuring force \vec{F} and torque \vec{\tau} acting on it. Consider a mass M attached at point \vec{r} with respect to force sensor's origin, you'll have: \vec{F} = M \cdot \vec{g} ...

Looks similar to this issue: https://forum.coppeliarobotics.com/view ... hp?p=40808

If you want to block one script execution while another executes, you have to use a combination of threaded scripts and a synchronization mechanism such as signals (e.g. wait in the threaded script with sim.waitForSignal, and set the signal in the other script with sim.setInt32Signal)

Function simROS2.sendTransform (to send just one geometry_msgs/msg/TransformStamped) or simROS2.sendTransforms (to send multiple at once as an array of geometry_msgs/msg/TransformStamped messages) is the way to go; it uses the tf2_ros::TransformBroadcaster class of ROS2.

In the sensor script you already have the angle variable, and p[1],p[2],p[3] which are the coordinates of the point (you can compute vector length to figure out the distance, so you have polar coordinates. Thos coordinates are correct, as confirmed by the lines that you can see by setting showLines=...