Home | News | Products | Products|  24 Apr 2014 
Support Center » Knowledgebase » Why doesn’t my PSR-500/600 stop in the current Scan List when I press the “MAN” button after the Scanner stops on an active Object?
 Why doesn’t my PSR-500/600 stop in the current Scan List when I press the “MAN” button after the Scanner stops on an active Object?
You may have noticed that, when you are scanning and the scanner stops on an active Scannable Object, and you press MAN to hold the scanner on the object, the Scanlist and Object ID displayed in the upper left-hand corner of the LCD display show a Scan List number that is not what you believe to be the "current Scan List", or, the Scan List/Object ID display shows a Scan List that you do not currently have enabled.

This is probably one of the more difficult things to explain about object oriented scanning. The very short answer is as follows: 

Once the radio begins scanning, it really doesn't know what the "current Scan List" is.

A more detailed explanation is as follows:

In traditional bank/channel scanner designs, the scanner processes each bank of channels individually and in sequence until all enabled banks are scanned, then the process repeats. If you want a channel to appear in more than one bank, for example, an important channel that you want to monitor regardless of which banks you have enabled or disabled, you must make a separate copy of it for each bank that you want it in, and, it will be scanned multiple times in each scanning cycle if it is stored in more than one enabled bank. 

Your PSR-500/600 does not work like this. It does not process Scan Lists sequentially when scanning. Rather, it uses Scan Lists to organize your Scannable Objects into logical groups of your choosing. We call this "mapping objects to Scan Lists". 

Scan Lists make it easy for you to find your objects, and make it easy for you to enable and disable groups of objects when scanning. The objects aren't really stored "in" Scan Lists. Rather, they are "members of" one or more Scan Lists that you have identified in the Scan List mapping for each individual object.

Once scanning begins, the radio doesn't know what Scan List(s) an object is a member of. It just knows that an object it is scanning is mapped to one or more enabled Scan Lists, and is not locked out. In this way it is possible to have objects that are mapped to multiple Scan Lists, without having separate and independent "copies" of an object for each Scan List  that you want it to appear in, making memory usage much more efficient, and making scanning more effective, since the same object is not checked multiple times during a single scan cycle. 

It is important to remember that when you press MAN while scanning to stop the radio on an active Scannable Object, the radio always displays the lowest number Scan List that the object is a member of. You may then use the left and right arrow keys to navigate to another Scan List if desired. 

We suggest that you keep the following “OOUI Tenets” in mind as you use the radio. If you find yourself confused or stuck about the basics of Object Oriented Scanning, it may be helpful to review this this list 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.

Article Details
Article ID: 11
Created On: 12 Nov 2007 05:01 PM

 Login [Lost Password] 
Remember Me:
 Article Options
Home | Register | Submit a Ticket | Knowledgebase | News | Downloads

Help Desk Software By Kayako SupportSuite v3.60.04