Why are there 2 tables anyway?
Could be because of second step size. See following.
I don't exactly understand how the tables work, so I guess it might not be easy to explain to me, lol..
We will try.
Code:
[B]Custom Uniden Frequency Tables[/B]
Table 1:
Base: 452.0000
Space: 12.5
Offset: 380
Table 2:
Base: 460.0000
Space: 12.5
Offset: 570
The above tables are Motorola tables which starts at channel 380 for first table and ends at 569. Then again for second at 570 and ending at channel 759. Including both lower and upper, this provides a range of 380 go to channels form the first base frequency (which can itself be lowest channel in table).
In this WV scheme, the highest database frequency listed minus the lowest
460.63750 - 452.87500 = 7.7625. Divide this by Step size of 12.5Kh or .0125 = 621 which is 241 channels above the 380 range for a single table. Thus 2 tables are required (if Motorola system).
However, this system is in fact P25 which has channel range from 0 through 65535 at offsets of 4096 increments. See below for GRE type scanners including 96/2096.
Code:
4. "CH LOW" 8192 "CH HI" 12287 "BASE FREQ" 453.0250 "OFFSET" 8192 "STEP" 12.5
5. "CH LOW 12288 "CH HI" 16383 "BASE FREQ" 450.0000 "OFFSET" 12288 "STEP" 6.25
It surely appears to me this system should work on a single table as in my previous. However, over the past few years I've only run the system in Charleston area while passing through on I-64 with 96/2096. Last spring I had PSR scanners. Also note, the second table has Step size at 6.25 so that in itself may be the reason for two tables. I suspect the GRE tables were derived by running Pro96Com on a control.