2 definitions, 1 routers and levels, 2 clients and servers – Nevion Multicon MRP User Manual

Page 6: 3 message format and structure, 2definitions

Advertising
background image

Modular Routing Protocol - MRP

Rev. L


nevion.com | 6

2

Definitions

2.1 Routers and levels

Physical routers must be partitioned into one or more levels to make them controllable.
Level is a logical router inside a physical router. A physical router output can not be
included in more than one level. Input and output sequences are continuous and span from
0 to size-1. Refer to the Nevion Configurator user manual for more details.

Nevion products can only be partitioned into levels when Multicon is used. Without
Multicon, the level size is equal to the physical router size.

2.2 Clients and servers

Typically, control panels are clients connecting to a server. Units controlling a router or
Multicon system are clients. Servers are typically Sublime routers and the part of Multicon
communicating with control panels. Units being controlled by others are servers.

2.3 Message format and structure

All message and command data consists of ASCII characters.

There are three types of messages:

Commands.

Command responses. Responses that the server sends back after receiving a

command. Command responses are prefixed with a '?' character, may contain an
echo of the command and are sent only to the client issuing the command.

Status messages. Messages that the server sends to inform about status changes.

Status messages are prefixed with a % character, do not echo any commands, and
are sent to all connected clients.

A message consists of a sequence of ASCII characters (a string), terminated by two
linefeed (value 0x10) characters. For the rest of this document, <LF> will represent a
linefeed. Message termination is not shown in syntax descriptions for clarity. Literal strings
are enclosed in single quotes in this document.

No part of the message will be executed before the complete message is received. The
optional CRC is placed immediately preceding the pair of linefeed characters, see chapter
2.5 and 4.2. For commands, the CRC should be added after the last character of the
command, before the pair of linefeeds. For command responses and status messages the
CRC is preceded with a linefeed:

Command message:

<message> ::= <command> ['*'<CRC>]<LF><LF>

Command response:

<message> ::= '?' ['"'<command>'"']<LF><response>
[<LF>'*'<CRC>]<LF><LF>

Status message:

<message> ::= '%'<LF><status>[<LF>'*'<CRC>]<LF><LF>

Example:

z l3 52 27 *53A2

? "z l3 52 27"
ERROR: Unknown command
*61AD

Advertising