I want to use the module network/Ethernet command, to send some control data to an external SDI switcher. However, it seems that no data is coming out of that module, whereas I can easily use telnet or even a standard browser on the same machine, to connect. Firewall is deactivated. So the question is: how to wire the Ethernet Command module (in particular I am concerned about the yellow port 'Render Chain').

Next question is: how can I send ASCII control chars, like newline, tab, CR. In a form like \n, \r, \t, or in some byte code?

Here is how it looks like:- very finally I want to send something like

Code:

VIDEO OUTPUT ROUTING \n7 2 \n\n

(\n is for the required newline character)- currently AI is running on 192.168.1.171, the target test machine is at 192.168.1.43, the target port is 9090- I can e.g. telnet 192.168.1.43 9090, or point a browser to 192.168.1.43:9090. But if I use the module in AI, nothing happens.- I tried several approaches, including inserting it into the render chain, and using the other ports to trigger the send process etc. No avail.

I am a bit further now: the module 'Ethernet Command' (a) seems to work nicely without being linked into the render chain, and (b) outputs UDP - whereas I was listening for TCP. Now, let's see how BlackMagic's switcher reacts to that. Or has anyone already gathered some eyperience with that machine? Please find the Manual here- it expects TCP data on port 9090.

The Blackmagic Videohub Ethernet Protocol is a text based protocol that is accessed by connecting toTCP port 9990 on a Videohub Server. Integrated Videohub Servers and Videohub Server computers aresupported by the protocol.

Then, when you can issue network commands, you can easily change the routing with a command like this:

VIDEO OUTPUT ROUTING:↵7 2↵↵

Now, there is the AI module 'ethernet command'. Sounds great, but unfortunately it is not exactly fit for the job, since it outputs commands only via UDP, whereas our nice little switcher requires TCP. Luckily I found a little software named socat, which can translate alost every protocol (look for the Windows/Cygwin binaries). Download and unzip it, open a DOS prompt in the right folder, and issue a command like this:

Code:

socat -s udp4-listen:9091,reuseaddr TCP:192.168.0.100:9090

This way, socat listens on port 9091/UDP, and forwards everything it receives to 192.168.0.100 port 9090/TCP. You'll get a nice little window like this:

We can now easily use AI's ethernet command module. Instead of sending the data to our target device, we must now send it to the local network, because this is where socat sits and listens - on port 9091, that is. I found that I needed to send it to broadcast (I didn't bother to install a loopback adaptor):

(I used other ports in my example - but you have to tweak the IP addresses anyway )