beautypg.com

Tp-net, Protocol – Ecler TP-NET User Manual

Page 4

background image

4

TP-NET

protocol

(Third-Party NET)

The TP-NET protocol lets a client device get and/or set the values of several parameters of the EclerNet
compatible devices (the MIMO88 digital matrix, the NXA digital audio manager series, the NZA amplifier
series, the NPA amplifier series, etc.), like volumes, mutes, alarms, etc.

The communication with these EclerNet devices is established using Ethernet and the UDP/IP transport
protocol, always by means of the

5800

UDP port. It’s not allowed to have more than one simultaneous

access from several clients to the same EclerNet device.

A second option for this communication is using the RS-232 interface that some EclerNet compatible
devices do also have (MIMO88, NXA series, etc.). In this case, the serial connection should comply with
the following specifications:

 Baud rate: 57600 (fixed, no autonegotiation)
 Data bits: 8
 Parity: None
 Stop bits: 1
 Flow control: None

The serial cable wiring, from the device’s connector to a standard DB9 serial interface connector, should
be the following:


The protocol is simple and direct, making it easy to read, write and modify the generated code. It is
based on messages with no begin and end delimiter: each message is self-delimited by the UDP packet
size, which is defined with a maximum of

80 characters

. All the messages must be written in capital

letters.

To let some control systems (like CRESTRON®, AMX®, RTI®, VITY®, MEDIALON®, etc.) process the
messages more easily, the EclerNet device adds the character

LF (0x0A)

to the end of each message.

This way the client can buffer the messages to process them, if it’s required. The EclerNet device can
also handle several messages received in a single message packet by using the

LF

delimiter.


The available messages are built with one or more fields separated with blank spaces (

= blank

space):

[PARAM1]

[PARAM2]

[PARAM3]

[PARAM4][LF]


The first field (

TYPE

) defines the message type and then, the required parameters for it (each kind of

message requires a given number of parameters). The field

TYPE

can have these values:

SYSTEM

GET

SET

INC

DEC

SUBSCRIBE

UNSUBSCRIBE

DATA

ERROR