Custom Band Plans
Custom Band Plan(s) for Rebanded Systems
These are two widely accepted Custom Band Plans (Trunking Tables) that work with rebanded Motorola Type II SmartZone Trunking systems. A Custom Band Plan is needed in your GRE PSR-500/600 to be able to follow the rebanded sites as well as those yet to be switched.
This chart might be a little easier to read and follow, but must be entered into your programming software manually. For WIN500 users, open the WIN500 program > select the TSYS Objects tab > click on the Trunking Tables bar > enter the table exactly as shown > click Okay. Now click on the Trunking Tables drop down menu and select Custom. Upload to scanner and save to your *.p500 file.
Lo Chan Hi Chan Offset Base Freq Step 0 439 0 851.012500 25.000 440 559 440 851.025000 25.000 560 719 560 865.012500 25.000 720 759 720 866.000000 25.000 815 831 815 867.000000 25.000 958 958 958 868.975000 25.000 961 1022 961 867.425000 25.000
There's a slightly smaller version, one that merely moves the "rebanded" channels in front of the default 800 MHz table and is included in the current version of the WIN500 software. Open the WIN500 program, select TSYS Objects tab > click on the Trunking Tables bar > click the drop down menu in the new window > select "800 MHz Rebanded" > click Okay. Now click on the Trunking Tables drop down menu and select Custom. Upload to scanner and save to your *.p500 file.
Lo Chan Hi Chan Offset Base Freq Step 440 559 440 851.025000 25.000 0 719 0 851.012500 25.000 720 759 720 866.000000 25.000 815 831 815 867.000000 25.000 958 958 958 868.975000 25.000 961 1022 961 867.425000 25.000
(This version is also the one that should be used on a PRO-96/2096, since that scanner only has 6 table entries available.)
As far as the PSR-500/600 (and PRO-96/2096) are concerned, the 6-entry version is functionally equivalent to the 7-entry version. The 7-entry version may be necessary for apps like UniTrunker, though. If you experience a hiccup with one Band Plan, try the other one.
Converting LCN (Logical Channel Number) to frequency
For an example let’s say the Control Channel sends voice traffic to channel 445.
Looking at the Band Plan(s) we know that channel 445 falls in between the low channel of 440 and the high channel of 559. So that points us to use the line of the table that covers that group of channels. We then use the following formula to compute the requested frequency: 1. Channel Number minus the offset (445 – 440 = 5).
2. The result of that is multiplied by the step. In our case 25 kHz or .025 MHz (5 x .025 = .125).
3. The result of that is added to the base frequency (851.025000 + .125 = 851.150000). So we know that channel 445 using either table is 851.150000
The scanners that are not capable of rebanding will not work on LCN channels between 440 & 559.
The frequencies that will not work are the ones that start with 851, 852 or 853 and contain a 0 as the fourth decimal place.
851.***0 will not work but 851.***5 will work. 852.***0 will not work but 852.***5 will work. 853.***0 will not work but 853.***5 will work.
(I am using * as a wild card.)
We have found that older, non-rebandable Trunk Tracking scanners will retain limited usage. If the Control Channel routes a call to a frequency that begins with 851, 852, or 853, and has a "0" in the fourth decimal place, that call will not be heard by the scanners that cannot be upgraded (flashed).
EDIT TO ADD: Information I have in this post was supplied by gadgetmikey and DonS in other forums or in personal e-mail. It is information given in answers to questions I have had and/or posts I have made. I'm not smart enough to come up with all of this on my own.
WikiNote: Special thanks to User:qlajlu who put this information together. This was originally a post here - RR Forums
