CoppeliaSim forums

Happy to see, that you can reproduce the bug xD
Thanks for the workaround !

Cheers

When I do a netstat -ltnp , I got this result : tcp 0 0 0.0.0.0:19997 0.0.0.0:* LISTEN 60891/coppeliaSim tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1037/cupsd tcp 0 0 0.0.0.0:23000 0.0.0.0:* LISTEN 60891/coppeliaSim So I got the warning for the legacy remote API, ok I understand. But why, they don't con...

Hello, When I launch coppeliaSim, I add this parameter : -GzmqRemoteApi.rpcPort=23006 I launched several simulators with the port being 23000+i*2 with the index of the simulator. On the last rev, i've seen that all the ZMQ remote servers were launched in the 19997 port... Does the set-up to configur...

Just to update the subject.
So doing N install folders solve the problem.

Hope, this bug will be fixed in the next update.

Cheers,

Alexis

Ok, I will try to do that, if there is not so much solution right now.

Thanks for your help !

Alexis

So, after what we discussed, I checked that the ZMQ_remote API was called within the same thread and same process for each running simulation. And with the new coppelia version that got uploaded recently, I wanted to see if the crash disappeared but unfortunately not. But at least, I got some logs w...

Hello, as long as you are calling ZeroMQ remote API functions from within the same thread (within the same process), you should be fine. But a crash can always happen. It would help to know why or where CoppeliaSim crashed... do you think it is specifically related to the ZeroMQ remote API function...

Working Environment : Ubuntu 22.04 CoppeliaSim v4.5.1 (rev4) ZmQRemoteApi Context I launch 5 programs simultaneously in headless mode like: coppeliaSim.sh -GzmqRemoteApi.rpcPort=port -h -gnamespace model_path The port are : 23000+2*i ( i being the id of the program) I'm using ROS2 in each of my pro...

Hello, yes, this could be a synchronization problem between two separate threads. But in general, if OMPL does not return a path that comes close to what is desired, this means that you ran out of time with computation. Try specifying a larger timeout value, or redo your computation if you notice t...

Ok I found a solution. It seems that it's caused by the interaction between my Python code and the Lua side within the simulator.

It might be a problem of synchronization between the 2 threads?