WIN 500 Trunking Tables

[InlandAZ]

I have a pair of old scanners (Pro-106/197) that I'm trying to reprogram to monitor Pinal Co Fire dispatch (AZ) - When I import the Sacaton Peak and Simulcast C sites the trunking tables are empty. My old setup for Chandler contained the following, and worked just fine.

0 4095 0 851.006250 6.250
4096 8191 4096 762.006250 6.250
8192 12287 8192 136.000000 12.500
12288 16383 12288 136.000000 12.500
16384 20479 16384 136.000000 12.500
20480 24575 20480 136.000000 12.500
24576 28671 24576 136.000000 12.500

It's been many years since I've used the software, what am I doing wrong here? I've tried every combination of options for Trunking Tables & Band Plan, but nothing ever appears to match the above settings.

 

[Spitfire8520]

The vast majority of P25 systems will not need an explicit trunking table as long as the system is programed as P25 AUTO. The trunking table information is sent over the control channel by the site and will automatically be used by the scanner.

 

[buddrousa]

pro-106 problems after rebanding

Every since my area rebanded, I have not gotten anything from my pro 106 scanner. Had it a year. Is it time for a new scanner already?

forums.radioreference.com

 

[InlandAZ]

Cool - I'll give that shot - Thx

 

[InlandAZ]

Doesn't seem to work - as I recall (it's been a long time ago) the firmware required the re-banding tables. So, my question is: Why do my old archives contain the offsets, and the new imports are all missing?

 

[Spitfire8520]

For the sake of repetition, virtually all P25 systems will not need you to program the trunking tables. When you import a P25 AUTO system, it reads all the trunking table information from the control channel. Rebanding would not apply because these scanners pull that trunking table information directly from the system itself. What might have happened if you downloaded the programming from your scanner is that it saved this information into the tables, but it is not required to monitor.

If you believe that you need to manually program the trunking tables, then you can do so by clicking on the "Trunking Tables" button for the system you are programming and manually punching in the values to match your old programming.

 

[tvengr]

Can you attach your programming file so that we can check it for any problems? The Pro-106 and Pro-197 work fine on 700/800 MHz P25 systems without tables. I have programmed many. You may be suffering from simulcast distortion on that system. How long ago did you use those scanners? The 136.000000 entries in the table would seem to indicate they were using 150 band frequencies.

 

[ka3jjz]

It would also be helpful if you said precisely which system you are trying to hear....Mike

 

[tvengr]

I found a reference that Chandler previously used a Motorola Type II system. That would explain the use of a table.

 

[InlandAZ]

You may be right guys, these are fairly old scanners - I fired up an old 197, and it was receiving just fine. I think the 106 may have been bumped around a bit in our move to Maricopa from Chandler.

I'm trying to receive the Arizona RWC (Simulcast C - Chandler PD, Maricopa PD & Fire).

The 197 had these offsets - which may not be needed.

Char Hi-Chan Offset Base Freq Step
0 4095 0 851.006250 6.250
4096 8191 4096 762.006250 6.250

 

[budevans]

You may be right guys, these are fairly old scanners - I fired up an old 197, and it was receiving just fine. I think the 106 may have been bumped around a bit in our move to Maricopa from Chandler.

I'm trying to receive the Arizona RWC (Simulcast C - Chandler PD, Maricopa PD & Fire).

The 197 had these offsets - which may not be needed.

Char Hi-Chan Offset Base Freq Step
0 4095 0 851.006250 6.250
4096 8191 4096 762.006250 6.250

When I looked up the RWC Simulcast system. I don't see any entries for Maricopa Fire. Regarding Chandler PD & Maricopa PD most of those Talk Groups are Encrypted. So you can't monitor them.

Look at the MODE column. If the listing is DE (Digital Encrypted) you can't monitor. If the MODE is D (Digital) you maybe able to monitor if you aren't experiencing Simulcast distortion.

Regional Wireless Cooperative (RWC) Trunking System, Phoenix, Arizona

Regional Wireless Cooperative (RWC) Trunking System Profile

www.radioreference.com

Maricopa Police (City - Pinal County) Talkgroups

DEC HEX Mode Alpha Tag Description Tag
2599 a27 D MPD Dispatch Dispatch Law Dispatch
2598 a26 D MPD Info Info Law Tac
2597 a25 DE MPD TAC TAC Law Tac

Fire isn't listed.

Chandler Police Talkgroups

DEC HEX Mode Alpha Tag Description Tag
2499 9c3 DE CPD-Info A A01 - Info A Law Talk
2498 9c2 D CPD-Ptrl A A02 - Patrol A Law Dispatch
2497 9c1 DE CPD-HOT A03 - HOT Law Tac
2496 9c0 DE CPD-C2C A04 - Car-to-Car Law Talk
2495 9bf DE CPD-Traffic A05 - Traffic Law Tac
2494 9be D CPD-Metro A06 - Metro Law Tac
2493 9bd DE CPD-CIB 1 A07 - CIB 1 Law Tac
2492 9bc DE CPD- SAU A08 - SAU Law Tac
2491 9bb DE CPD-K9 A09 - K9 Law Tac
2490 9ba D CPD-Bike A10 - Bike Law Tac
2489 9b9 D CPD-Event 1 A11 - Event 1 Law Tac
2488 9b8 D CPD-Event 2 A12 - Event 2 Law Tac
2487 9b7 DE CPD-Training A13 - Training Law Talk
2486 9b6 DE CPD-Info B B01 - Info B Law Talk
2485 9b5 D CPD-Ptrl B B02 - Patrol B Law Dispatch
2484 9b4 DE CPD-Info C C01 - Info C Law Talk
2483 9b3 D CPD-Ptrl C C02 - Patrol C Law Dispatch
2481 9b1 DE CPD-CAU C11 - CAU Law Tac
2482 9b2 DE CPD-CIB 2 D10 - CIB 2 Law Tac
2480 9b0 DE CPD-Persons D12 - Persons Law Tac
2479 9af DE CPD-Property D13 - Property Law Tac
2478 9ae DE CPD-NARC D15 - NARC Law Tac
2477 9ad DE CPD-GANG D16 - Gang Law Tac
2476 9ac DE CPD-Event 3 E09 - Event 3 Law Talk
2475 9ab D CPD-Explorer E11 - Explorer Law Talk
2469 9a5 D CPD-Jail J16 - Jail Law Talk

 

[budevans]

You may be right guys, these are fairly old scanners - I fired up an old 197, and it was receiving just fine. I think the 106 may have been bumped around a bit in our move to Maricopa from Chandler.

I'm trying to receive the Arizona RWC (Simulcast C - Chandler PD, Maricopa PD & Fire).

The 197 had these offsets - which may not be needed.

Char Hi-Chan Offset Base Freq Step
0 4095 0 851.006250 6.250
4096 8191 4096 762.006250 6.250

I found Maricopa Fire. Maricopa Fire is listed in the Phoenix Fire Talkgproups. The first two 1656 & 1657 are encrypted. 1658 & 1659 are not encrypted. In this case as above, it's a Simulcast system, so you may or may not be able to monitor them. You might consider posting your questions about the RWC system in the Arizona Forum.

1656 678 DE Maricopa K5 Maricopa FD K5 Fire-Tac
1657 679 DE Maricopa K4 Maricopa FD K4 Fire-Tac
1658 67a D Maricopa K3 Maricopa FD K3 Fire-Tac
1659 67b D Maricopa K2 Maricopa FD K2 Fire-Tac

 

[InlandAZ]

Maricopa PD has been on the Simulcast C site for quite some time, and can still be monitored, you're probably referencing the new P25 Phase II System (and yep, totally encrypted). Our fire is dispatched by Phoenix on FD1.

My 668 will at times receive these just fine. Unfortunately I located a Cell Tower in extremely close proximity to our home, and I'm waiting for an attenuator to try and dampen it down. It totally overloads the 668 most of the time.