I suspect I'm going to run into this in a few minutes, so this is timely. I do have some related questions, mostly having to do with assigning quick keys to trunked entries. First, here's a screenshot I have of this morning's experiment:
Of specific interest is the [MOT2] CNYICC[Onon] System area. Now normally I probably would have numbered this whole thing with a QK of 3 (in keeping with the first two CNV systems.) However, FreeSCAN went out of it's way to dissuade me from doing this, and I didn't want to throw a monkey wrench in the works.
Soo, let's assume I want to treat this whole system as a monolith and take it out of scanning rotation? Would I assign a QK to the "[MP25] Onondaga" site and do it that way, or would it be better to assign QK's to each group under the system?
The next question sort of links the original poster's question and this one. There are three or four other counties that are all under this same interoperative consortium, they all (presumably) use the same control channels, etc. Should I create separate systems for each county and just duplicate the site for each system, or should I clump them all under one system? By default, FreeSCAN pulled up the whole thing, but issued a warning saying I'd run into quickkey assignment problems (there were close to 40 groups if I had kept it the way it pulled it in.)
Finally (for now, anyway), I noticed that FreeSCAN turns on ID Search by default. It is apparently finding additional traffic (as indicated by
ID: xxxx in the channel display.) It sounds like legit traffic (law enforcement), so should I be making note of these transmissions and actually adding the ID's or just keep letting it search on its own? The "detail-oriented" part of me would like to have something beyond a rather anonymous ID show up in the display, but if that's the way the game is played, I'll play by the house rules.
OK, that should about do it for now. Thanks for your help, and Merry Christmas!