TCP/UDP

TCP/UDP:

TCP - Start commands are fully configurable, support for live classes, automatically sends Keep Alive commands, knows when the socket connection opens and closes and waits for a response.

UDP - same as TCP but does not know when the socket connection opens and closes.

The key difference between UDP and TCP communication is that UDP connections are one way, with no concept of a connection handshake. UDP does not fully support HTTP communication to devices outside the local network at this time. 

The Virtual App only speaks ASC11, it doesn't speak HEX.

Automation enabled: this need to be toggled to green (ON) to display the automation fields.

Live automation enabled: automation for Live classes. Ensures sound is set to the correct volume, lights are dimmed.

Keep Port alive command: the app sends this out to make sure iOS doesn't close it off. By default it sends out POWR? approx. every 40 seconds. Whatever automation is setup will need to ignore this message all together or handle it elegantly.  That means, you can’t use Virtual automation with 'toggle' based automation systems - like some serial systems that just toggle the power on and off anytime a signal is received regardless of what the signal says.

Port: is specific to the control unit installed.  Can be found online.

In the attached docs, one does not have an EDID installed, this is because the Atlona has an in-built EDID and can perform that function.  Kim Walker designed these docs and can be contacted for more info

I thought you should know the RS232 over TELNET worked using TCP. (from Greg in Aus)