Object Oriented Scanning Described

From The RadioReference Wiki

Revision as of 10:49, 5 January 2009 by Ka3jjz (talk | contribs) (new article for object oriented scanning)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
  • Object oriented memory management. Talkgroups can be associated with a single system. Systems can be defined as multi-site for statewide and networked systems. Talkgroups can be members of multiple scan lists. There are "Scan Lists" where you group the objects you wish for scanning. You do not need to enter frequency or talkgroup info more than once as you can just use those "objects" in the scan lists as you desire.
  • The V-Scanners work like the Radio Shack PRO-96 in that they store the radio's working memory (settings, frequencies etc.) to a separate area of internal memory. The radio's main memory is no longer banks/channels, but "objects". The Scan lists are now how you group the objects for scanning and you toggle them on/off with the traditional method of pressing the number keys during scanning. The arrow keys do not page through the V-Scanners. The V-Scanner function is in a separate menu much like the Radio Shack PRO-96.
  • The trunking "object" includes a "VHF/UHF" selection, and you can put in all of the offset/base etc. It also has a full trunking table capability for each trunking object (with plenty of entry slots!). As far as can be determined, there is no freq limitation on trunking like the Pro-96 had. Enter the data in the trunking object, and it will tune to any freq (except cellular of course).
  • When creating a talk-group object, you associate the talkgroup-object with the system object. The system-object has all the control channel information and is only entered once. Scan lists can have pointers to talkgroup-objects such as Fire, EMS, Police. As you create the talkgroup-objects you can assign them to any number of scanlists while you create them. You can also edit the scanlists later. You only create a system-object once, and associate multiple talkgroup-objects with it. Then the talkgroup-objects can be pointed to any number of scanlists (including none if you want to temporarily just set aside the talkgroup, but not delete it). If a talkgroup-object points to a system-object the paused talkgroup will stay synced up with the entire system over multiple control channels.