PanJurekMrJerry
Member
Whathappened to the RED & BLUE.
I just see BLUE now.
I only see Control Frequencies and no more Priamry or Secondary ones.
I just see BLUE now.
I only see Control Frequencies and no more Priamry or Secondary ones.
Whathappened to the RED & BLUE.
I just see BLUE now.
I only see Control Frequencies and no more Priamry or Secondary ones.
Other then opting out of alt controls with the PSR scanners when using Web Import on Statewide Mot or P25 systems. E.g., ya get more for your TSYS without unneeded secondary controls.as I recall it, was based on the fact that there's virtually no benefit to knowing whether a frequency is a "primary" or "secondary" CC.
I remember a discussion about this - perhaps it was only in the DB admin forum. Jon_k is right - the decision, as I recall it, was based on the fact that there's virtually no benefit to knowing whether a frequency is a "primary" or "secondary" CC. The fact of the matter is, 99 times out of 100, it's only really beneficial to know if a frequency carries, or can carry, a CC or not.
I don't think it's the DB admins' choice; it would be Lindsay Blanton's ultimate decision.
I think someone is misunderstanding the concept of alternate control channels, and I'm not sure who it is. As used in my area and in my experience, and evidently likely in Lindsay's view as well, alternate CCs are ones that cycle along with the "main" CC on a regular basis. You're going to need to have these CCs in your programming all the time, for when the control channel DOES change to those frequencies.
If a frequency is not used as a control channel at all, it should not be shown in the DB as a CC frequency.
In my experience, the average site has 3 control channel frequencies that it rotates through (on a system which has a rotating CC). Are you really that short of space on a modern scanner that you can't afford 3 frequencies per site? What do you do when the 'alternate' CCs that you haven't bothered to program in, since they're 'alternates', come active because the system controller detects interference on the 'primary' CC?
The MPSCS has over 200 sites statewide. Using only the Primary control channels, and removing the duplicates, I counted 51 unique control channel frequencies. Those do not fit into a single bank on the Pro-96/2096, and will not fit into a single TSYS object on the PSR-500/600. I'll grant you that in most cases you would want to limit the sites in the radio anyway, but if you take all of the sites within a single zone of the MPSCS, trying to enter all of the control channels can easily fill a Pro-96/2096 bank or PSR-500/600 TSYS object without entering all of them.
I have to admit total ignorance of what a TSYS is, as I have not used a RS/GRE product since the PRO-60 (child of the PRO-43). I gather it's analogous to a system, in Uniden-speak?
Why can't you just put all three control channels in the one system/TSYS, and let the scanner use whichever one is active? This is how my scanner's programmed; each site/system's control channels or alternate control channels are all in one system.
EDIT: If the software packages mentioned are creating multiple systems based on how many control channels they find, it appears those software packages need updates/fixes to catch up to the revised design Lindsay has placed on the RRDB.
I wouldn't want to put that many sites in a single system (or TSYS, if I understand it correctly) anyway. I have enough trouble with my six-site Smartzone system (total of 17 CCs) on the 396. In the 996, I needn't worry as each site gets its own slot, so I just have six slots - five with 3 CCs each and one with 2.
A "fact" that isn't true. If I'm planning on doing some mobile analysis of a large SmartZone system, I'll program all of the unique control channel frequencies (into a conventional bank/system) and label them according to their usage; for example:the decision, as I recall it, was based on the fact that there's virtually no benefit to knowing whether a frequency is a "primary" or "secondary" CC.
A poor definition IMO. A PCC is the RF channel pair on a SmartZone/OmniLink site that is currently handling control channel duties. An ACC is an RF channel pair on a SmartZone/OmniLink site that has been programmed to handle control channel duties and is currently capable of handling CC duties (e.g. isn't disabled/malfunctioning), but is currently not carrying CC traffic. Cycling or not is immaterial.As used in my area and in my experience, and evidently likely in Lindsay's view as well, alternate CCs are ones that cycle along with the "main" CC on a regular basis.
That's not the point being debated here.You're going to need to have these CCs in your programming all the time, for when the control channel DOES change to those frequencies.
For SmartZone systems, that seems to be the minority these days. If you look in the database at the large (and small) SmartZone systems in Ontario, Ohio, etc.,etc. you'll see that generally, each zone uses a single preferred primary control channel plus a single alternate. Oh wait, you can't - they're all blue now. So much for doing your own survey/analysis on how SmartZone systems are configured these days. Bad move...In my experience, the average site has 3 control channel frequencies that it rotates through (on a system which has a rotating CC).
That's another issue I have with this change. There was no advanced notice to any of the software developers that this change was coming. Making a change without any advanced notice that could effectively "break" numerous software packages is not the best way to handle an issue like this. In my testing with PSREdit500, it appears that the RR web service currently still has the Primary/Alternate flag in it, so nothing has changed yet as far as the software packages are concerned. Hopefully it never does in this regard.
A "fact" that isn't true. If I'm planning on doing some mobile analysis of a large SmartZone system
Mikey60, you need to go back and read the message that I posted in this thread -- I'll repost the relevant part for you:
The web service (which provides data to the programming apps) will still have the data
I didn't change a thing in the Web service, so the same functionality still exists there.