Secundario

Syrus and the Listener Server

Page 1

Syrus and the Listener Server

February 22th 2011

DIGITAL COMMUNICATIONS TECHNOLOGIES
DIGITAL COMMUNICATIONS TECHNOLOGIES
CONFIDENTIAL: This document is for the exclusive use of Digital Communications
Technologies. All type of reproduction or divulgation must be authorized .
December 23th, 2010 http://www.digitalcomtech.com

Syrus and theListener Server

Page 2

DIGITAL COMMUNICATIONS TECHNOLOGIES
CONFIDENTIAL: This document is for the exclusive use of Digital Communications
Technologies. All type of reproduction or divulgation must be authorized .
December 23th, 2010 http://www.digitalcomtech.com

Syrus and the Listener Server

Page 3

Document history
Revision

Comments

001 - 23/12/2010

First release

002 –22/02/2011

Added information about the AR configuration command.

DIGITAL COMMUNICATIONS TECHNOLOGIES
CONFIDENTIAL: This document is for the exclusive use of Digital Communications
Technologies. All type of reproduction or divulgation must be authorized .
December 23th, 2010 http://www.digitalcomtech.com

Syrus and the Listener Server

Page 4

Introduction
This document isdirected to Syrus-AVL-Sytem integrators designing the server program
which receives and communicates with Syrus units via TCP and/or UDP.
This document lists important recommendations that must be followed to prevent data
loss between the Syrus units and the listener server.

DIGITAL COMMUNICATIONS TECHNOLOGIES
CONFIDENTIAL: This document is for the exclusive use of Digital CommunicationsTechnologies. All type of reproduction or divulgation must be authorized .
December 23th, 2010 http://www.digitalcomtech.com

Syrus and the Listener Server

Page 5

Types of messages sent by Syrus
Depending on the user set configuration, the Syrus units may report different types of messages. The
listener server must be able to receive and correctly interpret the following types of messages.
•Simple TAIP reports. These are the regular TAIP messages sent by Syrus when an event is
reported. These type of messages must always be parsed by the server. For example:
>REV111615353447+3570173+1397742703203012;ID=356612020083541<
Indicates that Syrus has reported event 11.

•

Extended TAIP reports. These are the regular TAIP messages sent by Syrus when an event
containing EVextended tags is reported. These type of messages and its extended tags must
always be parsed by the server. For example:
>REV021615353839+3570173+1397742703203212;BL=4094;AL=+11;ID=Test<
Indicates that Syrus has reported event 02 which contains the BL and AL tags.

•

TAIP messages responses to queries. These are messages sent by Syrus as a response to any
query (i.e. >QPVQALQVRQRV<
The unitwill send the response:
>RVR; Syrus 1.1.39;ID=Test<
The listener shall process the message according to the purpose of the query

•

Unexpected TAIP responses to none-silent event-actions (i.e. events set with ;ACT=). Syrus
will send a TAIP message indicating that an action was executed when an event defined with nonsilent actions is triggered. For example:

DIGITAL COMMUNICATIONSTECHNOLOGIES
CONFIDENTIAL: This document is for the exclusive use of Digital Communications
Technologies. All type of reproduction or divulgation must be authorized .
December 23th, 2010 http://www.digitalcomtech.com

Syrus and the Listener Server

Page 6
The event definition:
>SED69XV0;C19+;ACT=SSSU080<
Will generate to the listener a normal event report:>REV691615354941+3570173+1397742703203212;ID=Test<
And will also generate a response for the executed action:
>RSSU080;ID=Test<
These messages may be parsed by the listener depending on the purpose of the executed action.
Actions can be set as silent (i.e. ;XCT=) to prevent these types of messages. Please refer to the
ED configuration command on the Syrus' manual.
•

Keep alives. The Syrus' Keep Alive message is sent after a...