Genesis GenWatch3 GW RSP25 Product guide

GenWatch3®
GW_RSP25 Module
Software Version 2.16.15
Module Book
600-2.16.15-EE.1
4/2/2020

2
600-2.16.15-EE.1

3
600-2.16.15-EE.1
Trademarks
Any brand or product names are trademarks or registered trademarks of their respective holders.
The Genesis Group Trademark Information
GenWatch3® is a registered trademark of GenCore Candeo, LTD., a subsidiary of Burks GenCore
Co., Inc. D.B.A. The Genesis Group and Phil Burks.
Copyright
Copyright © 2006-2020; Burks GenCore Co., Inc. D.B.A. The Genesis Group and Phil Burks. All
rights are reserved. No part of this publication or the associated program may be reproduced,
transmitted, transcribed, in whole or in part, in any form or by any means, whether it is
mechanical, magnetic, optical, electronic, manual or otherwise, without the prior written consent
of Burks GenCore Co., Inc. D.B.A:
The Genesis Group and Phil Burks
5800 Eagles Nest Blvd
Tyler, Texas 75703.
Includes technology licensed from Motorola.
Disclaimer
The GenWatch3 User’s Manual is printed in the U.S.A. Burks GenCore Co., Inc. D.B.A. The
Genesis Group and Phil Burks believe that the information included in this manual is correct;
however, Burks GenCore Co., Inc. D.B.A. The Genesis Group and Phil Burks reserves the right to
alter, revise and make periodic changes to the manual and its contents. Burks GenCore Co., Inc.
D.B.A. The Genesis Group does not assume responsibility to notify any person of such revisions
or changes. While we have taken strides to carefully examine our software and documentation and
believe that it is reliable, the Genesis Group and Phil Burks assume no responsibility for the use of
the manual, or GenWatch3 software, nor for any patent infringements or other rights of third
parties who may use the manual or the GenWatch3 software. Burks GenCore Co., Inc. D.B.A. The
Genesis Group and Phil Burks make no representations or warranties with respect to the contents
or fitness for a particular purpose beyond the cost of the software paid by the end-user.
The software contains valuable trade secrets and proprietary information. Unauthorized use of the
manual or software can result in civil damages and canal prosecution. As an end user, you agree to
abide by and heed these statements.
License
Title to the media on which the program is recorded and to the documentation in support of the
product is transferred to you, but title to the program, and all subsequent copies of the program,
despite the form or media in or on license is not a sale of the original or any subsequent copy. You
assume responsibility for the selection of the program to achieve your intended results, and for the
installation, use, and results obtained from the program.
Refer to the GenWatch3 Manual Overview for your full license. All license information contained
on pages 4-7 (Book 600-2.16.15-AA.1) are to be considered as contained herein.
Support
Customer satisfaction is our number one priority at Genesis. We are here to provide you with the
best software possible, and we want to know when you have any questions, concerns or problems
with GenWatch3 so that we can make it a better product for everyone.
Refer to the Troubleshooting & Support section of the GenWatch3 Manual Shell (Book 600-
2.16.15-AA.1) for complete support and contact information.

4
600-2.16.15-EE.1
Document History
Revision
Description
Author
2.0.2
Created Document
KIH
2.0.3
Release Revisions
KIH
2.0.3
Topaz Revisions
KIH
2.0.4
Release Revisions
KIH
2.0.4
Bug Fix: 3491
KIH
2.0.5
Added Millennium setup options
JAW
2.0.5
Release revisions
JAW
2.0.6
Updated screenshots
REB
2.0.6
Update Connection types
KIH
2.0.6.6
Release revisions
TDW
2.2
Document reviewed
WRK
2.3
Release Revisions
REB
2.4
Revision Before Release
CWF
2.5
Revisions Before Release
CWF
2.6
Revisions Before Release
CWF
2.7
Revisions Before Release
JAW
2.8
Revisions Before Release
CWF
2.9
Revisions Before Release
CWF
2.10
Revisions Before Release
ATG
2.11
Conversion to docx
BCY
2.12
Revisions Before Release
ATG
2.13
Revisions Before Release
ATG
2.14
Revisions Before Release
JAW
2.15
Revisions Before Release
REB
2.16
Revisions Before Release
JPS

5
600-2.16.15-EE.1
Table of Contents
Trademarks........................................................................................................................................... 3
The Genesis Group Trademark Information......................................................................................... 3
Copyright .............................................................................................................................................. 3
Disclaimer............................................................................................................................................. 3
License.................................................................................................................................................. 3
Support.................................................................................................................................................. 3
DOCUMENT HISTORY ................................................................................................................................. 4
TABLE OF CONTENTS............................................................................................................................. 5
ABOUT THIS MANUAL ............................................................................................................................ 7
GOALS........................................................................................................................................................ 7
WHO SHOULD READ THIS MANUAL?......................................................................................................... 7
HOW THIS MANUAL IS ORGANIZED ........................................................................................................... 7
CHAPTER 1 OVERVIEW..................................................................................................................... 9
WHAT IS THE GW_RSP25 MODULE?......................................................................................................... 9
EF JOHNSON DIGITAL TRANSCEIVER ......................................................................................................... 9
Radio..................................................................................................................................................... 9
Power.................................................................................................................................................... 9
Antenna................................................................................................................................................10
Placement.............................................................................................................................................10
Connection to the PC...........................................................................................................................10
MOTOROLA XTL SERIES DIGITAL TRANSCEIVER......................................................................................10
Radio....................................................................................................................................................10
Power...................................................................................................................................................10
Antenna................................................................................................................................................11
Placement.............................................................................................................................................11
Connection to the PC...........................................................................................................................11
Connection Management .....................................................................................................................11
Programming.......................................................................................................................................12
CHAPTER 2 MANAGING P25 CONNECTIONS .............................................................................13
P25 CONNECTIONS ....................................................................................................................................13
Adding a Connection............................................................................................................................13
Updating a Connection........................................................................................................................14
Deleting a connection ..........................................................................................................................14
CONNECTION PROPERTIES.........................................................................................................................14
Connection Settings .............................................................................................................................14
System Information ..............................................................................................................................16
Non-Millennium Channel Settings.......................................................................................................17
When to use Non-Millennium Channel Settings...................................................................................17
Millennium Channel Settings...............................................................................................................17
Reason Codes.......................................................................................................................................20
CHAPTER 3 FILTERING P25 DATA ................................................................................................23
WHAT ARE CONNECTION FILTERS?...........................................................................................................23
WHY WOULD ICREATE CONNECTION FILTERS?.......................................................................................23
LOADING THE ADVANCED OPTIONS SCREEN.............................................................................................24
CONNECTION ADVANCED OPTIONS...........................................................................................................25
More on Raw Data Files......................................................................................................................26
Changing the Raw Data File Directory ........................................................................................................... 27

6
600-2.16.15-EE.1
CHAPTER 4 HARDWARE COMPATIBILITY................................................................................29
RADIO .......................................................................................................................................................29
RADIO INTERFACE.....................................................................................................................................30

7
600-2.16.15-EE.1
About this Manual
Goals
This manual provides instructions on creating and managing GW_RSP25
connections.
Who Should Read This Manual?
This manual is intended for an audience of Project 25 (P25) compliant system
administrators and persons tasked with maintaining GenWatch3 on a P25 system.
How This Manual Is Organized
This manual is organized as follows:
•Overview: Describes the GW_RSP25 module and its role in the
GenWatch3 solution.
•Managing P25 Connections: Describes how to create and manage
GW_RSP25 connections.
•Filtering P25 Data: Describes how to create a packet filter for a
GW_RSP25 connection.
•Hardware Compatibility: Defines the hardware compatible with the
GW_RSP25 module.
This manual contains the following images, used to indicate that a segment of text
requires special attention:
Additional Information: Additional information is used to indicate
shortcuts or tips.
Warning: Warnings are used to indicate possible problem areas, such as a
risk of data loss or incorrect/unexpected functionality.

8
600-2.16.15-EE.1

9
600-2.16.15-EE.1
Chapter 1 Overview
This chapter defines the GW_RSP25 module and its role in the GenWatch3
product.
This chapter contains the following sections:
•What is the GW_RSP25 Module?: Defines the GW_RSP25 module and
its role in the GenWatch3 solution.
•EF Johnson Digital Transceiver: Describes the EF Johnson radio
hardware and proper installation practices.
•Motorola XTL Series Digital Transceiver: Describes the Motorola XTL
series radio hardware and proper installation practices.
What is the GW_RSP25 Module?
The GW_RSP25 module enables GenWatch3 to monitor Common Air Interface
(CAI) compliant system control channels. CAI packets are received via serial,
TCP/IP or PPP connection to a digital transceiver or from a remote GW_RSP25
that is setup to rebroadcast CAI packets.
Each CAI packet source is maintained by a GW_RSP25 connection. The
GW_RSP25 graphical user interface (GUI) allows you to manage each
GW_RSP25 connection. The number of connections allowed within the
GW_RSP25 GUI is restricted by your GenWatch3 license.
EF Johnson Digital Transceiver
Radio
The radio needs to be an EF Johnson digital transceiver capable of outputting P25
control channel data. System monitoring requires a Topaz-enabled digital
transceiver. The EF Johnson RS-5300 and 53SL mobile radios are digital
transceivers.
Power
A standard EF Johnson power supply can be used to power the transceiver. To
ensure reliability, an uninterruptible power supply (UPS) should be considered.

10
600-2.16.15-EE.1
Antenna
The radio must be installed within range of the trunk
system’s control channel. A high gain, Yagi-style
directional antenna is recommended for all installations.
Good coax design is required between the antenna and
the radio. In order to minimize phasing interference in a
Simulcast trunking system, the use of a Yagi directional
antenna is of utmost importance.
Placement
The radio should be placed where RF interference that may interrupt its RF
reception is minimized. Since there is rarely any need to touch the radio, there is
no need for the radio to be easily accessible.
Connection to the PC
The transceiver is connected to the computer using one of two methods.
•If the transceiver has the Topaz Interface enabled, a TCP/IP connection
will be used to receive data from the radio. Standard networking
equipment and cables can be used to connect to the PC.
•If the transceiver is connected via serial port, the EFJ Remote
Programming Interface (RPI) can provide a PC connection through the
PTT port on the front of the transceiver. At least one RPI is required to
program the transceiver.
A serial connection to the PC is completed by way of a DB9 RS-232 cable. If
necessary, this cable may be extended. A cable length over 50 feet (15 meters) is
not recommended. Use good data standards to decide if shielded cable is required
for a situation and RF environment.
Motorola XTL Series Digital Transceiver
Radio
The radio needs to be an RF-modem capable Motorola XTL series radio. System
monitoring requires a Millennium-enabled digital transceiver. The Motorola XTL
2500 and Motorola XTL 5000 are examples of these types of radios. The RF-
modem feature must be purchased from Motorola.
Power
Genesis offers a power supply for the Motorola XTL series radios. This power
supply includes a place to mount the Motorola XTL series radio. To ensure
reliability, an uninterruptible power supply (UPS) should be considered.

11
600-2.16.15-EE.1
Antenna
The radio must be installed within range of the trunk
system’s control channel. A high gain, Yagi-style
directional antenna is recommended for all installations.
Good coax design is required between the antenna and
the radio. In order to minimize phasing interference in a
Simulcast trunking system, the use of a Yagi directional
antenna is of utmost importance.
Placement
The radio should be placed where RF interference that may interrupt its RF
reception is minimized. Since there is rarely any need to touch the radio, there is
no need for the radio to be easily accessible.
Connection to the PC
The transceiver is connected to the computer using the USB programming cable
provided by Motorola. This cable allows the GW_RSP25 module to communicate
to the radio using the Motorola Millennium protocol over a PPP connection. The
PPP connection is created and maintained by the GW_RSP25 module.
Connection Management
PPP Communication with a Motorola XTL series radio requires a Windows
remote access service (RAS) connection. GW_RSP25 automates the process of
creating and dialing this connection when necessary. You can view the RAS
entries created by GW_RSP25 by browsing to Control Panel\Network
Connections.

12
600-2.16.15-EE.1
Programming
The XTL series radio must be programmed with only the following features. Any
additional features may prohibit the radio from functioning as an RF Modem.
Figure 1.1 –Required XTL Series Radio Programming

13
600-2.16.15-EE.1
Chapter 2 Managing P25 Connections
This chapter gives instructions on how to manage GW_RSP25 connections.
This chapter contains the following sections:
•P25 Connections: Describes GW_RSP25 connections.
•Connections Properties: Detailed description of the GW_RSP25
connection properties.
P25 Connections
Each connection shown in the Connections list, in the left of the GW_RSP25
GUI, represents a connection to a packet source. Connections receive CAI packets
via serial, TCP/IP or PPP. The status of each connection is represented by a radio
icon that appears in the Windows system tray (the bottom right of your desktop).
The icon has the following statuses:
•: Connection status unknown (white).
•: Connection has received packets within the last 5 seconds (green) for
connections that are not Topaz Conventional. Topaz Conventional
connections will turn green as soon as a connection is established and will
stay green if the socket the connection is using remains open.
•: Connection has not received packets within the last 5 seconds (blinks
between red and white background) for all connections that are not Topaz
Conventional.
The Connection Type of Serial + TCP/IP forwards packets received from the
serial connection to a specified TCP port. If a client connects to this port, the
following connection icons will indicate connection state:
•: Connection status unknown (white) and the TCP/IP client is
connected.
•: Connection has received packets within the last 5 seconds (green),
and the TCP/IP client is connected.
•: Connection has not received packets within the last 5 seconds (blinks
between red and white background) and the TCP/IP client is connected.
Adding a Connection
To receive packets from a packet source, you must add a GW_RSP25 connection.
To add a GW_RSP25 connection, take the following steps:
1. Click the Add button: The GW_RSP25 GUI will show the default settings
for a new connection and a Connection Alias value of something like
“New Connection 1.”
2. Change the connection properties (described below) to the desired values.
3. Click the Update button.

14
600-2.16.15-EE.1
Updating a Connection
In most cases, after you configure a GW_RSP25 connection, you will not need to
update it. However, you can update the GW_RSP25 connection properties if you
make a data entry error or if the settings change for some reason. To update an
existing connection, take the following steps:
1. In the Connections list, select (click on) the connection that you wish to
update. This will show the properties of this connection.
2. Update the properties that you wish to change.
3. Click the Update button.
You can cancel a pending add or update and discard changes by clicking the Cancel button.
Deleting a connection
In most cases, after you add a GW_RSP25 connection, you will not need to delete
it. However, you can delete a GW_RSP25 connection if you no longer want to
monitor the connection’s packet source. To delete an existing connection, take the
following steps:
1. In the Connections list, select (click on) the connection that you wish to
delete. This will show the properties of this connection.
2. Click the Delete button. This will result in a confirmation prompt.
3. Click Yes.
Connection Properties
Each GW_RSP25 connection contains many properties. The properties are
defined in detail below.
Connection Settings
•Connection Alias: This name will be used to reference the connection.
•Connection Type: Used to set the input mode used by this connection.
oSerial: When selected, the connection will use the Port Number
(COM Port) specified to connect to a data source.
oTopaz: When selected, the connection will use the Host Name /
IP value to connect to a Topaz-enabled digital transceiver. The
Port option is not displayed and is automatically set to 9130.
oTCP/IP: When selected, the connection will use the Host Name /
IP and Port values to connect to a TCP/IP socket.
oSerial + TCP/IP: When selected, the connection will use the Port
Number (COM Port) specified to connect to a data source. Each
packet received is then echoed via TCP/IP on the specified Port.
oMillennium: When selected, the connection will automatically use
the next available XTL Series Digital Transceiver connected to the
machine via USB.

15
600-2.16.15-EE.1
oMillennium + TCP/IP: When selected, the connection will
automatically use the next available XTL Series Digital
Transceiver connected to the machine via USB. Each packet
received is then echoed via TCP/IP on the specified Port.
•Port Number*: When using Serial or Serial + TCP/IP input, defines
which COM port to use for this connection.
•Host Name / IP*: For TCP/IP connections, the network computer name or
IP address of the computer set up as a GW_RSP25 TCP/IP server. For
Topaz connections, the network computer name or IP address of the
Topaz-enabled radio.
•Port*: For Topaz connections, this is the port used to connect to the
Topaz-enabled radio. For TCP/IP connections, this is the port of the CAI
data source. For TCP/IP + Serial and Millennium + Serial, this is the
forwarding TCP/IP port on the local machine for all data received.
•Redundancy Position: For Millennium connections, this allows the
configuration of multiple connections per site for redundancy. The values
can be assigned arbitrarily but must be unique per site.
The port range available for selection is the default dynamic range, therefore the ports at the
start of the range might be in use by other applications.
•Start Connection: If checked, then the GW_RSP25 module will start this
connection when the connection is updated. If you want to retain the
settings for a connection but do not want to receive packets from the
connection, uncheck this option. In most cases, this option should be
checked.
•APX Modem: For Millennium and Millennium + Serial connection types,
this indicates that this connection will use a Motorola APX series radio.

16
600-2.16.15-EE.1
*See Table 2.1 for more information on these settings and how they relate to
Connection Type.
Setting
Connection Types
Serial
Topaz
TCP/IP
Serial +
TCP/IP
Millennium
Millennium
+ TCP/IP
Port
Number
Serial
(COM)
port
N/A
N/A
Serial
(COM) port
N/A
N/A
Host
Name /
IP
N/A
Computer
name or IP
address of
the Topaz-
enabled
radio
connected
via TPC/IP
Computer
name or IP
address of
the CAI
data source.
This is
usually
another
RSP25
connection
set up as a
Serial +
TCP/IP.
N/A
IP address
of the APX
modem
connected
via USB.
IP address of
the APX
modem
connected via
USB.
Port
N/A
TCP/IP
port used
to connect
to the
Topaz-
enabled
radio. This
is restricted
to 9130.
TCP/IP port
of the CAI
data source.
This is
usually
another
RSP25
connection
set up as a
Serial +
TCP/IP.
Forwarding
TCP/IP port
on the local
machine for
all data
received
from the
serial port.
N/A
Forwarding
TCP/IP port
on the local
machine for
all data
received from
the serial
port.
Table 2.1 –Setting Definition Based on Connection Type
System Information
•WACN ID: 5-digit hexadecimal WACN ID. WACN IDs are retrieved
from your license.
•System ID: 4-digit hexadecimal system ID. System IDs are retrieved from
your license.
•RFSS ID: Decimal RFSS ID. The CAI RFSS is equivalent to the Zone ID
in a SmartZone system. Valid range is 1-255.
•Site ID: Decimal site ID. This number identifies the site that provides the
control channel data. Valid range is 1-255.
•Channel ID: Decimal channel ID. Only valid with the Topaz connection
type. This number identifies the conventional channel monitored by this
connection.
•Conventional: Check if connecting to a Conventional P25 System.
Uncheck if connecting to a Trunking P25 System.

17
600-2.16.15-EE.1
Non-Millennium Channel Settings
The channels within a P25 trunking system are grouped using up to 16 unique
identifiers. Each identifier represents a base frequency/channel-spacing pair and is
used in conjunction with a channel number. In order to translate this information
into a frequency, the GW_RSP25 module requires the following information
about each identifier used by your system:
•Base Frequency: Base frequency for this identifier.
•Channel Spacing: Spacing between each frequency for this identifier.
If needed, this information can be provided by your system manufacturer.
When to use Non-Millennium Channel Settings
In most cases, the channel settings will be decoded from the control channel.
Entering the channel settings manually is necessary only for channels that cannot
be decoded from the control channel. To see if channels are being decoded,
launch the GW_Activity GUI and verify that frequencies are displayed in the
frequency column. If channel settings are not being decoded, frequencies will not
be displayed and packets that should contain a frequency will be listed as corrupt.
In this case, you must manually enter the channel settings.
Millennium Channel Settings
Millennium RF-modems require programming in order to tune into the current
control channel on a system. Many of the values are repeated in the form of TX
(transmit) and RX (receive) to allow for UHF/VHF programming. Transmit and
receive are from the perspective of the RF-modem. The following channel
settings are available only when the Connection Type of Millennium is selected.
•Increment Step Size RX: Spacing between radio receive channels.
Values include:
o5.0 KHz
o6.25 KHz
o2.5 KHz
o3.125 KHz
•Increment Step Size TX: Spacing between radio transmit channels.
Values are the same as Increment Step Size RX.
•Range Frequency RX: Radio receive channel range. The lower end of
this range is used as the base channel. Values include:
o20-55.0025 MHz
o63-93 MHz
o103-230 MHz
o375-525 MHz
o801-963.835 MHz
o740-870 MHz
•Range Frequency TX: Radio transmit channel range. Values are the
same as Range Frequency RX.

18
600-2.16.15-EE.1
•System Deviation RX: Defaults are 2.5 KHz for P25, 4.0 KHz for
NPSPC and 5.0 KHz for interleave analog. Values include:
o0 KHz: Not known to be used.
o2.5 KHz:Used on P25 systems.
o4.0 KHz: Used by NPSPC systems.
o5.0 KHz: Used by analog interleave systems.
•System Deviation TX: Defaults are 2.5 KHz for P25, 4.0 KHz for
NPSPC and 5.0 KHz for interleave analog.
•Channel Band Width RX: Values include:
o12,500 Hz: Generally used by all digital systems.
o20,000 Hz
o25,000 Hz
o30,000 Hz
•Channel Band Width TX: Values are the same as Channel Bandwidth
RX.
•Modulation: Frequency modulation. Values include:
o12.5 KHz / C4FM: Rebanded or digital systems
oCQPSK: Not known to be used.
oWide Pulse: Not known to be used.
•IF Filter: Intermediate Frequency filter. Values include:
o5.76 KHz: Used for P25.
o7.8 KHz: Used for analog.

19
600-2.16.15-EE.1
•Control Channels # RX/TX: Control channels used on this system.
Control channel values must be entered in hertz. Most control channels are
shown in megahertz, so you may need to multiply the number by 1 million
to determine the hertz value. All eight control channels must be provided.
Please note:
oIf your system uses only one control channel, repeat that control
channel value for each channel; enter it in all four positions of the
same type (RX or TX).
oIf your system uses only two control channels, then repeat the
second control channel value in the third and fourth positions.
oIf your system uses only three control channels, then repeat the
third control channel value in the fourth position.
Control Channel RX is for the frequency that is receiving control channel activity. Control
Channel TX is for the frequency transmitting (sending) control channel activity.
Changing the RX values will set their respective TX value to the values’expected RX values.
This feature speeds setup for non-UHF/VHF connections.
Figure 2.1 –Settings for Millennium Connection
Non-APX Millennium connections require the Remote Access Connection Manager service.
If this service is disabled, it will not be possible to connect to a Millennium device.

20
600-2.16.15-EE.1
Reason Codes
The CAI used by P25 systems defines two types of reason codes. Within each
type, certain values are defined by the CAI and others are defined by
manufacturers and users.
•Deny Reasons: Unit requests service/call that is denied by the system.
User or system defined values: 91-239 & 244-254 (hexadecimal 61-EF &
F4-FE).
•Queue Reasons: Unit must wait for service/call to be available again.
User or system defined values: 128-255 (hexadecimal 80-FF).
The GW_RSP25 GUI allows users to define the same codes for use in
GenWatch3. Start by clicking the Reason Codes… button on the GW_RSP25
GUI.
Figure 2.2 –Reason Codes button
The Reason Codes window will appear. Each list of user-defined reason codes is
displayed and can be edited on this window. Modifications to the lists can be
saved by clicking the Save button or ignored by clicking the Cancel button.