Don, do you have an example of the Scan-set feature. I see the default is all Scanlist are turned on, then you can select a "set" of scanlists to be activated individually, but it looks like the scanlist have to be turned on in order to be scanned from a Scan-set. It looks like the advantage to this is that you can turn a set of scanlist on and off for a situation or location.
The Scan Sets feature is geared toward people who have lots of different things (where "different" is based on geography, agency, usage, etc.) they want to monitor, and want a somewhat easier method of choosing what to monitor than the default toggling of individual Scan Lists.
There are 200 Scan Lists. Each talkgroup and conventional channel belongs to no, any, or all of those Scan Lists. Scan Lists are toggled on/off via a "Scan Lists" menu (all 200 lists are in that menu).
There are 20 Scan Sets. Each Scan Set contains a list of 200 flags, one for each Scan List. Scan Sets are edited (their member Scan Lists toggled) by menus that looks just like the one mentioned in the previous paragraph. Scan Sets themselves are enabled/disabled via another menu (20 Scan Sets with a checkbox for each).
In order to be "scanned", an object (talkgroup or conventional channel) must:
a) be a member of at least one enabled Scan List, where that Scan List
b) is a member of at least one enabled Scan Set
By default:
* Scan List 001 is enabled, all others are disabled
* Scan Set 01 contains all 200 Scan Lists, all other Scan Sets are empty
* Scan Set 01 is enabled, all other Scan Sets are disabled
These defaults effectively make the Scan Sets feature transparent. Since Scan Set 01 is enabled and contains all 200 Scan Lists, condition (b) above is always satisfied: you can completely ignore the Scan Sets feature, and just use Scan Lists like you might on a PSR-500, PSR-310, PSR-700.
The default settings are geared toward the [presumed] majority of users, who will only have a few Scan Lists they want to monitor or toggle. Those users can control what they hear by just toggling a few Scan Lists on or off.
For more "advanced" users, who might have many areas or agencies they want to split among
many Scan Lists but who might have a few "common listening setups" (certain unique groups of Scan Lists they commonly monitor), toggling 200 Scan Lists might be cumbersome. The Scan Sets are intended to help with that.
It's hard for me to give an example, because I don't have that much that I commonly monitor - just the city PD and FD, county Sheriff, and CHP. A generic example, though, might be something like this:
* 10 cities, each with their own PD and FD
* specific channels/talkgroups for PD and FD dispatch
* 40 Scan Lists: <10 cities> x <PD vs. FD> x <dispatch vs. "everything else">
* All 40 Scan Lists enabled
* Scan Sets for things like:
+ All cities' PD dispatch
+ City #1 Fire (both dispatch and "everything else")
+ City #2 PD (both dispatch and "everything else")
+ City #1 and City #2 PD, dispatch only
+ City #1, City #3, and City #4, all PD and all Fire
* Toggling Scan Sets on/off can enable/disable such "groupings" much more easily than going through 40 Scan Lists
