[Albert]

Thank you for such detailed report. Taking a look at the log of the first issue I see the following which was a bug on our end when we implemented the RoboDK API in C:

Code:

Debug: Running API Command: "\x00"

This has just been fixed on GitHub with a small edit (tempString variable when establishing the connection):
https://github.com/RoboDK/RoboDK-API/blo...dk_api_c.c
This may help properly establishing the connection without delays and should make the C API more robust.

Also, on Linux we noticed that adding the -API_NODELAY argument helped speed things up. Example:

Code:

["-NOUI", "-DEBUG", ..., "-API_NODELAY"]

The TCP No delay could also be enabled on the C client side by changing this new variable in _RoboDK_connect:

Code:

int use_nodelay = 1; // Change from 0 to 1

Your STDOUT/Debug prints should not do any harm to your project. Quite the opposite, it can help narrow the issue.