User's Manual

We suggest that you keep the following “OOUI Tenets” in mind as you proceed with your study of this
manual. If you find yourself confused or stuck about the basics of Object Oriented Scanning, it may be
helpful to review this section again.
1. The OOUI memory organization is nothing more than a large list of "Scannable Objects".
2. A "Scannable Object" is simply "something that can be scanned", including conventional channels,
trunking talkgroups, limit searches, service searches and Spectrum Sweeper setups.
3. In OOUI scanning, there are no "systems", "banks", "groups", "sub-groups" or "ID lists". There is simply a
very large collection of objects, each with their own attributes. Scannable Objects all exist at the same level
or hierarchy within the scanner - no single type of Scannable Object is more important than another, and
Scannable Objects do not have dependencies on or links to other Scannable Objects in order for them to
function properly.
4. The primary method of grouping the collection of objects is by mapping them to Scan Lists. Mapping a
Scannable Object to one or more Scan Lists does not change the physical location of the object in the
memory system. Even when an object is mapped to one or more Scan Lists, the object itself has not moved
nor changed from what it is - a simple, standalone object that is part of a larger collection.
About this manual
Object abbreviations used in this document
We described how your new GRE scanner utilizes an Object Oriented User Interface in the Introduction
and Overview sections of this manual. You learned that the key components of this new user interface are
the Scannable Objects, which are, of course, “things that can be scanned”. As you begin to use your new
scanner, you will notice that the object names are abbreviated so that they can easily fit into the 16
character LCD. (Imagine what the radio's display would look like if “Trunking Talkgroup Object” was spelled
out in its entirety every time it was necessary to show it in the display.)
You should take a moment and become familiar with these abbreviations now. For consistency, the same
abbreviations for the different object types are used in the radio and here in the manual.
TGRP
TGRP is used to represent a Trunking Talkgroup Object. Trunking Talkgroups are “virtual” channels that
exist on a trunked radio system. A trunked radio system is a radio system where a small group of radio
channels are automatically shared between a larger number of users and user groups. This sharing of
channels is managed automatically by a special computer, called a controller, or by other specialized
hardware. For now, all you need to know is this; if you want to monitor a talkgroup on a trunked radio
system, you must store that talkgroup's parameters in a TGRP object.