Ericsson RX8 Series User manual

RX8xxx Receivers

Software Version 1.0.0 (and later)

REMOTE CONTROL PROTOCOL

RX8xxx Receivers

Document No. ST.TS.EXXXXX.1

2 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

ContentsIntroduction

Copyright

Disclaimer

No part of this document may be reproduced in any form without the written

permission of the copyright owner.

The contents of this document are subject to revision without notice due to

continued progress in methodology, design and manufacturing. Ericsson AB shall

have no liability for any error or damage of any kind resulting from the use of this

document.

Customer Services

Europe, Middle East

and Africa

Tel: +44 (0) 23 8048 4455

Fax: +44 (0) 23 8048 4467

Email: [email protected]

Americas Tel: +888 671 1268

Tel: +678 812 6255

Fax: +678 812 6262

Email: [email protected]

US and Canada

International

Compression

Software Support Centre

China Tel: +86 10 8476 8676

Fax: +86 10 8476 7741

Tel: +852 2590 2388

Fax: +852 2590 9550

Email: [email protected]

Beijing

Hong Kong

Australia and New

Zealand

Tel: +612 (0) 9111 4027

Fax: +612 (0) 9111 4949

Email: [email protected]

Internet Address www.ericsson.com

Technical Training

International Tel: +44 (0) 23 8048 4229

Fax: +44 (0) 23 8048 4161

Email: [email protected]

Document No. ST.TS.EXXXXX.1 2010-03-04

3 (59)

Supported Alteia Protocol Commands and Messages

Contents

1 Introduction.......................................................................................................... 6

1.1 Overview.............................................................................................................6

1.2 Who Should Use this User Guide?......................................................................6

1.3 Which equipment is covered by this User Guide?...............................................7

1.4 Needed Hardware Options..................................................................................7

2 Installing the Equipment......................................................................................8

2.1 Hardware Interface..............................................................................................8

2.2 User interfaces..................................................................................................11

3 Protocol Implementation....................................................................................13

3.1 Alteia Remote Control........................................................................................13

3.2 Remote control operating mode.........................................................................14

3.3 Alteia Support....................................................................................................14

3.4 Receive Timeouts..............................................................................................15

3.5 Data Transmission.............................................................................................15

4 Supported Alteia Protocol Commands and Messages....................................16

4.1 Overview...........................................................................................................16

4.2 Front-end Commands........................................................................................18

4.3 Service Enquiry Commands..............................................................................29

4.4 Service Selection Commands............................................................................33

4.5 System Info Bypass Service Selection Commands...........................................34

4.6 Operational Status Commands..........................................................................35

4.7 CA commands...................................................................................................37

4.8 Video Commands..............................................................................................39

4.9 4:2:2 Mode Commands.....................................................................................45

4.10 Subtitle/VBI Commands...................................................................................45

4.11 Audio Commands............................................................................................47

4.12 Transport Stream Output Commands..............................................................54

4.13 Director V5 Commands...................................................................................55

4.14 Remote Commands.........................................................................................55

4.15 System Commands.........................................................................................58

4.16 No PID Commands..........................................................................................59

List of Figures

Figure 1. The backplane of the RX8200 including Remote Data Card.................8

Figure 2. Connecting different RS-485 wirings...................................................11

List of Tables

Table 1 Equipment Model Descriptions.................................................................7

Table 2 Hardware Options......................................................................................7

4 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

Supported Alteia Protocol Commands and Messages

Table 3 Pin Connections for RS-232 Mode on the 9-way (male pin) D-type Serial

Remote Connector................................................................................9

Table 4 RS-485 communication modes at different wiring.................................10

Table 5 Pin connections with separated RS-485 wiring.....................................10

Table 6 Pin connections with connected RS-485 wiring....................................10

Document No. ST.TS.EXXXXX.1 2010-03-04

5 (59)

Supported Alteia Protocol Commands and Messages

1 Introduction

1.1 Overview

This User Guide document describes the serial remote control interface available on

the RX8200 IRD Software versions 5.9.0 and above. This allows the control of the IRD

from a PC or similar device through a standard serial port.

The RX8200 supports:

• Ericsson TV Serial Remote Control Protocol

The Ericsson TV protocol is based on the original System 3000/Alteia protocol. In this

document this protocol is referred to as Alteia Remote Control.

1.2 Who Should Use this User Guide?

This User Guide is written for operators/users of the RX8200 Receivers to assist in

installation and operation of Serial Remote Control.

Caution!

Unauthorized maintenance or the use of non-approved replacements may affect the

equipment specification and invalidate any warranties.

6 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

Supported Alteia Protocol Commands and Messages

1.3 Which equipment is covered by this User Guide?

Table 1 Equipment Model Descriptions

Model Number Marketing Code Description

RX8200 RX8200/BAS

RX8200/BAS2

Professional receiver for MPEG2, H.264

decoding.

1.4 Needed Hardware Options

See Table 2 for a list of hardware options, which are needed for the Serial Remote

Control protocol.

Table 2 Hardware Options

Marketing Code Description

Daughter Card Options

RX8200/HWO/RS232 Remote Data Card

Needed for the Remote Control and Low Speed Data

functionalities.

Document No. ST.TS.EXXXXX.1 2010-03-04

7 (59)

Supported Alteia Protocol Commands and Messages

2 Installing the Equipment

Warning!

Do not remove the covers of this equipment. Hazardous voltages are present within

this equipment and may be exposed if the covers are removed. Only Ericsson AB

trained and approved service engineers are permitted to service this equipment.

2.1 Hardware Interface

There is a single hardware port available on the back plane of the RX8200 IRD for the

Serial Remote Control, if the Remote Data (Legacy) Card is present. The port is

denoted with RS232/RS485 Remote.

Figure 1. The backplane of the RX8200 including Remote Data Card

The serial communication mode can be Half-Duplex and Full-Duplex.

The Remote Control Port supports the RS-232 and RS-485 serial interfaces. The

electrical characteristics for the interface must be selected between RS-232 or RS-485

via one of the user interfaces. (See User interfaces in Chapter 2.2)

RS-485 is intended for controlling multiple IRDs from a single controller. The Alteia

protocol includes addressing capabilities and will operate with both RS-232 and

RS-485.

Default configuration:

 Remote address: 2

 Remote interface: RS-232

 Remote duplexity: Half duplex

8 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

Supported Alteia Protocol Commands and Messages

2.1.1 Baud Rate Parity – Data bits/Stop bits

The default parameters for this interface are:

Baud rate: 9600 bit/s

Parity: No

Data bits: 8

Stop bits: 1

These parameters are fixed, they can not be modified.

2.1.2 RS-232 Connections

Table 3 Pin Connections for RS-232 Mode on the 9-way (male pin) D-type Serial

Remote Connector

PIN RS-232 SIGNAL IN/OUT

1 Data Carrier Detect (DCD) Input

2 Receive Data (RxD) Input

3 Transmit Data (TxD) Output

4 Data Terminal Ready (DTR) Output

5 Ground -

6 Data Set Ready (DSR) Input

7 Request to Send (RTS) Output

8 Clear to Send (CTS) Input

9 Not connected -

These connections are designed to be compatible with both the Tandberg TT1220 and

RX1290 style connector and the (original) Alteia style connector, such that existing

serial remote cabling installations for these units can be used with the RX8000.

At the IRD the RS-232 handshaking control signals are used as follows:

• The DSR, CTS, and DCD inputs are ignored by the IRD

• DTR output is always active

• RTS output is always active

NOTE…

The IRD does not support hardware or software flow control; the active control signals are

designed to ensure a standard PC RS-232 serial port will not be prevented from transmitting or

receiving by its flow control hardware. Like a standard PC the IRD is configured as a DTE so

twists in the Tx/Rx signals and control signals (where used) are required in the cable when

connected to a PC. The DTE configuration is used to allow the IRD to be directly connected (i.e.

no twists required) to a DCE device such as a modem.

Document No. ST.TS.EXXXXX.1 2010-03-04

9 (59)

Supported Alteia Protocol Commands and Messages

2.1.3 RS-485 Connections

The RS-485 allows the controlling of multiple IRDs from a single controller, where the

devices are connected to a common cable-rail. All of the IRDs get the sent commands,

but the target receiver identifies their own command by the remote address.

The RS-485 signals are available as independent transmit and receive differential pairs

in the Remote Control Connection port. The IRD can be used therefore also in a 2-wire

(connected Tx and Rx pairs) or 4-wire (separate Tx and Rx pairs) RS-485 network.

The 2-wire cabling allows only a half-duplex communication. The 4-wire cabling allows

also the half-duplex and full-duplex communication. The duplexity mode has to be set

on the user interface corresponding to the RS-485 wiring:

Table 4 RS-485 communication modes at different wiring

Communication mode

Half

duplex

Full

duplex

RS-232 X X

2-wire RS-485 X -

4-wire RS-485 X X

The chosen communication (duplexity) mode must be consistent with the wiring. If two-

wire RS485 is used, the communication mode must be set to half duplex. In the other

cases all wiring, porting and communication mode combinations can be used.

There are no handshaking signals neither in separated, nor in connected RS_485

wiring.

2.1.3.1 Wiring with separated Rx and Tx pairs (4+1 wires network)

Table 5 Pin connections with separated RS-485 wiring

PIN RS-485 SIGNAL IN/OUT

1 Not connected -

2 Not connected -

3 Not connected -

4 RX Input (+ve)

5 Ground Ground

6 Not TX Output (-ve)

7 TX Output (+ve)

8 Not RX Input (-ve)

9 Not connected -

2.1.3.2 Wiring with connected Rx and Tx pairs (2+1 wires network)

Table 6 Pin connections with connected RS-485 wiring

PIN RS-485 SIGNAL IN/OUT

10 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

Supported Alteia Protocol Commands and Messages

1 Not connected -

2 Not connected -

3 Not connected -

4 A+ In/Out (+ve)

5 Ground Ground

6 B- In/Out (-ve)

7 A+ In/Out (+ve)

8 B- In/Out (-ve)

9 Not connected -

RS-485 always requires at least three or five conductors: 2 or 4 signal wires and 1

signal return path. (+1 wire ground)

2.1.3.3 Connecting a 2-wire network to 4-wire devices (and inversely)

There is compatibility between the 2 and 4-wire RS-485 devices.

Figure 2. Connecting different RS-485 wirings

In this case only the Half-Duplex communication mode can be used at all connected

devices.

2.1.3.4 RS-485 terminations

Although it is suggested to use 120 Ohm resistors to terminate the network at its two

ends against reflection, at 9600 baud with local cables it doesn’t have any significance.

The termination is optional.

2.2 User interfaces

Remote Control is always enabled. The IRD’s Remote Control parameter settings are

available from the Web interface , Front panel and from SNMP.

The following parameters can be adjusted from there:

• Remote Address: 0-999

• Remote Interface: RS-232 / RS-485

• Remote Duplexity: Half-Duplex / Full-Duplex

Document No. ST.TS.EXXXXX.1 2010-03-04

11 (59)

TX+

RX+

A+

TX-

RX-

B-

Supported Alteia Protocol Commands and Messages

2.2.1 Web interface

The Remote Control Parameters can be set on the web interface under the Device info

tab.

Device Info

└ Remote Control

2.2.2 Front panel

In the Front Panel the parameters can be found in the following menu-structure:

1. System

└ 1.6 RC / Remote Control

2.2.3 SNMP

The SNMP mibs are the followings:

Serial Remote Address 1.3.6.1.4.1.1773.1.3.208.1.2.1

Serial Remote Interface 1.3.6.1.4.1.1773.1.3.208.1.2.2

Duplex Mode 1.3.6.1.4.1.1773.1.3.208.1.2.3

12 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

Supported Alteia Protocol Commands and Messages

3 Protocol Implementation

3.1 Alteia Remote Control

The protocol is based on a set of defined commands covering the various functional

areas of the IRD. Message fields are ASCII text and can be easily interpreted by the

operator. This interface will only reply to the controller in response to a command

which has been previously sent. The protocol supports a single data rate of 9600 baud.

The IRD’s address identifies the Receiver, whose value is in range 0-999.

Refer to Chapter 3.3 for a list of Alteia remote control commands supported by the

RX8200.

Alteia Protocol Clarification

Implementation of RC protocol in RX8000 is based on that of RX1290’s. The

implementation on the RX1290 is based on the following rules:

1. Message ignored with no response at all if:

a) Address part of message does not match IRD address

b) Message checksum is included but is incorrect

c) Message does not follow the expected patterns indicated below:

\ddd:ccc;ccccc……………ccccccc_Cr

\ddd:ccc;ccccc……………ccccccc_$hhCr

where c is any ASCII character (included also ‘_’ character),

d is any ASCII character in the range ‘0’ to ‘9’,

h is any hexadecimal character in the range ‘0’ to ‘F’ for checksum,

Cr is a carriage return character

2. NAK returned if message passes rule 1 but:

a) Message command is not recognized

b) Message command is recognised but not implemented

c) Message sub-command is not recognized

d) Message sub-command is recognised but not implemented

e) Message parameter field format is not exactly as expected

(e.g. correct number of digits in numeric fields etc.), but this rule is not as strict in

RX8000 as before.

f) Any message parameter values are outside their allowed range

(as defined in Section 4).

3. ACK returned if:

1 and 2 are passed and the message is not a status request.

ACK will still be returned if the message was good but the IRD failed to carry out the

requested action for some reason, e.g. failure to select a requested service, or the

options fitted to the unit do not support the full parameter range, and some commands

are also ACK-ed which became unsupported in newer receivers.

Document No. ST.TS.EXXXXX.1 2010-03-04

13 (59)

Supported Alteia Protocol Commands and Messages

4. Status returned if:

1 and 2 are passed and the message is a status request. Status requests return a

message containing the required data. Refer to Section 4 for supported status

messages.

There are no returns other than those for status and those listed above. Commands

with and without checksums included at the end are accepted by the IRD.

3.2 Remote control operating mode

The RX8200 Receiver is working always in Remote Control Mode if the Remote Data

Card is present. In this case the Remote Control functionality will be always available.

That’s a difference compared to the RX1290 receivers, where the Remote Control

Operating Mode was switchable.

3.3 Alteia Support

The supported Alteia protocol commands are a subset of the previous remote control

protocol. The RX8200 implementation of this protocol provides all Alteia commands

within the limits of this unit’s specification. Any required set-up that is not supported by

the remote control must be carried out using the other user interfaces.

The Alteia protocol main commands are listed below.

Refer to Section 4 for the full list of supported commands and sub-commands:

• Tuner commands (TUN)

• Demodulator commands (DEM)

• Decoder commands (DEC)

• DVB-T commands (DTV)

• IP input commands (IPI)

• G703 input commands (703)

• Terrestrial input commands (DTV)

• 8VSB tuner/demodulator commands (ATS)

• Service Enquiry commands (ENQ)

• Service Selection commands (SER)

• System Index Bypass Service Selection commands (SIB)

• Operational Status commands (OPR)

• CA commands (CAS)

• Video commands (VID)

• 4:2:2 Mode commands (422)

• Subtitle/VBI commands (SVB)

• Audio 1 commands (AUD)

• Audio 2 commands (AU2)

14 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

Supported Alteia Protocol Commands and Messages

• Audio 3 commands (AU3)

• Audio 4 commands (AU4)

• Audio 5 commands (AU5)

• Audio 6 commands (AU6)

• Transport Stream output commands (TSO)

• NCP commands (NCP)

• Remote commands (REM)

• System commands (SYS)

• No PID Commands (NOP)

3.4 Receive Timeouts

No timeout is applied for the Alteia protocol; if the end of a message is lost, the

message parsing state machine will be reset when the next message start sequence is

detected and the old data automatically discarded.

3.5 Data Transmission

No mechanism is used to indicate when transmission is complete.

3.5.1 Half duplex mode

The protocol is command/response, so no further commands should occur until the

controller has received the previous reply. Attempts to send more data before the

previous transmission is complete will result in the new transmission request being

ignored.

3.5.2 Full duplex mode

Both the received messages and the reply messages of the executed commands are

queued. So it’s allowed to occur further messages while the previous command

message is under procession.

No command messages will be ignored.

Document No. ST.TS.EXXXXX.1 2010-03-04

15 (59)

Supported Alteia Protocol Commands and Messages

4 Supported Alteia Protocol Commands and

Messages

4.1 Overview

4.1.1 General Command Format:

\ADD:CMD;SUB=NNN…._$FFCr (with optional checksum)

or:

\ADD:CMD;SUB=NNN…._Cr (without optional checksum)

Group command format:

\ADD:CMD;SUB-GRPCMD=NNN-GRPCMD=NNN…._$FFCr

or without optional checksum:

\ADD:CMD;SUB-GRPCMD=NNN-GRPCMD=NNN…._Cr

Where:

ADD is 3 digit decimal IRD address. (range 000 to 999; 000 is used in all examples shown)

CMD is main command given as three ASCII characters

SUB is sub-command given as three ASCII characters

GRPCMD is a grouped sub-command given as three ASCII characters

NNN is variable length control string including parameter values

$FF is optional hex checksum given as two ASCII characters (FF is used in all

examples shown)

Cr is ASCII carriage return terminating the message

Parameters are given in ASCII text. In the examples d represents a decimal value,

(e.g. dddd is four decimal digits) and h represents a hexadecimal value (e.g. hh is two

hex digits). These values must include leading zero padding where appropriate so that

the number of digits used is independent of value. In the examples c represents an

ASCII character (e.g. ccc is identifier composed of three ASCII characters

NOTE…

An unsupported command can be still a recognized and implemented command therefore the

RX8200 will return an ACK to an unsupported command but will take no action. The RX8000 can

behave in a similar manor for unsupported values of a supported command (e.g. the AUD;LVL

command), it will ACK the command without taking any action.

If more information is required about a command that is not supported please contact customer

services.

16 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

Supported Alteia Protocol Commands and Messages

The changes (compared to RX1290) are denoted with Yellow backgrounded text.

4.1.2 Calculating the Checksum

For the entire message up to and including the last underscore, get the value of each

character from the table add them together and then drop all but the first 2

hexadecimal digits. This entire operation is easier done in hex.

For the message \000:SYS;SRQ_ this is

\ 0x5C +

0 0x30 +

: 0x3A +

S 0x53 +

Y 0x59 +

S 0x53 +

; 0x3B +

S 0x53 +

R 0x52 +

Q 0x51 +

_ 0x5F = 0x03B5

Only the 2 least significant digits are used for the check sum (that is 0xB5) so the

entire message is

\000:SYS;SRQ_$B5Cr

Some other examples are:

\000:TUN;SRQ_$ADCr

\000:TUN;RFI=NO2_$A4Cr

\000:SER;SEL=00001_$BCCr

Document No. ST.TS.EXXXXX.1 2010-03-04

17 (59)

Supported Alteia Protocol Commands and Messages

4.2 Front-end Commands

4.2.1 Tuner Commands

Command = TUN

The tuner commands control the function and operation of the L-band tuner.

SUB Description NNN Parameter Description

FRQ

Manual tune to given

frequency dddddd

Frequency in 125 kHz steps,

range 0 to 19.999GHz

LNB

Set LNB local oscillator

frequency (LO1) dddddd

LNB frequency in 125 kHz

steps,range 0 to 19.999 GHz

POL

Set the LNB polarization HOR

VER

Horizontal

Vertical

SPC

Set spectrum

normal/inverted

AUT

NRM

INV

Automatic detection

Normal spectrum sense

Inverted spectrum sense

RFI

Set RF input to use

NO d

RF input number, d = 1 to 4

(Note space)

RFS

Get RF input status -

Gets the current RF input

Format: NO d

LO2

Set LNB local oscillator

(LO2) Command not supported

SOF

Set LNB switch over

frequency Command not supported

PWR

Set LNB power ON

OFF

BST

DC output enabled

DC output disabled

DC output boosted

(BST not supported)

SER

Set tuner search range dddd 1 kHz steps from 1000 to

10000

MOD

Set modulation type

QPS

BPS

8PS

16Q

AUT

QPSK modulation

BPSK modulation

8PSK modulation

16QAM modulation

Auto configuration

Command not supported

(modulation is auto-

configured)

ROL

Set roll-off

20

25

30

20 % Input roll-off filter

25% roll-off

30% roll-off

GRP

Set tuner parameter group

See details

below

This is a group command

and follows the format given

in the overview

(Section 4.1.1)

STD

Set satellite modulation

mode

S1

S2

DVB-S

DVB-S2 (if licensed)

18 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

Supported Alteia Protocol Commands and Messages

SRQ

Requests tuner status - See below

\

000:TUN;FRQ=dddddd_AFC=OFF_LNB=dddddd_PWR=ccc_POL=ccc_SPC=ccc_RFI

=d_LNT=NOR_LO2=000000_SOF=000000_SER=dddd_MOD=ccc_ROL=dd_STD=Sd

$FFCr

where parameters are as given above, and the following additional parameters:

SUB Description NNN Parameter Description

AFC

Automatic frequency

control

OFF (always returned)

PWR

LNB power

ON.

OFF

BST

Power on normal level

(note: full stop)

Power off

Power on boosted level

(not supported)

SPC

Spectrum normal/inverted

AUT

NRM

INV

Automatic detection

Normal spectrum sense

Inverted spectrum sense

RFI

Selected RF input d

RF input, range 1 to 4.

Returned value is only a decimal

value here.

LNT

LNB type

NOR Normal (single oscillator) LNB

(Always returned – dual LNB not

supported)

LO2

LNB Local oscillator

frequency (LO2)

dddddd Frequency in 125 kHz steps.

(Value of 000000 always returned

– dual LNB notsupported)

SOF

LNB switch over frequency

(22 kHz tone on above this

frequency)

dddddd

Frequency in 125 kHz steps.

(Value of 000000 always returned

– automatic tone switching for

dual LNB not supported)

SER

Tuner search range dddd

Frequency in 1 kHz steps from

1000 to 5000

GRP Sub-Command Details:

SUB Description NNN Parameter Description

FRQ

Manual tune to given

frequency dddddd

Frequency in 125 kHz steps,

range 0 to 19.999GHz

LNB

Set LNB local oscillator

frequency (LO1) dddddd

LNB frequency in 125 kHz steps,

range 0 to 19.999 GHz

POL

Set the LNB polarization HOR

VER

Horizontal

Vertical

RFI

Set RF input to use NO d

RF input number, d = 1 to 4 (Note

space)

PWR

Set LNB power ON

OFF

DC output enabled

DC output disabled

Document No. ST.TS.EXXXXX.1 2010-03-04

19 (59)

Supported Alteia Protocol Commands and Messages

BST DC output boosted (not

supported)

MOD

Set modulation type

QPS

BPS

8PS

16Q

AUT

Command not supported

(modulation is auto-configured)

QPSK modulation

BPSK modulation

8PSK modulation

16QAM modulation

Auto

FEC

Forward error correction

rate

AUT

1/2

2/3

3/4

4/5

5/6

6/7

7/8

8/9

Automatic

FEC rate 1/2

FEC rate 2/3

FEC rate 3/4

FEC rate 4/5

FEC rate 5/6

FEC rate 6/7

FEC rate 7/8

FEC rate 8/9

SYM

Set symbol rate dddddd Symbol rate in units of 100 sym/s,

range 1.0 to 48.0 Msym/s

All GRPCMDs must be present in a GRP sub-command for it to be valid.

GRP Sub-Command Acknowledgement Messages

The GRP sub-command has an extended set of acknowledgement messages. It uses

the ACK acknowledgement for the same purpose as all other messages but there is an

extended set of negative acknowledgements that can be returned in place of NAK as

follows:

GRP command example:

\000:TUN;GRP-FRQ=1002-LNB=1003-POL=HOR-RFI=NO 1-PWR=OFF-MOD=QPS-

FEC=1/2-SYM=027500_

GRP Sub-Command Details:

Acknowledgement Description

NA2 PWR payload not found

NA3 PWR payload incorrect

NA4 POL payload not found

NA5 POL payload incorrect

NA6 Grouped sub-command starts with P, but is not PWR or

POL

NA7 FEC payload not found

NA8 FEC payload incorrect

20 (59)

Document No. ST.TS.EXXXXX.1 2010-03-04

Page is loading ...

Ericsson RX8 Series User manual

This manual is also suitable for

Ericsson RX8 Series User manual

Related papers

Other documents