Orland Park P25

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
Orland Park PD is using the main dispatch frequency of 154.785 in P25 conventional mode with NAC 448 / TGID 1. I'm seeing some mobiles come up on TGID 2059 too.

Testing on the previously confirmed frequency 151.1525 with a variety of talk groups. "Radio service" has frequently referred to this frequency as Tac-2. NAC 467 and a variety of talk groups documented.
 

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
Based on some of the radio traffic and "radio service" performing various tests, this might have just happened today? I don't monitor them regularly so can't confirm.

A little "glitch" is appearing. Mobile units that are using TGID's 2057 and 2059 are having problems hearing mobiles programmed on TGID 1. "Heading into the garage to get radio programmed" has been heard a couple times. So far, all is in the clear.
 

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
Some mobiles/portables coming up with a TGID 2057, others on TGID 1. Orland Hills PD is also dispatched by Orland PD, and have a activity from them too.

OFT (One Frequency Trunk) programming is not optimal when two talk groups are in use, This adds a degree of difficulty if anyone else is text tagging the radio ID's. Hopefully Uniden will make the radio ID text tagging available for digital conventional systems in future firmware upgrades. Conventional P25 programming is reccomended until something changes.

I see the database has been updated...thank you!
 

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
Some mobiles/portables coming up with a TGID 2057, others on TGID 1. Orland Hills PD is also dispatched by Orland PD, and have a activity from them too.

OFT (One Frequency Trunk) programming is not optimal when two talk groups are in use, This adds a degree of difficulty if anyone else is text tagging the radio ID's. Hopefully Uniden will make the radio ID text tagging available for digital conventional systems in future firmware upgrades. Conventional P25 programming is reccomended until something changes.
Dispatch has been using TGID 2056, I beleive portables are using TGID 2057, and mobile units seem to be using TGID 1 primarily. As I mentioned, using OFT programming to tag radio ID's will be pretty tough if it remains this way. No analog heard since Wednesday on this frequency.
 

nhfirefighter

Member
Joined
Jun 2, 2007
Messages
71
Reaction score
46
Not in the area so can’t monitor. But strange setup. Being conventional the TG programming would add little value. There’s only one talk path so only one TG could communicate at a time.
 

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
Not in the area so can’t monitor. But strange setup. Being conventional the TG programming would add little value. There’s only one talk path so only one TG could communicate at a time.
If P25/DMR/NXDN Conventional systems are programmed as "in Uniden terminology" OFT (One Frequency Trunk), you can document and text tag radio ID's in P25, separate Slots and talk groups in DMR systems, and use different RAN's / talk groups in NXDN conventional systems. This is why I mention the talk groups. I've seen systems using 2 talk groups...1 for base/dispatch and the other for mobiles, but using three (so far) talk groups is a new one for me.
 

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
According to the modification request last year, both 154.785 (current analog dispatch), and 155.5725 had P25 conventional emissions added which might explain the testing of the different talk groups by the dispatch console? Car-to-car, Tact channels maybe?
Heard some Car-to-Car (Local? per the old analog database listing) using P25 Conventional with a NAC of 462 on 155.5725 this morning. Radio traffic sounded like they were testing Opticom activation on Lagrange Road. This covers the three new licensed P25 conventional frequencies on the license. We still can't access the FCC database to confirm this morning.

Over the weekend, they had an open key on the main police frequency (154.785) and the dispatcher announced an "open key on Channel 1", so this can be confirmed. Another TGID of 34176 from the dispatch over the weekend has been showing. Definitely not P25 OFT monitoring friendly with TGID's 1/2057 and now 34176 in use. It appears the car radios are using TGID 1, portables are using 2057 and dispatch is using 34176. I am not a close follower of Orland Park, so if anyone who is can fill in any blanks, please do.
 

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
Heard some Car-to-Car (Local? per the old analog database listing) using P25 Conventional with a NAC of 462 on 155.5725 this morning. Radio traffic sounded like they were testing Opticom activation on Lagrange Road. This covers the three new licensed P25 conventional frequencies on the license. We still can't access the FCC database to confirm this morning.
The FCC database is back up:


I'll guess the mobile station class listings are the input to the FB2 station class.

Looks like fire has some P25 conventional emissions licensed frequencies too:

 

ecps92

Member
Joined
Jul 8, 2002
Messages
15,975
Reaction score
4,522
Location
Taxachusetts
The FCC database is back up:


I'll guess the mobile station class listings are the input to the FB2 station class.
Generally YES if on a license with FB2's etc, however they could also be simplex channels
and with this License only having two Repeater frequencies 154.7850 and 155.5725 but 3 MO frequencies (not on the Repeater output) matching will require patience and monitoring

ahh the joys of mapping out new licenses in the VHF spectrum :)
 

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
Generally YES if on a license with FB2's etc, however they could also be simplex channels
and with this License only having two Repeater frequencies 154.7850 and 155.5725 but 3 MO frequencies (not on the Repeater output) matching will require patience and monitoring

ahh the joys of mapping out new licenses in the VHF spectrum :)
They have a separate license for this frequency in P25 conventional and has been confirmed as Tac-2:

 

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
all 3 channels are using Linear Simulcast so the modulation needs to be configured for LSM (CPQSK
On a scanner, I just set the modulation to Auto.

Is 155.5725 still considered to a be a "Local" channel, or "Car-to-Car" on the P25?

I did see 159.2475 NAC 448 come up this morning, and appeared to be a mobile or an input frequency to the main dispatch channel?
 

WILLAMNEUMANN

Member
Joined
May 30, 2008
Messages
12
Reaction score
3
Location
Orland Park, Il
On a scanner, I just set the modulation to Auto.

Is 155.5725 still considered to a be a "Local" channel, or "Car-to-Car" on the P25?

I did see 159.2475 NAC 448 come up this morning, and appeared to be a mobile or an input frequency to the main dispatch channel?
Direct from Radio Tech: I do not think they use the car to car anymore. It does sound so much better

PD-MAIN

RX: 154.78500 NAC: 448

TX: 159.24750 NAC: 448

OP-TAC1

RX: 155.57250 NAC: 462

TX: 158.97750 NAC: 462

OP-TAC2

RX: 151.15250 NAC:467

TX: 159.14250 NAC: 467
 

werinshades

Member
Premium Subscriber
Joined
Jan 21, 2002
Messages
6,644
Reaction score
3,176
Location
Chicago , IL
With the help of @WILLAMNEUMANN , we have confirmation of the frequencies and channel assignments in use and the database has been updated, thank you.

Yesterday, radio service was performing an update to the consoles to give them the capabilities to transmit an alert tone similar to ISP's tones when they have an alert to go out to the receivers. It also returned the dispatch talk group to 1 and made the audio less loud and distorted. Dispatch and mobiles use talk group ID of 1, portables use talk group 2057. Mobiles are using radio ID's in the 44870xx series, portables are using radio ID's in the 44860xx series.

Metra Police had an incident in Orland Park and has access to the new system. The radio ID came up as a 929xx which is the same as the radio ID's used on Starcom.

This system is in the clear, like neighboring Oak Forest, the analog Southwest Central Dispatch Center and Will County's P25 system. Looking back, Orland Park had it's first license on it's main dispatch frequency of 154.785 since 1987, so if it's not broke, why try and fix it applies here. If you happen to live out this way, many of us are jealous since you can hear the police in the clear...LOL!

They have one unused licensed frequency of 154.770 emissions in both P25 and analog. I have added, but suspect it might be reserved for some future use and haven't heard any activity yet. Orland Central Fire has some P25 emission frequencies in their license, so will keep an ear to them.

As mentioned, conventional programming is the preferred method with two separate talk groups in use. I like to tag my radio ID's in digital systems, but until Uniden makes a change in firmware and Sentinel, will have to be patient. (I'm not the only one asking about this in the Uniden forums, so it might be in the works.)

If I have anything pertinent to add, to this thread, I'll update. For the average listener, you have what you need. Fingers crossed it stays in the clear.
 
Top