I remember reading something a while back stating that Phase-2 couldn't be used for input/simplex frequencies. Essentially one Phase-2 output frequency will have two phase-1 input frequencies.
If you look at Arvada's site the two tables are the exact same with the exception of TableID, Bandwidth, & Slots. I am assuming that this means Pro96com calculates input frequencies with bandwidth & output frequencies with spacing....
Code:
FileVersion:7
-TowerInfo
#This section is here for information only. With the exception
#of the Call Sign(s), This data is not Read back into the program at all.
System ID : 00A
System Name : Denver Metro Area (formerly Lakewood PD / West Metro Fire / Wheat Ridge)
WACN : 924B3
Tower Number (Decimal): 21-21
Tower Number (Hex) : T1515
Tower Description :
Control Capabilities : Data,Voice,Registration
Call Sign(s) :
Timestamp : Wed Dec 18 21:59:19 2013
-Tables
#Format: Table ID,Base Freq,Spacing,Input Offset,Assumed/Confirmed,BandWidth,Slots
00,851.00625,0.00625,-45.00000,"Confirmed",0.00625,1
08,851.00625,0.00625,-45.00000,"Confirmed",0.01250,2
-Frequencies
#Format: Channel,Usage,Frequency(/Slot),Input Channel,Input Frequency(/Slot),Input Explicit(1/0),Hit Count
"00-0049","a",851.31250,"00-0049",806.31250,0,0
"00-0597","c",854.73750,"00-0597",809.73750,0,0
"00-0813","a",856.08750,"00-0813",811.08750,0,0
"00-1045","av",857.53750,"00-1045",812.53750,0,0
"00-1149","av",858.18750,"00-1149",813.18750,0,0
"00-1209","av",858.56250,"00-1209",858.56250,1,0
"00-1289","av",859.06250,"00-1289",859.06250,1,0
"00-1365","av",859.53750,"00-1365",814.53750,0,1
I was able to calculate frequencies with the following formula:
[output frequency] = Base + (ch x spacing)
DTRS Example:
-Tables
#Format: Table ID,Base Freq,Spacing,Input Offset,Assumed/Confirmed,BandWidth,Slots
00,851.00625,0.00625,-45.00000,"Confirmed",0.00625,1
01,762.00625,0.00625,30.00000,"Confirmed",0.00625,1
-Frequencies
#Format: Channel,Usage,Frequency(/Slot),Input Channel,Input Frequency(/Slot),Input Explicit(1/0),Hit Count
"00-0099","v",851.62500,"00-0099",806.62500,0,2
851.625 = (99 x .00625) + 851.00625
Westy Example:
-Tables
#Format: Table ID,Base Freq,Spacing,Input Offset,Assumed/Confirmed,BandWidth,Slots
00,806.06250,0.01250,-45.00000,"Confirmed",0.00625,1
01,811.00000,0.01250,-45.00000,"Confirmed",0.00625,1
-Frequencies
#Format: Channel,Usage,Frequency(/Slot),Input Channel,Input Frequency(/Slot),Input Explicit(1/0),Hit Count
"00-3600","cv",851.06250,"00-3600",806.06250,0,28
"01-3871","cvp",859.38750,"01-3871",814.38750,0,27
851.0625 = (3600 x .0125) + 806.0625
859.3875 = (3871 x .0125) + 811.000
Based on some research the P25 TableID determines Ch-Hi & Ch-Lo:
Ch-Lo = [P25 TableID] x 4096
Ch-Hi = Ch-Lo + 4095
Offset = Ch-Lo
(if you multiply by zero the world will end. Ch-Lo will be 0 for P25 TableID 0)
With that being said, the following should theoretically do the trick for Westy:
First Custom Table (P25 TableID 00):
Ch-Lo = 0
Ch-Hi = 4095
Offset = 0
Base = 806.0625
kHz step: 6.25
Second Custom Table (P25 TableID 01)
Ch-Lo = 4096
Ch-Hi = 8191
Offset = 4096
Base = 811.0000
kHz step: 6.25
Westy only has one frequency using P25 TableID #1. Perhaps they will use this as a Phase-2 frequency in the future?
-Steve