So it is recommended to use UDP instead of TCP, if possible.
In principle, TCP communication can be implemented via C# scripting,
but I have to issue a warning in this regard:
Scripts should always have a short runtime (they block the entire(!) workflow as long as they are running).
Waiting times (e.g. threads or timeout for network connections/sockets/etc.) are not good at all. They can throw the system off course.
We point out in the manual not to use threads.
So you can't leave the TCP connection open, otherwise the workflow will block.
Establishing a short connection, send a command, then close again, will probably work.
but I have to issue a warning in this regard:
Scripts should always have a short runtime (they block the entire(!) workflow as long as they are running).
Waiting times (e.g. threads or timeout for network connections/sockets/etc.) are not good at all. They can throw the system off course.
We point out in the manual not to use threads.
So you can't leave the TCP connection open, otherwise the workflow will block.
Establishing a short connection, send a command, then close again, will probably work.