Cygnus 517

CYGNUS 517
HIGH INTEGRATION
STATISTICAL MULTIPLEXER
USERS MANUAL
Manual Part Number 200-0034

March 2008
CYGNUS MICROSYSTEMS PRIVATE LIMITED

93, Phase II, IDA, Cherlapally, Hyderabad 500 051, INDIA
Tel: +91 (40) 2726 1326 Fax: +91 (40) 2726 1167
e-mail: techsupport@cygnusmicro.com
Internet: www.cygnusmicro.com
NOTICE
{ All rights reserved. Reproduction of this manual in any form whatsoever without prior
written permission from CYGNUS is forbidden.

{ Due to continuous product upgradation the specifications and features of the product,
and consequently the contents of this manual, are subject to change without notice.
{ All efforts have been made to ensure the accuracy of this manual. However,
CYGNUS assumes no responsibility for any errors in this manual or their
consequences.
{ CYGNUS would greatly appreciate being informed of any errors detected in this
manual
Manual Revision History

Manual
Release Date
Details of Changes
October 2004
Initial Release
March 2005
Manual updated; Appendices I, J, K and L added
March 2008
Appendices M & N added
Applicable
Firmware version
S/W Ver 4.81
S/W Ver 4.85
H/W Version 1.3
S/W Ver 4.87
H/W Version 1.4
CONTENTS
1. INTRODUCTION ..................................................................... 1.1
1.1 STATISTICAL MULTIPLEXING ......................................... 1.1
1.2 THE CYGNUS 517 HIGH INTEGRATION STATISTICAL
MULTIPLEXER ................................................................. 1.1
1.2.1 Features ................................................................. 1.2
1.2.2 Product Description ................................................ 1.3
1.2.2.1 Terminal Ports .................................................1.4
1.2.2.2 Voice Port ........................................................1.4
1.2.2.3 Composite Port ............................................... 1.4
1.2.2.4 Supervisory Port...............................................1.5
1.2.2.5 Usage ............................................................. 1.5
1.3 SPECIFICATIONS ............................................................. 1.6
2. UNPACKING ......................................................................... 2.1
2.1 UNPACKING ...................................................................... 2.1
2.2 SITE SELECTION AND PREPARATION ........................... 2.1
3. CONFIGURATION AND COMMANDS ................................... 3.1
3.1 SWITCH CONFIGURATION .............................................. 3.1
3.2 SUPERVISORY PORT OPERATION .................................3.5
3.3 SUPERVISORY PORT COMMANDS ................................ 3.6
3.3.1 Modifying Parameters ............................................. 3.7
3.3.2 Displaying Parameters ............................................3.19
3.3.3 Copying terminal port parameters .......................... 3.21
3.3.4 Setting factory default parameters .......................... 3.22
3.3.5 Storing Parameters .................................................3.23
3.3.6 Resetting the multiplexer ........................................ 3.23
3.3.7 Initialising a single port ........................................... 3.23
3.3.8 Viewing unit status ..................................................3.24
3.3.9 Connect Facility ...................................................... 3.28
3.3.10 Identification of software and hardware version ..... 3.29
3.3.11 Remote and Local Operation .................................. 3.29
3.3.12 Error Statistics ........................................................ 3.31
3.3.13 Utilisation Statistics ................................................. 3.32
3.3.14 Clearing Voice Port Statistics ..................................3.33
3.3.15 LED and DIP switch test ......................................... 3.33
3.3.16 Watchdog Test ....................................................... 3.34
3.3.17 Clearing the Time .................................................. 3.34
3.3.18 Loading terminal ports with test data ...................... 3.34
4. INSTALLATION AND TROUBLESHOOTING .......................... 4.1
5. CYGNUS 517 OPERATION ..................................................... 5.1
5.1 TERMINAL PORT OPERATION ........................................ 5.1
5.2 COMPOSITE PORT OPERATION ..................................... 5.1
5.3 VOICE PORT OPERATION ............................................... 5.2
5.4 FRONT PANEL INDICATORS ........................................... 5.3
5.5 BACK PANEL INDICATORS .............................................. 5.6
Appendix A ............................................................................... A.1

Connector Pinouts
Appendix B ............................................................................... B.1
Link Changeover and Audible Alarm
Appendix C ............................................................................... C.1
Self-tests
Appendix D ............................................................................... D.1
Default Composite Port Values
Appendix E ............................................................................... E.1
Extended Supervisory Access
Appendix F ............................................................................... F.1
Command Summary
Appendix G ............................................................................... G.1
Cable Connections
Appendix H ............................................................................... H.1
Voice Module
Appendix I ...............................................................................
64 kbps Co-directional G.703 Interface Module
I.1
Appendix J ............................................................................... J.1

2 Mbps G.703 (E1) Interface Module
Appendix K ............................................................................... K.1
64 kbps IDSL Modem Module
Appendix L ............................................................................... L.1
Hardware Mounting Information
Appendix M ............................................................................... M.1
LAN Based Remote Management Option
Appendix N ............................................................................... N.1
Additional Supervisory Commands in Software Version 4.87
1
INTRODUCTION
1.1 STATISTICAL MULTIPLEXING
With the continuing proliferation of computers, there is a requirement to provide access to computers from remote terminals. Consider the problem of providing access from a cluster of remote
terminals to a centrally located computer. One solution to this problem is to provide a complete
communication facility (e.g. a telephone line with modems or line drivers at either end) between
each terminal and the computer. This is a fairly expensive proposition since it requires a number of
telephone lines (often leased) and modems to provide the connectivity. A statistical multiplexer can,
however, eliminate the need for multiple sets of communication facilities between the terminals and
the computer.
A multiplexer, in the data communication context, is a device which allows a number of terminals to
share a common communication facility (such as an analog telephone line or a digital line) to a
remote computer. It achieves this by allocating the shared communication channel to each device in
turn - this technique is called Time Division Multiplexing (TDM).
A conventional Time Division Multiplexer gives fixed weightage to each device (terminal) connected
to it. It allocates individual time slots to each terminal during which that terminal has exclusive use
of the channel. Time slots are allocated in a predetermined manner. This approach to multiplexing
has the drawback that it ignores whether the device actually has data to send during its time slot.
Since traffic from asynchronous start-stop terminals is normally intermittent and bursty in nature this
scheme ends up allocating a number of time slots which are not actually used by the devices. A
statistical Time Division Multiplexer, on the other hand, allocates the shared communication channel
to devices on a need basis. The allocation pattern is statistical rather than predetermined - i.e., it
depends on the data traffic generated by the devices. Because of this feature a statistical multiplexer is able to utilise the bandwidth available on the shared communication channel much more
efficiently than an ordinary Time Division Multiplexer.
Whereas the need for being able to access remote computers through statistical multiplexers
comes as a necessity, advancements in the field of analog modem technology has pushed up the
available speeds, thereby leaving additional bandwidth at the users disposal. The widespread
availability of digital lines at speeds of 64 kbps supports this view. It is but natural that the available
bandwidth should be used for some other purpose than computer access. What comes naturally to
one's mind is whether the additional available bandwidth can be used for carrying out voice communication. The answer here is yes, provided that the available bandwidth is enough to carry voice. On
the other hand techniques such as low bit rate voice encoding allows voice to be encoded at rates
as low a 4800 bits per second, thereby permitting its transmission along with data on links operating
at speeds lower that or equal to 64 kbps.
While handling voice, the statistical multiplexers have to ensure that voice, whenever present,
should be given higher priority in transmission than that for data as delaying it will cause the quality
to suffer.
1.2 CYGNUS 517 HIGH INTEGRATION STATISTICAL MULTIPLEXER

CYGNUS 517 is a Statistical Time Division Multiplexer which allows eight or sixteen asynchronous
terminals and a voice port to share a common communication channel to a remote computer. The
multiplexer automatically detects and corrects any data transmission errors on the shared communication channel. Operation of the multiplexer is transparent to user devices. This avoids the need
to modify or reprogram any of the devices connected to the multiplexers. The voice port provides a
- 1.1 -
CYGNUS 517 Users Manual
Introduction
hotline functionality allowing phone-to-phone, phone-to-EPABX and fax machine-to-fax machine

interconnection at the two sites. Voice compression and other bandwidth conservation techniques
allow high quality voice conversations to be carried on simultaneously with data traffic even when
the composite channel speed is as low as 9600 bps.
Up to two leased links can be connected to the CYGNUS 517, with a facility to automatically switch
the multiplexed data stream to a standby link if the presently active link fails. An audible alarm is
available to alert users if either of the two links fails. A choice of several built-in line interfaces is
also provided to allow the product to be connected to the leased links through a variety of
interfaces.
CYGNUS 517 multiplexers are compatible with and can inter-work with CYGNUS 516 8/16-port
and CYGNUS 508V2 8-port multiplexers.
1.2.1 Features
The features of CYGNUS 517 High Integration Statistical Multiplexer include:
w Multiplexes and demultiplexes traffic from eight or sixteen asynchronous RS232 data terminals
onto a single composite stream. Ordering time option for eight port or sixteen port unit. Eight port
units can be upgraded to sixteen port units.
w Provision to connect up to two leased links to the unit, where one is the active link and the other
acts as a standby link. It is possible to direct the composite stream automatically to the standby
link if the active link fails. It is also possible to direct the composite stream to either of the two
links by manual selection.
w Various options for leased link interfaces. These interfaces include field selectable RS232/V.35
interface for connection to external modems, built-in E1 interface operating at 2048 kbps from
which the multiplexer can extract a 64 kbps slot, built-in 64 kbps codirectional G.703 interface,
and built-in 64 kbps IDSL modem compatible with CYGNUS 606 IDSL modems.
w Audible alarm provided, to alert the operator if the unit detects failure of either the main or the
standby composite link. The alarm stops sounding after it is acknowledged by the operator. It is
possible to disable the alarm.
w The status of the failure of active or standby link is optionally available as a relay output for
external use. This output indicates whether the active and standby links are working properly or
not.
w Modular design allows link interfaces to be added or changed through plug-in modules.
w Voice port is available as an option. If the voice option is installed voice and data are simultaneously transmitted on the composite port. The voice port is field configurable for FXS (for connection to phone instruments or fax machines) or FXO (for connection to PABX ports) interface and
provides a hotline functionality. Voice compression is programmable and starts from as low as
4800 bps so that simultaneous voice data multiplexing is possible on composite link speeds of
even 9600 bps. Dynamic bandwidth allocation and silence suppression minimise requirement for
voice bandwidth. Supports connection of G.3 fax machines to the voice port.
w Multiplexing protocol ensures low end-to-end transmission delay for each terminal port, regardless of composite line speed and traffic load and also provides high link utilisation efficiency.
w Dedicated supervisory port with software commands to configure parameters, monitor the unit
and diagnose faults. It also has LED indicators for showing the status of main and standby
composite links, status of data traffic on each data port and the status of the voice port. It is
possible to access the remote unit's supervisory function from the local units supervisory terminal, over the composite link. No separate communication line is required for this purpose.
w Comprehensive power-on diagnostics and online diagnostics for quick fault isolation
w Rugged switched-mode power supply (SMPS) capable of reliable operation.
w Product can inter-work with CYGNUS 516/508V2 statistical multiplexers and can also work as a
feeder to CYGNUS 701/701E/731 DCMs. It can also interwork with CYGNUS 403 and CYGNUS
404 modem switches.
w 19 inch rack mountable.
- 1.2 -
Introduction
1.2.2 Product description

Fig. 1.1 shows the front panel of a typical CYGNUS 517 unit.
64 kb G.703 Module
2 Mb G.703 Module
TST
SYNC
TXD
RXD
T ON
PA OFF
T
PA
INT
LL
LINK
L
LC
E1 E
LIN
E1
DI
SEC
CYGNUS 517
64 kbps G.703
line interface
HIGH INTEGRATION STATISTICAL MULTIPLEXER
J
R IN
ER LL
E
DT
SUP
TERMINAL PORT ACTIVITY
COMPOSITE PORT/SYSTEM
VAD
TXD
PWR
TX
RX
RMT T/DFLT ALRM DSBL
TP1
TP2
TP3
TP4
TP5
TP6
TP7
TP9 TP10
TP11
TP12
TP13
TP14
TP15
SECONDARY
PRIMARY
TP8
DCD FLAG PRI-SEL
DCD FLAG SEC-SEL
CHANGEOVER
AUTO
MST CTEST
FXS/FXO
IFOK
BUZZ
DIAG1
INT
DIAG2
LINK LNERR ADERR
V2
V516
MXERR ENBL
TP16
CLK-INV
V.35
V.24
CLK-INV V.35
V.24
MAN
SLV DMODE
PRI
PRI
DL
CYGNUS 517
FXO
VLINK
ERR
ERR
IFOK
FXS
PWR
ALARM
RXD
T
PA
Voice Module
T//DFLT
PWR
AIS
R
CL
FF DL
E
DT
DIAG3
SEC
DI
DIAG4
CYGNUS 517
DIS-BUZZ
SEC-SEL
MANUAL
SLV
CYGNUS 517
CYGNUS 517
Voice port
E1 line interface
Unit & link status; port activity
Link changeover facility
Supervisory port
Indicators & switches
Fig. 1.1 Typical CYGNUS 517 Front Panel
The front panel contains:

w Indicators and control switches for the unit as a whole and individual indicators for terminal port
activity
w Indicators and control switches for each of the installed leased link interfaces
w Indicators and control switches for the voice port (if installed)
w A 25 pin D-type plug for supervisory port
Fig. 1.2 shows the back panel of the CYGNUS 517.
TP1
TP2
TP3
TP4
TP5
TP6
TP7
TP8
TP9
TP10
TP11
TP12
TP13
TP14
TP15
TP16
FXS
2 Mb G.703 I/F
64 kb G.703 I/F
FXO
OH1 FXS
ON
+24V
RX
RX
TX
TX
-24V
OH2
FXO
230VAC
FUSE T1A
AC power input
DESIGNED AND MANUFACTURED BY CYGNUS MICROSYSTEMS (P) LTD., HYDERABAD, INDIA
CYGNUS 517
Terminal Ports 1-8
Terminal Ports 9-16
CYGNUS 517
Voice port
E1 line interface
Fig. 1.2 Typical CYGNUS 517 Back Panel
- 1.3 -
CYGNUS 517
64 kbps G.703
line interface
Introduction
The back panel contains:

w Up to sixteen D-type sockets for TERMINAL PORT 1 through TERMINAL PORT 16.
w 25-pin D-type plug for each installed V.35/RS232 composite link interface. Composite port-tomodem cables (supplied along with the unit if required) can be used to connect these ports to
external leased line modems
w A terminal block for each built-in E1 interface, 64 kbps co-directional G.703 interface and built-in
IDSL modem on the composite link
w Two RJ-11 sockets for each installed voice interface (one FXS and one FXO)
w Link status output relay connector (if this option is installed)
w AC input power connector with built-in fuse holder and ON/OFF switch
Pinouts of all back panel connectors are given in Appendix A.
1.2.2.1 Terminal ports

Asynchronous devices are connected to the multiplexer via the 25-pin D-type connectors on the
back panel. These connectors are labelled TP 1 through TP 16.
Devices may be connected directly or through asynchronous line drivers or modems capable of fullduplex communication.
Terminal ports can operate at speeds up to 19200 bps, with various combinations of character
length, number of stop bits, parity and flow control options. Operating parameters for individual
channels can be specified from the supervisory port using commands described in Sec. 3.3.1.
1.2.2.2 Voice port

The CYGNUS 517 can be ordered with a voice port. Two types of devices can be connected to the
voice port of the CYGNUS 517. To connect devices such as telephone instruments or fax machines
to CYGNUS 517 the voice port must be configured for "FXS" mode and the user device must be
connected to the "FXS" connector. To connect extension ports of a PABX to the CYGNUS 517 the
voice port must be configured for FXO mode and the PABX port must be connected to the "FXO"
connector. FXS/FXO selection is through a front panel switch.
1.2.2.3 Composite port

The CYGNUS 517 may be ordered with or without a link changeover option. If ordered with this
option the unit is supplied with two composite link interfaces. If ordered without this option the unit is
supplied with only one composite link interface. Whether ordered with or without the changeover
option, several ordering time options are available for the composite link interfaces.
w If ordered with a field selectable RS232/V.35 link interface, a male 25-pin D-type connector is
provided for the composite port. Two LED indicators are also provided to show whether the interface is RS232 or V.35. The CYGNUS 517 can be connected to any CCITT V. series synchronous modem for communication on the shared line. The multiplexer is supplied with one
multiplexer-to-modem cable per RS232/V.35 composite link interface. Extra cables can be
ordered separately if required. Appendix G provides details of the cables for connecting the
composite port to the appropriate type of modem.
Over shorter distances of few hundred meters, low cost line drivers may be used instead of
synchronous modems for connection between the multiplexers. A particularly useful feature of
CYGNUS 517 multiplexers is their ability to operate on the composite port with NRZI data encoding at speeds up to 64000 bps (nominal). NRZI encoding allows the multiplexer units at either
end of the communication link to recover clocking information from the received data by
themselves. For distances up to a few kilometres, the two multiplexers may be connected
through baseband synchronous modems such as CYGNUS 606/V.35 which provides 64 kbps
synchronous connectivity over a single cable pair.
- 1.4 -
Introduction
w If ordered with an E1 interface, a terminal block is provided for connecting the CYGNUS 517 to
the E1 circuit. Control switches to initiate diagnostic tests and LED indicators are also provided.
w If ordered with a 64 kbps co-directional G.703 interface, a terminal block is provided for connecting the CYGNUS 517 to the G.703 PCM interface. Control switches to initiate diagnostic tests
and LED indicators are also provided.
w If ordered with a built-in 64 kbps IDSL modem, a terminal block is provided for connecting the
CYGNUS 517 to the 2-wire line. Control switches to initiate diagnostic tests and LED indicators
are also provided.
Operating parameters for the composite port are selected through DIP switches at the base of the
unit and via commands from the supervisory port (see Secs. 3.1 and 3.3.1).
1.2.2.4 Supervisory port

The front panel of the CYGNUS 517 provides a 25-pin D-type female connector for the unit's supervisory port. The supervisory port is used to configure the operating parameters of all terminal ports,
the voice port and the composite port. A comprehensive set of commands is provided to allow the
parameters to be specified. Detailed descriptions of these commands are given in Chapter 3.
The supervisory port can also be used to initiate on-line diagnostics on terminal and composite
ports (see Chapter 3).
Any asynchronous terminal may be connected to the supervisory port via a suitable RS232 cable.
The operating parameters of the supervisory port itself are specified by means of switches located
at the bottom of the unit (see Sec. 3.1).
1.2.2.5 Usage
Fig. 1.3 shows a simple configuration needed to achieve end-to-end connectivity between a cluster
of remote terminals and a central computer over a leased telephone line. Two CYGNUS 517 units
are required - one connected to the cluster of remote terminals and the other to the computer (the
CYGNUS 517 can also inter-work with CYGNUS 508V2 or CYGNUS 516 units on the other side).
Once this configuration is operational, devices connected to the terminal ports of one unit behave
as if they were directly connected to the devices connected to the corresponding terminal ports of
the other unit. The voice port, if present may be connected to a PABX on one side and a telephone
instrument on the other side. The telephone instrument then acts as an extension of the PABX.
..
...........
T ST
T S T / DF LT
P WR
PAT
AIS
........
F XS
T ST
P WR
PAT
A LA RM
F XO
PAT
RX D
LI NK
T XD
T EST
E 1 LI NE LP
E RR
TX
RX
RMT
LI NK
LNE RR
A DE RR
V2
T / DF LT
A LRM
E NB L
T P1
T P2
T P3
T P4
T P5
T P6
T P7
T P 12
T P 13
T P 14
T P 15
T P8
DCD
DA T
CHS
DCD
DA T
CHS
A UT O
MS T
CT E S T
MA N
S LV
DMODE
T XD
V 516
MX E RR
DS B L
T P9
T P 10
T P 11
T P 16
CLK -I NV I
V . 35
V . 24
CLK -I NV
V . 35
V . 24
V LI NK
VAD
NP 1
P WR
TX
RX
RMT
LI NK
LNE RR
A DE RR
V2
T / DF LT
A LRM
I NT
E RR I NJ
DT E DL
E NB L
T P1
T P2
T P3
T P4
T P5
T P6
T P7
T P 12
T P 13
T P 14
T P 15
T P8
DCD
DA T
CHS
DCD
DA T
CHS
MX E RR
DS B L
T P9
T P 10
T P 11
T P 16
CLK -I NV I
V . 35
V . 24
CLK -I NV
V . 35
V . 24
CT E S T
S LV
DMODE
NP 1
NP 2
S E C-S E L
MA NUA L
NP 2
F F CLR
CT E S T
DI A G4
S
B UZ Z E R_RE S E T
Terminal Server/Computer
MS T
MA N
B UZ Z
V 516
DI A G2
DI A G3
DI A G4
B UZ Z E R_RE S E T
PABX
A UT O
F XS/F XO
I F -OK
DI A G1
I NT
DL
F XO
RX D
T XD
E RR
E 1 LCL LP
DT E LL
LL
NP 2
F F CLR
F XS
P WR
T EST
E 1 LI NE LP
E RR
I F -OK
I NT
NP 1
DI A G3
NP 2
A LA RM
LI NK
S Y NC
B UZ Z
DI A G1
DI A G2
E RR I NJ
DT E DL
PAT
RX D
P WR
F XS/F XO
I F -OK
E 1 LCL LP
DT E LL
I NT
NP 1
AIS
VAD
T XD
E RR
I F -OK
DL
T S T / DF LT
P WR
V LI NK
RX D
S Y NC
LL
......
CYGNUS 517
Supervisory terminal
Leased telecom lines
S E C-S E L
MA NUA L
CT E S T
CYGNUS 517
Fig. 1.3 Typical connectivity using CYGNUS 517
- 1.5 -

User Terminals
Telephone
Introduction
1.3 SPECIFICATIONS
TERMINAL PORTS (TPs)
Communication
protocol:
Serial asynchronous start-stop
Number of TPs:
8 or 16 (ordering time option)
Maximum aggregate
speed:
153.6 kbps
Interface:
RS232-C (ITU-T V.24) on 25-pin D-type socket
Data communication
speed:
Selectable: 50 - 19200 bps. Autospeed detection up to 9600 bps
Data format:
Selectable: 5,6,7 or 8 bits; 1, 1.5 or 2 stop bits, odd, even or no parity
Flow control:
Selectable: through software (XON/XOF) or hardware (RTS/CTS) in both

directions
Break propagation:
Transparent
EIA signal
propagation:
The status of the local DTR signal can be propagated to the remote end
Echo:
Character echo can be selectively enabled for each TP
VOICE PORT (VP)

No. of voice interfaces: None or 1 (ordering time option) - modular design allows the voice interface to be installed by inserting appropriate modules into the chassis
Voice interface:
Selectable between FXS and FXO; on RJ-11 socket
Voice bit rate:
Selectable from 4.8 to 10.4 kbps
Fax compatibility:
Up to 9.6 kbps; Group 3 fax protocol
COMPOSITE PORT (CP)

No. of composite
ports:
Communication
protocol:
ITU-T X.25 Level 2 LAPB
Speed:
Up to 64 kbps as per selected link interface
Error detection &

correction:
16-bit CRC with ARQ
No. of physical links on 1 (standard) or 2 (if changeover option is installed - see below)
composite port:
Physical compatibility
on each link interface:
Option of:
RS232/V.35 (field selectable)
64 kbps codirectional G.703
E1 (framed or unframed) (With 64 kbps bandwidth extraction)
64 kbps IDSL modem compatible with CYGNUS 606 modems
Modular design allows the desired interface(s) to be installed by inserting
appropriate modules into the chassis
- 1.6 -
Introduction
RS232/V.35 link interface specifications

Connector:
25-pin D type male
Signals:
TxD, RxD, TxClk, RxClk, DTR, DSR, DCD
Speed:
Selectable between 1.2 kbps and 64 kbps
Data encoding:
Selectable between NRZ and NRZI
Clocking modes:
Receive clock: external; Transmit clock: selectable as external or internal
Selection between
RS232 and V.35
interface:
Through switches
64 kbps codirectional G.703 link interface specifications

Connector:
Terminal Block
Speed:
64 kbps
Clocking modes:
Selectable between: internally generated clock and clock recovered from

co-directional G.703 interface
E1 link interface specifications

Connector:
Terminal block
Speed:
2.048 Mbps (framed or unframed) from which 64 kbps bandwidth is

extracted for composite port operation
Clocking modes:

E1 signal
64 kbps IDSL modem interface specifications

Connector:
Terminal block
Speed:
64 kbps
Clocking modes:

line signal
Compatibility:
With CYGNUS 606 baseband IDSL modems
Distance
Upto 7.5 km over 0.5 mm dia (24 AWG) copper wire, in error-free
condition.
LINK CHANGEOVER FACILITY

Function: To switch the unit to a standby leased link in case the presently active leased link fails.
For changeover to work the remote unit must also be a CYGNUS 517, or a CYGNUS
516/CYGNUS 508V2 with an appropriate CYGNUS modem switch.
Modes of operation:
Automatically switch to standby leased link in case of failure; work only on

a selected leased link
Configuration selection Select Master/Slave mode, Select data/clock inversion on each link
options:
AUDIBLE ALARM
Function: Beeper activated when either of the two composite links is detected to have failed. The
alarm can be enabled, disabled and reset.
- 1.7 -
Introduction
LINK STATUS OUTPUT RELAY

Function: Relay remains in tripped condition as long as the link(s) is detected as having failed; if
changeover facility is installed, relay remains in tripped condition as long as either of the two links
is detected as having failed.
Type:
Dry, potential-free relay contact
SUPERVISORY PORT (SP)

Supervisory commands:
Set/modify/view parameters; View status; Store parameters; Copy parameters between ports; Run
switch/LED test; Provide loop backs on ports; Obtain statistics reports; Unit reset/user port reset;
Establish connectivity between supervisory and terminal ports; Remote supervisory access;
Enable/disable remote access
Physical interface on SP
Communication
protocol:
Asynchronous start-stop
Speed:
50 to 9600 bps
Data format:
7/8 bits, 2 stop bits, odd/even/no parity
Echo:
Configurable
Physical compatibility:
RS232 (ITU-T V.24)
Connector:
25-pin D type female
INDICATORS
Unit level indicators:
Power, Default parameters, Test Mode, Remote Supervisory Access,

Address Error/Override, Alarm Status, Mux Error, Alarm Disable/Enable,
516 and 508V2 Compatibility
Composite port
indicators:
Link Status, Error, Transmit, Receive
Data port indicators:
Transmit/Receive activity on each data port
Voice port indicators:
Voice Link Status, Voice Activity Detect, Voice port type (FXS or FXO),
24 V supply present
Changeover circuit
indicators:
Master/Slave, Auto/Manual Operation, Data Mode, Channel Test

For each link: DCD, Flag, Ch Select, I/f type: V.35/RS232, Clock Invert
E1 interface indicators: Power on status, E1 Link status, Clock mode, Test condition, Error,
Alarm, Received data, Transmitted data, Whether connected to primary or
secondary link, Mux interface status, Inverted data
64 kbps codirectional
G.703 interface
indicators:
Power on status, Link status, Clock mode, Test condition, Error, AIS,
Received data, Transmitted data, Whether connected to primary or
secondary link, Mux interface status, Inverted data
64 kbps IDSL modem Power on status, Link Activation status, Clock mode, Test condition,
indicators:
Error, Alarm, Received data, Transmitted data, Whether connected to
primary or secondary link, Mux interface status, Inverted data
CONTROL AND DIAGNOSTIC SWITCHES
Alarm control switch:
Disable/acknowledge audible alarm
Changeover related
switches:
Primary/Secondary channel select, Auto/Manual operation, Master/Slave

configuration
- 1.8 -
E1 interface related
diagnostic switches:
Introduction
E1 line loop back, E1 local loop back, DTE local loop back, DTE digital
loop back, E1 port loop backs, Error inject, Pattern generation and
checking
64 kbps codirectional Local loop back, Digital loop back, Pattern generation and checking
G.703 interface related
64 kbps IDSL modem Local loop back, Remote loopback, Digital loopback, Pattern generation
and checking
Voice interface selection switch:
Selects FXS or FXO interface
GENERAL
Power:
170-260 VAC, 20 W max (With all options mounted as applicable)
Dimensions:
483 mm x 89 mm x 300 mm i.e. 19 x 2U x 300 mm
ORDERING INFORMATION
Ordering Part No.: 517/TT/UU/VV/WW/XX/YY where:
TT specifies no. of data ports; TT = 8D or 16D for 8/16 data ports
UU specifies no. of voice ports; UU = 0V or 1V for 0/1 voice ports
VV specifies whether relay output in installed; VV=RL if relay output is required and NR if relay
output is not required
WW specifies whether link changeover option is installed; WW=CH for this option, NC for no
changeover option
XX specifies interface on 1st link; XX = SER for serial RS232/V.35; COD for 64 kbps
co-directional G.703 interface, E1 for E1 interface, IDSL for built-in 64 kbps IDSL modem
compatible with CYGNUS 606 modems
YY specifies the interface on the 2nd link in the same manner as XX (if link changeover option is
installed)
- 1.9 -
2
UNPACKING
2.1 UNPACKING
The following items are shipped in the multiplexer box from the factory:
{
{
{
{
Statistical multiplexer unit

Upto two multiplexer-to-modem cables (depending on the composite link interfaces ordered)
AC power cable
CYGNUS 517 User's Manual (this manual)
Examine the contents of the box carefully for any damage.

CAUTION
Do not apply power to a damaged unit.
Store the original packing material carefully for future re-packing and shipment.
2.2 SITE SELECTION AND PREPARATION

The CYGNUS 517 High Integration Statistical Multiplexer can be placed on a tabletop or mounted
in a 19 equipment rack. It should be placed within 3 metres of a properly earthed power outlet
capable of supplying power in accordance with the specifications given in Sec. 1.3. A clearance of
about 15 cm must be provided at the rear of the unit to allow for connecting external signal cables.
A clearance of about 5 cm is recommended at both the sides and top of the unit to allow for proper
ventilation. The installation area should be clean, dust-free and should not be subject to extremes
of temperature, humidity, shock and vibration.
CAUTION
Always operate CYGNUS 517 multiplexers from a properly earthed AC power source.
The voice port (FXO or FXS) devices such as PABX, telephone instruments and fax machines
should be in the same premises, up to a maximum of a few hundred metres from the CYGNUS
517.
CAUTION
Care should be taken to connect only appropriate devices to the voice port. A telephone
instrument or a fax machine should be connected to the FXS interface, and a PABX
extension should be connected to the FXO interface. A mistake in this may result in
improper operation of the unit and may even damage the unit.
- 2.1 -
3
CONFIGURATION AND COMMANDS
Setting up the CYGNUS 517 High Integration Statistical Multiplexer for use in your application
involves configuring the following sections of the unit:
w basic 8/16 port multiplexer, including selecting operating parameters for terminal ports,
composite port and overall system
w voice section (if installed)
w audible alarm
w link changeover section (if installed)
w V.35/RS232 composite link interface
w 64 kbps G.703 composite link interface (if installed)
w E1 composite link interface (if installed)
w 64 kbps IDSL modem (if installed)
The basic multiplexer is configured by switches and through supervisory commands given from a
supervisory terminal connected to the supervisory port of the unit. These commands are described
in Sec. 3.3. To be able to access the supervisory port of the unit however it is necessary to ensure
that the communication parameters of the asynchronous terminal used as the supervisory terminal
match with the parameters of the supervisory port. To facilitate this a DIP switch is provided at the
base of the unit through which it the supervisory port parameters can be set to known "default"
values. This switch is also used to specify certain other fundamental configurable modes. Details of
this switch are given in Sec. 3.1 below.
The voice section is configured through jumpers, switches and supervisory commands. Jumpers
and switches related to the voice port operation are described in Appendix H. Supervisory
commands related to voice operation are described in Sec. 3.3.
The volume of the audible alarm provided in the unit can be adjusted through jumpers provided on
the main PCB in the unit. Jumpers and switches are also provided on the main PCB to control the
operation of the link changeover facility. These jumpers and switches are described in detail in
Appendix B.
The CYGNUS 517 offers a choice of ordering time options for each of its composite link interfaces
(The number of link interfaces depends on whether the unit is ordered with or without link
changeover facility. If ordered with link changeover facility there are two link interfaces. If ordered
without link changeover facility there is only one link interface). Appendices I, J and K respectively
describe how to configure the 64 kbps codirectional G.703 link interface, the E1 link interface, and
the built-in 64 kbps IDSL modem.
3.1 SWITCH CONFIGURATION

Up to three DIP switches are located at the bottom of the CYGNUS 517 unit. These are labelled
SW1, SW2 and SW3.
The CYGNUS 517 has an option of two composite link interfaces with automatic link changeover
feature, so that data traffic can automatically switch to a standby link in case the presently active
link fails (see Appendix B for a description of the link changeover function). These links are called
the Primary (PRI) and the Secondary (SEC) links. Switches 1-5 of DIP switch SW2 control the
interface on the Primary link and switches 1-5 of SW1 control the interface on the Secondary link,
as shown in Table 3.1(a).
- 3.1 -
Configuration and commands
TABLE 3.1 (a)

Selection of interface type on Primary and Secondary Composite links
DIP
SWITCH
GROUP
SW2
SW1
SWITCH NO. IN THE GROUP

2
3
4
SELECTED INTERFACE
5
Open
Open
Open
Open
Open
Open
Close
Open
Open
Open
Open
Open
Close
Open
Open
Open
Close
Close
Open
Open
Close
Close
Close
Close
Close
Open
Open
Open
Open
Open
Open
Close
Open
Open
Open
Open
Open
Close
Open
Open
Open
Close
Close
Open
Open
Close
Close
Close
Close
Close
PRIMARY: V.35 interface with clock and

data inversion.
PRIMARY: V.35 interface with clock inversion but no data inversion
PRIMARY: V.35 interface with data inversion
but no clock inversion
PRIMARY: V.35 interface with no data inversion and no clock inversion
PRIMARY: RS232 (V.24) interface with no
data inversion and no clock inversion.
SECONDARY: V.35 interface with clock and
data inversion.
SECONDARY: V.35 interface with clock
inversion but no data inversion
SECONDARY: V.35 interface with data
inversion but no clock inversion
SECONDARY: V.35 interface with no data
inversion and no clock inversion
SECONDARY: RS232 (V.24) interface with
no data inversion and no clock inversion.
NOTE
1. Inversion of clock or data signal on the V.35 interface is equivalent to interchanging the
signals A and B leads at the connector.
2. If only one interface is installed (i.e., no changeover facility) only the PRI link has to be
configured
3. CYGNUS 517 also supports built-in telecom interfaces such as 64 kbps codirectional
G.703, E1 and 64 kbps IDSL modem on each composite link. When these built-in
telecom interfaces are installed on a particular link interface (PRI or SEC) that interface
should be configured for V.35 operation (with or without clock/data inversion)
SW3 is used to configure certain basic parameters for operation of the unit. Table 3.1(b) details the
significance of the individual switches in the DIP switch combination.
TABLE 3.1(b)
SW3 DIP switch functions (During normal operation)
SWITCH NO.
FUNCTION
FACTORY SET VALUES
Off-line diagnostics selection
OPEN (on-line operation)
Voice Port selection
OPEN (voice port is not installed/not enabled)

CLOSE (voice port is installed and enabled)
Reserved for future use
OPEN
8 port/16 port operation

selection
OPEN (8 port operation)

CLOSE (16 port operation)
Auto Test Selection
OPEN (no auto test)
OPEN
OPEN
Supervisory port default

parameters selection
OPEN (no default)
- 3.2 -
Individual switches on SW3

Switch 8:
This switch should be set to OPEN for normal multiplexer operation and to CLOSE for invoking
detailed off-line diagnostics (see Appendix C). This switch is factory set to OPEN.
Switch 7:
This switch should be set to CLOSE if voice port is installed and enabled and to OPEN if voice port
is not installed, or is to be disabled.
Switch 6:
This switch is reserved for future use. It should be set to OPEN.
Switch 5:
This switch selects whether the unit will operate with 8 or 16 terminal ports.
Set this switch to OPEN to select 8 port operation. The V2 indicator on the front-panel is "on" in this
mode. The multiplexer can work with a CYGNUS 508V2 or 8 port CYGNUS 516 or CYGNUS 517
unit at the other end in this mode.
Set this switch to CLOSE for 16 port operation. In this mode the unit can inter-work with a 16 port
CYGNUS 516 or CYGNUS 517 multiplexer. The V.2 indicator is "off" in this mode.
Switch 4:
Setting this switch to CLOSE selects the "automatic traffic testing" mode. This is an offline test
mode used to check the functioning of the unit, or to exercise it. Setting this switch to CLOSE
selects "Address override mode" (see Sec. 3.3.1) on power up and data traffic is started
automatically in about 10 seconds after link up. To sustain the traffic, the network port and terminal
ports should have loop back connectors on them (see Appendix C).
For normal operation, this switch should be set to OPEN.
Switch 3,2:
These switches are reserved for future use and should be set to OPEN.
Switch 1:
Setting this switch to CLOSE forces the supervisory port to assume default parameters as per
Table 3.2, irrespective of the stored supervisory port parameters. Setting it to OPEN programs the
supervisory port parameters with values stored in the non-volatile system memory. This switch is
factory set to OPEN.
TABLE 3.2
Default (factory-set) parameters for the Supervisory Port
PARAMETER
Speed
Number of data bits
Parity
Stop bits
Echo
Disconnect character
Input flow control (IFC)
Output Flow Control (OFC)
VALUE
4800 bps
8
Disabled
2
Enabled
03 (Control-C)
None
None
- 3.3 -
NOTE
The supervisory port always operates without input (IFC) or output flow control (OFC)
irrespective of the programmed value of this parameter.
The multiplexer contains non-volatile Configuration Memory to store operating parameters of the
ports and the system. The factory-set values of these parameters are given in Tables 3.3.1, 3.3.2,
3.4 and 3.5.
TABLE 3.3.1
Factory-set parameters for Terminal Ports
PARAMETER
VALUE
Speed
4800 bps
Number of data bits
Number of stop bits
Parity Status
No parity
Output flow control
XON/XOF
Input flow control
XON/XOF
Echo option
Disabled
EIA propagation
Off
Link Down Message
Off
TABLE 3.3.2
Factory-set parameters for Voice Port
PARAMETER
VALUE
Interface Type
(Set by FXS/FXO switch)
FXS
Encoding Rate
4800 bps
Echo Cancellation
On
Post Filter
On
Volume
-9 dB
Voice Activity Detection and

silence Suppression (VAD)
On
TABLE 3.4
Factory-set parameters for Composite Port
PARAMETER
VALUE
Speed
9600 bps
Data Encoding
NRZ
Transmit Clock Source
External
Address
"A"
Autoenables
Off
TxLine Type
Land
RxLine Type
Land
Timeout
30 (3 seconds)
Max retry count
10
Window size
Packet size
54 bytes
- 3.4 -
TABLE 3.5
Factory-set parameters for System
PARAMETER
VALUE
Tuning
Response
Hardware configuration of the link changeover feature and audible alarm are described in Appendix
B, that of the voice port is described in Appendix H, and of the inbuilt telecom line interfaces in
Appendices I and J.
3.2 SUPERVISORY PORT OPERATION

A few seconds after power on the supervisory port on a properly working unit displays the message
CYGNUS LS 517 VX.XX
Stored params pgmd
Here "X.XX" refers to the version number of the software in the unit.
In case switch 1 on DIP switch SW 3 at the base of the unit is set to CLOSE, the multiplexer also
displays the following message on power on
SUP PORT FORCED WITH DEFAULT PARAMS VIA SWITCH 1
Following these messages the "prompt"
L>
is displayed.
Commands can be entered once the prompt appears on the screen. The "L" in the prompt indicates
that the supervisory terminal is communicating with the local unit's Supervisory Function.
The Configuration Memory in the unit contains a checksum of its contents along with the stored
operating parameters. In addition, it also contains the identification code "CYGNUS LS YYY
VX.XX", which can be read via the ID command (see Sec. 3.3.10). The appearance of the above
message(s) indicates the following:
{ The Configuration Memory checksum has been verified
{ The identification code in the Configuration Memory has been checked and found good
{ All terminal ports, voice port, the composite port, and the System have been programmed
with the respective operating parameters stored in Configuration Memory
If the identification code stored in Configuration Memory is found to be bad, the message
CONFIG MEM ID ERR
Dflt params pgmd
is displayed on power up, and default values are assumed for all parameters.
In case the checksum stored in Configuration Memory is found to be bad the following message
appears on the supervisory port:
CONFIG MEM CHKSUM ERR
Dflt params pgmd
- 3.5 -
All operating parameters are again set to their default values.

The default values are the same as the factory-set parameters detailed in Tables 3.3.1, 3.3.2, 3.4
and 3.5.
NOTE
The "DFLT" indicator on the front panel of the unit is lit continuously if the unit assumes
default parameters at reset because of invalid non-volatile configuration memory contents.
However, if subsequently the unit is put in a test mode (by initiating diagnostics, or by the
"CONNECT" command, or by selecting "ADDRESS OVERRIDE" on the composite port),
this indicator starts flashing. The indicator will flash until the test mode is removed, after
which the indicator again glows steadily indicating the unit is in default mode.
In case 8-port operation has been selected through DIP switch, the following message will also be
displayed.
508V2 Compatible mode.
Also, unless the CYGNUS 517 is configured otherwise, following message is also displayed
516 compatible mode.
3.3 SUPERVISORY PORT COMMANDS

All supervisory port commands (except COPY) follow one of the following syntax's:
<CMD> [RETURN]
<CMD> <PORT> [RETURN]
<CMD> <PORT> <PARAM KEYWORD> [RETURN]
<CMD> <PORT> <PARAM KEYWORD> <PARAM VALUE> [RETURN]
Here [RETURN] means the CARRIAGE RETURN or ENTER key on the keyboard.
The COPY command syntax is given in Sec. 3.3.3.
Here
{ <CMD> is the command to be executed
{ <PORT> identifies the port on which the command is to be effected. CP is the composite
port, SP is the supervisory port, TP1 through TP8 (TP16) are terminal ports, VP is the voice
port and SYS is the system
{ <PARAM KEYWORD> is the keyword which identifies the specific parameter sought to be
changed/ displayed by the command
{ <PARAM VALUE> is the value to be assigned to the parameter (used only for the SET
command)
Commands may be entered in upper or lower case. If any mistake is made in entering the
command, one of the following error messages is displayed on the supervisory terminal:
ERROR IN COMMAND
or
ERR: WRONG NO OF PARAMS
Detailed descriptions of various commands are given below.
- 3.6 -
3.3.1 Modifying parameters

The SET command is used to modify parameters for any port or the system.
Syntax: SET <PORT> <PARAM KEYWORD> <PARAM VALUE> [RETURN]
or S <PORT> <PARAM KEYWORD> <PARAM VALUE> [RETURN]
<PORT>:
This identifies the port on which the operation is to be performed. Valid values are:
{
{
{
{
{
TP1 through TP8 (TP16) for terminal ports

VP for the voice port
CP for the composite port
SP or SUP for the supervisory port
SYS for the system
<PARAM KEYWORD>:
This identifies the particular parameter that is to be modified for the channel. Table 3.6 lists valid
parameter keywords, their significance, and the type of port for which the particular parameter is
applicable. This table is essentially a list of the configurable parameters for various ports.
<PARAM VALUE>:
This is the value to be assigned to the parameter specified by the KEYWORD above. Table 3.6
also lists valid values for each of the parameters.
Not all combinations of <PORT>, <PARAM KEYWORD> and <PARAM VALUE> are valid. The
following error message is displayed on the supervisory terminal in case an invalid SET command
is given:
ERR: INVLD PARAM
TABLE 3.6
Parameter keywords and their values for the SET command
Keyword(s)
Port type
Valid values
Effect
ADDRESS
Composite
A, B, O or OVERRIDE
See Comments
AUTOENABLES, AE
Composite
ON,OFF
See Comments
CLOCK, CLK
Composite
EXTERNAL,EXT
INTERNAL, INT
External Tx clock
Internal, Tx clock
See Comments
DATABITS, DTB
Terminal
5,6,7,8
Supervisory
Desired no. of data bits set
DISCCHAR
Supervisory <Decimal No.>
See Comments
ECHO
Terminal
ON,OFF
Supervisory
Echo enabled
Echo disabled
See Comments
ECHOCANCELLATION Voice
ON,OFF
See Comments
EIAPROP
Terminal
ON,OFF
EIA propagation enabled

EIA propagation disabled
See Comments
ENCODING, ENC
Composite
NRZ, NRZI
Desired encoding set

See Comments
FLOWCONTROL, FC
Terminal
SW or XON/XOF
HW or RTS/CTS
NONE
See Comments
HOOK
Voice
ON,OFF
See Comments
- 3.7 -
Keyword(s)
Port type
Valid values
Effect
IFC
Terminal
SW or XON/XOF
HW or RTS/CTS
NONE
See Comments
LINKMSG
Terminal
ON , OFF
See Comments
LPBK, LOOPBACK
Terminal,
Composite
Voice
LOCAL,REMOTE,ML, See Comments

MR
PCM,CODER,ANALOG
OFF
MAXRETRY
Composite
<Decimal No.>
See Comments
NAME
System
<string>
See comments
OFC
Terminal
SW or XON/XOF
HW or RTS/CTS
NONE
See Comments
PACKETSIZE
Composite
<Decimal No.>
See Comments
PARITY, PAR
Terminal
ODD,EVEN, NONE
Supervisory
Desired parity option set for

send and receive
POSTFILTER
Voice
ON,OFF
See Comments
RING
Voice
ON,OFF
Generates or stops ring on

FXS interface
See Comments
RXLINE
Composite
LAND,SAT1HOP,SAT2 Receive line type on TP

HOP
RATE
Voice
4800, 6400,8000,10400 Encoding Rate

See Comments
SPEED, SP
Terminal,
Supervisory
&
Composite
50, 75, 110, 150, 300,

600, 1200, 1800, 2000,
2400, 3600, 4800, 7200,
9600, 14400, 19200,
28800, 38400, 64000,
AUTO
STOPBITS, STPB
Terminal
1, 1.5, 2
Supervisory
Desired no. of stop bits set
TIMEOUT
Composite
<Decimal No.>
See Comments
TONE
Voice
ERRTONE,ET
TESTTONE,TT
RINGBACKTONE,RB
OFF
Generated tones in voice path
Sets desired baud rate

Min CP speed: 1200
Terminal port speed <=19200
or AUTO
See Comments
See comments
TXLINE
Composite
LAND,SAT1HOP,
SAT2HOP
Transmit line type on TP
TUNING
System
EFFICIENCY,
RESPONSE
See Comments
VOLUME
Voice
MUTE,-21,-18,-15,-12,- Relative volume, in dB

9,-6,-3,0,3,6,9,12,15,18, See Comments
21
WINDOWSIZE
Composite
<Decimal No.>
See Comments
NOTE
The new values of any parameters that are changed using the SET command do not
become effective immediately. The new values have to be stored in the non-volatile
Configuration Memory and the unit has to be reset, or the particular port on which the
change is made has to be initialised, before the new parameters will take effect (see Secs.
3.3.5, 3.3.6 and 3.3.7).
- 3.8 -
- 3.9 -
Comments
ADDRESS
This parameter is used to set the address of the multiplexer. Valid values for the addresses are "A",
"B" and "O" (or "OVERRIDE"). Under normal operation, the address of one multiplexer should be
set to "A", that of the multiplexer at the other end of the link to "B", and the address override mode
should not be selected on either unit. Like other operating parameters, setting the address to "A" or
"B" takes effect only when a STORE command (see Sec. 3.3.5) is given followed by a RESET (see
Sec. 3.3.6). However, the override mode takes effect immediately on selection (see below).
NOTE
If the addresses of both multiplexers are identical and the override mode is not selected
on them, the link between the two multiplexers will not establish even if the interconnecting
physical circuit is functioning properly. The "ADERR", "TX" and "RX" indicators on the
front panel of both units will flash in this case.
The "O" (or address "OVERRIDE") mode is provided to enable loop back testing on the composite
port of the multiplexer. In the address override mode the multiplexer will establish a link with itself if
a loop back is given on the composite port of the unit; without address override, it will not. The
"TEST" indicator on the front panel will flash as long as the address override mode is selected. The
address override status of the composite port can also be seen by giving the "STATUS" command
(see Sec. 3.3.8).
Address override is a temporary directive to the multiplexer, and is not a substitute for "A" or "B".
The override mode takes effect immediately after the directive is given, and stays till the unit is
reset. The override directive cannot be made permanent by the "STORE" command.
NOTE
The override address is a purely diagnostic feature. It is not to be used during normal
operation of the multiplexer. On power-on or after resetting, the override status is always
"OFF".
AUTOENABLES
This parameter is valid for the composite port only. If it is set to ON, the multiplexer will not transmit
on its composite port until the CTS signal on the RS232-C interface from the modem is active; also
it will not receive from the modem until the DCD signal is active. If this parameter is set to OFF, the
multiplexer ignores the status of CTS and DCD during transmission and reception on the composite
port.
CLOCK
This parameter allows the user to specify the source of the Transmit Clock on the composite port.
On asynchronous (terminal) ports this clock source is always internal - any attempt to set it to
external results in the error message
ERR: INVLD PARAM
On the composite port, external clock is allowed only with NRZ encoding. With NRZI encoding the
Transmit clock is internal and is combined with data at the time of transmission. The Receive clock
is derived from the received data stream.
The error message
ERR: ENC NOT NRZ
is displayed if external clock is specified with NRZI encoding on the composite port.
- 3.10 -
When operating with synchronous modems on the composite port, NRZ encoding should be used
as the modem supplies the clock (i.e. clock is external). When operating with a line driver, however,
NRZI encoding with internal clock may be used if the transmit clock is not received from the remote
end.
DISCCHAR
This parameter is valid for the supervisory port only. Specifying any other port results in the error
message
ERR: NOT SUP CHNL
CYGNUS 517 multiplexers provide a diagnostic facility to CONNECT to any terminal port (See Sec.
3.3.9) from the supervisory port. Once connected, data can be transferred between the supervisory
port and the concerned terminal port. This connection can be terminated by typing a special
"disconnect character" from the supervisory terminal. The disconnect character is specified via the
command:
SET SP DISCCHAR <DDD> [RETURN]
where <DDD> is the ASCII code (in decimal) of the required disconnect character. The specified
disconnect becomes effective only after a STORE command followed by a RESET is given.
The disconnect character is factory set to Cntrl-C (ASCII 03). This is also the default value
assumed in case the non-volatile Configuration Memory contents are found invalid on reset, or if
the "DEFAULT" command is given (see Sec. 3.3.4).
Apart from its diagnostic utility, the CONNECT facility may also be used to set up a single
centralized supervisory console for a number of CYGNUS 517/516/508V2 multiplexers. See
Appendix E for more information.
ECHO
This parameter is valid only for terminal and supervisory ports. If the Echo mode is enabled on a
terminal port, characters received from the terminal are echoed back by the multiplexer according
to the following rules:
{ A Carriage Return character (ASCII 13) is echoed back as a Carriage Return followed by a
Line Feed (ASCII 10)
{ All other characters are echoed as such, except that if the software (XON/XOF) option is
selected for OUTPUT FLOW CONTROL (see under FLOW CONTROL and OFC below),
XON and XOF characters (ASCII 17 and 19 respectively) are not echoed
If the device connected on the terminal port is a computer, Echo operation should normally be
disabled (OFF). If the connected device is a terminal, and the remote computer does not echo
characters, this parameter may be enabled (ON). For Echoplex operation, where the remote
computer echoes characters input from the terminal, this option should be disabled.
ECHOCANCELLATION
This parameter is valid only for voice port. If enabled, it provides echo cancellation on the voice
path so that the remote echo is avoided. This parameter should normally be enabled.
EIAPROP
This parameter is valid only for terminal ports. If this parameter is enabled the state of the DTR
signal from the terminal is reflected at the DSR pin on the corresponding terminal port of the remote
multiplexer. Since DTR from a terminal is normally active when the terminal is on, this feature may
be used by a computer to determine whether a terminal is powered-on or not. The cable connecting
- 3.11 -
the terminal to the multiplexer must carry DTR on the appropriate pin of the Terminal Port
connector (Pin 20 on D-type connector) if EIAPROP is on.
ENCODING
Only NRZ (Non Return to Zero) encoding is allowed on terminal ports. If NRZI is specified for a
terminal port, the message
ERR: INVLD PARAM
is displayed on the supervisory port. On the composite port, either NRZ or NRZI (Non Return to
Zero Inverted) encoding may be specified.
The CLOCK and ENCODING parameters together allow selection of a range of data
communication equipment for use on the composite port of the multiplexer. For connection to
synchronous modems, NRZ encoding and EXTERNAL clock should be selected. With line drivers
which propagate only Transmit and Receive data, NRZI encoding with INTERNAL clock should be
used. If the line drivers also propagate transmit and receive clock in addition to the data signals,
NRZ encoding with EXTERNAL clock may be used.
FLOWCONTROL
This parameter is valid only for terminal ports. It specifies the mechanism adopted when the
multiplexer or the terminal runs out of input buffer memory and is temporarily unable to receive
data.
With XON/XOF flow control the device (multiplexer or terminal) which has a temporary shortage of
input buffer memory sends a XOF character (CTRL-S or ASCII 19) to the other device. The other
device should then stop sending further data. When the first device has buffer space available, it
asks for resumption of transmission by sending a XON character (CTRL-Q or ASCII 17).
With RTS/CTS flow control, the terminal should deactivate the RTS input signal on the RS232-C
connector of the multiplexer if it runs out of buffer space. If the multiplexer has a temporary
shortage of buffer space it deactivates the CTS signal on its RS232-C connector. The
corresponding signals are reactivated when there is enough buffer space available.
If this parameter is set to NONE, no flow control mechanisms will operate on that port.
If any of the flow-control modes is selected on a particular terminal port of the multiplexer, the
selected input flow control mechanism is activated on that port whenever the number of characters
in the port's input buffer exceeds a count called the "high-water-mark" (HWM), and deactivated
when the number of characters falls below the "low-water-mark" (LWM)).
This parameter selects flow control operation in both input and output directions, i.e. from
multiplexer-to-terminal and terminal-to-multiplexer. If flow control is required in only one direction, or
if different flow control mechanisms are required in the two directions, the input and output flow
control may be separately configured by specifying the IFC and OFC parameters as described
below.
HOOK
This command changes the current loop condition of voice port immediately if operating as a FXO
interface. By setting this parameter to ON value, the voice port closes external loop simulating an
OFF-HOOK. By setting this parameter to OFF value, the voice port forces the loop to open (low
current) condition thereby simulating an ON-HOOK condition.
In case this command is given while the port is selected to have FXS interface, an error message
ERR. VP Interface is not FXO
- 3.12 -
is displayed and no action is taken.

NOTE
Since this command enforces a loop condition on the FXO interface, it may interfere with
the status of an any ongoing call.
IFC
This parameter selects flow control from multiplexer to the terminal. If this parameter is set to
XON/XOF the multiplexer sends XOF to the connected terminal whenever it wants the terminal to
stop sending data, and XON when it wants the terminal to resume sending data. If the parameter is
set to RTS/CTS the multiplexer flow controls the terminal by deactivating the CTS signal on the
RS232-C interface, and removes flow control by activating CTS. If the parameter is set to NONE,
the multiplexer does not flow control the terminal at all.
LINKMSG
If the LINKMSG parameter is ON for a TP, the CYGNUS 517 mux will send the following message
to the device connected on the TP whenever the composite port link goes down:
*** LINK DOWN ***, along with a BELL character;
When the composite link is restored the following message is sent to the device connected to that
TP:
*** LINK UP ***, along with a BELL character.
If the LINKMSG parameter is OFF for a TP the above messages are not sent on the TP when the
composite link goes down or comes up.
LOOPBACK
This parameter is used to enable loop back diagnostics on a particular port (terminal, voice or
composite). Setting TP or CP loop back to LOCAL loops back data internal to the multiplexer (See
Fig. 3.1.1). Setting LPBK to REMOTE loops back data to the external DCE (Data Communication
Equipment) connected to that port; e.g., to the modem/line driver/converter on the composite port
and to the terminal/computer on the terminal port. Setting CP loop back to ML (Modem Local) sets
the CP LL signal active, which in turn request the DCE to provide a loop back (see Fig. 3.1.1).
Setting CP loop back to MR (Modem Remote) makes the RL signal to the DCE active, thereby
asking the local DCE to request the remote DCE to provide loop back (see Fig. 3.1.1). The ML and
MR loop back are useful to verify the local mux to modem connection, and the leased line operation
respectively. However, for the ML and MR loop back to be possible, a proper modem cable which
carries the LL and RL signal to the modem is a must, and the modems also should provide the
facility of providing local and remote loop backs using the LL and RL signals.
All the TP and CP loop backs may be removed by SETting LPBK OFF. On a particular port only
one type of loop back is allowed to be active at a given time.
For voice port, three types of loop back are allowed. The Analog loop back is equivalent to a local
loop back in which the voice sent by the multiplexer to the voice port devices is looped back in
analog form to the multiplexer itself. Thus if a voice call is present and an analog loop back is
effected, the voice generated by the voice port device on the remote multiplexer should be heard
back by the user of that device at the remote site. Since the analog section is the last section in the
voice port, operating the analog loop back checks the end-to-end voice path except the local line
portion, for which the coder or PCM loop back may be used. The PCM and Coder loop backs are
remote loop backs which loop back the data received by the multiplexer on its voice port.
Successful operation of PCM loop back checks the operation of internal analog to digital conversion
- 3.13 -
function of the multiplexer whereas the coder loop back function checks the function of the voice
encoder function which carries out voice compression algorithm.
The loop back test for voice port cannot be carried out when a tone test is ON for the voice port. If
attempted while a tone test is running, the message
ERR. TONE TEST IS ON
is displayed and no action is taken. The loop back command takes precedence over the normal
voice propagation and may affect the operation of voice call.
Whenever a loop back is enabled on any port the "DFLT/TEST" indicator on the front panel will
flash till the loop back is removed by giving the appropriate command. The status of whether a loop
back test is on for any port is indicated in response to STATUS command for terminal and
composite ports and in response to VPSTATUS command for voice port.
Loop backs may also be initiated on the remote multiplexer by going REMOTE (See Section
3.3.11), and giving the SET LPBK command. However the composite port on the remote
multiplexer is not allowed to be looped back since this would lead to loss of control. The following
error message is displayed if this is attempted.
ERR: Not allowed in Remote
Unlike most commands the loop back diagnostic activation/ deactivation commands take effect as
soon as they are given. There is no need to perform a STORE followed by a unit RESET or port
INIT to effect loop backs.
Loop back testing is useful when trying to determine whether a multiplexer unit is working properly
or not. A loop back on the composite port may be given in various ways; e.g.. by connecting a loop
back connector on the port; by enabling loop back from the modem/ line driver attached to the port;
by initiating a loop back through command, or by looping back data at the remote end. Once the
link is thus established, any data entered from the terminal ports will be transmitted back to them
after being looped back on the composite port. The "OVRD" indicator on the multiplexer is lit as
long as the address override mode is selected.
Loop back testing on the composite port cannot be carried out without enabling "Address Override".
Sup. Terminal
RL
Terminal
Port
LL
CYGNUS 517
ML
MR Remote
Local
Modem
Modem
Composite Port
Leased Line
LL RL
LL: Local Loopback

RL: Remote Loopback
To
Remote
Mux
ML: Modem Local Loopback

MR: Modem Remote Loopback
Fig. 3.1.1 Loopbacks on Terminal and Composite Ports
- 3.14 -
CYGNUS 517
AL
PCM CODER
Voice Port
Composite Port
AL: Analog Loopback
PCM: PCM Loopback
CODER:Coder Loopback
Fig. 3.1.2 PCM, CODER and ANALOG loopbacks on

LINKSHARE 516 voice port
Note that giving a loop back on the composite port will result in data coming back to the transmitting
side. To ensure that the link stays up in such a case, the ADDRESS OVERRIDE mode of operation
should be selected on the unit to which data is being looped back (See discussion on ADDRESS
above).
NOTE
The action initiated by the SET LOOPBACK command for a voice or data port take precedence over the normal operation of that port. Hence, for normal operation to resume on
the port, any loopback started with the SET LOOPBACK command should be made OFF.
NOTE
Since this command enforces a loop condition on the FXS interface, it may interfere with
the status of an existing call, if any.
MAXRETRY
This parameter is valid only for the composite port. It specifies the maximum number of attempts
made on the composite port to transmit a packet, after which the link is declared to be down. A
packet is retransmitted if no acknowledgement is received for it from the remote multiplexer after
waiting for the TIMEOUT value (See TIMEOUT below). This can happen if there are errors on the
link).
If a value of 32 is chosen as MAXRETRY, then the CYGNUS 517 then the retries are carried out till
the link is restored, i.e. Internally the link is never declared to be down. This provision has been
made as in certain application, the flushing of terminal port memory buffers, associated with
declaration of link to be down may not be desired, and it is preferred to wait till the link comes up,
and use the data being held in the terminal port buffers.
NAME
This paramater when programmed assigns a name to the CYGNUS 517 unit with which it is
possible to idenify the unit uniquely if named appropriatily. The name parameter accepts a 1-9
character alphanumeric string, which when programmed and unit parameters stored, becomes
operational.
This string is then displaed in the :STATUS command report. When the unit is in default parameter
state, the name DEFAULT00 is assigned till it is changed by programming.
A typical use of the name assignment is to identify the unit by its assigned name when the
supervisory function of the unit is being accessed in such a way that the physical path of the
accessing terminal to the unit being accessed cannot be traced easily, such as when the
- 3.15 -
supervisory function is accessed over LAN using Telnet facility (See appendix M). In such case the
terminal could be situated hundreds of kilometers away from the CYGNUS 517 unit which iwhose
supervisor it accesses.
OFC
This parameter selects flow control from terminal to multiplexer. If this parameter is set to
XON/XOF the multiplexer stops sending data to the connected terminal when it receives an XOF
from the terminal, and resumes sending on receipt of XON. If the parameter is set to RTS/CTS the
multiplexer stops transmission to the terminal when the RTS signal on the RS232-C interface is
de-activated by the terminal, and resumes transmission when RTS goes active. If the parameter is
set to NONE, the multiplexer can not be flow controlled by the terminal.
See also discussion on IFC.
PACKETSIZE
This parameter is valid only for the composite port. It specifies the maximum number of bytes that
are allowed in a packet transmitted on the composite link (See also discussion on TUNING below).
POSTFILTER
This parameter is applicable for voice port only. Activation of this parameter applies soothing
algorithm to the voice output. This parameter should normally be kept "ON". However, if two 517
voice channels are to be cascaded, then this parameter should be disabled.
RATE
This parameter is valid only for voice port. It specifies the encoding rate used for sending the voice
signals in digitised form from one multiplexer to the other. The encoding rate should be chosen in
such a way that during the voice call, enough bandwidth is available for sending terminal port data
between the multiplexers. A rule of thumb is that the selected encoding rate should not exceed half
the data rate of composite port link speed. For example, if the composite port operates at speed of
9600 bps, the encoding rate should be kept at 4800 bps only. If the composite port link speed is 64
kbps, then encoding rate of 10,400 bps may be selected. Note that if the voice port is used for
sending facsimile signals, the negotiated fax data rate will always be less that the selected
encoding speed of voice channel.
A 4800 bps encoding rate gives a workable voice quality, whereas voice quality for 6400, 8000 and
10400 is better. The rates 8000 and 10400 may be mainly used for obtaining higher fax speed. The
fax speed achievable are 2400 bps for 4800 rate selection, 4800 bps for 6400 and 8000 bps rate
selection and 9600 bps for 10400 bps rate selection. The actual decision of selecting the encoding
rate should be made after considering factors such as available composite port speed, number of
active data ports, desirable voice quality, required fax speed etc.
IMPORTANT
As the CYGNUS 517 is designed for predominantly data applications, certain minimum
bandwidth is always required for the multiplexer over and above the selected encoding
rate of voice to make voice-data multiplexing possible. Thus the composite port bandwidth
should always be higher than the selected voice encoding rate. If this rule is not followed,
both voice and data transfer may be affected.
RING
This command starts or stops ring on the FXS interface immediately if the external device is
ON-HOOK. If the external device is OFF-HOOK, this command does not take effect. By setting this
parameter to ON value, the voice port generates ring simulating an presence of a call. By setting
this parameter to OFF value, the voice port stops generation of ring if present. The ring being
generated will stop if the external device connected to the FXS voice port goes OFF-HOOK.
- 3.16 -
In case this command is given while the port is selected to have FXO interface, an error message
ERR: VP INTERFACE IS NOT FXS
is displayed and no action is taken.
NOTE
Since this command enforces a RING condition on the FXS interface, it may interfere with
the status of an existing call, if any.
RXLINE
These parameters are valid only for the composite port. They are used to define the type of
composite link being used for RECEIVE and TRANSMIT respectively. Valid options are:
{ LAND: If the composite link in that direction is a land line (such as microwave, radio, or a
land telephone line)
{ SAT1HOP: If the line is a single-hop satellite link
{ SAT2HOP: If the line is a two-hop satellite link
It is required to specify the line type because of the different propagation delays associated with
these different types of line types. The composite link communication protocol adjusts certain
time-outs based on the specified line type. Also the following parameters are automatically set to
proper default values whenever the Line Type is changed:
MAXRETRY, PACKETSIZE, TIMEOUT, WINDOWSIZE
Appendix D gives the default values set for each of these parameters for various line types, and
also the ranges within which the user may set each of them (if the parameters need to be tuned
further). If the value specified for a parameter is outside the valid range given in Appendix D, the
following message is displayed on the supervisory terminal:
ERR: INVALID VALUE
Both the line types are factory-set to LAND. This is also the default value assumed in case the
non-volatile Configuration Memory contents are invalid at reset, or if the "DEFAULT" command is
given (see Sec. 3.3.4).
SPEED
On the composite port only speeds of 1200 bps or more (up to 64000 bps) are allowed. The
message
ERR: MIN SYNC SP 1200 BPS
is displayed on the supervisory port if a speed less than 1200 bps is specified for the composite
port.
On terminal and supervisory ports the maximum programmable speed is 19200 bps. The error
message
ERR: MAX ASYNC SP 19200 BPS
is displayed if the specified speed for a TP or SUP is attempted to be greater than 19200 bps.
A terminal port may also be programmed for "AUTOBAUD" operation by setting its speed to
"AUTO". The multiplexer will automatically determine the speed of the attached terminal in this
- 3.17 -
case. The multiplexer starts looking for the terminal's speed on detecting an OFF-to-ON transition
on the DTR signal on the RS232 interface (this transition is normally achieved by putting the
terminal off and on). The speed recognition character is ASCII 13 (CARRIAGE RETURN). The
operator should press the CARRIAGE RETURN key one or two times immediately after
powering-on the terminal. The multiplexer is able to correctly determine the following terminal
speeds in AUTOBAUD mode:
75, 150, 300, 600, 1200, 1800, 2400, 3600, 4800, 7200, 9600 bps
The DTR signal from the terminal must be present on the cable connecting the terminal to the
multiplexer for AUTOBAUD operation.
In case both the corresponding terminal ports on a pair of connected CYGNUS 517 multiplexers
have their speed programmed as "AUTO", detection of speed on one side will result in same speed
being programmed on the corresponding terminal port on the other unit provided the link is up, and
the DTR signal on the other side is active.
Note that other communication parameters on the autobaud port, such as number of data bits,
number of stop bits and parity, are not detected by the multiplexer, and should be properly
programmed.
TIMEOUT
This parameter is valid only for the composite port. It specifies (in multiples of 100 milliseconds) the
maximum time for which the multiplexer will wait for an acknowledgement after transmitting a
packet to the other multiplexer. If no acknowledgement is received in this time, the packet is
retransmitted.
TONE
This parameter setting is used to generate test tones in the voice path of voice path and may be
used for testing purposes. The effect of this parameter is seen in a call-on state of the voice port.
The direction in which tones are generated are described in figure 3.2. The tone test cannot be
carried out when a loop back test is ON for the voice port. If attempted while a loop back test is
running, the message
ERR. LOOPBACK TEST IS ON
is displayed and no action is taken. The front panel indicator TEST/DFLT flashes as long as this
test is active. The status whether this test is ON or OFF may be obtained in response to the
VPSTATUS command. The tones generated by this command take precedence over the normal
tones. Hence as long this test tone command is in force, the normal operation of the ports may be
affected.
NOTE
The tones set by the SETTONE command take precedence over the normal operation of
the voice port. Hence, for normal operation to resume, any tone started with the
SETTONE command should be made OFF.
- 3.18 -
RINGBACK
SUP
TESTTONE
CYGNUS 517
RECEIVE
Voice Path
TRANSMIT
AL
Voice Port
PCM
CODER
ERRTONE
Composite Port
AL: Analog Section

PCM: PCM Section
CODER:Coder Section
Fig. 3.2 Generation of tones by SET TONE command

for CYGNUS 517 voice port
TUNING
This parameter is valid for SYStem only. SETting it for one of the ports results in the error
message:
ERR IN COMMAND
The performance of the multiplexer can be tuned with respect to two different parameters efficiency of the communication protocol in utilising the composite link, and the response time
offered to user terminals. As described in Sec. 5.1 data from various terminal ports in the
multiplexer is combined into "Packets" for transmission over the composite link. "Packet" formation
involves addition of some extra control bits which identify the start and end of the packet, data from
various terminal ports, etc. These extra bits constitute an overhead on the communication protocol
since they are not user data bits. The efficiency of the communication protocol (which can be
roughly defined as the ratio of the number of user data bits to the total number of bits in a packet) is
better if the packet size is larger, because then the overhead is spread over a larger number of data
bits.
However, larger packets take more time for transmission over the composite link. Thus the
"response time", which is the time taken between typing a character at a terminal and receiving the
computer's response to the character, increases with packet size. To ensure a reasonable
response time the packet size should not be too large.
To summarize, with larger packet sizes communication protocol efficiency improves, but response
time worsens. A trade-off between efficiency and response time is thus possible. Depending on the
application the multiplexer may be tuned for one of these two parameters via the commands:
SET SYS TUNING EFFICIENCY
or
SET SYS TUNING RESPONSE
After storing and resetting, the proper packet size will be selected based upon the programmed
composite port speed (see Appendix D). The multiplexers are factory set for RESPONSE tuning.
This is also the default setting assumed if the non-volatile Configuration Memory contents are found
invalid at reset, or if the "DEFAULT" command is given (see Sec. 3.3.4).
For interactive applications normally RESPONSE tuning should be selected, while for
non-interactive applications EFFICIENCY tuning may be selected.
- 3.19 -
TXLINE
See discussion on RXLINE.
NOTE
It is essential that the TXLINE parameters on one end should be the same as the RXLINE
parameters for the multiplexer at the other end of the link, and vice versa. Else the link
between them may not be established. If both lines (TXLINE and RXLINE) are defined to
be LAND lines on one multiplexer, and the corresponding lines on the other unit are
defined to be SATELLITE lines, the "LINK" indicator on both units will blink, and the link
will not be established between the units.
VOLUME
This parameter is applicable for voice port only. It programs the relative volume level of transmit
section of the voice port in steps of 3 dB. The effect of this command takes place after storing the
parameter and powering off/on the unit. Setting the parameter to MUTE will cause the multiplexer to
cut-off the transmit to voice port completely.
WINDOWSIZE
This parameter is valid only for the composite port. It specifies the number of packets that are
allowed to be outstanding (i.e., for which acknowledgements have not yet been received) at any
time.
3.3.2 Displaying parameters

CYGNUS 517 multiplexer contains non-volatile Configuration Memory which retains operating
parameters for the various ports and the system even when power to the unit is off. Any changes
that are made to operating parameters are, however, not updated in Configuration Memory till
explicitly stored (see Sec. 3.3.5).
At any given moment there are two sets of operating parameters - the "Old" parameters, which are
the ones with which the unit is actually configured; and the "New" parameters, which have been
specified since the last time the unit was powered on/reset. At power on, parameters from
Configuration Memory are copied into both the "Old" and "New" parameter sets, and the unit is then
configured with parameters from the "Old" set. Any subsequent changes in the parameters are
reflected only in the "New" set. When the "STORE" command is given, the "New" set is copied into
the Configuration Memory. The changed parameters will therefore actually take effect only when a
"RESET" is performed after the "STORE".
A point to be noted however: If the unit assumes default parameters at power-on (because the
Configuration Memory contents are found to be invalid, or because default parameters have been
forced by the "DEFAULT" command - see Sec. 3.3.4), both the "Old" and "New" parameter sets will
contain the default parameters at initialisation. If a STORE command is now given, the default
parameters will be stored in the Configuration Memory.
Two commands are provided on CYGNUS 517 multiplexers to display operating parameters for a
port. "OLD" displays the parameters that are actually in effect on the port, whereas "NEW" reflects
any modifications made in the parameters since the last time the unit was reset. If no modifications
have been made after resetting the unit, the two commands display same values.
Syntax:
or
OLD <PORT> <PARAM KEYWORD> [RETURN]

O <PORT> <PARAM KEYWORD> [RETURN]
or
NEW <PORT> <PARAM KEYWORD> [RETURN]

N <PORT> <PARAM KEYWORD> [RETURN]
- 3.20 -
Valid PORT values for terminal ports are TP1 through TP8 (TP16). CP is the composite port, SP is
the supervisory port and SYS is the system. Valid parameter keywords and their significance are
given in Table 3.7.
The command
OLD TP ALL [RETURN]
or
NEW TP ALL [RETURN]
lists all the operational or the modified parameters of all terminal ports.
TABLE 3.7
Parameter keywords for OLD and NEW commands
Keyword(s)
Port type
Displayed values
ADDRESS, ADDR
Composite
A,B
ALL
Composite, Terminal,
Supervisory, System
See Comments
AUTOENABLES
Composite
ON, OFF
CLOCK, CLK
Composite
EXTERNAL, INTERNAL
DATABITS, DTB
Terminal,
Supervisory
5,6,7,8
DISCCHAR
Supervisory
<Decimal No.>
ECHO
Terminal,
Supervisory
ON, OFF
ECHOCANCELLATION
Voice
ON, OFF
EIAPROP
Terminal
ON, OFF
ENCODING, ENC
Composite
NRZ, NRZI, FM
FLOWCONTROL, FC
Terminal
XON/XOF, RTS/CTS, NONE
IFC
Terminal
XON/XOF, CTS, NONE
LINKMSG
Terminal
ON, OFF
LPBK
Terminal &
Composite
LOCAL, REMOTE, OFF
MAXRETRY
Composite
<Decimal No.>
OFC
Terminal
XON/XOF, RTS, NONE
PACKETSIZE
Composite
<Decimal No.>
PARITY, PAR
Terminal,
Supervisory
ODD, EVEN, NONE
POSTFILTER
Voice
ON,OFF
RATE
Voice
4800,6400,8000,10400
RXLINE
Composite
LAND, SAT1HOP, SAT2HOP
SPEED, SP
Terminal
Supervisory &
Composite
50, 75, 110, 150, 300, 600, 1200, 1800, 2000,

2400, 3600, 4800, 7200, 9600, 14400, 19200,
28800, 38400, 64000, AUTO
STOPBITS, STPB
Terminal,
Supervisory
1, 1.5, 2
TIMEOUT
Composite
<Decimal No.>
TXLINE
Composite
LAND, SAT1HOP, SAT2HOP
TUNING
System
EFFICIENCY, RESPONSE
VOLUME
Voice
MUTE, -21,-18,-15,-12,-9,-6,-3,0,
3,6,9,12,15,18,21
WINDOWSIZE
Composite
<Decimal No.>
- 3.21 -
Comments:
ALL
This parameter is used to display all relevant parameters for a port. For the composite port these
parameters are:
{ Speed
{ Clock source
{ Encoding
{ Address
{ Autoenables Status
{ Tx and Rx Line type
{ Timeout count (in multiples of 100 msec)
{ Maximum retry count
{ Window size
{ Packet size
For a terminal port they are:
{ Speed
{ Echo Status
{ Number of data bits per character
{ Parity selection
{ Number of stop bits per character
{ I/p and O/p flow control option
{ EIA Propagation status
{ Link Down Message enable status
For voice port they are:
{ Encoding Rate
{ Echo cancellation enable status
{ Post Filter enable
{ Voice Activity Detection enable
{ Transmit volume
For the supervisory port they are:
{ Speed
{ Echo Status
{ Parity selection
{ Disconnect Character
For SYS they are:
{ Tuning
3.3.3 Copying terminal port parameters

The COPY command can be used to copy all configurable parameters from one terminal port to
another.
Syntax: COPY <PORT n> TO <PORT m> [RETURN]
or
CP <PORT n> TO <PORT m> [RETURN]
or
C <PORT n> TO <PORT n> [RETURN]
- 3.22 -
Here <PORT n> is the source terminal port number and <PORT m> is the destination terminal port
number. TP1 through TP8 (TP16) are valid values for both. In addition, if the source port's
parameters are to be copied to all terminal ports, ALL can be specified for <PORT m>.
COPY <PORT n> TO ALL [RETURN]
If CP (composite port) is specified as the source or destination port, the message
ERR: COMPOSITE PORT
is displayed on the supervisory port. If SP (supervisory port) is specified as one of the ports, the
error message displayed is
ERR: SUP PORT
NOTE
The COPY command always copies the "NEW" set of parameters (see Sec. 3.3.2) from
the source terminal port to the destination.
The parameters copied by this command are:
{ Speed
{ Echo Status
{ Parity selection
{ Number of stop bits per character
{ I/p and O/p flow control option
{ EIA Propagation
{ Link Down Message status
Loop back, being merely a status, is not copied.
As described in the discussion of "Old" and "New" parameters in Sec. 3.3.2, the copied parameters
are not effective on the destination port until they are stored and the unit is reset, or until that
particular port is initialised (see Secs. 3.3.5 and 3.3.6 and 3.3.7).
3.3.4 Setting factory default parameters

All operating parameters of the unit can be temporarily set to the factory-default values by giving
the DEFAULT command.
Syntax: DEFAULT [RETURN]
The following message is displayed on the supervisory terminals when this command is given:
CYGNUS LS 517 V4.81
TEST MODE
Dflt params pgmd.
The unit automatically executes a reset when this command is given, except that it temporarily
assumes default values for all parameters, and the "TEST" indicator on the front panel flashes.
In case the parameters are already default parameters (due to invalid Configuration Memory, or
due to a previously given "DEFAULT" command), this command is not executed and the message:
ERR: ALREADY IN DFLT
- 3.23 -
is displayed.
After a "DEFAULT" command is accepted, only a "RESET" to the unit will get it out of the "Default"
test mode to normal mode (where the unit is programmed with the parameters stored in
Configuration Memory). However, if a "STORE" command is given while the unit is operating with
default parameters, the default parameters are stored in the Configuration Memory, and the
previous contents of the Configuration Memory are lost.
3.3.5 Storing parameters

All modifications made to the operating parameters using the SET command may be stored in
non-volatile Configuration Memory using the STORE command.
Syntax: STORE [RETURN]
In response, the following message is displayed on the supervisory port:
Storing config. Wait..
After a few moments the message
Params stored
is displayed. This indicates that the operating parameters have been stored in the Configuration
Memory and the checksum has been verified after storage.
In case there is an error during storage, the message
ERR: UNABLE TO STORE
is displayed instead of the above message
NOTE
The stored parameters take effect in the entire unit only when the unit is reset (see Sec.
3.3.6), and on a specific port, when that port is INITialised (see Sec 3.3.7).
3.3.6 Resetting the multiplexer

The multiplexer may be reset using the RESET command:
Syntax: RESET [RETURN]
The effect is the same as that of switching off power to the unit and switching it on, except that the
initial power-on diagnostics is not carried out.
NOTE
Any untransmitted user data in the multiplexer is lost when this command is given. Also
any changes made in operating parameters (using the "SET" command) that are not yet
stored, are lost.
3.3.7 Initialising a single port

Individual terminal ports, or the composite port may be initialised (reset) without resetting the entire
multiplexer.
Syntax: INIT <PORT> [RETURN]
- 3.24 -
Valid values for <PORT> are TP1 through TP8 (TP16) and CP.
On terminal ports the port is reprogrammed with operating parameters from the non-volatile
Configuration Memory and all internal memory variables associated with the port are initialised. The
initialisation is done on the complete end-to-end path. In case the composite link is down when the
command is given on a terminal port, initialisation at the local end is done anyway, and the following
message is displayed:
LNK DN: ONLY LOCAL END INITED
NOTE
Any untransmitted user data in the multiplexer is lost when this command is given. Also
any changes made in this port's operating parameters (using the "SET" command) that
are not yet stored, are lost.
If the contents of the non-volatile Configuration Memory were found to be invalid at power-on, or if
the unit was forced to default parameters using the "DEFAULT" command (see Sec. 3.3.4), the
"INIT" command will use the default parameters instead of the parameters in the Configuration
Memory. The following message is displayed in this case:
USING DFLT PARAMS FOR INIT
The multiplexer port for which an INIT command is given pulses its DSR signal for about 100
milliseconds while the port initialisation is carried out.
3.3.8 Viewing unit status

The status of Terminal and Composite ports and the status of non-volatile system memory
multiplexer may be seen at a glance by giving the STATUS command.
Syntax: STATUS [RETURN]
The status of various ports is displayed as shown in Table 3.8.1(a) and Table 3.8.1(b) depending
on whether link changeover facility is installed/operational in the unit.
TABLE 3.8.1(a)
Status display on CYGNUS 517 (Without Link Changeover Facility)
Elapsed time in Days:Hr:Min:Sec::d:hh:mm:ss
NVRAM_ID: CYGNUS LS 517(*) V4.81 ROM_ID: CYGNUS LS 517 V4.81 HW_ID:1.2
508V2 compatible mode. (#) 516 compatible mode.(##) V.3/V.4 mode negotiated (#*)
Parameters: Stored (**) Ch_O: Not_mtd.
CP:
TP1:
TP2:
:
:
:
TPn:
LPBK LINK OVRD DSR(P) CTS DCD(P) TM

..
..
..
..
..
..
..
..
IFC OFC LPBK IBRK OBRK DTR RTS
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
- 3.25 -
..
..
TABLE 3.8.1(b)
Status display on CYGNUS 517 (With Link Changeover Facility)
Name: (%)
LAN Mon:(%)
NVRAM_ID: CYGNUS LS 517(*) V4.81 ROM_ID: CYGNUS LS 517 V4.81 HW_ID:1.3
508V2 compatible mode. (#) 516 compatible mode.(##) V.3/V.4 mode negotiated (#*)
Parameters: Stored (**) Ch_O: Mtd. Sw_sel: XXX, YYY, ZZZ, AAA, BBB, CCC (&)
CP:
TP1:
TP2:
:
:
:
TPn:
LPBK LINK OVRD DSR(P) CTS DCD(P) TM DSR(S) DCD(S) L_FLT

..
..
..
..
..
..
..
..
..
..
IFC OFC LPBK IBRK OBRK DTR RTS
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
(%), (%%) Added w.e.f software ROM ID version V 4.87

(*): If configuration memory ID is valid
(**): If parameters are configured from Configuration Memory
(#): This message appears if 8 port compatibility with 508V2 is selected. In such case status is displayed only for TP1
through TP8.
(##): This message appears if the unit is configured to interwork with a remote LINKSHARE 516 unit.
(#*): This message appears if, after establishment of link with the remote multiplexer, the remote multiplexer is detected
to be Linkshare 508V2 with version later that 2.xx, or Linkshare 516 or CYGNUS 517.
(&): For explanation of the fields XXX, YYY, ZZZ, AAA, BBB and CC see below.
First the name of the Systems is displayed in 1 to 9 alphanumeric characters. This is the system
name assigned with SET SYS NAME <name> command.
Next status of LAN based Remote Monitoring options is displayed against LAN Mon:. The valid
values diplayed are
No
(Indicates LAN based remote monitoring oiption is not installed)
YES. Sup on LAN (Indicates LAN based monitoring option is installed, and supervisory
function access is being accessed over LAN using Telnet
YES. Sup on TERM (Indicates LAN based monitoring option is installed but supervisory
function of CYGNUS 517 is being accessed by a terminal connected to the SUP port.
Then, the time elapsed since last power up or last CLRTIME command was given.
Then the NVRAM_ID code of the unit is displayed. In case the ID stored in the Configuration
Memory is invalid, the following message is displayed instead of the ID:
NVRAM_ID ERR. ROM ID: CYGNUS LS 517 VX.XX HW_ID:A.B
If the unit is operating in a LINKSHARE 508V2 compatible mode (see sections 3.1 and 3.2), this is
displayed next.
- 3.26 -
The next status displayed is whether the parameters programmed for the unit are taken from the
Configuration Memory ("Stored"), or whether they are the default parameters ("Default"). If default
parameters have been assumed, the reason for this is also indicated. Possible reasons are:
{ NVRAM_ID Error (see section 3.2)
{ NVRAM Chksum Error (see section 3.2)
{ User Request (by "DEFAULT" command - see sec. 3.3.4)
The next status displays whether the automatic link changeover option is mounted and is enabled
or not.
Ch_O:Not mounted
Indicates that the option is not mounted.
On the other hand, the message
Ch_O:Mounted. Sw_Sel:XXX, YYY,ZZZ,AAA,BBB,CCC
Indicates that the changeover option is mounted and is also enabled. In such case, the fields XXX,
YYY, ZZZ, AAA, BBB, and CCC may be displayed as follows (See also Appendix B):
XXX: AUT indicates that the changeover option is configured for automatic link fault detection.
MAN indicates that the changeover option is configured for manual mode.
YYY: MST indicates that the changeover option is configured to operate as master.
SLV indicates that the changeover option is configured to operate as slave.
ZZZ: PRIO indicates that the changeover option is configured to have priority assigned to
primary or secondary channel.
N_PRIO indicates that the changeover option is configured not to have any priority towards
either primary or secondary.
AAA: DAT indicates that the chaneover algorithm uses data analysis and DCD status for
determining whether the links are up or down.
N_DAT indicates that the changeover algorithm uses only DCD status for determining
whether the links are up or down.
BBB: PSEL indicates that the chosen link for data transfer is the primary link. Note that when
changeover option is not mounted, it is the primary link which always carries the data.
SSEL indicates that the chosen link for carrying user data is the secondary link.
CCC: CT_ON indicates that offline changeover option test (CTEST) is selected. Normal operation
is not possible when this test is selected through an on-board jumper.
CT_OF indicates that no test is currently on as far as the changeover option is concerned.
Next the status of certain dynamically changing parameters is displayed for various ports. For the
composite port these are:
{ LPBK (Loop back status) : lcl/rmt/(this is "lcl/rmt" if local/remote loop back is loop back is enabled on the composite port, and "-"
if it is not
{ LINK (link status) : up/dn
(indicates whether link with the remote multiplexers is currently up ("up") or down ("dn")
{ OVRD (address override status) : on/(this is "on" if address override has been selected on the composite port, else it is "-")
{ DSR(P) (Data Set Ready for primary), CTS (Clear to send from the changeover selected
channel), DCD(P) (Data Carrier Detect for primary), TM (Test Mode signal from the
changeover selected channel)
- 3.27 -
(Indicates the status of respective control signal present on the composite port. An "on"
indicates that the signal is active (i.e. +12V). A "-" indicates that either the signal is inactive
(-12V) or not connected).
{ DSR(S) (Data Set Ready for secondary), DCD(S) (Data Carrier Detect for the secondary
channel)
(Applicable when changeover option is mounted, these indications provide the status of
respective control signal present on the composite port. An "on" indicates that the signal is
active (i.e. +12V). A "-" indicates that either the signal is inactive (-12V) or not connected).
{ L_FLT (Line fault): on/Applicable when changeover option is mounted, this indication reports on when the
changeover logic reports any fault condition on the primary or secondary link. It reports -
when there is no fault condition on primary or secondary link.
For terminal ports the parameters displayed are:
{ IFC (Input flow control status) : on/(this is "on" if the multiplexers has currently flow-controlled the device connected to this port,
and "-" if it has not)
{ OFC (Output flow control status) : on/(this is "on" if the device connected on this port has currently flow-controlled the multiplexer,
and "-" if it has not)
{ LPBK (Loop back status) : lcl/rmt/(this is "lcl/rmt" if local/remote loop back is enabled on that terminal port, and "-" if no loop
back is enabled
{ IBRK (input Break status) : on/(is "on" if the multiplexer is currently receiving a break on that terminal port
{ OBRK (output Break status) : on/(is "on" if the multiplexer is currently transmitting a break on that terminal port
{ DTR (Data Terminal Ready), RTS (Request for Sending): on/(Indicates the status of respective control signal present on the terminal port. An "on"
indicates that the signal is active (i.e. +12V). An "-" indicates that either the signal is
inactive (-12V) or is not connected.
- 3.28 -
The status of voice port may be seen with the VPSTATUS command which has the following
syntax:
Syntax: VPSTATUS [RETURN]
In case the voice port is not available or is disabled, the following message is displayed:
Elapsed time in Days:Hr:Min:Sec::dd:hh:mm:ss
Interface: Disabled (Switch 7 set to OPEN)
In case the voice card option is not found to be present, the following message is displayed:
Not installed or not connected.
Table 3.8.2 gives a typical response to the VPSTATUS command if the voice port is enabled
TABLE 3.8.2
Voice Port status display on CYGNUS 517

Interface: FXS
Voice Link State: Conversing
Call Direction: From Remote Mux
Call Type:Voice
Programmed Rate: 6400
Negotiated Rate: 4800
Prev./Present Call Duration (seconds): 155
Prev./Present Call Voice Act Ratio: 20/30
Cum. Dur. From Remote Mux (minutes): 30
Cum. Dur.To Remote Mux (minutes):45
Rcv Overruns: 0
Test Status:: LoopBack : Off Tone:Off
Various fields in the VPSTATUS display are:
{ Elapsed Time: The time since power on or since this the previous CLRTIME command was
given.
{ Interface: The type of port interface selected by the back panel switch. The value could be
one of the following:
"FXS" where the switch selects the interface as "FXS" where the user can
connect a telephone instrument.
"FXO" where the switch selects "FXO" interface so that a PABX extension can be
connected to the voice port.
{ Voice Link State: This indicates the current state of the voice interface. It can have the
following values
w "Idle" indicating that there is no activity on the voice port.
w "Alerting" indicating that the multiplexer has received a request from the telephone
interface (FXS or FXO) and it is alerting the remote multiplexer to establish the
voice link.
w "Conversing" indicating that a voice link is established between the voice port of the
multiplexers and the user is able to converse over it.
w "Ringing" indicating that the remote side voice port want to establish the link as a
result of which the local FXS port is generating the ring on the telephone line.
w "RingDetectConfirming" indicating that the local FXO port has just detected a
ringing signal from the telephone line.
- 3.29 -
w "Parking" indicating that the local FXS port has found that the user has gone
off-hook but no voice link is or could be established. In this state the multiplexer
awaits for the user to go on-hook.
{ Call Direction: This indicates the direction of the present call, and is displayed only if voice link
state is in "Conversing" state. It can have the following values
w "From Remote Mux" indicating that the present call has originated from the voice
port of the remote multiplexer.
w "To Remote Mux" indicating that the present call has originated from the voice port
of the local multiplexer.
{ Call Type: This field is displayed only if the voice link is in conversing state. It shows one of
two possible call types.
w "FAX" indicates that the present user is carrying out a fax transaction.
w "Voice" indicates that the present user of the voice link is carrying out voice
conversation.
{ Programmed Rate: This field indicates one of the four rates (4800, 6400, 8000, 10400) as a
stored parameter for the voice port. The multiplexer will try to use this rate while establishing
the voice link.
{ Negotiated Rate: This field the actual rate being used for voice link. This rate may be equal to
or less than the programmed rate as indicated above because since the programmed rate
could be different for the two multiplexers, the link is established using the minimum of the
two. The minimum rate is negotiated during voice link establishment.
{ Prev./Present Call Duration: This field indicates the duration, in seconds, of the present voice
link session. If presently the voice link is inactive, the indicated figure pertains to the previous
voice link session.
{ Prev./Present Call Voice Act. ratio: This field indicates the ratio of voice frames with voice
activity to the total voice frames generated during the present call. If presently the voice link
is inactive, the indicated figure pertains to the previous voice link session. Every time the
VPSTATUS command is given, the ratio of cumulative number of voice frames is displayed.
However, the ratio is not updated after the denominator reaches 255 which is reached
approximately after 30 minutes of a voice link call duration.
{ Cum. Dur. From Remote Mux: This indicates, in minutes, the sum of duration of all the voice
calls which were received from the remote multiplexer since power-up. This value can be
reset to zero by giving a "CLRSTAT VP" command.
{ Cum. Dur. To Remote Mux: This indicates, in minutes, the sum of duration of all the voice
calls which were made towards the remote multiplexer since power-up. This value can be
reset to zero by giving a "CLRSTAT VP" command.
{ Overrun Errors: This indicates the number of occurrences when the multiplexer was unable
to send voice packets to the remote multiplexer due to insufficient bandwidth of the composite
port link. If the voice quality is bad, a probable reason is that too many overrun errors are
taking place. In such case either a link of higher speed should be used, or the voice encoding
rate should be reduced.
{ Test Status: This indicates the status of loop back test and the tone generation test. For the
loop back test status field, as selected by the Set Loop back command. The possible values
are:
- 3.30 -
w "Off" meaning that no loop back test is in force.

w "Analog" indicating that analog loop back is in force.
w "PCM" indicating that PCM loop back is in force.
w "Coder" indicating that coder loop back is in force.
In the Tone field, the multiplexer displays whether any test tone is being generated by the
multiplexer as a result of Set Tone command. following are the possible values:
w "Off" indicating that no tone test is in progress.
w "TestTone" indicating that a continuous 1 KHz tone is being injected at the coder
input.
w "ErrorTone" indicating that error tone is being generated and sent on the telephone
line by the multiplexer.
w "Ring Back" indicates that ringback tone is being generated and is being sent on
the telephone line
3.3.9 Connect facility

It is possible to establish a connection between the supervisory port and any terminal port. This is a
diagnostic facility useful when debugging terminal port problems.
Syntax: CONNECT <PORT> [RETURN]
Valid values for <PORT> are TP1 through TP8 (16). Once connection is established, the message
Connected
is displayed on the supervisory terminal, followed by the Prompt and
CON <n>:
where <n> is the number of the connected terminal port. On the screen of the terminal to which the
Connection is made the message
Connected to local SUP
or
Connected to remote SUP
will appear depending on whether the CONNECT command is given in LOCAL or REMOTE mode
(see Sec. 3.3.11 below). The "TEST" indicator on the front panel starts blinking when this
command is given, and will stay blinking till the connection is disconnected.
Once the connection is established, whatever is typed on the supervisory terminal appears at the
terminal port, and vice-versa. The connection may be broken by typing the "disconnect character"
from either of the two connected terminals (See DISCCHAR under Sec. 3.3.1 above). The ECHO
status on the terminal port resumes the value that was effective prior to the CONNECT command.
In addition to its utility as a diagnostic aid, the "CONNECT" command can also be used to be set up
a centralized supervisory console for a number of CYGNUS multiplexers. See Appendix E for
details.
3.3.10 Identification of software and hardware version

A unique product identification code is stored in the non-volatile Configuration Memory. This code is
viewed with the ID command on the supervisory port.
- 3.31 -
Syntax: ID [RETURN]
The response from the supervisor is
NVRAM_ID: CYGNUS LS 517 VY.YY ROM ID:CYGNUS LS 517 VY.XX HW_ID:VZ.Z
where X.XX is the software version number. Y.YY, if different than X.XX indicates that the software
version is different than the operating version when the last "STORE" command was given. No
harm will be caused due to this difference. Note that the "STORE" command updates the NVRAM
ID to the ROM ID.
In case the ID stored in the Configuration Memory is invalid, the following message is displayed:
NV_RAM ID ERR. ROM ID: CYGNUS LS 517 VX.XX HW_ID VZ.Z
The expected ID here is the one that should have been read from the Configuration Memory if its
contents were valid. One reason for the NVRAM_ID to be declared invalid is that the first or the
second digit of the version does not match with that of the ROM_ID.
The Hardware ID is the ID of the PCB and associated logic.
When reporting any problem, it is advised that the NV_RAM ID, ROM_ID and HW_ID are informed.
3.3.11 Remote and Local operation

CYGNUS 517 multiplexers provide the ability to control the unit at the other end of the link from the
supervisory terminal connected to the local unit. This facility is particularly useful when the remote
site is unmanned, or there are no trained personnel available at the remote site to configure the
multiplexer.
The "REMOTE" command may be used to connect to the supervisory function of the remote unit.
Syntax: REMOTE [RETURN]
In response the message
Wait..
is displayed. At this time the supervisory port is connecting to the remote unit. After connecting to
the remote unit the Prompt changes from
L> to
R>
In REMOTE mode, any commands entered from the Supervisory terminal are actually processed by
the remote multiplexer. All supervisory port commands discussed in this chapter are available to
control and monitor the remote unit. On the remote unit the "REMOTE" indicator will glow during
this time to indicate that a remote control link has been established.
NOTE
The supervisory port on the remote unit is disabled as long as it is being controlled
REMOTEly. There will not be any response to commands typed in on the unit's supervisory terminal during this time.
In case the supervisory terminal is already logged on to the remote unit, the message displayed is
- 3.32 -
ERR: ALREADY RMT

If the composite link to the remote unit is down the message displayed in response to a "REMOTE"
command is:
ERR: LNK NOT ESTD
and the supervisory port remains logged on to the local unit.
In order to switch back to the local unit, the "LOCAL" command may be used.
Syntax: LOCAL [RETURN]
In response, the supervisory terminal will log itself back onto the local unit and display the message
In local mode
and the Prompt reverts to
L>
Once this switch over is accomplished, the "REMOTE" indicator on the remote unit stops glowing.
If the "LOCAL" command is given when the supervisory terminal is already logged on to the local
unit, the message
ERR: ALREADY LCL
is displayed.
3.3.12 Error statistics

CYGNUS 517 multiplexers provide extensive reporting of error statistics. To view the error statistics
for any line, the "ERRSTAT" command may be used.
The response to error statistics commands is always preceded by the display of time elapsed since
the powering up of the unit or the time elapsed since the last CLRTIME command was given.
Syntax: ERRSTAT <PORT> [RETURN]
When this command is issued for a TP, the display is as follows:
F:xxx P:xxx O:xxx B:xxx
Here "xxx" is the count of errors of that type. The count following "F" refers to framing errors
detected on that particular TP. "P" refers to the number of parity errors, "O" to the number of
overrun errors (the number of characters that the terminal port communication chip could not
receive because it was overrun with following characters), and "B" to the number of characters that
were received but could not be accommodated in the input buffer. This last count will be non-zero
only if flow-control between the multiplexer and the connected terminal device is not functioning
properly.
For the composite port the displayed statistics are:
- 3.33 -
C:xxx R:xxx O:xxx U:xxx DC:xxx

"C" refers to the number of frames received on the Composite port with CRC errors. "R" refers to
the total number of retransmissions that occurred because transmitted frames were lost and hence
not acknowledged by the remote unit. "O" refers to the number of times that the composite port was
overrun by received characters, and "U" refers to the number of times the composite port underran
while transmitting. High values of "C" and "R" counts normally indicate a poor quality link between
the two multiplexers. "DC" refers to the number of times the composite port link went down since
power on or since the last time "CLRERR CP" command was given, whichever is later.
Error statistics on any port may be reset to zero using the "CLRERR" command.
Syntax: CLRERR <PORT> <RETURN>
Valid value for <PORT> are TP1 through TP8 (TP16 for CYGNUS 517) and CP. All relevant error
counts for the channel are reset to zero by this command.
NOTE
The maximum count for any of the errors listed above (for TPs and the CP) is 255. Any
errors occurring after a count reaches 255 leave the count unchanged.
3.3.13 Utilisation statistics

CYGNUS 517 multiplexers also provide extensive reporting of line and buffer utilisation statistics.
Commands are provided to view Transmit and Receive counts for all ports (TPs and CP) and
Transmit and Receive buffer utilisation for TPs. Current, Average and Peak values are displayed for
all these statistics.
The response to utilisation statistics commands is always preceded by the display of time elapsed
since the powering up of the unit or the time elapsed since the last CLRTIME command was given.
To see Transmit and Receive counts the following commands may be used.
Syntax: TXCOUNT <PORT> [RETURN]
or
TC <PORT> [RETURN]
and
or
RXCOUNT <PORT> [RETURN]

RC <PORT> [RETURN]
The display is
Cur:xxx Av:xxx Pk:xxx
The count following "Cur" is the current value of the count; that following "Pk" is the peak value and
that following "Av" is the average value, calculated as described below.
The multiplexer samples these counts every sixteen seconds. The "Cur" value is the last sampled
value. "Pk" is the maximum of such sampled values. "Av" is a weighted average of the sampled
values computed as follows: If the old average is OldVal, and the latest sampled value is NewVal,
then "Av" is given by the formula
Av = (15*OldVal + NewVal)/16
- 3.34 -
CYGNUS 517 multiplexers also provide commands using which it is possible to find out the usage
of Transmit and Receive buffers on TPs.
Syntax: TXBUFUTIL <PORT> [RETURN]
or
TBU <PORT> [RETURN]
and
or
RXBUFUTIL <PORT> [RETURN]

RBU <PORT> [RETURN]
Valid values for <PORT> are TP1 through TP16.

In response the "Cur", "Pk" and "Av" values are displayed as above.
A command is also provided to reset the "Pk" value for any (or all) channel to zero.
Syntax: CLRPK <PORT> [RETURN]
or
CLRPK [RETURN]
If no port number is specified, the peak values of all counts on all channels will be reset to zero. If a
port is specified, then the peak values for only that port are cleared. Valid port values are TP1
through TP8 (TP16 for CYGNUS 517) and CP. After clearing the required counts the message
Done
is displayed on the supervisory terminal.
3.3.14 Clearing voice port statistics

The voice port utilisation and error statistics such as Cumulative call duration, and overrun error
count may be reset to zero with this command.
Syntax: CLRSTAT VP [RETURN]
After clearing the required counts the message
Done
is displayed on the supervisory terminal.
3.3.15 LED and DIP switch test

The front-panel LEDs (Light-Emitting-Diodes) on the unit can be tested by giving the command
Syntax: LEDTEST [RETURN]
First all LEDs except the POWER LED are made off, then all LEDs are made on, and again they
are made off sequentially. After this the normal operation of the LEDs resumes. Note that the
operation of the multiplexer is not affected when the LED test is conducted. The "FXS" and "FXO"
LED may be tested by operating the FXO/FXS switch on the multiplexer. When the LED test is on
the buzzer is also made to sound.
The setting of SW3 DIP switch at the base of the unit setting can be read by giving the command
Syntax: SWITCHTEST [RETURN]
- 3.35 -
The switch is read, and its value is displayed in hexadecimal format. Switch 8 is the Most Significant
Bit (MSB) in the displayed value, and Switch 1 is the Least Significant Bit (LSB). The message
displayed is:
Switch value (hex): <XX>
where <XX> is the read switch value, displayed in hexadecimal format.
3.3.16 Watchdog test

The CYGNUS 517 multiplexer has built in watchdog timer which automatically resets the multiplexer
if its software goes haywire due to any reason. The watchdog function may be tested by giving the
watchdog test.
Syntax: WDTEST [RETURN]
The multiplexer gives the message
Wait for 10 secs
and resumes its function after initiating the watchdog test. If the watchdog test is successful, the
"MUXERR" LED lights up, and the multiplexer resets itself in about 10 seconds of giving the
watchdog command. The "MUXERR" LED remains on and may be made off only by powering off
and on the multiplexer. However, after resetting the multiplexer all the operations are resumed
automatically.
3.3.17 Clearing the time

The system maintains the time elapsed since powering up or resetting of the unit. The time is
maintained in terms of days, hours, minutes and seconds elapsed. The current time elapsed can be
displayed by giving the status display or statistics display commands. The current time can be
reset to zero by giving the "CLRTIME" command. This command has the following syntax:
Syntax: CLRTIME [RETURN]
The maximum time which can be displayed is 255 days, 23 hours, 59 minutes and 59 seconds after
which the time is reset to zero again.
3.3.18 Loading terminal ports with test data

The CYGNUS 517 provides a command to generate test data on all its terminal ports. This
command has the following syntax:
Syntax: TPTEST [RETURN]
NOTE
This is a diagnostic command and should not be given when the multiplexer is in online
operation.
When this command is given the multiplexer sends a string of printable ASCII data characters on all
its terminal ports. This command can be used to test a pair of multiplexers as shown in Fig. 3.3
below.
- 3.36 -
Loopback connectors on terminal ports
Multiplexed data stream
CYGNUS 517
Loopback connectors on terminal ports
CYGNUS 517
Data path
TPTEST
Fig. 3.3 Data path - TPTEST command with loopbacks on TPs
Connect two CYGNUS 517 units to each other and activate loopbacks on their terminal ports (either
by local loopback supervisory command or by inserting loopback connectors on the ports - see
Appendix C for loopback connector details). When the two units are linked up give the TPTEST
command on one of them. This will lead to test data being sent on the terminal ports of this unit.
Because of loopbacks on its TPs the data will come back to the unit, be multiplexed by it and sent
to the remote unit. The remote unit will demultiplex the data and send it to its TPs . Because of the
loopbacks there the data will again be received by unit B on its TPs, be multiplexed, and sent back
to unit A. The cycle repeats and data is thus trapped into circulation.
This test can be used to test the end-to-end path, or to exercise the two multiplexer units.
- 3.37 -
4
INSTALLATION AND TROUBLESHOOTING
The acceptance, installation and troubleshooting procedures for CYGNUS 517 multiplexers are
described in the flowchart given in this chapter. The following steps should be followed when installing a unit:
{ Check for any damage to the unit. DO NOT PROCEED IF THE UNIT IS DAMAGED.
{ Select a suitable place or 19 equipment rack for installing the unit (See Chapter 2).
{ Check that the unit powers on properly. (The rating of the fuse is 1 Amp/230V (slow blow - 20
mm). A spare fuse is provided in the fuse holder assembly. For continued protection the fuse
should always be replaced with one of the same rating.
{ Set the DIP switch to the required value and check that the Supervisory port functions
normally (see Sec 3.1 for details).
{ In case voice port is provided, select the FXO/FXS switch for desired operation.
{ In case you desire the supervisory port to have the parameters such as speed, parity, and
data bits different than those given in Table 3.1, perform the following in the given order:
1. ON SW 3 DIP switch at the bottom of the unit, set switch 1 to CLOSE and power on the
unit. The supervisory port now assumes the default parameters as per Table 3.1.
2. Connect a terminal with the same parameter to the supervisory port.
3. Program the supervisory port to the desired parameters and store the parameters by
giving "store" command
4. Set the switch to OPEN
5. Power off and on the unit.
6. The supervisory port now assumes the newly programmed parameters.
{ Now program the operating parameters for all terminal ports, the composite port, voice port
(if present) and the System as desired, store this operating configuration and reset the unit
(see Secs. 3.3.1, 3.3.5 and 3.3.6). If voice port is present, the composite port should operate
at a speed of 9600 bps or more.
{ Connect appropriate modem depending on the type of composite port interface provided. In
case you have ordered both the RS232 as well as the V.35 interface, select the active
composite port interface properly. Test multiplexer operation in loop back mode, by looping
back the composite port from the modem locally and checking whether link is established
(see Sec. 3.3.1 for a description of the "address override" mode required for loop back
testing on the composite port).
{ Once the composite port link is established check the operation of all terminal ports
For Data Ports test by connecting a terminal to each port in turn and typing a few characters
- you should get back the echoed characters on the terminal's screen.
- 4.1 -
Installation and Troubleshooting
For CYGNUS 517 with Voice Port test the voice port as follows:
In case voice port is selected for FXS operation, connect a telephone instrument to the FXS
connector at the back panel. Lift the receiver from the telephone and speak into the receiver.
You should hear an echo of your voice.
In case voice port is selected for FXO operation, connect a PABX extension cable to the FXO
connector. From any other extension, dial into the extension number of the extension cable
connected to the FXO port. After hearing ringback tone, the multiplexer will go off-hook. Now
whatever is spoken into the receiver should be echoed back.
Repeat the above steps for the second unit, which is to be installed at the other end of the
link.
{ Connect the two units to the communication line via modems/ line drivers. Make sure that the
unit address is different on both the units to be interconnected. Once the link is established,
the system is ready for use (see Sec. 3.3.1 for information on encoding and clock source
selection on the composite port).
The flowchart in this chapter describes the installation procedure in detail. It also suggests the path
to be adopted in case problems are encountered at any of the steps above. Note that this flowchart
does not include testing of the changeover facility. Testing of the changeover facility is described in
Sec. B.3, Appendix B.
Even after successful installation of the multiplexers there could be operational problems at a later
date. Usually these problems are to do with malfunctioning of some of the terminal ports in the unit.
Such malfunctions are most often caused by excessively high voltages coming in from the
connected terminal, or by the lack of a common Earth between the multiplexer and the attached
terminal. To minimise such malfunctions it is important that the Earth for all the terminals and the
multiplexer be common.
The CYGNUS 517 multiplexer performs a self-test at power on. Appendix C gives details about this
self-test. Any faults detected during this test are indicated by displaying specific patterns on the
front-panel LEDs. Additionally, these multiplexers provide several commands which aid in on-line
diagnosis of operational faults on the terminal ports. These include the following commands:
{ LOOP BACK commands to loop back a terminal or voice port

{ CONNECT command to connect the supervisory terminal to any terminal port
{ STATUS command to show the status of various ports (including the status of the control
signals on the interface connectors)
{ ERRSTAT command to show error statistics on various ports
{ TONE command for setting various tone on the voice port.
All these commands can be given when the unit is in operation, and they affect only the port on
which the diagnostic is being run - other ports continue to work normally.
The CYGNUS 517 multiplexers also provide more comprehensive off-line error diagnostics, which
can be invoked from the DIP switch on the bottom of the unit. Details of these off-line diagnostics
are given in Appendix C.
- 4.2 -
CYGNUS 517 STATISTICAL MULTIPLEXER

Acceptance and installation procedure
START
Any
visible damage to
the unit?
YES
UNIT NEEDS
SERVICING
NO
Connect AC power cord to mains
(230VAC) and power up by
operating ON/OFF switch
POWER LED on?
NO
A
YES
MXERR LED off?
NO
YES
Switch off power
Connect terminal to supervisory port.

Power on the terminal.
Keep switch 1 on DIP switch SW3 in
CLOSE position. Select 4800 bps, 8 bit,
no parity on terminal
Power-on the unit. Wait for 10 seconds
Continued on Sheet 2
- 4.3 -
SHEET 1
Continued from Sheet 1
Press <CR> on supervisory terminal
Prompt appears
on supervisory
terminal?
NO
YES
Sup parameters
required to be
different?
YES
Program sup parameters as required, store

them and power off unit. Keep switch 1 on
DIP switch SW3 in OPEN position
NO
Configure terminal port parameters
(see Users Manual)
Configure composite port parameters

(see Users Manual)
Configure voice port parameters

if voice port is available
(see Users Manual)
Store parameters and power unit off

and on (see Users Manual)
"Stored
parameters pgmd" appears
on sup terminal?
NO
UNIT NEEDS
SERVICING
YES
If voice port is available select "FXS"

interface through selection switch
on voice module and connect telephone
instrument to FXS connector
Connect line driver/modem to composite
port with supplied cable and power up
Select "address override" mode by giving

command from sup port (see Users Manual)
Give loopback to CP through
line driver/modem (**)
SHEET 2
**: If changeover option is installed carry out the following

procedure on both link interfaces
- 4.4 -
NO
"LINK" LED on?
YES
Connect terminal to each port.
Type a few characters
NO
Characters echoed?
Ensure FXS/FXO switch is in FXS position

Connect telephone instrument to FXS port.
Keep telephone in on-hook position.
Connect terminal to Sup and give
"SET VP RING ON" command
YES
Voice Port
Available?
NO
Telephone
is ringing?
YES
YES
Lift telephone handset
NO
NO
'VLINK' LED
"ON"?
YES
Multiplexer OK.
Speak into the telephone

ACCEPTANCE TEST COMPLETED
ECHO
being heard?
INSTALLATION PROCEDURE STARTS
NO
Unit
needs
servicing
YES
Make sure that communication line is working

and modems/line drivers are installed
Remove telephone from FXS

port. Select FXO interface on
FXS/FXO switch. Connect
PABX extension to FXO
connector. Dial the PABX
extension number from
any other extension of PABX.
Select appropriate encoding mode, speed and

clock source for CP on both side multiplexers
(see Users Manual)
Select CP address of one side as "A" and

other as "B"
'VLINK' LED
"ON"?
YES
NO
Speak into the telephone
ECHO
being heard?
NO
YES
SHEET 3
- 4.5 -
Set terminal port parameters on both units
Connect muxes to modems/line drivers

with supplied cable (**)
I
Reset both units and wait for ten seconds
YES
"LINK" LED on?
Voice
Port
Available?
YES
NO
INSTALLATION
OVER
NO
M
Sheet 12
"TX" LED flashing?

NO
YES
G
NO
"RX" LED flashing?
POOR SIGNAL QUALITY ON

LINE. RECTIFY IT.
YES
YES
"ADERR" LED flashing?
NO
"LNERR" LED
flashing often?
YES
NO
Change address of local mux

(see Users Manual)
MUX NEEDS SERVICING
EITHER THE REMOTE MODEM OR

THE LINE IS IN LOOPBACK
"ADERR" LED flashing?

YES
NO
**: If changeover option is installed carry out the following

procedure on both link interfaces
SHEET 4
- 4.6 -
Switch off AC power. Remove power cord.

Remove fuse housing with a flat screw
driver and check fuse continuity
Fuse OK?
YES
NO
Replace with 1A/250V 20 mm slow-blow
fuse (spare fuse is provided). Replace
spare fuse at the earliest
Connect power cord and switch on power
NO
"PWR" LED on?
MUX NEEDS SERVICING
YES
CONTINUE
SHEET 5
- 4.7 -
Switch 8 on
DIP switch SW3
is OPEN?
YES
NO
Set switch 8 on DIP switch SW3 to OPEN
Reset the unit
"MXERR" LED stays off?
NO
UNIT NEEDS SERVICING
YES
CONTINUE
SHEET 6
- 4.8 -
Check if communication parameters of the

terminal match with the sup. port parameters
NO
Parameters match?
Select matching terminal

parameters and type
YES
NO
Characters echoed?
Change terminal cable and type

YES
YES
Characters echoed?
NO
Change terminal. Set terminal communication

parameters and type
NO
Characters echoed?
YES
UNIT NEEDS
SERVICING
CONTINUE
SHEET 7
- 4.9 -
D
Select Address
Override mode
NO
"TEST" LED on?
YES
"TEST" LED on?
YES
NO
NO
"TX" LED flashing?

"TX" LED on?
YES
NO
YES
NO
YES
UNIT NEEDS
SERVICING
YES
CP set for
internal clk?
YES
"RX" LED flashing?

NO
Replace modem cable
"LINK" LED on?

NO
Replace modem/line driver.

Give loopback.
YES
"LINK" LED on?
NO
UNIT NEEDS
SERVICING
CONTINUE
SHEET 8
- 4.10 -
Check if communication parameters of the

terminal match with terminal port parameters
NO
Parameters match?
Select matching terminal

parameters and type
YES
NO
Characters echoed?
Change terminal cable and type

YES
YES
Characters echoed?
NO
Change terminal. Select matching
parameters and type
NO
Characters echoed?
UNIT NEEDS
SERVICING
YES
Installation over
SHEET 9
- 4.11 -
"TX" LED
continuously on?
YES
Mux not getting transmit clock.

Check composite port configuration
NO
YES
MUX NEEDS
SERVICING
Configuration OK?
NO
Rectify configuration
"RX" LED off?
YES
NO
EITHER THE REMOTE MODEM OR MUX
(OR BOTH) ARE POWERED OFF, OR
THE RECEIVE CIRCUIT IS BAD
UNIT NEEDS
SERVICING
SHEET 10
- 4.12 -
Verify that FXS/FXO

switch is in FXS
position and telephone
is connected to
FXS connector
YES
Switch O.K.?
Verify that backpanel

+24 and -24 V LEDs
are on
NO
Set switch to FXS
position and repeat
LEDs are on?

L
NO
+/- 24 V supply bad.

Unit needs servicing
YES
Verify that the
PABX port is OK
by connecting a
telephone and
conversing with it
Unit needs
servicing
NO
Verify that FXS/FXO

switch is in FXO
position and PABX port
is connected to
FXO connector
Restore PABX
connection and retry
PABX
port OK?
YES
Yes
Switch O.K.?
Verify that the

PABX port
is O.K with a
telephone
No
Set switch to FXO
position and repeat
PABX
port OK?
NO
Restore PABX
connection and retry
YES
- 4.13 -
SHEET 11
M
Select FXO or FXS interface
for each multiplexer
by operating
FXS/FXO switch
Connect a telephone
instrument to FXS port
if FXS interface is selected
Connect a PABX extension

port to the FXO port
if FXO interface is selected
Lift handset from the

telephone instrument
Other
end interface?
FXS
FXO
PABX
Dial tone heard?
NO
Ringback
tone heard?
NO
YES
YES
Dial any valid PABX

extension number,
wait for other side to
answer and converse
Wait till phone is lifted on

other side and converse.
Conversation
OK?
NO Local or remote
mux requires
servicing
NO
YES
YES
Break call by going on-hook. Ask
remote end personnel to go
off-hook while local phone is
on-hook
Local
telephone
ringing?
YES
NO
Local unit needs
servicing
Conversation
OK?
Break call by going on-hook. Ask

any PABX user to dial the extension
number of PABX line connected
to the voice port of remote mux
Lift handset and

converse
Conversation
OK?
YES
Installation done
successfully
- 4.14 -
YES
NO
Phone ringing?
NO
Local unit needs
servicing
SHEET 12
5
CYGNUS 517 OPERATION
This chapter discusses operational details of CYGNUS 517 multiplexers.
5.1 TERMINAL PORT OPERATION

The multiplexer terminal port operation can be described as follows:
{ External devices such as terminals or computers connected to the terminal ports generate
asynchronous character data and send it to the statistical multiplexer.
{ The multiplexer receives these characters and stores them in a dedicated input buffer permanently allocated for the respective terminal ports, (if space is available in the buffer). If the
total number of characters in the input buffer crosses a limit (called High Water Mark or
HWM), the multiplexer activates input flow control as explained in Chapter 3. If no space is
available in the input buffer, the received characters are discarded by the multiplexer.
{ A software function called the Assembler continuously monitors the input buffers of the terminal ports. It removes characters from the input buffers and puts them (with the TP identification) in dynamically allocated buffers called packets. These packets are then transmitted over
the composite link to the multiplexer at the other end. While removing characters from an
input buffer, the Assembler checks if the terminal port is flow controlled. If it is, then the flow
control is deactivated as soon as the character count in the input buffer falls below a level
called the Low Water Mark (LWM).
{ Just as the multiplexer sends packets on the composite link, it also receives packets sent by
the multiplexer at the other end of the composite link. These received packets contain characters with the identification of the terminal port to which they are to be output. A program called
the Disassembler distributes the characters in the received packets to another set of permanently allocated buffers called the output buffers. Each terminal port has its own output buffer.
{ Characters are picked up from the output buffers and sent to the respective terminal ports if
the output is not flow controlled by the external device.
5.2 COMPOSITE PORT OPERATION

The composite port operates in terms of packets. A full-duplex protocol allows simultaneous transmission of packets between the two multiplexers ensuring high link capacity utilization. Each packet
contains a checksum of its contents. This checksum is calculated as per a standard procedure
called CRC-CCITT. The checksum is appended to the packet by the sending multiplexer. The
receiving multiplexer also calculates the checksum of the data that it receives and matches it with
the checksum appended to the incoming packet. If the two checksums match it means that the
received packet is free from any transmission errors introduced on the composite link. Only such
packets are accepted and processed. Erroneous packets are discarded and a reject packet is sent
so that the sending multiplexer retransmits the same packet.
Before operations on the composite link can start, the link has to be set up. This is done whenever
either of the two multiplexers is powered-on or reset.
NOTE
The link changeover function of the CYGNUS 517 is described in Appendix B.
- 5.1 -
CYGNUS 517 Operation
An audible alarm is provided, which is activated on certain alarm conditions, including failure of any
of the composite links. Operation of this alarm is described in Sec. B.6, Appendix B.
5.3 VOICE PORT OPERATION

The voice port is selected to operate with either "FXS" interface or "FXO" interface. Separate
connectors are provided for the two interfaces. Only the connector for the selected interface should
be used. The multiplexer should be reset or powered off/on if the front panel FXO/FXS switch is
changed.
Both multiplexers can be selected to work with "FXS" interface, in which case they are connected to
devices such as a telephone instrument or a FAX machine.
Alternatively, one of the multiplexers may be selected to work with "FXS" interface and devices
such as telephone instrument or a fax machine may be connected to it. The other side multiplexer
may be chosen to operate with "FXO" interface in which case it may be connected to a PABX
extension.
Before using the voice port for communication a voice link is required to be established between the
voice ports of the two multiplexers connected to each other. The voice link can be established from
the voice port of any of the multiplexers, but only when the composite port link is established
between the two multiplexers. If the operational interface is "FXS", the multiplexer initiates the
process of establishing the voice link if the device connected to the port (referred to as calling end)
goes "off-hook". If the calling end interface is "FXO", the multiplexer initiates the link establishment
process as soon as it detects ringing on the telephone line. In either case, the multiplexer sends a
"call-request" packet to the other end (referred to as called end) multiplexer informing it that its
voice port desires to establish the voice link with that of the remote multiplexer. In case the composite port link between the multiplexer is not up the "FXO" interface just ignores the ring whereas the
"FXS" interface generates an "errortone".
Once the called end multiplexer receives the request, it takes action depending on the type of its
voice interface.
If this interface is "FXS", the called end multiplexer starts ringing on the line if the connected device
is "on-hook". If the connected devices is "off-hook", no action is taken. If the called interface is
"FXO", then the called end itself goes "off-hook" immediately, and sends an indication to the calling
end that the voice link between the two multiplexers is established.
if the called interface is "FXS", once the called end starts ringing, a "ringback tone" is sent by the
called end multiplexer to the calling end voice port. Reception of this ringback tone by the calling
device indicates that link establishment has been initiated and the called side device is being
alerted. The ringing on the called end and generation of ringback tone continues till either the called
end device answers the call by going "off-hook" or the calling side indicates that it no longer wants
to establish the voice link. The calling side can indicate its desire not to pursue with the establish
request by either going "on-hook" (for FXS interface) or when the incoming ring stops (for FXO
interface). Once the called device connected on the "FXS" port goes "off-hook", the voice link is
established.
As soon as voice link is established, voice (or fax) communication between the called and calling
end can take place. Each side receives the voice signals, converts them into digital form and
encodes them so that they can be sent to the remote multiplexer at a rate lower than the rate at
which they are digitized. In case the signals are facsimile signals, the encoding algorithm recognizes this and forwards the signals to the other end without encoding. During a voice call, the
encoder also monitors whether the voice signal is low indicating absence of voice activity, i.e.
detection of silence. The multiplexer does not send the encoded voice signal if no voice activity is
detected.
- 5.2 -
Once the voice link is no longer required, it can be deactivated by any end which has an "FXS"
interface by going "on-hook". After the disconnecting side goes "on-hook", an indication is sent to
the other side. If the other side has "FXS" interface, it generates the "errortone", indicating that the
disconnecting side has initiated disconnection. If the remote side has "FXO" interface, then the
remote multiplexer itself goes "on-hook", thereby indicating to the connected device such as a
PABX that a disconnection has occurred.
During a voice-link session if the composite port link goes down, the multiplexers initiates disconnection procedure and takes action depending on the type of interface selected. If the interface is
"FXS", the multiplexer indicates disconnection by generating an error tone to the connected device
whereas if the interface is "FXO", multiplexer itself goes "on-hook" indicating that the voice link has
been disconnected.
5.4 FRONT PANEL INDICATORS

Fig. 5.1 shows the several indicators on the CYGNUS 517 front-panel. These indicators display the
operational status of the unit.
64 kb G.703 Module
2 Mb G.703 Module
TST
ALARM
TXD
FF
TO
PA
LINK
TXD
ERR
ERR
IFOK
L
LC
E1 INE
L
E1
IFOK
SEC
PWR
TX
RX
TP1
TP2
TP3
TP9 TP10
TP11
TP4
TP5
TP6
TP7
TP12
TP13
TP14
TP15
SECONDARY
PRIMARY
TP8
DCD
FLAG PRI-SEL
DCD
FLAG SEC-SEL
CHANGEOVER
AUTO
MST CTEST
FXS/FXO
BUZZ
LINK LNERR ADERR
DIAG2
V2
V516
MXERR ENBL
PRIMARY
TP16
CLK-INV
V.35
SECONDARY
V.24
CLK-INV V.35
V.24
MAN
SLV DMODE
PRI
PRI
DI
VAD
INT
J
R IN
ER LL
E
DT
DL
VLINK
DIAG1
INT
LL
FXO
RXD
RXD
SYNC
CYGNUS 517
FXS
PWR
PWR
AIS
T
PA
Voice Module
T//DFLT
R
CL
FF DL
E
DT
DIAG3
SEC
DI
CYGNUS 517
DIAG4
CYGNUS 517
CYGNUS 517
DIS-BUZZ
Front panels for

various composite
link interfaces
(as installed)
SEC-SEL
Main front panel:

Indicators related to unit and link status
and to port activity
MANUAL
SLVT
Changeover front panel

(if installed)
Voice front panel

(if installed)
Fig. 5.1 Front panel indicators and switches
Indicators related to the various optional built-in telecom link interfaces are described in Appendices
I to K.
Indicators related to the optional voice interface are described in Appendix H.
Indicators related to the optional changeover facility are described in Appendix B.
The basic indicators related to the unit and link status and port activity are on the main front panel.
These are described below:
"PWR" Indicator
This indicator glows whenever the unit is powered-on.
- 5.3 -
"LINK" Indicator
This indicator gives information about the status of the composite port. Continuous glowing of this
indicator indicates that communication on the composite port is established with the remote unit. If
this indicator does not glow, it indicates that the communication is not established. Flashing of this
indicator points to mismatch between the TXLINE and RXLINE parameters on the two units (see
Sec. 3.3.1). In case this indicators blinks at a constant rate, it indicates line problem with one
communication (either Tx or Rx) between the to multiplexer not working properly.
"TX" Indicator
This indicator glows whenever packet transmission on the composite port is in progress.
"RX" Indicator
This indicator glows whenever packet reception is in progress on the composite port.
NOTE
Even when there is no user traffic the "TX" and "RX" indicators will flash every 10 seconds
This is because the multiplexers keep checking the link between them even during idle
line conditions.
The "LINK" indicator will stop glowing if the link is found to be down.
"LNERR" Indicator
This indicator flashes whenever:
{ retransmission of a packet is initiated by the multiplexer. A retransmission is initiated if a
transmitted packet is not acknowledged by the remote multiplexer (see Sec. 5.1).
{ a CRC mismatch is detected for a packet received from the remote unit.
Frequent glowing of this indicator denotes error-prone transmit and/or receive paths.
"ADERR" Indicator
This indicator glows steadily if the "address override" mode is selected on the composite port (see
sec. 3.3.1). In this mode loop back testing can be carried out on the composite port.
The indicator flashes if both the multiplexers have identical composite port addresses (see sec.
3.3.1). The multiplexers will not be able to establish a link among themselves in this case. See
Section 3.3.1 for information on how to change the address of one of the multiplexers.
"MXERR" Indicator
This indicator glows whenever the integral watchdog timer detects a malfunction in the unit (see
Sec. 3.1).
"RMT" Indicator
If the "REMOTE" command is given from a supervisory terminal connected to the unit in order to
log on to the remote unit's supervisory function (see discussion on REMOTE operation in Section
3.3.11), the RMT indicator on the remote unit will light up if the link is up. When the supervisory
terminal reverts to LOCAL this indicator will go off on the remote unit. As long as this indicator is lit
on a unit it is not possible to access its supervisory function from a locally connected supervisory
terminal.
"V2" Indicator
This indicator is lit to indicate that the unit is operating in a mode compatible with the CYGNUS
508V2. In this mode the CYGNUS 517 can inter-work with a CYGNUS 508V2 unit (see secs. 3.1
and 3.2).
- 5.4 -
"V516" Indicator
This indicator is lit to indicate that the unit is operating in a mode compatible with the CYGNUS 516.
In this mode the CYGNUS 517 can inter-work with a CYGNUS 516 unit.
"T/DFLT" Indicator
This indicator glows steadily (DFLT) if the unit assumes default parameters at power-on or reset
due to the Configuration Memory contents being invalid.
The indicator flashes on and off (TEST) if the unit is executing one of the following tests:
{ Loop back on a port
{ Connection from the supervisory port to a terminal port
{ "DEFAULT" command in effect (see Sec. 3.3.4)
{ Address override is in effect (see Sec. 3.3.1)
The particular test in effect can be seen by giving the "STATUS" or "VPSTATUS" command (see
Sec. 3.3.8).
"TPn" (TP1-TP16) Indicator
This indicator flashes whenever data is received on or transmitted from Terminal Port "n" where n is
1..8 (16). Continuous glowing of this indicator denotes increased activity on the terminal port.
ALRM Indicator
This indicator is on if the unit detects an alarm condition. Alarm conditions include failure of the
primary or secondary (if changeover facility is installed) composite links. This indicator goes off
when the alarm condition is cleared.
BUZZ ENBL Indicator
This indicator is on if the internal audible buzzer is enabled. It is off when the buzzer is disabled
(see Sec. B.6).
BUZZ DISBL Indicator
This indicator is on if the internal audible buzzer is disabled. It is off when the buzzer is enabled
(see Sec. B.6).
The following indicators on the main front panel are related to the operation of the PRI (Primary)
composite link interface. If the changeover option is installed a similar set of indicators is also
provided for the SEC (Secondary) channel - see Appendix B.
DCD Indicator
This indicator is on when the DCD signal on the PRImary interface is active (see Appendix B).
FLAG Indicator
This indicator is on when DATA pattern from the remote unit is detected on the PRImary link interface (see Sec. B.2).
PRI-SEL Indicator
This indicator is on when the CYGNUS 517 is sending user data traffic over the PRImary composite
link (channel).
V.35 Indicator
This indicator is on if the PRImary link is configured for V.35 operation (see Sec. 3.1).
V.24 Indicator
This indicator is on if the PRImary link is configured for RS232 operation (see Sec. 3.1).
- 5.5 -
CLK-INV Indicator
This indicator is on if clock inversion is selected on the PRImary link (see Sec. 3.1).
5.5 BACK PANEL INDICATORS

Note: The following indicators are present on the back panel if the field configurable RS232/V.35
interfaces are installed in the unit. The indicators for the voice module, the 64 kbps co-directional
G.703 interface, the E1 interface, and the 64 kbps IDSL modem are described in Appendices H, I, J
& K respectively.
Fig. 5.2 shows the back panel fascia plate for the field configurable RS232/V.35 this interface.
V.35
.
.
COMPOSITE PORT
V.24
.
PRI
.
.
SEC
CYGNUS 517
Fig. 5.2 Back panel fascia for V.35/RS232 composite link
"V.24" Indicator
This indicator, if present and ON, indicates that the composite port is configured for V.24/RS-232
operation and a RS-232 CP-to-modem cable should be used at the composite port for connection
to the external device at the composite port.
"V.35" Indicator
This indicator, if present and ON, indicates that the composite port is configured for V.35 operation
and a V.35 CP-to-modem cable should be used at the composite port for connection to the external
device at the composite port.
PRI Indicator
If this indicator is ON it indicates that this link is the primary composite link (see Appendix B).
SEC Indicator
If this indicator is ON it indicates that this link is the secondary composite link (see Appendix B).
- 5.6 -
Appendix A
Connector Pinouts
Composite link connector for RS232/V.35 interface:
A 25-pin D-type plug (male) connector is provided on the back panel of the CYGNUS 517 for this
interface. The port acts as a DTE. When configured for RS232 operation (see Sec. 3.1) the pinout
of this port is as given in Table A.1. When configured for V.35 operation the pinout of this connector
is as given in Table A.2. In both cases this port can be connected to standard modems (DCEs) by a
straight 1-to-1 DTE-to-DCE cable. See Appendix G for cable details.
TABLE A.1
Pin assignments for the composite port male 25-pin D-type connector (RS 232 interface)
(N.B.: port acts as a RS232 DTE)
Pin No.
Function
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Protective (Frame) Ground

Transmitted Data (TxD)
Received Data (RxD)
Request To Send (RTS)
Clear To Send (CTS)
Data Set Ready (DSR)
Signal Ground
Data Carrier Detect (DCD)
Unused
Unused
Unused
Unused
Unused
Unused
Transmitter Signal Timing Element DCE Source (External Transmit Clock)
Unused
Receiver Signal Timing Element
(Receive Clock)
Local Loop back (LL)
Unused
Data Terminal Ready (DTR)
Remote Loop back (RL)
Unused
Unused
Transmitter Signal Timing Element DTE source (Internal Transmit Clock)
Test Mode (TM)
16
17
18
19
20
21
22
23
24
25
- A.1 -
Input/Output
to Mux
Output
Input
Output
Input
Input
Input
Input
Input
Output
Output
Output
Output
Input
Connector pinouts
TABLE A.2
Pin assignments for the composite port male 25-pin D-type connector (V.35 interface)
(N.B.: port acts as a V.35 DTE)
Pin No.
Signal Name
Input/Output
to mux
Frame Ground
Unused
Unused
Request To send (RTS)
Output
Clear To Send (CTS)
Input
DCE Ready (DSR)
Input
Signal Ground
Common
Receive Line Signal Detector (DCD)
Input
Transmitted Data A
Output
10
Transmitted Signal Timing Element B

(DCE source)
Input
11
Transmitted Data B
Output
12
Received Data A
Input
13
Received Data B
Input
14
Transmitted Signal Timing Element A

(DCE source)
Input
15
Unused
16

(DTE source)
Output
17
Unused
18
Output
19
Transmitted Signal Timing Element A

(DTE source)
Output
20
DTE Ready (DTR)
Output
21
Output
22
Received Signal Timing Element B

(DCE source)
Input
23
Received Signal Timing Element A

(DCE Source)
Input
24
Unused
25
Test Mode
- A.2 -
Input
Connector pinouts
Table A.3 gives the pinout of the 25-pin D-type socket (female) supervisory port connector provided
on the front panel of the CYGNUS 517. This port can be connected to most standard asynchronous
terminals (such as DEC VT100 and VT220 or compatible terminals) via 1-1 DTE-to-DCE cables.
See Appendix G for cable details.
TABLE A.3
Pin assignments of the terminal port / supervisory port female D-type connector
(RS232 interface)
Pin No.
Function
Input/Output
to Mux
1
Protective (Frame) Ground
Input
Received Data (RxD)
Output
Input
Clear To Send (CTS)
Output
Output
Signal Ground
Unused
Unused
10
Unused
11
Unused
12
Unused
13
Unused
14
Unused
15
Unused
16
Unused
17
Unused
18
Unused
19
Unused
20
21
Unused
22
Unused
23
Unused
24
Unused
25
Unused
- A.3 -
Input
Connector pinouts
The voice interface on the CYGNUS 517 is brought out on a RJ-11 connector as shown below.
Table A.4 gives the pinout of this connector.
TABLE A.4
Pin assignments of the voice FXS/FXO port
female 6-position, 4-wire RJ-11 connectors
Pin No.
Signal Name
1
Unused (Not inserted)
Unused
Tip
Ring
Unused
Unused (Not inserted)
- A.4 -
Appendix B
LINK CHANGEOVER AND AUDIBLE ALARM
B.1 LINK CHANGEOVER FACILITY - BACKGROUND

In critical applications involving statistical multiplexers it is often a requirement that connectivity
between the two sites be maintained even if the communication link between the two sites fails. For
this purpose users may sometime arrange a second leased line and keep it as a standby link (Fig.
B.1). If the primary link fails, personnel at both ends of the circuit switch the multiplexer to the
secondary link.
Leased line
Modem
Main leased line

(analog or digital)
Leased line
Modem
Mux
Mux
RS232 or V.35
interface
Leased line
Modem
Standby leased line

(analog or digital)
Leased line
Modem
RS232 or V.35
interface
Fig B.1 : User equipment is switched to standby link manually if the main link fails
This arrangement provides the standby link required by the critical application, but it needs manual
intervention at either end of the circuit to switch the user equipment to the standby link.
The link changeover facility in the CYGNUS 517 High Integration Statistical Multiplexer provides
an automated solution to this problem. A typical application of this facility is shown in Fig. B.2.
Active leased line

(analog or digital)
517
517
Standby leased line
(analog or digital)
Fig B.2 : Automatic link changeover facility in CYGNUS 517

The CYGNUS 517 at each location is connected to the active as well as the standby link and can
be configured to switch to the standby link if the active link fails. The action to be taken when the
previously active link is restored can be selected on the CYGNUS 517 - for instance, it can switch
back to the previously active link, or continue working on the present link.
- B.1 -
Link changeover and audible alarm
B.2 OPERATION OF LINK CHANGEOVER FACILITY

To understand the operation of the link changeover facility the CYGNUS 517 may be visualised as
consisting of the functional blocks shown in Fig. B.3.
PRI Link i/f PRI Link DCE (int or ext)**
User devices
.
.
Multiplexer block
Changeover
switch block
SEC Link i/f
SEC Link DCE (int or ext)**
**: PRI and SEC Link DCEs could be modems or converters - either built into
the CYGNUS 517, or connected externally to it via RS232/V.35 interface
Fig. B.3 CYGNUS 517 functional block diagram

Data from user devices is multiplexed into a single composite stream by the multiplexer block. The
multiplexed data stream is handed over to the changeover switch block, which then sends it over
one of the two link interfaces based on the status of the links, and on how the changeover is configured to operate. Note that the DCEs (modems or converters), which convert data into a form
required by the leased line, may be external to the CYGNUS 517 (connected to the CYGNUS 517
through RS232/V.35 interface), or may be modules built-into the CYGNUS 517.
To implement the changeover function the first question to be answered is how the CYGNUS 517
detects whether a link is up or down. The changeover block in the CYGNUS 517 has two basic
methods for determining link status:
w DCD (or NO_DATA) mode of link status detection: In this mode the DCE connected to that link
interface (whether internal or external to the CYGNUS 517) indicates the status of the link to the
changeover block in the CYGNUS 517 via the DCD signal. An active DCD signal indicates that
the link is up and an inactive DCD signal indicates that the link is down.
w DATA mode of link status detection: In this approach the changeover blocks in the two units
monitor the DCD signal and also look for certain data patterns from each other. If they receive
these patterns they assume that the link between them is up; if they are unable to receive these
patterns, or if DCD is inactive, they assume that the link is down.
The DCD (NO_DATA) mode of link status detection is suitable when the DCD signal accurately
reflects the status of the end-to-end link. This is true when the DCE is an analog modem, (analog
modems are able to detect the status of the end-to-end link and indicate the same via the DCD
signal). Digital access units such as 64 kbps /2 Mbps modems or converters, however may only be
able to detect the status of the local segment of their connection (between the user premises and
the service exchange), and not of the end-to-end link. With these modems, an inactive DCD
indicates that the link is down. However an active DCD only indicates that the local loop is OK - the
status of the end-to-end link is still in doubt. The DATA mode should be used in such cases.
The next question to be answered is what is the action to be taken when the link fails. The
CYGNUS 517 offers three different changeover modes - Auto changeover mode with priority, Auto
changeover mode without priority and Manual changeover mode. These modes are described
below:
w Auto changeover mode with priority: This mode is used when one of the two links is preferred
over the other (e.g., when this link has higher bandwidth or lesser cost than the other one). In
this mode the traffic is directed to the preferred link as long as that link is up. If the preferred link
fails traffic is switched to the standby link. When the preferred link is restored, traffic is again
- B.2 -
switched back to it. It may be used with DCD or DATA mode of changeover, and is normally
recommended when link speed is below 9600 bps. This mode should be selected when the
CYGNUS 517 has to inter-work with a remote CYGNUS 403 modem changeover switch, in
which case the CYGNUS 517 should be configured only for DCD changeover mode.
w Auto changeover mode without priority: This mode is used when both links are equally preferred
(e.g., when both links are have similar bandwidth and cost). It is similar to Auto changeover
mode with priority, except that when the failed link is restored, traffic is not switched back to it.
For this configuration to work properly only the DATA mode of changeover should be selected. It
is recommended for link speeds 9600 bps or higher. In this mode the CYGNUS 517 can interwork with CYGNUS 404 modem switch.
w Manual changeover mode: In this mode the multiplexer is always connected to a particular specified link regardless of whether that link is up or not. If both the CYGNUS 517 units are set for
Manual mode both units must also be configured to operate on the same link. It is also
possible to select Manual mode on one unit and configure the other unit in AUTO mode - in this
case the link selected on the Manual mode unit will be the one used by both units; it is not
necessary to select the same link on the unit set to AUTO mode. However this will work if the
unit configured to work in AUTO mode is also operating in DATA mode of changeover.
To operate in AUTO changeover mode with DATA mode (with or without priority), one of the
CYGNUS 517 units has to be designated as the Master, and the other as the Slave. The unit
configured as Master monitors the link status using DCD signal and Data pattern and takes the
decision as to which link should be used for carrying the user traffic. It then informs its decision to
the slave unit so that both together select the same link for carrying data traffic.
When configured with AUTO changeover in DCD mode, Master and Slave configuration is not
important. However priority has to be enabled, and both the units are required to be configured to
give priority to the same link.
The status of switches and jumpers related to the changeover logic can be obtained through the
supervisory port by giving STATUS command (see Sec. 3.3.8).
NOTE
When the traffic changes over from one link to the other, communication between the two
units may be disrupted for a few seconds. If the presently active link fails too often disrupting the traffic frequently, it is advisable to change over from AUTO mode to MANUAL
mode and select the good link for operation.
B.3 CONFIGURING LINK CHANGEOVER OPERATION

Operation of the link changeover facility is configured through jumpers and switches on the main
PCB (Part No. 100-0188) inside the unit and through switches on the front panel of the unit.
Main PCB jumpers related to changeover function
The layout of the main PCB is shown in Fig. B.4 below:
- B.3 -
CN2
CN1
CN4
CN3
RLY
U18
CN5
U19
U20
U21
CN7
U22
BUZZ
CN6
CN8 CN9
U27
U28
U30
J1
J2
J3
J4
U31
CN10
J5 J6 J7 J8
P12V N12V
CN11
J9
CN12
J11
CN14
SW1
J13 CN16
SW2
CN15
1
SW3
CN20
VCC
J14
J15
CN19
1
1
U65
CN21
GND
CN18
VCC
1
SW4
J16 J17 J18
GND
SW5 SW6 SW7SW8 SW9
Fig. B.4 Layout of Main PCB Part No. 100-0188
Jumpers J9 and J14 on the main PCB are used to select whether the changeover facility is installed
in the unit or not. Selection is as follows:
TABLE B.1
Changeover Facility Selection
J9
Mounted
Not mounted
J14
2-3 shorted
1-2 shorted
Description
Changeover facility is installed in the unit
Changeover facility is not installed in the unit
Jumper J17 on the main PCB is used to specify how the changeover block detects link status (see
Sec. B.2). Selection is as follows:
TABLE B.2
Changeover Criteria Selection
J17
Not Mounted
Mounted
Description
DCD (NO_DATA) mode of link status detection - the
changeover block determines link status by monitoring DCD
DATA mode of link status detection - the changeover
block determines link status by monitoring DCD and data
pattern
Jumper SW6 on the main PCB is used to specify whether the unit will give priority to one of the two
links (see Sec. B.2). Selection is as follows:
- B.4 -
TABLE B.3
Priority Function Section
SW6
Not mounted
Mounted
Description
Priority Function is enabled
Priority function is disabled and both channels
have equal priority
Note that SW6 only selects whether the unit will operate in priority mode or not. The actual link to
which priority is to be given is selected through a front panel switch.
Front panel switches related to changeover function
Fig. B.5 shows changeover related indicators and switches on the front panel of the unit.
TP13
TP6
TP7
TP14
TP15
SECONDARY
PRIMARY
TP8
TP16
DCD
CLK-INV
FLAG PRI-SEL
V.35
V.24
DCD
FLAG SEC-SEL
CLK-INV V.35
SEC-SEL
V.24
CHANGEOVER
AUTO
MAN
MANUAL
MST CTEST
SLV DMODE
SLV
Fig. B.5 Indicators and switches

MANUAL
When this switch is in, manual mode of operation is selected. When it is out, AUTO mode is
selected. In manual mode the SEC-SEL switch selects the link which will carry data traffic.
SEC-SEL
This switch has multiple functions:
In manual mode, the multiplexer is connected to SEC Link if this switch is in and to PRI Link if this
switch is out.
In AUTO mode, this switch determines the priority of the two links when both of them are up. When
this switch is in, SEC Link has priority, and when it is out, PRI Link has priority. The priority
function must of course first be enabled (via SW6 on the main PCB - see above). Note that the
priority of the two links is significant only if both links are up. If one of the links is down the switch
will send traffic on the working link only.
In CTEST mode, it decides the direction of traffic flow between the primary and secondary link (see
sec. B.4 below)
SLV
When this switch is in the unit acts as a slave unit. When it is out the unit acts as a master
unit (see Sec. B.2).
- B.5 -
B.4 TESTING LINK CHANGEOVER OPERATION

The CYGNUS 517 has a convenient built-in test facility (CTEST) to allow the changeover function
to be tested independently. Jumper J9 on the main PCB is used to initiate the test - if the jumper is
IN, the test is initiated. To run the test do the following: First connect a pair of back to back DCEs
(modems) to the primary and secondary interfaces of the CYGNUS 517 (the method of establishing
this back-to-back connection will depend on the type of DCEs). Now with the SEC-SEL switch in
out position, insert jumper J9. With this the data path in the unit is as shown in Fig. B.6. The multiplexed data output of the multiplexer block is sent over the PRI Link interface by the changeover
block. Because of the back-to-back connection between PRI Link and SEC Link interfaces this data
is received by the SEC Link interface. The changeover block sends the received data back to the
multiplexer block. In effect therefore the whole data path simulates a loopback on the Multiplexer
blocks output. If Address Override mode is selected on the multiplexer (see Sec. 3.3.1) the
CYGNUS 517 will now link up with itself. If loopback connectors are now put on each terminal port
(see Appendix C for loopback connector details) and TPTEST command given (see Sec. 3.3.18)
the unit will generate test data on each terminal port, receive it back from each terminal port, multiplex it, send it on PRI Link, receive it on SEC Link, demultiplex it and send it back on the terminal
ports, thus continuously circulating data. This tests out the functioning of all parts of the multiplexer.
Loopback connectors
on all terminal ports
Data path
PRI Link
Transmit
DCE (int/ext)
.
.
.
.
Changeover
switch block
Multiplexer block
Back-to-back
connection
DCE (int/ext)
Addr Ovrd
TPTEST
Receive
SEC Link
Fig. B.6 CTEST data path - SEC-SEL "out"
Note that for CYGNUS 517 units with external modems/DCEs connected on the two links, the backto-back connection must be established between the external DCEs.
Now repeat the test with SEC-SEL in. The data path is now as shown in Fig. B.7. This tests out
transmission through SEC Link and reception through PRI Link.
Loopback connectors
on all terminal ports
Data path
PRI Link
Receive
DCE (int/ext)
.
.
.
.
Changeover
switch block
Multiplexer block
Back-to-back
connection
DCE (int/ext)
Addr Ovrd
TPTEST
Transmit
SEC Link
Fig. B.7 CTEST data path - SEC-SEL "in"
- B.6 -
B.5 FRONT PANEL INDICATORS RELATED TO LINK CHANGEOVER

OPERATION
SECONDARY
PRIMARY
TP8
DCD
FLAG PRI-SEL
CLK-INV
V.35
FLAG SEC-SEL
CHANGEOVER
AUTO
MST CTEST
SECONDARY
PRIMARY
TP16
DCD
V.24
CLK-INV V.35
V.24
MAN
SLV DMODE
PRI link indicators

SEC link indicators
SEC-SEL
MANUAL
SLV
Fig. B.8 Indicators and switches

The following indicators on the front panel of the CYGNUS 517 are provided to display the status of
the changeover related functions:
AUTO: This indicator is on if AUTO mode of changeover is selected. It is off in manual mode. It
blinks when changeover facility is bypassed.
MAN: Manual: This indicator is on if Manual mode of changeover is selected. It is off when AUTO
mode is selected. It blinks when changeover facility is bypassed.
MST: Master: This indicator is on if this unit is configured as the Master, otherwise it is off.
SLV: Slave: This indicator is on if this unit is configured as the Slave otherwise it is off.
CTEST: This indicator is on if CTEST is selected (see Sec. B.4) otherwise it is off.
DMODE: DATA Mode: This indicator is on if the unit is configured to detect link status by monitoring
DATA pattern. It is off when the unit is configured for DCD (NO DATA) mode.
The following indicators are provided on the front panel of the CYGNUS 517 for each link interface:
DCD: Data Carrier Detect: This indicator is on when the DCD signal on that interface is active.
FLAG: This indicator is on when DATA pattern from the remote unit is detected on the link interface
PRI-SEL: Provided for primary link, this indicator is on when the Primary link is selected for carrying
traffic.
SEC-SEL: Provided for secondary link, this indicator is on when the Secondary link is selected for
carrying traffic.
V.35: This bi-colour indicator is on if this link is configured for V.35 operation (see Sec. 3.1). In that
case it glows red if data inversion on the concerned link is selected, otherwise it is green. It is off
when the link is not configured for V.35.
V.24: This bi-colour indicator is on if this link is configured for RS232 operation (see Sec. 3.1) In
that case it glows red if data inversion on the concerned link is selected, otherwise it is green. It is
off when the link is not configured for RS232.
CLK-INV: This indicator is on if clock inversion is selected on this link (see Sec. 3.1). It is off for
normal clock.
- B.7 -
B.6 AUDIBLE ALARM

The CYGNUS 517 has a built-in beeper to alert the operator when an alarm condition occurs. For
instance if the unit detects that any one of the two composite links has failed it can sound the alarm.
The beeper will continue beeping as long as the alarm condition lasts, or, until the operator
acknowledges the alarm by pressing and releasing the BUZZER-RESET switch on the front
panel. If the BUZZER-RESET switch is pressed and left (i.e., in position) the alarm will not sound.
The loudness of the alarm can be controlled through jumpers on the main PCB, as given below:
TABLE B.4
Adjusting the volume of the Alarm Beeper
J1
Not
Mounted
Not
Mounted
Not
Mounted
Mounted
Not
Mounted
J2
Not
Mounted
Not
Mounted
Mounted
Not
Mounted
Not
Mounted
J3
Not
Mounted
Mounted
J4
Mounted
Not
Mounted
Not
Mounted
Not
Mounted
Not
Mounted
Not
Mounted
Not
mounted
Not
Mounted
DESCRIPTION
Volume Level 4
(loudest)
Volume Level 3
Volume Level 2
Volume Level 1
Buzzer is OFF (silent)
The audible beeper is also sounded during power-on LED test or LED test initiated from the supervisory port.
B.7 RECOMMENDED CONFIGURATION FOR AUTO MODE

In its AUTO mode of operation, the usage of changeover facility may be done in a manner indicated
in Table B.5, based on the type of primary or secondary link.
TABLE B.5
Recommended Configuration of Changeover Facility in AUTO mode
Speed of link
Primary
Secondary
Link speed below
Link speed below
9600 bps
9600 bps
Recommended
Changeover criteria
DCD (NO DATA)
Link speed 9600 bps

and above
Link speed 9600 bps

and above
DATA
Link speed 9600 bps

and above
Link speed below
9600 bps
Link speed below

9600 bps
Link speed 9600 bps
and above
DATA
Any of the two:

PRIO for Primary
PRIO for Secondary
Any of the three:
NO_PRIO
PRIO for Primary
PRIO for Secondary
PRIO for Primary
DATA
PRIO for Secondary
- B.8 -
Priority selection
Appendix C
Self Tests
The power-on self-test is executed before the normal execution of the multiplexer software if switch
8 on DIP switch SW3 is set to OPEN. If this switch is set to CLOSE, the unit enters a detailed
off-line diagnostic mode. With the switch set to OPEN, the multiplexer operating software takes
over on successful completion of the self-test (see Sec. 3.1).
In case the power-on self-test detects any errors, an error code will be displayed on the front panel
LEDs.
The power-on self-test checks out the major logic sections in the unit. The following tests are
performed during the self-test:
1. LED test
2. DIP switch SW3 test
3. RAM test
4. Timer test
5. Serial channel internal loop back test
6. Voice port test (if voice option is provided and enabled by setting DIP switch 7 to CLOSE
position).
Some details about these tests are given below:
1. LED test
A shifting pattern is output on the front panel LEDs. This tests both the ON and OFF states of the
LEDs except the MUXERR LED.
2. DIP switch SW3 test
The DIP switch SW3 (on the bottom of the unit) is read and displayed on the front panel LEDs for
2-3 seconds. As the switch settings are changed, they are reflected immediately on the LEDs. Each
change in the DIP switch setting extends the test by a further 2-3 seconds. This allows all combinations of the DIP switch to be checked. If the DIP switch setting is not changed during the 2-3
seconds display period, the diagnostic goes to the next test. The LEDs corresponding to various
switches are as shown in Fig. C.1 (S1 indicates switch 1, S2 indicates switch 2, etc.).
CYGNUS 517
FXS
FXO
S8 S7 S6 S5 S4 S3 S2 S1
PWR
TX
RX
TP1
SECONDARY
PRIMARY
TP2
TP3
TP4
TP5
TP6
TP7
TP9 TP10
TP11
TP12
TP13
TP14
TP15
TP8
DCD FLAG PRI-SEL
DCD FLAG SEC-SEL
CHANGEOVER
AUTO
MST
FXS/FXO
BUZZ
LINK LNERR ADERR
V2
V516
MXERR ENBL
TP16
CLK-INV
DIS-BUZZ
V.35
V.24
CLK-INV V.35
SEC-SEL
Fig. C.1 Indicators for DIP switch test

- C.1 -
V.24
MAN
MANUAL
SLV
Self Tests
Ensure that Switch 8 on the DIP switch SW3 is set back to OPEN after the DIP switch test.
3. RAM test
Two different tests are carried out on the Random Access Memory:
1. Read/write test
2. Moving inversions test
In the read/write test, each location is tested by writing and verifying the data patterns 10101010
and 01010101. If there is an error in verifying, the self-test enters a loop where the erroneous
location is continuously written and read back with the same data pattern which caused the error.
In the "moving inversions" test the following sequence is followed.
A. Write data 55 (Hex) in the entire memory.
B. For each location,
{ Read the location and verify that it is 55 (Hex)
{ Write data 0AA (Hex)
{ Read and verify that 0AA (Hex) has been written
{ Go to the next location.
This test verifies address uniqueness. If there is an error during this test, the self-test enters a loop
where the entire RAM is written and read back.
4. Timer test
This test checks out the Timer IC in the unit. Verifies the accuracy of timer clock vis--vis the CPU
speed.
5. Serial channel internal loop back test
In this test, each of the ten (for 8 port model) or eighteen (for 16 port model) serial communication
controller (SCC) channels are tested out. The following tests are carried out on each of the SCC
channels.
a) Read/write to the SCCs.
b) A moving inversions test on the SCCs.
c) Data transmission and reception on the serial channel, with the Transmit of the SCC internally
looped back to its Receive.
6. Voice port test
This test writes initialization code word on the voice codec and reads it back. It also checks if the
voice codec activates its interrupts on power-on.
Any errors encountered during the power-on self-test lead to unique codes being displayed on the
front-panel LED indicators. For the purpose of the error-codes listed below, the LEDs on the frontpanel are assumed to have place values as given in the diagram below:
- C.2 -
Self Tests
CYGNUS 517
D8 D7 D6 D5
D4 D3 D2 D1 D0
PWR
TX
RX
TP1
TP2
TP3
TP4
TP5
TP6
PRIMARY
TP7
TP8
DCD FLAG PRI-SEL
SECONDARY
DCD FLAG SEC-SEL
CHANGEOVER
AUTO
MST CTEST
FXS/FXO
BUZZ
LINK LNERR ADERR
V2
V516
SECONDARY
PRIMARY
MXERR ENBL
TP9 TP10
TP11
TP12
TP13
TP14
TP15
TP16
CLK-INV
V.35
V.24
CLK-INV V.35
V.24
MAN
SLV DMODE
C7 C6 C5 C4 C3 C2 C1 C0
DIS-BUZZ
SEC-SEL
MANUAL
Fig. C.2 Indicators for diagnostic tests
The digit to which each LED corresponds is indicated above. In the codes given below a 1 in a
digit indicates that the corresponding LED is lit and a 0 indicates that it is unlit.
TABLE C.1
List of Error Codes
------------ DISPLAY DIGIT ---------------
MEANING
D8 D7 D6 D5 D4 D3 D2 D1 D0
0
ROM test started
0 ROM checksum error
0 RAM data stuck error
RAM address error
Start of Timer test
Timer Read Error
Timer too early
1 Timer too late
0 Start of Voice test*
1 Codec Interrupt Stuck**
0 Codec Init Word Mismatch*
X SCC register read err
SCC address clash error
SCC transmit too early
X SCC transmit too late
Char not received by SCC
IEI is stuck active
No interrupt
Wrong interrupt
Received char not matching
SCC receive errors
RAM test started
MUXERR test started
- C.3 -
Self Tests
------------ DISPLAY DIGIT ---------------
MEANING
D8 D7 D6 D5 D4 D3 D2 D1 D0
The following tests require external loop back connectors on the ports and are
executed only if detailed diagnostics mode is selected (Switch 8 on DIP switch
SW3 is in CLOSE position)
1
Ext loop back test started
DCD stuck high
DCD stuck low
DSR stuck high
DSR stuck low
CTS stuck high
CTS stuck low
Unable to send character
Character not received
X Rcvd character not matching
X TM Stuck high
X TM Stuck low
* Valid only if Switch 7 on DIP switch SW3 is in CLOSE position and voice option is installed
** Valid only when voice option is installed. When this error code is displayed, following are
additional information codes:
Indicator C7 On : Indicates Hint is active on reset
Indicator C6 On : Indicates Hack is active on reset
Indicator C5 On : Indicates Hint not becoming active on reset removal
Indicator C4 On : Indicates Hack not becoming active on initialization
1. "XXXXX" denotes the serial channel on which the error has occurred, as per the table below.
D4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
TABLE C.2
Interpretation of LED indicators for
power-on and detailed tests of serial ports
(Note: Last eight entries are for 16 port model only)
LED INDICATORS
FAULTY SERIAL
CHANNEL
D3
D2
D1
D0
0
0
0
0
Composite port
0
0
0
1
Supervisory port
0
0
1
0
Terminal Port 1
0
0
1
1
Terminal Port 2
0
1
0
0
Terminal Port 3
0
1
0
1
Terminal Port 4
0
1
1
0
Terminal Port 5
0
1
1
1
Terminal Port 6
1
0
0
0
Terminal Port 7
1
0
0
1
Terminal Port 8
1
0
1
0
Terminal Port 9
1
0
1
1
Terminal Port 10
1
1
0
0
Terminal Port 11
1
1
0
1
Terminal Port 12
1
1
1
0
Terminal Port 13
1
1
1
1
Terminal Port 14
0
0
0
0
Terminal Port 15
0
0
0
1
Terminal Port 16
- C.4 -
Self Tests
2. In case any errors are detected during diagnostics refer the unit to CYGNUS or its authorized
representatives for servicing.
3. Detailed diagnostics test selection is done as per the table below. The error codes for these tests
are as per Table C.1. Note that the detailed tests require special connectors to be connected at
the respective ports. The connections for these special loopback connectors are provided in the
following text.
TABLE C.3
Switch selection for detailed diagnostics tests
-------- DIP SWITCH SETTING -------TESTED SUBSYSTEM
S8 S7 S6 S5 S4 S3 S2 S1
1
Composite port
Supervisory port
Terminal Port 1
Terminal Port 2
Terminal Port 3
Terminal Port 4
Terminal Port 5
Terminal Port 6
Terminal Port 7
Terminal Port 8
Terminal Port 9
Terminal Port 10
Terminal Port 11
Terminal Port 12
Terminal Port 13
Terminal Port 14
Terminal Port 15
Terminal Port 16
All subsystems (8 port model)
All subsystems (16 port model)
Voice interface *
Reserved
Watchdog/Muxerr
All other combinations are invalid

"X" denotes don't care
* Valid only if voice option is installed
4. Loopback connector for "D" type Terminal/Supervisory port.
TABLE C.4
25-pin D-type (male) TP/SP Loopback Connector
Short pin ..
3
5
20
to pin ..
2
4
6
- C.5 -
Remarks
RxD to TxD
CTS to RTS
DSR to DTR
Self Tests
5. Loopback connector for RS-232 Composite Port

TABLE C.5
25-pin D-type (female) CP Loopback Connector for RS-232
Short pin ..
2
4
6
18
24
to pin ..
3
5
8 and 20
25
17
Remarks
TxD to RxD
RTS to CTS
DSR to DCD and DTR
LL to TM
TxClk (ext) to RxClk
6. Loopback connector for V.35 Composite Port

TABLE C.6
25-pin D-type (female) CP Loopback Connector for V.35
Short pin ..
9
11
4
6
23
22
to pin ..
12
13
5
8 and 20
19
16
- C.6 -
Remarks
TxDA to RxDA
TxDB to RxDB
RTS to CTS
DSR to DCD and DTR
RxCA to TxC(E)A
RxCB to TxC(E)B
Appendix D
Default Composite Port Values
The tables below list the default values for various composite port operating parameters depending
on the speed and line types programmed for the composite port (see sec. 3.3.1). Number of hops
for LAND line is 0, for SAT1HOP line is 1 and for SAT2HOP line is 2. For instance, if TXLINE type
is SAT1HOP and RXLINE type is SAT2HOP, the "No. of hops" is 3. The minimum "No. of hops" is 0
(LAND lines in both directions), and maximum is 4 (SAT2HOP in both directions).
TABLE D.1
Default and maximum user settable values of port packet size for different TUNING settings
CP Speed (bps)
PACKET SIZE (BYTES)
For EFFICIENCY Tuning For RESPONSE Tuning
DFLT
MAX
DFLT
MAX
1,200
36
54
18
54
1,800
72
108
36
108
2,000
72
108
36
108
2,400
72
108
36
108
3,600
108
162
54
162
4,800
144
216
54
216
7,200
216
246
54
246
9,600
246
246
54
246
14,400
246
246
54
246
19,200
246
246
54
246
28,800
246
246
72
246
33,600
246
246
72
246
38,400
246
246
108
246
48,000
246
246
108
246
56,000
246
246
144
246
64,000
246
246
162
246
"Maximum" referred to in the above table is the maximum packet size that can be set through
command. Minimum settable packet size is 18 bytes for all combinations.
TABLE D.2
Default, minimum and maximum values of various Composite port parameters
for different number of round trip hops
No. of hops in
Max Retry
Time out
Window Size
round trip
Count
(X 100 msec)
(RXLINE +
TXLINE)
Min Dflt Max Min Dflt Max Min Dflt Max
0
10
32
30
50
32
33
52
28
10
32
10
36
53
28
10
32
13
39
55
10
28
10
32
15
42
57
12
28
- D.1 -
Appendix E
Extended Supervisory Access
In installations where a number of CYGNUS 517/516/508V2 statistical multiplexers are used to
connect a central computer to a number of remote locations, the Extended Supervisory Access
facility allows control and monitoring of a number of multiplexers from a single Supervisory console.
To use the Extended Supervisory Access facility one CYGNUS 517 unit is used as a dedicated
monitoring station (see Figure). Supervisory ports of up to eight (or sixteen) are connected to the
terminal ports of this monitoring station using crossover cables. A supervisory terminal connected to
the supervisory port of this unit then becomes the Supervisory Console for all these eight multiplexers, and their remote counterparts. Thus eight/sixteen pairs of multiplexers can be controlled by the
single Supervisory Console.
An operator can access the supervisory port of any of the eight connected units by using the
CONNECT command. This command is described in Sec. 3.3.9. To the operator the connection is
transparent, and it appears to him as if he is directly connected to the connected unit's supervisory
port. All the supervisory functions described in Chapter 3 can be performed by the operator on any
of the eight connected units and their remote counterparts (by using the "REMOTE" command after
CONNECTing to the local unit).
M1'
M1
M2'
SP
M2
M7'
.........
SP
SP
.........
M7
M8'
SP
M8
TP1 TP2 .... TP7 TP8
SP
CYGNUS 517
(Monitoring Station)
Supervisory terminal
LEGEND
M : Multiplexer
SP: Supervisory Port
TP: Terminal Port
Note: For 16 port model TP9-TP16 are also available
EXTENDED SUPERVISORY ACCESS USING CYGNUS 517
- E.1 -
Appendix F
COMMAND SUMMARY
CYGNUS 517 supervisory commands for accomplishing various functions are listed below (for
details see Chapter 3):
F.1 Modifying Parameters
SET <PORT> <PARAM KEYWORD> <PARAM VALUE> [RETURN]
F.2 Displaying Parameters
OLD <PORT> <PARAM KEYWORD> [RETURN]
OLD TP ALL [RETURN]
NEW <PORT> <PARAM KEYWORD> [RETURN]
F.3 Copying Terminal Port parameters
COPY <PORT 1> TO <PORT 2> [RETURN]
F.4 Forcing Default Parameters
DEFAULT [RETURN]
F.5 Storing Parameters
STORE [RETURN]
F.6 Resetting the multiplexer
RESET [RETURN]
F.7 Initializing a single Port
INIT <PORT> [RETURN]
F.8 Viewing unit status
STATUS [RETURN]
VPSTATUS [RETURN]
F.9 Connecting to a Terminal Port
CONNECT <PORT> [RETURN]
F.10 Identification of the unit
ID [RETURN]
F.11 Remote and Local Operation
REMOTE [RETURN]
LOCAL [RETURN]
F.12 Statistics
ERRSTAT <PORT> [RETURN]
CLRERR <PORT> [RETURN]
TXCOUNT <PORT> [RETURN]
TC <PORT> [RETURN]
RXCOUNT <PORT> [RETURN]
RC <PORT> [RETURN]
TXBUFUTIL <PORT> [RETURN]
TBU <PORT> [RETURN]
- F.1 -
Command Summary
RXBUFUTIL <PORT> [RETURN]

RBU <PORT> [RETURN]
CLRPK <PORT> [RETURN]
CLRPK [RETURN]
CLRSTAT <PORT>[RETURN]
F.13 LED, DIP switch and Watchdog test
LEDTEST [RETURN]
SWITCHTEST [RETURN]
WDTEST [RETURN]
F.14 Initializing Time
CLRTIME [RETURN]
TESTS FOR SERVICE PERSONNEL ONLY

F.15 Terminal Port Loading Test
(Make sure that TPs have loop back connectors and link is up for the test to recirculate data)
TPTEST [RETURN]
(Generates dummy output on all terminal ports)
F.16 NVRAM TEST

(Note: The NVRAM contents will be lost and the unit will assume default parameters after executing the NVRAM Write tests)
NVWRTEST1 [RETURN]
(Writes pattern 1 on NVRAM)
NVRDTEST1 [RETURN]
(Verifies pattern 1 from NVRAM)
NVWRTEST2 [RETURN]
(Writes pattern 2 on NVRAM)
NVRDTEST2 [RETURN]
(Verifies pattern 2 from NVRAM)
- F.2 -
Appendix G
CABLE CONNECTIONS
G.1 NETWORK PORT CABLES
The main cables used for network port are the network-port to modem cable and network port to
network port (Loop back and local connection cables).
TABLE G.1
Modem to Composite Port cable (EIA-232)
(To be used when the composite port connector is configured for EIA-232 operation)
CYGNUS 517 CP end
25 pin 'D' female
EIA-232 Signal
Modem End
25 pin 'D' male
Pin No. Pin No.
Remarks
EIA-232 Signal
Frame Gnd
Frame Gnd
TxD
TxD
RxD
RxD
RTS
RTS
CTS
CTS
Optional
DSR
DSR
Optional
Signal Ground
Signal Ground
DCD
DCD
Transmitter Clock (DCE source)
15
15
Transmitter Clock (DCE Source)
Receiver Clock (DCE source)
17
17
Receiver Clock (DCE source)
LL
18
18
LL
DTR
20
20
DTR
RL
21
21
RL
Transmitter Clock (DTE source)
24
24
Test Mode
25
25
Test Mode
- G.1 -
Optional
Optional
Cable Connections
TABLE G.2
Modem to Composite Port Cable (V.35)
(To be used when the composite port connector is configured for V.35 operation)
CYGNUS 517 CP end 25 pin "D" female
Modem end 34 pin V.35 connector (Male)
V.35 Signal
Pin
Pin
V.35 Signal
Frame Ground
Frame Ground
Clear To Send (CTS)
Clear To Send (CTS)
DCE Ready (DSR)
DCE Ready (DSR)
Signal Ground
Signal Ground
Transmitted Data A
Transmitted Data A

(DCE source)
10
AA
Transmitter Signal Timing Element B

(DCE source)
Transmitted Data B
11
Transmitted Data B
Received Data A
12
Received Data A
Received Data B
13
Received Data B
Transmitter Signal Timing Element A

(DCE source)
14

(DCE source)

(DTE source)
16

(DTE source)
18
JJ

(DTE source)
19

(DTE source)
DTE Ready (DTR)
20
DTE Ready (DTR)
21
HH
Recever Signal Timing Element B

(DCE source)
22
Receiver Signal Timing Element B

(DCE source)
Receiver Signal Timing Element A

(DCE Source)
23
Receiver Signal Timing Element A

(DCE Source)
Test Mode
25
KK
Test Mode
- G.2 -
Remarks
Optional
Cable Connections
TABLE G.3
CP - to - CP NRZ / NRZI / FM back-to-back connection cable (EIA-232)
(To be used when both the composite ports are configured for EIA-232 operation)
CYGNUS 517 CP end
25 pin 'D' female
CYGNUS 517 CP end

25 pin 'D' female
EIA-232 Signal Name
Pin
No.
Pin
No.
EIA-232 Signal Name
Frame Ground
Frame Ground
TxD
RxD
RxD
TxD
Signal Ground
Signal Ground
Receiver Clock (DCE Source)
17
24
24
17
Remarks
Transmitter Clock (DTE source) Not required for NRZI or

FM encoding
Receiver Clock (DCE Source)
Not required for NRZI or

FM encoding
TABLE G.4
CP - to - CP NRZ / NRZI / FM Cable (V.35)
(To be used when both the composite ports are configured for V.35 operation)
25 pin "D" female
V.35 Signal
Frame Ground
25 pin "D" female

Pin No Pin No
1
V.35 Signal
Remark
Frame Ground
Signal Ground
Signal Ground
Transmitted Data A
12
Received Data A
Transmitted Data B
11
13
Received Data B
Received Data A
12
Transmitted Data A
Received Data B
13
11
Transmitted Data B
Transmitter Signal Timing Element

B (DTE source)
16
22
Receiver Signal Timing

Element B (DCE source)
Not required for

NRZI/FM encoding
Transmitter Signal Timing Element

A (DTE source)
19
23

Element A (DCE Source)
Not required for

NRZI/FM encoding

Element B (DCE source)
22
16
Transmitted Signal Timing

Element B (DTE source)
Not required for

NRZI/FM encoding

Element A (DCE Source)
23
19
Transmitter Signal Timing

Element A (DTE source)
Not required for

NRZI/FM encoding
- G.3 -
Cable Connections
G.2 TERMINAL/SUPERVISORY PORT CABLES

TABLE G.5
Terminal/Supervisory Port (D-type) to Terminal/IBM PC Cable
CYGNUS 517 Terminal/Supervisory port end
25 pin 'D' male
Terminal/PC End
25 pin 'D' female
Signal Name
Pin No.
Pin No.
Signal Name
Frame Gnd
Frame Gnd
TxD
TxD
RxD
RxD
RTS
RTS
CTS
CTS
DSR
DSR
Signal Ground
Signal Ground
DTR
20
20
DTR
TABLE G.6
Terminal Port (25-pin D-type) to Asynchronous modem cable
CYGNUS 517 side connector (25-pin
D-type male)
Async Modem Side Connector

(25 pin D male)
Signal Name
Pin
No.
Pin
No
Signal Name
Received Data (RxD)
Received Data (RxD)
Clear To Send (CTS)
Clear To Send (CTS)
20
20
Signal Ground
Signal Ground
None /Frame Ground/

Signal Ground (see note)
None/Frame Ground/ Signal Ground (see

note)
- G.4 -
Appendix H
VOICE MODULE
H.1 PCBs AND CABLES
The voice module consists of two PCBs. PCB P/N 100-0203 is inserted into the CYGNUS 517
chassis from the front of the unit and PCB P/N 100-0202 is inserted from the rear (see Fig. H.1).
The front PCB contains the main circuit. In addition it provides LED indicators and the FXS/FXO
interface selection switch (see Fig. H.2). It also provides the connectors through which the voice
module connects to the main PCB. A flat ribbon cable (FRC) is used to connect the signals from the
main PCB (Connector CN14 on the main PCB - see Fig. B.4) to connector CN4 on the front PCB of
the voice module. Power is supplied to the voice module through connector CN8 on the front PCB.
A cable harness from this connector to CN8, CN9 or CN12 connector of the main PCB is used for
this purpose.
The rear PCB provide the FXS and FXO interface connectors and indicators to display the status of
these interfaces (see Fig. H.2). An earthing wire is also provided on the rear PCB. The lug at the
end of this wire should be fixed to the brass block provided on the base of the unit with a M3 screw.
CMS 100-0203 EC041004

J1
J2
CN4
J3
CMS 100-0194 EC040722
To CN4
J4
To CN8
CMS 100-0202 EC040922
CN8
Flat Ribbon Cable (FRC)

(Connects to main PCB connector CN14)
Power supply cable harness

(Connects to main PCB connector
CN8, CN9 or CN12)
Earthing wire
(Connects to brass block on base plate)
Fig. H.1 Voice module - PCBs and cables
H.2 CONFIGURING THE VOICE MODULE

The module is configured through jumpers and switches provided on the front and the rear PCBs.
The functions of the various jumpers and switches is described below.
Front Panel FXS/FXO switch
This is a push button switch on the front PCB, which is accessible from the front panel of the unit. It
is used to select whether the voice port interface is FXO or FXS. A small screw driver or similar
object with a pointed tip is needed to activate the switch. When this switch is pressed in, the interfaces selected is FXO. When it is released, the interface selected is FXS. The selected interface
(FXS or FXO) is displayed on LED indicators on the front and rear fascias (see Fig. H.2)
- H.1 -
Voice module
Jumpers on the rear PCB

The user configurable jumpers on the rear PCB (P/N 100-0202 EC 040922) are described below:
TABLE H.1
Configuration Jumpers for Rear Side Line Interface PCB P/N 100-0202 EC 040922
Function
Selected
Selection Details
Default Setting
by
Loop current adjustment
J1
1-2 IN : Loop
2:3 IN : Loop
Both 1-2 and 2-3
for FXS port
current adjusted for
current adjusted for OUT: (24 mA loop
long loops
short loops
current selected)
Selection of Ring detect
J2
Jumper OUT : Ring
Jumper IN : Ring
Jumper IN
threshold sensitivity for
detect sensitivity is
detect sensitivity is
FXO
30 V RMS (suitable
10 V RMS (suitable
for long loops)
for short loops).
Selection of Ringing
J3
Jumper OUT :
Jumper IN : Ringing Jumper IN
Voltage for FXS port
Ringing voltage
voltage enough for
enough for two
one terminal device.
terminal devices.
Selection of EarthJ4
1-2 IN : Earth2:3 IN : EarthBoth 1-2 and 2-3
Ground connection
ground shorted.
ground shorted
OUT (Earth-Ground
through a 180
not connected to
ohms, 0.5W
each other)
resistor.
H.3 LED INDICATORS ON THE VOICE MODULE

Fig. H.2 shows the front and back fascia panels for the voice module.
FXS
.
Voice Module
FXS .
VLINK
VAD
FXO
FXO
.
OH
.
FXS
+24V
.
FXS/FXO
-24V
.
OH
.
FXO
CYGNUS 517
CYGNUS 517
Front fascia
Back fascia
Fig. H.2 Voice module - front and back fascias
- H.2 -
Voice module
Front panel indicators

FXS indicator
When this indicator is on, it indicates that the front panel FXS/FXO switch has selected the voice
port to operate with FXS interface. In this mode a telephone instrument or a Group 3 fax machine
can be connected to the voice port.
FXO indicator
port to operate with FXO interface. In this mode the voice port of the CYGNUS 517 can be
connected as a PABX extension.
VLINK indicator
When this indicator is on, it indicates that the connection between the voice ports of the two multiplexers is operational. In case one of the CYGNUS 517 units is operating with the FXO interface,
this indicator merely indicates that the path between remote voice port and PABX has been established, and does not necessarily mean that the end-to-end voice connection has been established.
If this indicator flashes during normal operation, it means that the voice link between the voice ports
of the connected multiplexers is being established, or could not be established due to link-down
condition of the composite port.
VAD indicator
This indicator indicates voice activity on the receive section of the voice port. The CYGNUS 517
allocates bandwidth to voice on a dynamic basis - even within a voice conversation if the unit
detects silence on the voice port it does not generate any traffic on the composite port. The VAD
indicator glows when the CYGNUS 517 detects voice activity and is off when there is silence on the
voice port.
Back panel indicators

FXS indicator
port to operate with FXS interface. In this mode a telephone instrument or a Group 3 fax machine
can be connected to the voice port.
FXO indicator
port to operate with FXO interface. In this mode the voice port of the CYGNUS 517 can be
connected as a PABX extension.
OH indicators
The OH indicator next to the FXS connector glows when the telephone/fax instrument connected to
the "FXS" port is in off-hook state. The OH indicator next to the FXO connector glows when the
FXO port of CYGNUS 517 is in off-hook state.
+24V indicator
This indicator indicates the availability of +24V power supply inside CYGNUS 517 unit. The ring
generation function of FXS interface may not function without +24V supply.
-24V indicator
This indicator indicates the availability of -24V power supply inside CYGNUS 517 unit. The FXS
interface may not work without -24V supply.
- H.3 -
Appendix I
64 KBPS CO-DIRECTIONAL G.703 INTERFACE MODULE
I.1 PCBs AND CABLES
The 64 kbps co-directional G.703 module (COD Module) consists of two PCBs. PCB P/N 100-0204
is inserted into the CYGNUS 517 chassis from the front of the unit and PCB P/N 100-0205 is
inserted from the rear (see Fig. I.1).
The front PCB contains the main circuit. It also provides LED indicators and diagnostic switches
(see Fig. I.2).
The rear PCB provides the line interface connector. It also provides the connectors through which
the COD module connects to the main PCB. A flat ribbon cable (FRC) is used to connect the
signals from Composite Port 1 or 2 of the main PCB (Connectors CN5 or CN6 on the main PCB see Fig. B.4) to connector CN1 on the rear PCB of the COD module. Power is supplied to the COD
module through connector CN2 on the rear PCB. A cable harness from this connector to CN8, CN9
or CN12 connector of the main PCB is used for this purpose. An earthing wire is also provided on
the rear PCB. The lug at the end of this wire should be fixed to the brass block provided on the
base of the unit with a M3 screw.
The module is connected to the PCM interface providing the COD connection via a 5-way terminal
block located on the rear fascia. Two terminals are provided for Transmit Data, two for Receive
Data and one for Earth. See Fig. I.2.
CMS 100-0204 EC041009
CMS 100-0205
EC041009
CN2
J2
CN1
To CN1
J3
To CN2
J4 J5

CN8, CN9 or CN12)

connector CN5 or CN6)
Earthing wire
(Connects to brass
block on base plate)
Fig. I.1 64 kbps co-directional G.703 module - PCBs and cables
I.2 CONFIGURING THE 64 KBPS G.703 (COD) MODULE

The module is configured through jumpers provided on the front and the rear PCBs. The functions
of the various jumpers are described below:
TABLE I.1
Configuration jumpers on front PCB P/N 100-0204 EC 041009
(Note: Factory default settings are shown in bold face)
Function
Selected by
Selection Details
Selecting CTS signal
J2
2-3 IN: CTS always active
1-2 IN: CTS follows RTS
Selecting Clock Mode
J4
IN: Internal clock mode
OUT: Recovered clock
mode
Selecting Data Inversion
J5
OUT: Data is inverted
IN: Data is not inverted
- I.1 -
64 kbps co-directional G.703 interface module
Clock mode
In Recovered clock mode the COD module recovers the clock from the signal received by it on the
G.703 interface. This clock is used to send and receive data to the main PCB and also to send the
data on the G.703 interface. In Internal Clock mode the module uses its own crystal oscillator to
generate the clock used for transmission and reception on the G.703 interface and also for transmitting and receiving data to and from the main PCB. The factory default setting is Recovered
clock mode.
Two CYGNUS 517 units may be connected directly to each other using copper wire upto a distance
of about 500 meters if both have 64Kbps COD interface. In such case the COD interface of one of
the units should be programmed for internal clock mode, and the other for recovered clock mode.
Data Inversion
If Data Inversion is selected the 64 kbps G.703 interface in the CYGNUS 517 inverts each bit of
the multiplexed data stream before sending it on the line. It also inverts the data in the bit stream
received from the line. If data inversion is not selected, the bit stream in both directions is passed
without inverting it. Factory default setting is Data Inversion off.
Function
Shorting Earth and
Signal Ground
TABLE I.2
Configuration jumpers on rear PCB P/N 100-0205 EC 041009
Selected
Selection Details
Default setting
by
J3
1-2 IN: Signal Ground 2-3 IN: Signal
2-3 IN Ground and
and Earth are shorted Ground and Earth Earth are shorted.
through 100 Ohm
are directly
resistor
shorted
I.3 LED INDICATORS ON THE 64 KBPS G.703 (COD) MODULE

Fig. I.2 shows the fascia panels for the 64 kbps G.703 (COD) module at the front and back of the
CYGNUS 517 when the module is installed in the unit.
G.703 I/F
64 kb G.703 Module
TST
PWR
VLINK
VAD
T
PA
AIS
RXD
SYNC
TXD
RX
ERR
FXS/FXO
IFOK
INT
LL
TX
PRI
DL
DI
SEC
CYGNUS 517
CYGNUS 517
Front fascia
Back fascia
Fig. I.2 64 kbps co-directional G.703 module - front and back fascias
A description of the front panel indicators is given below:
- I.2 -
PWR indicator
When this indicator is on, it indicates that the module is powered up.
TXD indicator
This indicator flashes when the multiplexer transmits data to the line.
RXD indicator
This indicator flashes when the multiplexer receives data from the line.
IFOK indicator
This indicator shows the status of the internal connection between the network port on the
CYGNUS 517 main PCB and the COD module.
This indicator is on when the COD module detects that the DTR signal from the main PCB is
active, and when network port interface on the main PCB is configured as V.35 (see Sec. 3.1). The
indicator blinks steadily if the network port interface is configured as RS-232. The indicator is off if
the COD module does not detect an active DTR signal from the network port interface of the main
PCB.
INT indicator
This indicator is on if internal clock mode is selected on the COD module (See Sec. I.2). It is off if
recovered clock mode is selected on the module.
PRI indicator
This indicator is on if the COD module is connected to the primary channel of the multiplexer
section.
SEC indicator
This indicator is on if the COD module is connected to the secondary channel of the multiplexer
section.
TST indicator
This indicator is on when any diagnostic test (Local Loopback, Digital Loopback or Pattern Generation and checking) is running. It is off if no test is running.
SYNC indicator
This indicator is on if the G.703 interface on the module is synchronised with the PCM equipment. It
is off if no signal is being received on the G.703 interface by the module.
AIS indicator
This indicator blinks Alarm is received on the G.703 interface.
ERR indicator
During the Pattern generation and verification test (see Sec. I.4) this indicator flashes every time
the module detects a mismatch between the received pattern and the transmitted pattern.
DI indicator
This indicator is on if data inversion is configured on the port.
I.4 DIAGNOSTIC SWITCHES ON THE 64 KBPS G.703 MODULE

Three push button switches are provided on the front fascia for initiating and terminating diagnostic
tests. The functions of these switches are described below:
PATT switch
This switch is used to initiate and terminate the Pattern generation and Verification diagnostic test.
When this switch is pressed:
- I.3 -
w Instead of sending the regular multiplexer data to the G.703 interface, a local "Pattern
Generator" is logically connected to the G.703 transmit. The pattern generator continuously
generates a 2047 bit pseudo-random pattern (called 211-1 pattern) which is then encoded into
consecutive 8-bit words and sent on the G.703 interface.
w The data received on the G.703 receive path is given to a checker which tries to verify whether
the received data bit sequence is similar to the 2047 bit pseudo-random pattern. If it is, the
checker locks itself to the received data and continuously verifies whether the received pattern
has the same sequence as the transmitted sequence. If there is a mismatch between the two,
for every bit in mismatch, the front panel LED indicator "ERR" (see Sec. I.3) is flashed.
Fig. I.3 shows the operation during Pattern generation and verification test.
CYGNUS 517
Receive from
multiplexer section Pattern Generator
User devices
.
.
COD module
Transmit to
Multiplexer section multiplexer section
Pattern Checker
Transmit to G.703
Receive from G.703
Fig. I.3 Pattern generation and verification test

LL switch
When this switch is IN, the G.703 interface of the CYGNUS 517 loops the data received by it from
the multiplexer section of the unit back to the multiplexer section. See Fig. I.4. This should result in
flashing of the ADERR and TEST indicator on the multiplexer section (see Sec. 5.4).
Receive from
multiplexer section
User devices
CYGNUS 517
Transmit to G.703
.
.
COD module
Transmit to
Receive from G.703
Fig. I.4 LL Loopback

NOTE
This loop back can also be initiated and terminated by setting Modem Local loop back
ON by using SET CP LPBK ML supervisory command (see Loop back in Sec. 3.3.1)
DL switch
When this switch is IN, data received on the 64 kbps G.703 interface is sent back to the G.703 line
just before it handing over to the multiplexer section. See Fig. I.5.
Receive from
multiplexer section
User devices
CYGNUS 517
.
.
COD module
Transmit to
Fig. I.5 DL Loopback
- I.4 -
Transmit to G.703
Receive from G.703
Appendix J
2 MBPS G.703 (E1) INTERFACE MODULE
J.1 PCBs AND CABLES
The 2 Mbps G.703 module (E1 module) consists of two PCBs. PCB P/N 100-0208 is inserted into
the CYGNUS 517 chassis from the front of the unit and PCB P/N 100-0205 is inserted from the rear
(see Fig. J.1). The front PCB contains the main circuit. It also provides LED indicators and
diagnostic switches (see Fig. J.3). This PCB also supports a piggybacked PCB (PCB P/N
100-0209) which contains a number of switches used for configuring the operation of the E1`
module (see Sec. J.1) below.
the E1 module connects to the main PCB. A flat ribbon cable (FRC) is used to connect the signals
from Composite Port 1 or 2 of the main PCB (Connectors CN5 or CN6 on the main PCB - see Fig.
B.4) to connector CN1 on the rear PCB of the E1 module. Power is supplied to the E1 module
through connector CN2 on the rear PCB. A cable harness from this connector to CN8, CN9 or
CN12 connector of the main PCB is used for this purpose. An earthing wire is also provided on the
rear PCB. The lug at the end of this wire should be fixed to the brass block provided on the base of
the unit with a M3 screw.
The module is connected to the PCM interface providing the G.703 connection via a 5-way terminal
block located on the rear fascia. Two terminals are provided for Transmit Data, two for Receive
Data and one for Earth. See Fig. J.3.
O 1
N
CMS 100-0208 EC041225
SW1
O 1
N
SW2
O 1
N
SW3
O 1
N
SW4
O 1
N
SW5
CMS 100-0209
EC041225
O 1
N
SW6
J8
J3
CMS 100-0205
EC041009
CN2
CN1
To CN1
J3
To CN2
J1

CN8, CN9 or CN12)

Earthing wire
(Connects to brass
Fig. J.1 2 Mbps G.703 module (E1 module) - PCBs and cables
J.2 CONFIGURING THE E1 MODULE

The main PCB P/N 100-0208 has a few jumpers on it. None of these jumpers is user configurable. These jumpers (see fig. J.1 for jumper locations) should always be in the factory
default setting shown below:
J1: IN; J3: OUT; J8: 1-2 IN
- J.1 -
2 Mbps G.703 (E1) interface module
The E1 Module is configured using 48 switches located on the piggybacked PCB P/N 100-0209
(see Fig. J.1). These switches are organised as six groups of 8 switches each. The functions of
these switches are described in Table J.1.
TABLE J.1
Functions of switches on PCB P/N 100-0209
DIP
Switch
Group
SW1
OFF
ON
OFF
ON
Switch No.
4
5
Function
6
OFF
ON
ON
ON
ON
ON
OFF
OFF
ON
ON
OFF
ON
OFF
ON
ON
ON
ON
SW2
ON
OFF
OFF
ON
ON
SW3
SW4
SW5
SW6
TS8*
TS16*
TS24*
TS1*
TS9*
TS17*
TS25*
TS2*
TS10*
TS18*
TS26*
TS3*
TS11*
TS19*
TS27*
TS4*
TS12*
TS20*
TS28*
TS5*
TS13*
TS21*
TS29*
TS6*
TS14*
TS22*
TS30*
TS7*
TS15*
TS23*
TS31*
Selects Recovered Clock Mode

Selects Internal Clock Mode
Turn DTE Data Inversion On
Turns DTE Data Inversion Off
Unused, should be ON
Unused, should be ON
Unit operates in Cascaded mode
Non-cascaded mode; Idle pattern: 3Fh
Non-cascaded mode; Idle pattern: 7Fh
Non-cascaded mode; Idle pattern: FFh
Unused; should be ON
Should always be OFF
CRC4 Error checking on (PCM30C or
PCM31C operation)
CRC4 Error checking off (PCM30 or
PCM31 mode)
Should always be ON (this endures that
the E1 facility is operated in framed mode)
Specifies the time slot of the E1 stream
which is to be used by the unit.
*: If the corresponding switch is OFF, the
time slot is selected by the unit; If it is ON,
the time slot is not selected by the unit.
Default setting: TS1 is selected.
Time slot selection

The E1 interface in the CYGNUS 517 is meant for operation with a framed E1 stream. It can extract
specific 64 kbps time slot from this framed stream for its use. The specific 64 kbps time slot used
by the CYGNUS 517 out of this E1 stream can be selected through switches 3,4,5 and 6 as
described above. The factory default setting is for selecting TS1. Note that selection of more than
one slot will result in selecting a bandwidth higher than 64 kbps, which is not a design specification
for the CYGNUS 517.
Clocking Mode
In Recovered Clock mode the E1 module in the CYGNUS 517 recovers the clock from the signal
that it receives on the E1 interface and uses the clock for sending data back to the E1 interface. In
Internal Clock mode the CYGNUS 517 uses an internally generated clock to send data to the E1
interface. Factory default setting is Recovered Clock mode.
NOTE
In case the CYGNUS 517 has to operate on an unframed E1 circuit, or when two
CYGNUS 517 units are required to be connected directly over copper wire, the clock
should be selected as internal at least on one of the units. The other unit may be
programmed for internal or recovered clock. When the E1 service is framed service, clocking should be selected as recovered clock. Consult the E1 service provider before making
the clocking mode and slot selection configuration.
- J.2 -
DTE Data Inversion

If DTE Data Inversion is selected the E1 interface in the CYGNUS 517 inverts each bit of the
multiplexed data stream before sending it on the E1 interface. It also inverts the data in the bit
stream received from the E1 interface before demultiplexing it. If data inversion is not selected, the
bit stream in both directions is passed without inverting it. Factory default setting is DTE Data
Inversion off.
CRC4 Error Checking
ITU-T standard G.704 specifies a mechanism which allows a device connected to a framed E1
stream to determine whether incoming E1 frames have been received without error or not. For this
purpose G.704 specifies how a cyclic redundancy checksum (CRC) may be inserted into slot 0 of
the E1 frames by the transmitter, to allow the receiver to verify whether an data errors have
occurred on the channel between it and the sender. If CRC4 Error Checking is selected as
described in Table J.1 the E1 interface in the CYGNUS 517 verifies the CRC of the incoming E1
frame to see if the frame is received without errors. It also inserts the CRC in each outgoing frame.
Factory default setting is CRC4 Error Checking off.
Cascaded Mode
The E1 interface of the CYGNUS 517 can be cascaded with other DTEs having E1 interface. This
allows multiple DTEs at a location to be connected to a single framed E1 stream as shown in Fig.
J.2 below.
PCM E1 interface
DTE E1 interfaces
TX
RX
TX
RX
TX
RX
DTEs
Fig. J.2 Cascaded Mode operation on E1 interface

For cascaded mode operation to be possible all the DTEs to be connected to the E1 stream must
support cascaded mode operation, and the specific slots used by each DTE must also be configured on it. When configured for cascaded mode operation, the E1 interface on the CYGNUS 517
forwards the time slots from the incoming E1 stream which are not used by it to the next device in
the chain without disturbing the data in these slots.
As mentioned above, in cascaded mode operation the CYGNUS 517 E1 interface does not disturb
the data in the slots not used by it. However in non-cascaded mode of operation the interface
inserts an idle pattern into all the time slots not used by it. The idle pattern itself can be selected
as described in the table above.
In cascaded mode the slot selection for each CYGNUS 517 in cascade need to be different, matching with that of their respective remote units. Also, if the E1 facility being used is unframed, one and
only one out of all the CYGNUS 517 units taking part in the cascaded configuration (local or
remote) should be programmed for internal clocking mode. The pattern test may be carried out in
cascaded mode by putting all the cascaded unit in pattern test simultaneously.
The factory default setting of this parameter is non-cascaded mode, with idle pattern as FF hex.
The rear PCB in the E1 Module (PCB P/N 100-0205) has a configuration jumper on it. The function
of the jumper is described in Table J.2.
- J.3 -
Function
Shorting Earth and
Signal Ground
TABLE J.2
Selected
Selection Details
Default setting
by
J3
2-3 In. Signal
and Earth are shorted Ground and Earth Ground and Earth
through 100 Ohm
are directly
are shorted
resistor
shorted
J.3 LED INDICATORS ON THE E1 MODULE

Fig. J.3 shows the fascia panels for the E1 interface at the front and back of the CYGNUS 517
when the module is installed in the unit.
A description of the front panel indicators is given below.
T/DFLT Indicator
This indicator is on if the unit starts with default parameters at power on. It flashes if any diagnostic
test is activated on the E1 module.
PWR indicator
ALARM indicator
This indicator flashes continuously if the system alarm is raised.
RXD indicator
This indicator flashes when the multiplexers receives data from the line.
G.703 I/F
2 Mb G.703 Module
T/DFLT
PWR
ALARM
VLINK
VAD
ON
AT FF
RXD
LINK
P O
T
PA
L
LC
E1 INE
L
E1
J
R IN
ER LL
E
DT
TXD
RX
ERR
FXS/FXO
IFOK
DIAG1
INT
TX
DIAG2
PRI
R
CL
FF DL
E
DT
DI
DIAG3
SEC
DIAG4
CYGNUS 517
CYGNUS 517
Front fascia
Back fascia
Fig. J.3 E1 module - front and back fascias
- J.4 -
LINK indicator
This indicator is on as long as the receive signal is present and frame synchronisation is not lost on
the E1 interface. It is off if there is no receive signal on the E1 interface. It flashes if there is any
loss of frame synchronisation.
TXD indicator
ERR indicator
This indicator flashes on occurrence of E1 frame related errors such as CRC error, FEBE error or
PRBS test pattern error. When PRBS pattern test is running this indicator glows as long as there is
no pattern synchronisation. This indicator also flashes if AIS is received on the E1 interface.
IFOK indicator
CYGNUS 517 main PCB and the E1 module. It is on when DTR from the multiplexer section is
active, and the connected channel in the multiplexer section is selected for V.35 interface. It flashes
when DTR is active and the connected channel in the multiplexer section is selected for V.24 interface. The indicator is off when DTR from the multiplexer section is inactive.
DIAG 1, 2, 3,4 indicators
These four indicators are used for off-line debugging purpose. They are not used during normal
operation.
INT indicator
This indicator is on when the E1 interface in the CYGNUS 517 is configured for internal clock
mode. It is off if the mode selected is recovered clock.
PRI indicator
This indicator is on if the E1 module is connected to the Primary channel of the multiplexer section.
SEC indicator
This indicator is on if the E1 module is connected to the Secondary channel of the multiplexer
section.
DI indicator
J.4 DIAGNOSTIC SWITCHES ON THE 2 MBPS E1 MODULE

Four push button switches are provided on the front fascia for initiating and terminating diagnostic
PAT ON/PAT OFF Switch
When this switch is pressed:
w Instead of sending the regular multiplexer data to the E1 interface, a local "Pattern Generator" is
logically connected to the G.703 transmit. The pattern generator continuously generates a (215-1)
bit pseudo-random pattern on all slots (including the slot selected for CYGNUS 517 data) which
is then encoded into consecutive 8-bit words and sent on the E1 interface.
w The data received on the E1 receive path on all slots is given to a pattern checker which tries to
verify whether the received data bit sequence is similar to the (215-1) bit pseudo-random pattern.
If it is, the checker locks itself to the received data and continuously verifies whether the received
pattern has the same sequence as the transmitted sequence. If there is a mismatch between the
two, for every bit in mismatch, the front panel LED indicator "ERR" (see Sec. J.3) is flashed.
- J.5 -
Fig. J.4 shows the operation during Pattern generation and verification test.
CYGNUS 517
Receive from
User devices
.
.
E1 module
Transmit to
Multiplexer section multiplexer section Pattern Checker
Transmit to E1
Receive from E1
Fig. J.4 Pattern generation and verification test

E1 LCL/E1 LINE Switch
This switch has different functions depending on whether the PAT ON/PAT OFF switch is pressed
or not.
If PAT ON/PAT OFF switch is IN (i.e., the test pattern is being sent on the E1 interface) when the
E1 LCL/E1 LINE switch is pressed, a local loopback is provided on the E1 interface, i.e., the data
meant to go out on the E1 interface is looped back to the unit. See Fig. J.5.
If PAT ON/PAT OFF switch is OUT (i.e., no test pattern is being sent on the E1 interface) when the
E1 LCL/E1 LINE switch is pressed, a remote loopback is provided on the E1 interface, i.e., the data
being received on the E1 interface is looped back to the line at the E1 interface itself. See Fig. J.6.
Receive from
multiplexer section
User devices
CYGNUS 517
Transmit to E1
.
.
E1 module
Transmit to
Receive from E1
Fig. J.5 E1 LCL Loopback
Receive from
multiplexer section
User devices
CYGNUS 517
.
.
E1 module
Transmit to
Transmit to E1
Receive from E1
Fig. J.6 E1 Line Loopback

ERR INJ/DTE LL Switch
This switch also has different functions depending on whether the PAT ON/PAT OFF switch is
pressed or not.
If PAT ON/PAT OFF switch is IN (i.e., the test pattern is being sent on the E1 interface) the unit
inserts a pattern error in the pattern being sent to the E1 interface every time the ERR INJ/DTE LL
switch is pressed. If the E1 interface is looped back somewhere in the channel this should result in
the ERR indicator on the front panel flashing every time this switch is pressed and released.
If PAT ON/PAT OFF switch is OUT (i.e., no test pattern is being sent on the E1 interface) when the
ERR INJ/DTE LL switch is pressed, the E1 interface of the CYGNUS 517 loops the data received
- J.6 -
by it from the multiplexer section of the unit back to the multiplexer section. See Fig. J.7. This
should result in flashing of the ADERR indicator on the multiplexer section (see Sec. 5.4).
Receive from
multiplexer section
User devices
CYGNUS 517
Transmit to E1
.
.
E1 module
Transmit to
Receive from E1
Fig. J.7 DTE LL Loopback

NOTE
FF CLR/DTE DL Switch
Like the above two switches this switch also has different functions depending on whether the PAT
ON/PAT OFF switch is pressed or not.
If PAT ON/PAT OFF switch is IN (i.e., the test pattern is being sent on the E1 interface) the unit
clears the data buffer through which the E1 interface receives data from the multiplexer section
every time this switch is pressed and released.
If PAT ON/PAT OFF switch is OUT (i.e., no test pattern is being sent on the E1 interface) when this
switch is pressed, a digital loopback is provided; i.e., data is extracted from the specified time slot
of the received E1 frames and is sent back to the E1 line just before it handing over to the multiplexer section. See Fig. J.8.
Receive from
multiplexer section
User devices
CYGNUS 517
.
.
E1 module
Transmit to
Fig. J.8 DTE DL Loopback
- J.7 -
Transmit to E1
Receive from E1
Appendix K
64 KBPS IDSL MODEM MODULE
K.1 PCBs AND CABLES
The 64 kbps IDSL modem module (IDSL module) consists of two PCBs. PCB P/N 100-0214 is
inserted into the CYGNUS 517 chassis from the front of the unit and PCB P/N 100-0205 is inserted
from the rear (see Fig. K.1). The front PCB contains the main circuit. It also provides LED indicators and diagnostic switches (see Fig. K.2).
The 64-kbps IDSL module works opposite a CYGNUS 606 64-Kbps baseband modem or CYGNUS
609 64-kbps baseband modem, with 64 Kbps COD interface to connect to a local PCM exchange
through which the 64 kbps line is extended. Alternatively, in case terminal connectivity using two
CYGNUS 517 units is desired to be established in a local area over copper wire, the same may be
done by connecting two CYGNUS 517 units, each having an IDSL interface.
the IDSL module connects to the main PCB. A flat ribbon cable (FRC) is used to connect the
signals from Composite Port 1 or 2 of the main PCB (Connectors CN5 or CN6 on the main PCB see Fig. B.4) to connector CN1 on the rear PCB of the E1 module. Power is supplied to the E1
module through connector CN2 on the rear PCB. A cable harness from this connector to CN8, CN9
or CN12 connector of the main PCB is used for this purpose. An earthing wire is also provided on
the rear PCB. The lug at the end of this wire should be fixed to the brass block provided on the
base of the unit with a M3 screw.
The module is connected to the PCM interface providing the IDSL connection via a 3-way terminal
block located on the rear fascia. See Fig. K.2.
SW1
O 1
N
CMS 100-0205
EC041009
CN2
4321
CN1
To CN1
CMS 100-0214 EC041230
J7
J8
J6
J3
To CN2
1
1

CN8, CN9 or CN12)

Earthing wire
(Connects to brass
Fig. K.1 64 kbps IDSL module - PCBs and cables
K.2 CONFIGURING THE 64 KBPS IDSL MODEM MODULE

The module is configured through switches and jumpers provided on the front and the rear PCBs.
These are described below.
On the front PCB P/N 100-0214 a 4-way DIP switch (SW1) and some jumpers are provided for
configuration purpose. Their functions are described in Table K.1.
- K.1 -
Switch Position
SW1-1
SW1-2
SW1-3
SW1-4
Jumper
J6
J7
J8
64 kbps IDSL modem module
TABLE K.1
DIP Switch SW1 on front PCB P/N 100-0214 EC 041230
Function
Details
CLOCK mode
CLOSE: Internal clock
OPEN: Line slave
selection
(LT Mode)
(NT Mode)
DATA INVEROPEN: Enable data inversion
CLOSE: Disable Data inverSION selection
sion
Should always be OPEN
Off-line diagnosOPEN: Off-line diagnostic
CLOSE: Normal operation
tics selection
operation (not for user)
TABLE K.2
Configuration jumpers on front PCB P/N 100-0214 EC 041009
Function
Details
Selection of CTS functionality 1-2 IN : CTS follows RTS
2-3 IN: CTS always active
Selection of LT/NT Mode
2-3 IN : LT Mode
1-2 IN : NT mode
Selection of LT/NT Mode
2-3 IN : LT Mode
1-2 IN : NT mode
Clock Mode
When the IDSL module is to be connected to a CYGNUS 606/G.703 IDSL modem at the other end
(e.g., at the telephone exchange) which provides the clock for IDSL transmission, Clock Mode
should be selected as Line Slave (NT Mode). If the IDSL module is to provide clock to the remote
modem (e.g., when it is connected to a CYGNUS 517 IDSL module at the other end), its clock
mode should be selected as Internal (LT Mode).
When two units of CYGNUS 517 are required to be connected directly to each other over a copper
wire pair through their respective IDSL interfaces, the IDSL card of one unit should be programmed
for Internal clock (LT mode) and that of the other unit should be programmed for Line slave (NT
mode).
Data Inversion
If Data Inversion is selected the IDSL interface in the CYGNUS 517 inverts each bit of the multiplexed data stream before sending it on the IDSL line. It also inverts the data in the bit stream
received from the line. If data inversion is not selected, the bit stream in both directions is passed
without inverting it. Factory default setting is DTE Data Inversion off.
Off-line diagnostics
This switch can be used to put the IDSL modem in an off-line diagnostics mode. In normal operation this witch should be Close.
The rear PCB in the IDSL Module (PCB P/N 100-0205) has a configuration jumper on it. The
function of the jumper is described in Table K.3.
Function
Shorting Earth and
Signal Ground
TABLE K.3
Selected
Selection Details
Default setting
by
J3
2-3 IN: Signal
and Earth are shorted Ground and Earth
Ground and Earth
through 100 Ohm
are directly shorted
are directly shorted
resistor
- K.2 -
K.3 LED INDICATORS ON THE 64 KBPS IDSL MODEM MODULE

Fig. K.2 shows the fascia panels for the 64 kbps IDSL modem module at the front and back of the
CYGNUS 517 when the module is installed in the unit.
IDSL I/F
64 kb IDSL Module
TST
PWR
VLINK
VAD
T
PA
RL
LNERR
RXD
ACT
TXD
ERR
FXS/FXO
IFOK
L
I
N
E
LL
LT
LL
RL
PRI
DL
DI
SEC
CYGNUS 517
CYGNUS 517
Front fascia
Back fascia
Fig. K.2 64 kbps IDSL modem module - front and back fascias
A description of the front panel indicators is given below:
TST indicator
This indicator is on when any diagnostic test (Local Loop back, Remote Loop back, Digital Loop
back or Pattern Generation and checking) is running. It is off if no test is running.
PWR indicator
LNERR indicator
This indicator flashes if the IDSL module detects an internal checksum error during operation.
RXD indicator
This indicator flashes when the multiplexer receives data from the line.
ACT indicator
This indicator is on if the modem is synchronised with the counterpart modem at the other end of
the line, i.e., when the IDSL connection to the counterpart modem is ACTive.
TXD indicator
ERR indicator
During the Pattern generation and verification test (see Sec. K.4) this indicator flashes every time
the module detects a mismatch between the received pattern and the transmitted pattern.
IFOK indicator
CYGNUS 517 main PCB and the 64 kbps IDSL modem module. It is on when the IDSL module
- K.3 -
detects that the DTR signal from the main PCB is active, and when network port interface on the
main PCB is configured as V.35 (see Sec. 3.1). The indicator blinks steadily if the network port
interface is configured as RS-232. The indicator is off if the IDSL module does not detect an active
DTR signal from the network port interface of the main PCB.
LL indicator
This indicator is on if the IDSL module is configured for Local Loopback test (see Sec. K.4).
LT indicator
This indicator is on if Internal (LT) clock mode is selected on the IDSL module (See Sec. K.2). It is
off if Line Slave (NT) clock mode is selected on the module.
RL indicator
This indicator is on if the IDSL module is configured for Remote Loopback test (see Sec. K.4).
PRI indicator
This indicator is on if the IDSL module is connected to the primary channel of the multiplexer
section.
SEC indicator
This indicator is on if the IDSL module is connected to the secondary channel of the multiplexer
section.
DI indicator
K.4 DIAGNOSTIC SWITCHES ON THE 64 KBPS IDSL MODULE

Four push button switches are provided on the front fascia for initiating and terminating diagnostic
PATT switch
Fig. K.3 shows the operation during this test. When this switch is pressed:
w Instead of sending the regular multiplexer data to the IDSL line, a local "Pattern Generator" is
logically connected to the IDSL transmit. The pattern generator continuously generates a 2047
bit pseudo-random pattern which is then encoded into consecutive 8-bit words and sent on the
line.
w The data received from the line is given to a checker which tries to verify whether the received
data bit sequence is similar to the 2047 bit pseudo-random pattern. If it is, the checker locks
itself to the received data and continuously verifies whether the received pattern has the same
sequence as the transmitted sequence. If there is a mismatch between the two, for every bit in
mismatch, the front panel LED indicator "ERR" (see Sec. K.3) is flashed.
CYGNUS 517
Receive from
User devices
.
.
IDSL module
Transmit to
Pattern Checker
Transmit to line
Receive from line
Fig. K.3 Pattern generation and verification test
- K.4 -
LL switch
When this switch is IN, the IDSL modem loops the data received by it from the multiplexer section
of the unit back to the multiplexer section. See Fig. K.4. This should result in flashing of the
ADERR indicator on the multiplexer section (see Sec. 5.4).
Receive from
multiplexer section
User devices
CYGNUS 517
Transmit to line
.
.
IDSL module
Transmit to
Receive from line
Fig. K.4 LL Loopback

NOTE
RL switch
When this switch is IN, the local IDSL modem module installed in the CYGNUS 517 requests the
counterpart modem (e.g., CYGNUS 606 or another IDSL module installed in a CYGNUS 517) at the
other end of the copper local loop, to return the data sent by the local module. Once the remote
modem grants this loop the data sent by the local CYGNUS 517 unit comes back to it. See Fig. K.5.
This should result in flashing of the ADERR indicator on the multiplexer section (see Sec. 5.4).
Receive from
multiplexer section
User devices
CYGNUS 517
CYGNUS 606 modem/

CYGNUS 517 IDSL module
.
.
IDSL module
Transmit to
multiplexer section
Multiplexer section
Local loop
Fig. K.5 RL Loopback

NOTE
This loop back can also be initiated and terminated by setting Modem Remote loop back
ON by using SET CP LPBK MR supervisory command (see Loop back in Sec. 3.3.1)
DL switch
When this switch is IN, data received by the IDSL modem from the line is sent back to the line just
before handing it over to the multiplexer section. See Fig. K.6.
Receive from
multiplexer section
User devices
CYGNUS 517
.
.
IDSL module
Transmit to
Fig. K.6 DL Loopback
- K.5 -
Transmit to line
Receive from line
Appendix L
HARDWARE MOUNTING INFORMATION
1. 2 sets of handles, handle mounting bushes and handle mounting screws are supplied along with
the unit in the packet labelled Handles.
2. Fix one handle (along with bushes) to the panel at locations A1 and A2 with the handle mounting
screws supplied along with the handle (see Figs. L.1 and L.2). Note that the handle comes from
the front and the screw from the rear of the panel.
3. Fix the other handle to the panel at locations B1 and B2 with the M4 mounting screws in a similar
manner.
C1
A1
64 kb G.703 Module
2 Mb G.703 Module
TST
TXD
RXD
T ON
PA OF F
T
PA
IFOK
INT
L
LC
E
E1
LIN
E1
IN J
R
ER LL
E
DT
DI
SEC
CYGNUS 517
VAD
PWR
TX
RX
TP1
TP2
TP3
TP9
TP10
TP11
TP4
TP5
TP6
TP7
TP12
TP13
TP14
TP15
PRIMARY
TP8
DCD FLAG PRI-SEL
SECONDARY
CHANGEOVER
DCD FLAG SEC-SEL
AUTO
MST CTEST
FXS/FXO
IFOK
BUZZ
DIAG1
INT
LINK LNERR ADERR
DIAG2
V2
V516
MXERR ENBL
TP16
CLK-INV
V.35
V.24
CLK-INV V.35
V.24
MAN
SLV DMODE
PRI
PRI
DL
A2
C2
VLINK
TXD
ERR
ERR
LL
LINK
D1
B1
SUP
FXO
ALARM
RXD
CYGNUS 517
FXS
PWR
AIS
SYNC
PA
Voice Module
T//DFLT
PWR
R
CL
FF E DL
DT
DIAG3
SEC
DI
DIAG4
CYGNUS 517
DIS-BUZZ
SEC-SEL
MANUAL
SLV
CYGNUS 517
CYGNUS 517
B2
D2
Fig. L.1 Location of handle fixing holes
Handle
Bushes
FXS
TP1
TP2
TP3
TP4
TP5
TP6
TP7
TP8
TP9
TP10
TP11
TP12
TP13
TP14
TP 1 5
2 Mb G.703 I/F
TP16
64 kb G. 703 I / F
FXO
O H 1
FXS
ON
+24V
RX
RX
TX
TX
Side flange
-24V
O H 2
FXO
DESIGNED AND M ANUF ACT URED BY CYGNUS M ICROSYST EM S (P) L T D., HYDERABAD, INDIA
CYGNUS 517
CYGNUS 517
CYGNUS 517
M4 CSK
screws
Fig. L.2 Fixing handles to the flange
NOTE
The CYGNUS 517 can be mounted in a standard 19 inch rack. To mount the unit in the
rack use the mounting hardware supplied along with the rack to fix the unit at locations C1,
C2 and D1, D2 (Fig. L.1). Before mounting the unit into the rack remove the four feet
mounted at the base of the unit.
- L.1 -
Appendix M
LAN BASED REMOTE MANAGEMENT OPTION
A LAN (Local Area Network) based Remote Management Module (RMM) is available as an option
for the CYGNUS 517. Using this module it is possible to:
Access the units internal supervisory function via TELNET over an ethernet LAN
Read the multiplexers link up status and line alarm status from a remote SNMP management
station via an ethernet LAN
Have the unit generate and send SNMP TRAPs via an ethernet LAN to a specified IP address
(typically to a central Network Management Station) on occurrence of specified events (e.g.,
power on, link failure or restoral)
The ethernet LAN interface is 10/100 Base-T compatible, and is accessed via a RJ-45 UTP port on
the front of the unit.
CYGNUS 517
SUP
ACCESS
SEL

TP1
TP2
TP9 TP10
TP3
TP11
TP4
TP12
TP5
TP13
TP6
TP14
TP7
TP15
PRIMARY
TP8
TP16
DCD FLAG PRI-SEL
CLK-INV
V.35
V.24
SECONDARY
DCD FLAG SEC-SEL
CLK-INV V.35
SEC-SEL
V.24
CHANGEOVER
AUTO
MST CTEST
MAN
MANUAL
SLV DMODE
SLV
TERM ACC
LAN ACC
S
SUP
M
100 M
LINK/ACT
10 M
LAN
CYGNUS 517
REMOTE MANAGEMENT MODULE
LAN based Remote Management Module
Fig. M.1 Location of LAN based Remote Management Module

In units with RMM it is possible to access the supervisory function either from a terminal connected
to its RS232 supervisory port, or via its LAN port. The SUP ACCESS SEL recessed push button
switch on the module is used to select between these two modes. When this switch is in OUT
position, the Terminal Access Mode is selected. When it is pressed IN, LAN Access Mode is
selected. The two access modes are described below:
w Terminal Access Mode: LED indicator TERM ACC is ON in this mode. The supervisory function
can only be accessed from an asynchronous RS232 terminal connected to the 25 pin D-type
SUP port connector on the front panel. All supervisory commands described in Chapter 3 can
be given normally from this asynchronous terminal.
w LAN Access Mode: LED indicator LAN ACC is ON in this mode. The supervisory function can be
accessed from a PC by establishing a TELNET session with the CYGNUS 517 via the LAN
based Remote Management modules LAN port. The 25 pin D type SUP port is used to configure the RMM - it cannot be used to access the units supervisory function, and its default setting
is 19200 bps, no parity, 8 data bits, 1 stop bit.
- M.1 -
Introduction
LED indicators R, S and M on the front panel are used to indicate whether internal cable
connections between the RMM and the rest of the unit are proper. All three indicators should be ON
for proper functioning.
The figures below show block diagrams of how supervisory access is achieved in both LAN based
and terminal based access.
BLOCK DIAGRAM OF LAN BASED ACCESS TO CYGNUS 517 SUPERVISOR
( PC with Telnet software used for configuration of CYGNUS 517 over LAN
Terminal T used for configuration of LAN Based Remote Management Module)
SNMP
Manager
CYGNUS 517
Status for SNMP
Reporting
LAN
TCP/IP
NETWORK
10/100 Base T
SUP ACCESS
SEL SWITCH
PC with
Telnet s/w
LAN to Serial
serial
(Telnet) 4800,n,8,1
Module 19200,n,8,1
Config
port
Internal
Sup
Function
Main board
Terminal
T
Module
RS-232
25
pin
19200,n,8,1
Sup 'D'
Port
Serial
BLOCK DIAGRAM OF TERMINAL ACCESS TO CYGNUS 517 SUPERVISOR

Terminal T used for configuration of CYGNUS 517
SNMP
Manager
CYGNUS 517
Status for SNMP
Reporting
NETWORK
10/100 Base T
SUP ACCESS
SEL SWITCH
PC with
Telnet s/w
Terminal
T
RS-232
LAN to
serial
(Telnet)
Module
Config
port
25
pin
4800,n,8,1
Sup 'D'
Port
- M.2 -
Serial
Module
Serial
4800,n,8,1
LAN
TCP/IP
Internal
Sup
Function
Main board
Introduction
Configuring the RMM

- Connect an asynchronous RS232 compatible terminal to the SUP port of the unit. Ensure that the
terminal is configured for 19200, n, 8, 1 (19200 bits per second, no parity, 8 data bits, 1 stop bit).
- Press SUP ACCESS SEL switch IN. The LAN ACC LED indicator should come ON.
The terminal can now be used to configure the LAN based Remote Management Module described
below.
IP related settings
Consult your network administrator and decide the IP address and Default Gateway address to be
assigned to the RMM.
The RMM provides a menu based configuration interface. Using this interface,
Navigate to:
Navigate to:
Navigate to:
Main Menu > Network settings > IP address , and set it to the assigned IP address.
Main Menu > Network settings > NETMASK, and set it to 255.255.255.0
Main Menu > Network settings > Gateway, and set it to the assigned Default
Gateway IP address
Serial port settings

Serial Port 1 on board the RMM internally connects the module to the regular Supervisory Port of
the CYGNUS 517. The settings of Serial Port 1 must therefore match the settings of the multiplexers Supervisory Port. For this, navigate to:
Main Menu > Serial settings > Port 1
and set the communication parameters to match those of the units regular Supervisory Port. For
instance, if the regular supervisory port is set for 4800 bps, no parity, 1 stop bit, 8 data bits and no
flow control, set the parameters of the Remote Management Module to match these, as follows:
Baud rate
Data bits
Stop bits
Parity
Flow control
FIFO
Interface
: 4800
:8
:1
: None
: None
: Disable
: RS-232
SNMP related settings

The RMM allows the following status of the unit to be read over the TCP/IP network using SNMP
GET commands:
- Status of the multiplexers SUP ACCESS SEL switch
- Status of the multiplexers Link Alarm condition
- Status of the multiplexers logical Link with its counterpart multiplexer
The RMM maps these status as RS232 port status signals CTS, DSR and DCD on its Serial Port 1
interface. A SNMP management station on the network can read these status as the SNMP MIB
objects described below:
- M.3 -
Status being
reported
Introduction
RS232 signal of
Port 1 to which
this status is
mapped for reporting purpose
CTS
SNMP MIB Object

identifier for SNMP
GET command
Link Alarm status

of links (applicable for units with
automatic
changeover
option)
DSR
10.33.5.1.3.1.3
3 - off
2 - on
1 - none
Link status
DCD
10.33.5.1.3.1.6
3 -off
2- on
1- none
Status of SUP
ACCESS
SEL
switch
10.33.5.1.3.1.2
Possible values
of object
returned by
SNMP GET
command
3 - off
2 - on
1 - none
Description of value
3: Terminal Access selected

via SUP ACCESS SEL switch
2: LAN access selected
via SUP ACCESS SEL switch
3: Alarm on (Alarm raised)
2: Alarm off (No alarm)
Alarm On is reported only if
the unit has a built-in
changeover facility which is
configured for AUTO operation. Alarm will be reported as
ON if one or both links are
down, and OFF if both links
are up.
3: Link down
2: Link up
This status corresponds to the
status of the logical link
between the pair of counterpart CYGNUS 517 multiplexers.
To configure SNMP related settings on the RMM, navigate to:

Main Menu > Network settings, and set the parameters as follows
IP address
Netmask
Gateway
IP configuration
DNS server 1
DNS server 2
SNMP
SNMP community name
SNMP contact
SNMP location
Auto IP report to IP
Auto IP report to TCP port
Auto IP report period (seconds)
: <value> (Assigned IP address - discussed above)

: 255.255.255.0
: <value> (Assigned Gateway - discussed above)
: Static
: <value> (Specify the DNS address)
:
: Enable
: public
: <name> (Specify the contacts name)
: <location> (Specify the locations name)
:
: 4002
: 10
Once these settings are done the three status can be queried from the Management Station by
giving the SNMP commands. Typical of these commands would be as follows:
Snmpget <Module IP address> public 10.33.5.1.3.1.2
to know the setting of the Sup Access Sel switch
to know the Link Alarm status
To know status of logical Link between CYGNUS 517 and its remote counterpart
- M.4 -
Introduction
TRAP related settings

The RMM can also generate TRAP signals when certain specified events occur, and send these
TRAPs over the TCP/IP network to a specified Management Station. The events which can be
configured to generate TRAPs are:
- Cold start (when unit power is switched on)
- Warm start (when unit is reset by supervisory command)
- Change in Link Alarm status (when one or other link goes up or down)
- Change in logical Link status (when the multiplexers logical link with its counterpart multiplexer
goes up or down)
To configure TRAPs, navigate to:
Main Menu > Auto warning settings > Email and SNMP trap, and set the parameters as follows
Mail server
My server requires authentication
From email address
Email address 1
Email address 2
Email address 3
Email address 4
SNMP trap server IP or domain
:
: Disable
:
:
:
:
:
: <value>
(ignore)
(ignore)
(Give address of TRAP server)
Then navigate to
Main Menu > Auto warning settings > Event type, and select the events which you would like to
generate TRAPs
1. Cold start (Mail Off, Trap On) .
2. Warm start (Mail Off, Trap On)
3. DCD changed >>Port1
DCD changed (Mail Off, Trap On)
4. DSR changed >>Port1
DSR changed (Mail Off, Trap On)
(no e-mail on SNMP event, only trap)
(use this to configure TRAP on change in Link Alarm )

(use this to configure TRAP on change in logical Link
status)
NOTE: Link status read using SNMP GET command within thirty seconds of a Cold Start TRAP
may not reflect the correct value
TELNET access to the unit over LAN
Once the RMM is configured, and the SUP ACCESS SEL switch is set to LAN access, the supervisory function of the CYGNUS 517 can be accessed over the LAN using TELNET. The command to
access the unit via TELNET is:
telnet <IP address> 4001
The <IP address> is the address assigned to the module. 4001 is the fixed port for supervisory
access, corresponding to Serial Port 1 of the module (which is internally connected to the regular
supervisory port of the CYGNUS 517)
Note: 4001 is the socket address of the LAN monitoring module at which if TELNET/TCP access is
performed from a remote host, the supervisor of the CYGNUS 517 can be accessed. It is possible
to change the socket address to standard TELNET socket address 23. This may be achieved by
changing the Local TCP port address of the TCP server by appropriately programming the port 1:
Navigate to: Main Menu > Operating settings > Port 1
And set Local TCP port to 23.
- M.5 -
Appendix N
Additional Supervisory Commands in Software
Version 4.87
Version 4.87 of CYGNUS 517 software adds the optional facility of an LAN based Remote Management Module (RMM). This facility is described in Appendix M. This version of the software also
provides one extra programmable system parameter, and modifies the functioning of an existing
command.
Additional programmable system parameter
The extra programmable system parameter is SYS NAME. This is an arbitrary string of up to 9
printable characters. This string can be set to a descriptive name which identifies the unit uniquely.
The command to set the parameter is
Syntax: SET SYS NAME <system name> [RETURN]
Any lower case letters specified here will automatically be converted to upper case. Like any other
parameter the SYS NAME will take effect only after the parameters are stored in non volatile
memory (using STORE command) and the unit is reset.
To read the SYS NAME in effect on the unit the command is:
Syntax: OLD SYS NAME [RETURN]
To read the SYS NAME specified using a SET command, before the parameters are stored, the
command is:
Syntax: NEW SYS NAME [RETURN]
The default value of SYS NAME is DEFAULT00
Commands modifed
The STATUS command now shows two additional fields as described below.
1. NAME: <system name> - the SYS NAME programmed on the unit is displayed here.
2. LAN MON: <Response>, where
<Response> is:
No if the LAN based RMM is not installed in the unit
Yes, Sup on LAN if the RMM is installed, and the front panel SUP ACCESS SEL switch on
the RMM is set to LAN Access Mode (see App. M)
Yes, Sup on Term if the RMM is installed, and the front panel SUP ACCESS SEL switch on
the RMM is set to Terminal Access Mode (see App. M)
- N.1 -
Feedback Form
Please take a few minutes to fill this form and send it to us with your comments. This will help us
improve the quality of our products and documentation. We thank you for your cooperation.
1. Please give the following details regarding the unit(s):
(a) Serial Nos. of the units and date of purchase ________________________________________________________
(b) Are the units 8 port or 16 port ____________________________________________________________________
(c) Is a voice module installed? ______________________________________________________________________
(d) Is Automatic Link Changeover option installed? ______________________________________________________
(e) Are any telecom interfaces installed on the composite links? If so, which interfaces (64 kbps G.703, E1, 64 kbps IDSL)?
_______________________________________________________ _____________________________________
(f) Software/hardware versions installed in the unit (see Sec. 3.3.8): ROM_ID: _____________ HW_ID:_____________
2. Who installed the unit? __________________________________________________________
3. Did you encounter any problems during the installation? Please give brief details of the problem(s) and
also of how you solved the problem(s).
_________________________________________________________________________________
_________________________________________________________________________________
4. Did you need to refer to the manual at any time (during installation or later on)? If so, for what
information? Did you find the required information in the manual?
_________________________________________________________________________________
_________________________________________________________________________________
5. Did you need to contact Cygnus or your supplier/integrator for further information on installation or
usage? If so, what was your query? Was you query answered satisfactorily?
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
6. What further information should this manual contain to make it more effective?
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
7. Please give the page number and details of any mistakes that you found in this manual.
_________________________________________________________________________________
_________________________________________________________________________________
8. Please give the page number and details of any information that you found confusing or vague.
_________________________________________________________________________________
_________________________________________________________________________________
9. Please give your suggestions for improving the manual.
_________________________________________________________________________________
_________________________________________________________________________________
The feedback form may be sent to the Head, Technical Support Department, Cygnus Microsystems (P) Limited, 93,
Phase II, IDA Cherlapally, Hyderabad 500 051 or may be sent via e-mail to techsupport@cygnusmicro.com
CYGNUS 517 High Integration Statistical Multiplexer Users Manual P/N 200-0034 March 2008

Cygnus 517

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Cygnus 517

Transféré par

Droits d'auteur :

Formats disponibles

CYGNUS 517

Manual Part Number 200-0034

CYGNUS MICROSYSTEMS PRIVATE LIMITED

written permission from CYGNUS is forbidden.

Manual Revision History

Manual updated; Appendices I, J, K and L added

Appendices M & N added

Appendix A ............................................................................... A.1

Appendix J ............................................................................... J.1

1.2 CYGNUS 517 HIGH INTEGRATION STATISTICAL MULTIPLEXER

CYGNUS 517 Users Manual

hotline functionality allowing phone-to-phone, phone-to-EPABX and fax machine-to-fax machine

CYGNUS 517 Users Manual

1.2.2 Product description

HIGH INTEGRATION STATISTICAL MULTIPLEXER

TERMINAL PORT ACTIVITY

RMT T/DFLT ALRM DSBL

DCD FLAG PRI-SEL

DCD FLAG SEC-SEL

LINK LNERR ADERR

Unit & link status; port activity

Link changeover facility

Indicators & switches

Fig. 1.1 Typical CYGNUS 517 Front Panel

The front panel contains:

DESIGNED AND MANUFACTURED BY CYGNUS MICROSYSTEMS (P) LTD., HYDERABAD, INDIA

Terminal Ports 1-8

Terminal Ports 9-16

Fig. 1.2 Typical CYGNUS 517 Back Panel

CYGNUS 517 Users Manual

The back panel contains:

1.2.2.1 Terminal ports

1.2.2.2 Voice port

1.2.2.3 Composite port

CYGNUS 517 Users Manual

1.2.2.4 Supervisory port

Leased telecom lines

Fig. 1.3 Typical connectivity using CYGNUS 517

CYGNUS 517 Users Manual

Serial asynchronous start-stop

8 or 16 (ordering time option)

RS232-C (ITU-T V.24) on 25-pin D-type socket

Selectable: 50 - 19200 bps. Autospeed detection up to 9600 bps

Selectable: 5,6,7 or 8 bits; 1, 1.5 or 2 stop bits, odd, even or no parity

Selectable: through software (XON/XOF) or hardware (RTS/CTS) in both

Character echo can be selectively enabled for each TP

VOICE PORT (VP)

Selectable between FXS and FXO; on RJ-11 socket

Voice bit rate:

Selectable from 4.8 to 10.4 kbps

Up to 9.6 kbps; Group 3 fax protocol

COMPOSITE PORT (CP)

ITU-T X.25 Level 2 LAPB

Up to 64 kbps as per selected link interface

Error detection &

16-bit CRC with ARQ

CYGNUS 517 Users Manual

RS232/V.35 link interface specifications

25-pin D type male

TxD, RxD, TxClk, RxClk, DTR, DSR, DCD

Selectable between 1.2 kbps and 64 kbps

Selectable between NRZ and NRZI

Receive clock: external; Transmit clock: selectable as external or internal