OSCrouter, eos qlab and TCP.

It is not possible to connect QLab and EOS via TCP, both applications works as a TCP Server but one of the apps must work as a TCP Client.
There is a feature request to add a TCP Client to the EOS software.

Ok, thank you.

But the question is still unanswered, is there any dokumentation on how the software works? It is a lot of trail and error now for me.

This article is your starting point in general for connecting
https://support.etcconnect.com/ETC/Consoles/Eos_Family/Software_and_Programming/Triggering_QLab_from_Eos_using_OSC

For the router
https://github.com/ETCLabs/OSCRouter/wiki

And one more thing. In OSCrouter's TCP settings I can't connect to any of them (One by one) if I set them to server, but setting them as clients I can have both connected. I am having Eos set as client in TCP settings on OSCrouter and get TCP in to OSCrouter. The OSC router is outputting UDP to Qlab. I had drops of the important commands out of Eos on UDP not triggering Qlab. This way I can at least secure the Eos-OSCrouter connection and there filter out what to send to Qlab to get the traffic down. But TCP the whole way would be nice.

Thanks, I found them. It is nothing about how the TCP part work, the manual for OSCrouter is copied (?) from a (old) guide about to connect Eos and Qlab, telling you to "Check out the OSCRouter documentation for more amazing features" and "On the Qlab computer, download an application called OSCRouter (written by Eos developer, Chris Mizerak) from the ETC Labs Git Hub page: https://github.com/ElectronicTheatreControlsLabs/OSCRouter"

So nothing new for me there and I was more looking for a in depth made by the makers or someone focusing more on the software then Eos<->Qlab. I have alot of other things I mix up in there like Intercom (GreenGo V5); Bitfocus Companion to control Stagetimer.io, video projectors and more...

But then I guess it is not much more out there. Then back to rail and error and jus be happy when it works!

Thanks once more!

Johannes