Pro-96 P-25 RX problem

[Curfew]

At first a couple of years ago i entered the base, offset, and spacing to this system as BASE: 136.0, OFFSET: 49152, and SPACING 12.5 to include a setting via program-trunk- function -3 and i can't recall what setting i used there- i want to say MULTI-TABLE, but someone may be able to identify something different. I am dealing with a 9600 and again- i received just fine until i recently turned on the 96 and no tracking. I can hear the traffic on search- those are doing fine but i am not trunking. I am going to place the old table up her from a few years ago- then the new one so people that know how this works may be able to identify differences. The system techs on this system made some changes somewhere, whether it is base, offset- or the tables in use affecting this. I actually zeroized the 96, and used bank 0 to enter everything as above- NO GO.

Old Pro-96 Table readout-

12-2193 163.4125 A
12-2197 163.4625 A
12-2280 164.5 A
12-2317 164.9625 A
12-2321 165.0125 A
12-2335 165.1875 V
12-2338 165.225 V
12-2353 165.4125 V
12-2400 166.0000 V
12-2418 166.225 V

ID BASE SPACING TX Offset
00 851.00625 .00625 -45.0
01 762.00625 .00625 30.0
02 136.0 .01250 7.1250
03 .0125 7.1875
04 .0125
05 .0125
06 .0125
07 .0125
08 .0125
09 .0125
10 .0125
11 .0125
12 136.0 .0125
13
14
15


And now the new Pro-96 readout:

-Tables
#Format: Table ID,Base Freq,Spacing,Input Offset,Assumed/Confirmed,BandWidth
02,136.00000,0.01250,7.12500,"Confirmed",0.01250
03,136.00000,0.01250,7.18750,"Confirmed",0.01250
04,136.00000,0.01250,7.88750,"Confirmed",0.01250
05,136.00000,0.01250,7.62500,"Confirmed",0.01250
06,136.00000,0.01250,7.80000,"Confirmed",0.01250
07,136.00000,0.01250,8.30000,"Confirmed",0.01250
08,136.00000,0.01250,8.31250,"Confirmed",0.01250
09,136.00000,0.01250,8.45000,"Confirmed",0.01250
10,136.00000,0.01250,8.47500,"Confirmed",0.01250
11,136.00000,0.01250,8.91250,"Confirmed",0.01250
12,136.00000,0.01250,0.90000,"Confirmed",0.01250

-Frequencies
#Format: Channel,Usage,Frequency,Input Frequency
"12-2197","a",163.46250,164.36250
"12-2201","v",163.51250,164.41250
"12-2280","a",164.50000,165.40000
"12-2317","a",164.96250,165.86250
"12-2321","v",165.01250,165.91250
"12-2335","v",165.18750,166.08750
"12-2338","v",165.22500,166.12500
"12-2400","v",166.00000,166.90000
"12-2418","v",166.22500,167.12500
"12-2461","v",166.76250,167.66250

I do not know how to figure all this stuff, but it is very obvious there is some change to the table usage and channel numbers for example "12-2197" on this new readout vs."12-2193" on the old readout. All i would like to know is what i hand jam as far as BASE, OFFSET, and SPACING in the PRO-96 along if i have to have a setting right in program-trunk-function-3 (normal-table-splinter- multi table....)

I used a PSR-500 to listen to the system and that works- as i entered 136.0 as base, 49152 as offset, and 12.5 as spacing in the Pro-96 it would not track anymore. Something has changed within the system.. I dunno if this should be in a different area or not, i placed this here because i am dealing with a RS scanner... Thanks.

 

[Curfew]

I entered this in error....

 

[mobile_1]

VHF APCO P25 systems use explicit messaging. Your Pro96 cannot decode the multi-block messages being sent by the control channel but your PSR500 can. The Pro96 can only decode implicit P25 messaging. Changing the tables will not work. The Pro96 will never be able to decode the second and third blocks of these muliti-block messages. Sorry.

 

[dste]

"12-2461","v",166.76250,167.66250

I do not know how to figure all this stuff, but it is very obvious there is some change to the table usage and channel numbers for example "12-2197" on this new readout vs."12-2193" on the old readout. All i would like to know is what i hand jam as far as BASE, OFFSET, and SPACING in the PRO-96 along if i have to have a setting right in program-trunk-function-3 (normal-table-splinter- multi table....)

PGM-TRUNK-FUN-3 is for M:36.
PGM-TRUNK-FUN-4 is for M:96. Single or multi table will work if all active channels are 12-xxxx.

 

[DaveNF2G]

Apparently the PRO-96/2096 are also incapable of tracking P25 simulcast on 800.

 

[dste]

Apparently the PRO-96/2096 are also incapable of tracking P25 simulcast on 800.

I have no problem with my PRO-96 ( CPU F1.3 ) on Benton County ES in Washington State. I have had problems advising others on scanning this system with their PRO-96s. I never found out why they could not get it going.

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


The PRO-96 will certainly not scan a trunk out of it's original bands (700). I have scanned BCES 800 Simulcast (MotoX2 in mode 1) as well as Fairchild AFB (138 Moto II UHF/VHF) and Umatilla County in E. Oregon (400 Moto UHF/VHF).

The OP seems to be nearly there with the programming except PROG-TRUNK-FUNC-4 must be set to TABLE. for the 9600 baud control channel. You must be stopped in the correct bank when you make this change since each bank has it's own settings.