Riedel MediorNet, User Manual

Page: 301 / 310

301
MediorNet User Manual 2.00.0
Details of the TSL implementation
The intended audience of the following details are 3rd party vendors and people familiar with the details of
the TSL 5.0 UMD protocol which try to create an interface to MediorNet via the TSL interface.
Our TSL Server only accepts ASCII packets.
Unicode packets are rejected as well as Control packets, which are not defined in the TSL 5.0 standard.
Addressing scheme:
The scheme is designed to be able to address specific channels of any specific slot.
Each Channel can be a screen.
To set a certain text / tally information for a certain Channel the following addressing needs to be followed
(Note on TSL Terminology):
Screen: A screen may have multiple Displays
Display: A display is the "real" target of any text/tally information
Of the screen ID the [Lil-Endian] MSB of Screen uint16 ID will be used as the slot of the Card
Of the screen ID the [Lil-Endian] LSB of Screen uint16 ID will be used as the Channel of the Card
Addition to the protocol
In addition to the TSL protocol we send a reply:
A seven byte message with PCB (=5), VER, FLAGS, SCREEN of original packet and the seventh byte indicate if
we could not parse/read/process.
(PRR_OK = 0,
PRR_COULD_NOT_PARSE = 1,
PRR_CONTROL_DATA = 2,
PRR_UNICODE = 3,
PRR_UNKNOWN_SCREEN = 4,
PRR_ERROR = 5,
)
This extension to the protocol will not break functionality with any existing TSL Controller implementation
but can provide ways of easily identifying lost packets as well as useful debugging information.
USO
RESTRITO