Hello,
I had the exact same issue than the author of this post.
As explained here I fixed it by moving the remoteApiConnection.txt from Resources to MacOs, with CoppeliaSim 4.2.
However this fix does not work for CoppeliaSim 4.3 for MacOS and I now have again the exact same issue than at the beginning.
Do you have any hints on that ?
Best regards
remoteApi plugin problem
Re: remoteApi plugin problem
Hello,
what language are you using with the remote API?
what language are you using with the remote API?
Re: remoteApi plugin problem
I'm using Python.
It seems that there is no incoming connections with the continuous server running on port 19997.
It seems that there is no incoming connections with the continuous server running on port 19997.
Re: remoteApi plugin problem
If you are using Python, then please use the ZeroMQ remote API, which is much easier to use, has all API functions, and is more flexible.
Cheers
Cheers
Re: remoteApi plugin problem
I have found the same problem in CoppeliaSim 4.4.0. Copping the file remoteApiConnection.txt from coppeliaSim.app/Contents/Resources to coppeliaSim.app/Contents/MacOS does not solve the problem. Any ideas?
Re: remoteApi plugin problem
The legacy remote API is deprecated, and we highly recommend using the ZeroMQ remote API instead.
But if you still need to use the legacy remote API: does it print something when you type simRemoteApi in the status bar? In other words, I want to know if the legacy remote API plugin is correctly loaded. If it is, then you can start a remote API server service with simRemoteApi.start(portNb,1300,false,true), where portNb could be 19997 to have the same behaviour as with the remoteApiConnection.txt file.
Cheers
But if you still need to use the legacy remote API: does it print something when you type simRemoteApi in the status bar? In other words, I want to know if the legacy remote API plugin is correctly loaded. If it is, then you can start a remote API server service with simRemoteApi.start(portNb,1300,false,true), where portNb could be 19997 to have the same behaviour as with the remoteApiConnection.txt file.
Cheers