No work and it's all in one action unless you're configuring different areas like the Racom system. If I select 97 CC and ALT frequencies then it will automatically create 3 TSYS
It should create 4 TSYS objects, as 3 TSYS objects would only hold 96 freqs
and put any TGs I have selected with those TSYSs. I have no copying, no pasting, no repetitive import functions to do, nothing. Click on import, select sites, select TGs, assign scan list/s and click import. You're done with all three TSYS set and locked in the scanner and all ready to go. Believe me I've had systems up and running in less than 5 minutes because of that feature, it's really nice
If I'm understanding your description correctly...
Such "automatic" creation of multiple TSYS objects, duplicating "any TGs [you] have selected with those TSYSs", works if the talkgroups you're importing appear on all sites. If they don't (i.e. if some talkgroups are specific to certain sites, as in large statewide systems that might have sets of talkgroups for counties, cities, etc.), that automatic TSYS creation and TGRP duplication results in a potentially huge amount of wasted space (since some TSYS objects will contain TGRPs that they can never receive). You're still left with a bunch of hand-editing to prune out that extra data in each TSYS.
For example, a statewide system that has a couple of towers in each city, and has talkgroups that are specific to city operations (e.g. Fire, Police, etc.). The way you describe it, if you selected sites around (but not in or associated with) a particular city, as well as that city's talkgroups, those talkgroups would appear in the "extra" TSYS objects. With all due respect to Mike, that doesn't seem like a very efficient use of the 1852 blocks of memory in the scanner.
A more concrete example... the Michigan MPSCS system: You select all of the "sites" (88 unique CC freqs) so that at least 3 TSYS objects are required. You also select the 15 talkgroups that appear within category "Barry County" (e.g. "Freeport Police", "Hastings Police", etc.). You end up with 3 TSYS objects, each of which contains 15 TGRPs - even though those 15 TGRPs can only appear (or, at least can probably only be heard on) on a couple of sites within a single TSYS. You've wasted 30 blocks of scanner memory putting those 15 TGRPs into 2 "extra" TSYSes. And that's if you only selected 15 talkgroups. If you selected just 500 of that system's 1994 talkgroups, the "waste" is likely significantly higher. If you start running up against the 1852 block limit, you still have to (manually, within the software's UI) go back to each TSYS and remove the TGRPs that "don't belong". So, you can either do the extra steps at import-time or you can do them later on if you run out of memory.
Of course, for "statewide" talkgroups (talkgroups that appear on every site in the entire system), such a method would probably work quite well.
(The above presumes that all selected talkgroups are automatically duplicated across all created TSYS objects. Perhaps they're not.)
(None of this is meant to be a criticism of Mike's method. I've heard from several sources that his programs work quite well. The above is merely my own reason for not auto-creating multiple TSYS objects in my program(s). Personally, I'm waiting for the day when the scanner handles all system sites in a single TSYS object, making such duplication totally unnecessary.)
