01-22-2023, 05:35 PM
Can you try connecting the C API first, then the Python API? This issue could be related to the Safe mode and Auto Update flags which are defined with every new connection.
The API should work even if you have 2 or more clients connected to the same instance of RoboDK and the same port.
There may be a bug with a specific function such as getItem when you use multiple clients. Calling RDK.Render(False) may help so you won't provoke a new render event with every call of the API.
It would be great if you can share a RoboDK project to reproduce this issue. Otherwise, sharing a debug log file can also help us chase this crash. You can obtain this debug log file by following these steps:
1. Close RoboDK
2. Start RoboDK by double clicking the file:
C:/RoboDK/RoboDK-Debug.bat
3. Try to reproduce the problem in RoboDK until it crashes.
4. Right after the crash, send me this file:
C: / RoboDK / bin / RoboDK.debug.txt
The API should work even if you have 2 or more clients connected to the same instance of RoboDK and the same port.
There may be a bug with a specific function such as getItem when you use multiple clients. Calling RDK.Render(False) may help so you won't provoke a new render event with every call of the API.
It would be great if you can share a RoboDK project to reproduce this issue. Otherwise, sharing a debug log file can also help us chase this crash. You can obtain this debug log file by following these steps:
1. Close RoboDK
2. Start RoboDK by double clicking the file:
C:/RoboDK/RoboDK-Debug.bat
3. Try to reproduce the problem in RoboDK until it crashes.
4. Right after the crash, send me this file:
C: / RoboDK / bin / RoboDK.debug.txt