User manual

Automation Protocol TCP/IP-Based Automation
Miranda Technologies Ltd Page 31
TCP/IP-Based Automation
Serial Automation
Most Oxtel products
2
have the ability to run automation protocols over a
standard TCP/IP socket interface, provided the unit is equipped with Ethernet
interface. The packet layout and protocols are exactly as described above for
RS232/RS422 point-to-point packet flow, including STX and CRC checksum
bytes.
Connections are accepted on port 5006. Multiple connections can be
established to the Imagestore, allowing distributed or backup control without
the need for additional cabling.
When considering using TCP/IP automation, please note the following:
• Any Ethernet–based protocol cannot guarantee frame-accurate reception
and there may also be non-deterministic latencies due to network traffic.
• Each TCP/IP connection will have its own parameters for information
such as tally responses and audio metering. By default these are turned
off on new connections, and need to be enabled (if required) whenever a
new connection is established.
• Imagestore may limit the number of simultaneous sessions.
Network Automation
The Linux-based Imagestore products (Imagestore HD-TV, Imagestore 300,
Imagestore Intuition, Imagestore 750, LGK-3901, DSK-3901) will
additionally accept Network Automation commands on port 5007.
Network Automation is a simplified version of Serial Automation which
takes advantage of TCP's end-to-end reliability. It differs as follows:
• It does not use an STX byte.
• It does not use CRC bytes.
• No ACK/NAK byte is returned.
Otherwise the command list and status response format is exactly the same.
In particular the command terminator ':' (colon) is still required to mark the
boundaries in the byte stream.
2
Supported in Imagestore 2/2U/3 version 2.08 and later, plus all newer
products