[Scan-DC] Montgomery county rebanding

[Joel Kahn]

OK. Here's my 2 cents worth:
Per the following document, the frequencies SHOULD BE as listed:
https://tatoolssecure.800ta.org/PublicTaTools/(nidgpe2hfyxmcvf5rm4bjkav)/CallSignCheckerResponse.aspx

Joel R Kahn



jrkahn at att.net

--- On Tue, 1/24/12, mike agner <ka3jjz1 at verizon.net> wrote:
Not quite true, I'm afraid. If you examine the frequencies for the 
system on the RRDB, as shown here

http://www.radioreference.com/apps/db/?sid=2142

You will note that some of the frequencies have a zero in the fourth 
decimal position. In this case, when the frequency is rebanded, the 
resulting channel
calculation will put it on a channel that the old bandplan won't 
recognize. A custom table will very likely be needed to copy this system 
when it rebands, particularly since this is one of those 'mixed mode' 
systems. If it were fully digital, all this futzing around wouldn't be 
needed...

A lot of the information necessary for modifying scanners to follow 
rebanded systems (including the values for the custom table) can be 
found in links in Section 7 of the following wiki article;

http://wiki.radioreference.com/index.php/Rebanding

best regards..Mike


On Tuesday, Alan Henney wrote:
=============================================
If you have a scanner that is control-channel tracking, just add 
thesechannels to the Montgomery County system info:  You will be covered 
when thechange is made,
assuming talkgroups remain unchanged.

853.9375
853.8875
853.8625
853.6875
868.9375
868.8875
868.8625
868.6875

==========================================================