P25 System Help - Pro-96

[weblacsp]

Helpme

I have an RS pro96 , im use de pro96com , to monitor the 9600 control channel...
But i try to configure the rs scanner to follow an id group and it fail....
The file whit the information of the freqeuncies , ids , and all other is in atached files....
Please helpme to configure the scaner to follow an TG...
The files contais all the information extract from the control channel 9600...
Please...post the p96 file to use...

 

[N4JNW]

Get Win96 and a programming cable. The cable is also available at RadioShack.

These two tools will make programming the 96 super easy, and you won't get carpal tunnel from doing it. Trust me.. Both are worth the money. I'm a friggin tightwad, but after I bought my Pro-97, I quickly seen I NEEDED (not wanted) the cable and software.

If you're going to be listening to a lot of trunked or 800 mhz stuff, you might want to invest in a RadioShack 800 mhz duckie as well. In addition to the software, this is worth it's weight in gold when listening to anything 800 mhz.

If I had to buy only one, I'd still opt for the cabe and software. The stock antenna will recieve 800 mhz, but you'll soon be looking for an upgrade to boost signal strength.

 

[loumaag]

Attn: weblacsp

Attached you will find a zipped up P96 file that should work for you. I am guessing that you did not establish the tables for the radio to use in decoding the odd channeling used by this system.

To KG4LJF:
He obviously has the cable and the software, otherwise how would he be running the Pro96Com software or ask for a P96 file.

 

[weblacsp]

Thanks

Attached you will find a zipped up P96 file that should work for you. I am guessing that you did not establish the tables for the radio to use in decoding the odd channeling used by this system.

To KG4LJF:
He obviously has the cable and the software, otherwise how would he be running the Pro96Com software or ask for a P96 file.

Please just tellme how i can make the scanner follow the frequencies in a selected TG

 

[loumaag]

Please just tellme how i can make the scanner follow the frequencies in a selected TG

I provided you the P96 file you asked for, use it.

 

[weblacsp]

Thanks

 

[loumaag]

Attn: weblacsp

Thanks

Você deve calcular o "Lo", "Hi" e "Offset" valores para as tabelas múltiplas baseadas em o que você começou de Pro96Com. Eu fiz aquele para você e coloquei-o no banco 0 da lima P96.

 

[fmon]

I provided you the P96 file you asked for, use it.

Nice file Lou, though I guess one could delete VC's 170.03000 and 171.72000 from tower 104 entries since the duty Control will find them anyway. Also, won't the Extended Tables work with just the two VHF identifiers? I think the scanner will ignore the other 4 tables which do not apply.

 

[N4JNW]

To KG4LJF:
He obviously has the cable and the software, otherwise how would he be running the Pro96Com software or ask for a P96 file.

Oops... LOL... Sorry guys!!!

 

[loumaag]

Nice file Lou, though I guess one could delete VC's 170.03000 and 171.72000 from tower 104 entries since the duty Control will find them anyway. Also, won't the Extended Tables work with just the two VHF identifiers? I think the scanner will ignore the other 4 tables which do not apply.

To all your observations, yes. But having the extra channels in the bank won't make any difference, unless they are a CCh they are ignored anyway. As for the tables, I figured if the system was putting out those odd 800 MHz table values (and they are pretty odd), putting them in the table won't hurt and maybe they use a combination of VHF for rural and 800 for urban.

 

[fmon]

I figured if the system was putting out those odd 800 MHz table values (and they are pretty odd), putting them in the table won't hurt and maybe they use a combination of VHF for rural and 800 for urban.

Right on that, it can't hurt. It appears all VHF or UHF system which I run Pro-96Com on produce 851.0625 and 762.0625 identifiers in 00 and 01 respectively. Our Virginia STARS VHF systems list 8 Identifiers but only 3 are valid.

For troymial: It appears weblacsp hijacked the thread with his issue and Lou provided outstanding help to someone who is obviously handicapped in our language. Do you really want to hijack it again with the old (and very tired) Uniden vs Radio Shack issue?

 

[weblacsp]

Hello hlpme again please

Attached you will find a zipped up P96 file that should work for you. I am guessing that you did not establish the tables for the radio to use in decoding the odd channeling used by this system.

To KG4LJF:
He obviously has the cable and the software, otherwise how would he be running the Pro96Com software or ask for a P96 file.

which the steps you used to calculate the HI , LO and OFFSET ???

 

[fmon]

They are in your tower txt.

-Tables
#Format: Table ID,Base Freq,Spacing,Input Offset,Assumed/Confirmed,BandWidth
00,851.00625,0.00625,-45.00000,"Confirmed",0.00625
01,851.00625,0.00625,-45.00000,"Confirmed",0.00625
02,149.00000,0.00250,-23.00000,"Confirmed",0.01250
03,164.00000,0.00250,-23.00000,"Confirmed",0.01250
04,851.00625,0.00625,-45.00000,"Confirmed",0.00625

Where tables 02 and 03 are the only which apply because 00, 01 and 04 are 800MHz.

The range for each table is 0 to 4096, thus you multiply the table identifier (ID) times 4096. Starting with your first usable ID 02, 2*4096 = 8192. This value is placed in the Ch Lo and Offset box for table 02. Ch Hi for this table is 4095 (1 number less then a single table range) + Ch Lo or 8192 + 4095 = 12287.

Table identifier (ID) 03 is 3*4096 = 12288 and since it is only one ID above the previous it is one number above the Ch Hi of the previous ID. Of course its offset is the same as Ch Lo, or 12288.

Lou used Tables 00 through 04, however your two usable tables could have been entered in the blocks for 00 and 01 with the above calculations and saved. Blocks 02 through 05 could have been left with the unused "Default" data. Also note, he made a typo in the Ch Hi of the first line entry (00) as it should have been 4095 instead of 4094. However, since the 170.0000 MHz CC is not looking for 800 MHz tables, it doesn't make any difference what values are used with that base setting.

 

[loumaag]

Frank's explanation is accurate, but verbose for someone who only speaks Portuguese. The question is, does the file work on your system?

A explanação Frank é exata, mas verbose para alguém que fala somente o Português. A pergunta é, a arquivo trabalha em seu sistema?

 

[JohnnyGalaga]

loumaag,

are you using some translator, or do you really know Portuguese?

 

[loumaag]

are you using some translator, or do you really know Portuguese?

Using the Bable Fish Translator with an eye to the errors it usually produces (in both directions.)

 

[loumaag]

are you using some translator, or do you really know Portuguese?

Oh, thanks BTW, I realized that I had to fix a word in that translation. Somehow I didn't think "lima" was the correct word. I don't think he was filing (scraping) the data away. :lol:

 

[weblacsp]

Thanks

Frank's explanation is accurate, but verbose for someone who only speaks Portuguese. The question is, does the file work on your system?

A explanação Frank é exata, mas verbose para alguém que fala somente o Português. A pergunta é, a arquivo trabalha em seu sistema?

The archive that you send worked perfectly in my system...

Thanks

 

[weblacsp]

More one ask, if the calculos will be wrong facts and the missed filled values of the table, the archive goes to function wrong or not goes to function???
How do you know the range for each table is 0 to 4096, you multiply the table identifier (ID) times 4096 ?

 

[loumaag]

Translations corrected (as best as I can)

One more question, if the calculations are wrong and there are missed filled values of the table, the archive functions wrong or does not function???

If the calculations are wrong, the Pro-96 will go to a wrong frequency.
Se os cálculos forem errados, o Pro-96 irá a uma freqüência errada.

How do you know the range for each table is 0 to 4096, you multiply the table identifier (ID) times 4096 ?

The tables for P25 are defined. Each table contains 4096 possible frequencies. The Pro-96 uniquely uses both the table identifier and the offset to get a single value. Other radios do not use this method. Other radios use the two values separately. For the Pro-96/2096 this calculation is necessary to fill in the tables in the radio.
As tabelas para P25 são definidas. Cada tabela contem 4096 freqüências possíveis. O Pro-96 usa único o identificador de tabela e o offset chegar a um notável valor. Outros rádios não usam este método. Outros rádios usam o separada de dois valores. Para Pro-96/2096 este cálculo é necessário para preencher as tabelas no rádio.