All rights reserved. No part of this publication may be reproduced, stored in a retrieval
system, or transmitted, in any form by any means, electronic, mechanical, by
photocopying, recording, or otherwise without prior written permission.
Disclaimer
Information furnished in this manual is believed to accurate and reliable. However, no
responsibility is assumed for its use, or for any infringements of patents or other rights
of third parties that may result from its use.
Warning
This equipment utilizes voltages which are potentially dangerous and may be fatal if
contacted. Exercise caution when working with the equipment any time the protective
cover is removed.
The Networked Receiver Controller (NRC) is a single node network device capable of
simultaneously:
• controlling and configuring up to 8 attached receivers for data collection
• collecting and digitizing each receiver’s analog audio output signal
• formatting and routing the digitized receiver’s signal to an attached network client.
A simple diagram of the NRC system is shown below.
R
S
Networked Receiver Controller
CONTROL
DATA
CPU
NRC
Client
The NRC represents the server portion of a network based client/server architecture. NRC clients
connect and disconnect from the NRC via an Ethernet network connection as necessary. When
connected, a client has the ability to control, configure and collect digitized audio data from the
associated receiver.
Each receiver is physically connected to the NRC via an RS-232 command/control port and an
audio input port. The receiver’s analog audio output is connected to an A/D where it is sampled
at 16 KHz with 16 bit resolution. The resultant digitized audio signal is available for secondary
processing and distribution from the NRC as required. The default NRC configuration provides a
4 KHz band-limited, 8 KHz sampled data signal. This digital audio signal is available to the
NRC client through a simple packet based protocol, which aggregates samples into a single data
packet for forwarding to the client.
The NRC server is a 1 rack unit chassis system with the following front and back views.
In this chapter, the various features of the NRC will be discussed.
A channel defines a virtual connection between a client application and a receiver connected to
the NRC.
There are two types of channel connections which can be established to a receiver; a Primary
connection and a Piggy-back connection.
1. A Primary Connection
a. A Primary connection is established with a receiver when the receiver is free of
any other client connections.
b. A Primary connected client has full access and control of the receiver and its
resources.
2. Piggy-back Connection
a. A Piggy-back connection is established with a receiver when the receiver
currently has one or more other clients already attached to it.
b. A Piggy-back connected client cannot change any of the receivers settings,
although it can view the current receiver settings, and capture and format the
receivers audio output.
The NRC supports one Primary connection per receiver and multiple Piggy-back connections,
with the NRC able to support an aggregate of 64 simultaneous Primary/Piggy-back connections.
Audio Data Capture
The NRC uses an 8 channel PCI-based Analog/Digital converter card to digitize each receiver’s
audio output signal. Each receiver’s audio signal is digitized into 16-bit samples (14.8 effective
bits/sample) at a sampling rate of 16 KHz.
Each client attached to the receiver can receive a copy of this sampled audio data through a
simply packet based protocol, and can specify:
• the number of samples to be contained within a data packet
• the effective sampling rate of the data - either 8 KHz or 16 KHz.
• the audio data filtering option – 4 KHz LPF ON or OFF, and
• the packet time stamping – TAI64N ON or OFF
Sampling synchronization is achieved either via the NRC’s internal high precision crystal
oscillator circuitry or by a user provided external clock signal into the NRC’s EXT CLK port.
The user external clock signal, if used, should be a 50% duty cycle (TTL) square wave operating
at a frequency of 16 KHz.
The NRC abstracts the user from each receiver’s proprietary low-level communications protocol
by presenting a common receiver translation software tasking interface to the user. This common
software interface allows the user to task the receivers at a logical level without the need to
worry about how to implement this tasking. This allows a wide range of different receivers to be
tasked via the NRC in the same manner regardless of the number, model or configuration of the
receivers.
This receiver hardware abstraction allows the NRC:
• To be easily programmed to connect to almost any receiver with an audio output.
• To accommodate being connected to different receiver models simultaneously.
• To control the major functions of any receiver through a simple tasking protocol.
• To provide receiver vendor independence, allowing the user to utilize the most
appropriate receiver for any given application.
Receiver XML configuration files are used to define the different receiver protocol profiles. This
allows new receiver support to be added to the NRC relatively quickly and simply by generating
and integrating a new receiver XML profile file.
A list of currently supported receivers can be found in the specifications section of this
document, with additional receiver support able to be provided upon request.
The NRC supports both differential and single-end audio signals, with the factory system default
being configured to support Differential Mode.
If Single-End mode is required, proceed as follows:
1. Ensure the NRC is powered off
2. Remove the top cover of the NRC.
3. Locate the two banks of 4x DIP switches, D1 and D2.
4. Set all switches to the ON position for single-ended operation.
a. Conversely, set each switch to the OFF position for differential operation.
5. Replace the cover and install the screws.
Note: The NRC software’s default configuration is to support Differential Mode,
and hence it must also be configured to match the desired audio signal state. The
NRC Configuration section will address this requirement.
Step 2: Rack Mount the NRC unit
The NRC chassis supports Jonathan Type 375QD-20 chassis slides and these are recommended
for rack mounting the NRC where necessary.
Note: It is not recommended that the NRC Chassis be solely mounted in 19” rack by bolts
through the chassis’ front panel - rack slides or rack shelving recommended.
Step 3: Connect Power
The supplied power cable should connect the power adapter on the back panel power socket of
the NRC. The NRC power supply is an auto-sensing unit which can accept voltages between
100-240VAC @47-63Hz.
Step 4: Connect Receivers
Each brand and model of receiver has specific configuration and installation instructions that
must be followed prior to operation with the NRC. Please refer to Appendix A.
Step 5: Optional - Connect an External Clock
If an external clock connection is desired for A/D synchronization, use a coaxial cable to connect
a 16 KHz TTL (50% duty cycle) external clock signal to the EXT CLK port on the NRC’s back.
The NRC’s default configuration uses the internal clock and hence the system needs to be reconfigured to use an external signal for A/D synchronization. This can be achieved after the
Hardware Installation through the NRC Java client’s “Global NRC Properties” dialog, or via the
programmers’ SDK.
Step 6: Connect to the Network
A Cat-5 cable should be used to connect between the ETH port on the back panel of the NRC
and the local area network.
In order to successfully configure the NRC for operational use, the installer must have access to:
a. a terminal emulation program
i. Before using it on the network the NRC must be properly configured, by
running a configuration utility on the NRC through a remote terminal
session. This requires connecting serially to the NRC from another
computer. The operating system of the computer is not important as long
as it has a compatible terminal emulation program. For example, most
Linux distributions contain minicom and the Windows systems contain
HyperTerminal, both of which are appropriate for this application
requirement. In addition, the computer must contain an available serial
port.
b. A computer machine on which the NRC java client can be run
i. In order to configure the NRC to understand the type of attached receivers,
the supplied NRC Java client needs to be able to run. This computer needs
to be on the same network as the NRC unit so it can attach to the NRC.
Step 1: Connect to the NRC
Before using it on the network the NRC must be properly configured, by running a configuration
utility on the NRC through a remote terminal session. This requires connecting serially to the
NRC from another computer. The operating system of the computer is not important as long as it
has a compatible terminal emulation program. For example, most Linux distributions contain
minicom and the Windows systems contain HyperTerminal, both of which are appropriate for
this application requirement. In addition, the computer must contain an available serial port.
The following steps describe the remote terminal connection process:
1. Power on the NRC
2. Connect a DB9 null modem cable from the remote terminal port on the NRC to a serial
port on the computer.
3. Start the terminal emulation application on the computer.
4. Specify correct terminal settings on the terminal emulation application. Please refer to
the application documentation for instructions on how to make these settings.
• COM Port: use the serial port on the computer that connects to the NRC.
• Bits per second: 9600
• Data bits: 8
• Parity: none
• Stop bits: 1
• Flow control: None
• Terminal emulation: vt100
5. Activate the terminal (press Enter a few times). You may need to send a terminal break
if this doesn’t work.
6. Once this terminal is active the linux system and NRC boot-up messages will be echoed
to the remote terminal. Once the NRC system has finished booting, a user login prompt
will appear.