146
Set
tings
10.
TP-NET PROTOCOL
10.1
INTRODUCTION TP-NET PROTOCOL
The
TP-NET protocol allows a client machine (or control device) to query and modify
various internal parameters
.
Communication with such devices can be done over Ethernet and using the UDP/IP
transport protocol, using UDP registered port
5800
.
The protocol is simple and textual, making it easy to read, write code and modify, and is
message-based, with no need for start and end delimiters: each message is implicitly
delimited by the size of the UDP packet. The maximum message size is
80 characters
. All
texts must be written in capital letters.
To facilitate the processing of messages in control systems such as CRESTRON®, AMX®,
RTI®, VITY®, MEDIALON®, etc., the device adds the character
LF
(0x0A)
at the end of
each message. If the client program does not have time to process the received messages
one by one, it can concatenate consecutive messages into a single memory string (buffer)
and separate them again later using the
LF
delimiter.
The device also allows several
messages to be sent in a single data packet and read using the delimiter.
Messages are made up of one or more fields, separated by blanks (
= blank space):
<TYPE>
[PARAM1]
[PARAM2]
[PARAM3]
[PARAM4][LF]
The first field
(TYPE
) defines the
type of message
, and therefore the number of
parameters required below (each type of message requires a certain number of
parameters). The
TYPE
field can have the following values:
•
SYSTEM
•
GET
•
SET
•
INC
•
DEC
•
Subscribe to
•
UNSUBSCRIBE
•
DATA
•
ERROR
The
table in the chapter
describes the different types of
messages and their associated parameters
.
