As you've probably read over the Uniden forums, 996's are very touchy when it comes to simulcast. I'm sure that's more of the problem for you.
The only scanner that works for this is the SDS100.
TGID 5158 is the CPD/CFD Public Safety Training Center Security Operations. Kept hearing "Chicago to Kilbourn" numerous times which both intersects each other.
Forgot to mention that TGID 5146 is CPD's Education and Training Operations (Used for scenarios and active shooter training on 5/19/23.)
Both TGs added to the database, thanks.
Changes to the Code Plug and APXS000 HXE Portable Radio CODE PLUG CHANGES:
UMETRO 3 & 4 removed.
City Wide Fire frequency changing 470 to 460.
Removed the Direct Zone.
Removed PDD zone (CPD non-encrypted channels)
Old dispatch channels (470) becoming Back Up channels. Three new zones were added for Back Up Channels, Back UP FD, Back UP SE, and Back UP EMS.
New dispatch channels are being developed for our dispatch channels. FD, SE, and EMS zones will be the new channels on 460 frequencies.
UMETRO 1 & 2 now in UTAC Zone.
No confirmed information on new frequencies. Since the "new" 460 frequencies are in "development", how can the radios be reprogrammed? Why would the city invest in replacing apparatus radios with APX8500's tri band radios if they have no intention to utilize the 800 trunking system? Something seems a little off here.
UMETRO 3 & 4 removed.
City Wide Fire frequency changing 470 to 460.
Removed the Direct Zone.
Removed PDD zone (CPD non-encrypted channels)
Old dispatch channels (470) becoming Back Up channels. Three new zones were added for Back Up Channels, Back UP FD, Back UP SE, and Back UP EMS.
New dispatch channels are being developed for our dispatch channels. FD, SE, and EMS zones will be the new channels on 460 frequencies.
UMETRO 1 & 2 now in UTAC Zone.
No confirmed information on new frequencies. Since the "new" 460 frequencies are in "development", how can the radios be reprogrammed? Why would the city invest in replacing apparatus radios with APX8500's tri band radios if they have no intention to utilize the 800 trunking system? Something seems a little off here.
This information was sent out to the field due to an issue discovered on the newly programmed radios. The orange emergency button is "locking up" the Fireground channel when it's inadvertently being pushed. Since they didn't receive any "formal training", this radio information is being sent out, including how to reset it if you happen to be the "button pusher".
Based on what I've read, the UMETRO 3 & 4 ("old EMS North & South/460.600 & 460.625) have been eliminated from the radio code plugs. Also moving UMETRO 1 & 2 (453.750/453.950 ) to a UTAC Zone, would lead me to believe those frequencies won't be used for dispatching operations. The city has renewed licenses for frequencies in the 460 Mhz. range, so any one of them could be used.
As far as why I'm posting this under this thread, I would suspect alot of work needs to be done to add these new frequencies? Each transmit and receive site would need to be programmed. Testing would have to be a large part of this to gain confidence that the same interference issues will not return. If it is still problematic, the entire thing could be scrapped since they have a working radio system and the 800 trunking system doesn't appear to have any of the problems the 470 Mhz. system did, I would suspect the 800 trunking system will be in use for awhile. The "original" plan that I heard mentioned, was EMS to be switched over first...the continuation the proverbial "let Mikey try it"
.Is there any known reason why they are so desperate to get back to UHF when 800 mhz seems to be working well for them?
Their seems to be a "fear" that since New York's radio failures on 9-11 and the 800mhz. frequencies. Since then, communications systems have changed dramatically, but CFD doesn't like to roll with changes.
Testing heard today:
1010: (Command-Secure) Phase 2 in the clear, previously seen as encrypted Chief RID's, Radio ID 575xxxx (CPD Radio), testing with unknown/no RID transmitted (OEMC Console?)
1017: Not previously ID'd. Phase 1, in the clear, RID 575xxxx testing with unknown/no RID transmitted (OEMC Console?). "Can you see me?" was heard being asked.
1018: Not previously ID'd. Phase 1, in the clear RID 575xxxx. No reply heard.
OEMC Radio room heard doing frequent testing today from the OEMC.
1010: (Command-Secure) Phase 2 in the clear, previously seen as encrypted Chief RID's, Radio ID 575xxxx (CPD Radio), testing with unknown/no RID transmitted (OEMC Console?)
1017: Not previously ID'd. Phase 1, in the clear, RID 575xxxx testing with unknown/no RID transmitted (OEMC Console?). "Can you see me?" was heard being asked.
1018: Not previously ID'd. Phase 1, in the clear RID 575xxxx. No reply heard.
OEMC Radio room heard doing frequent testing today from the OEMC.
So is CFD still using 800 system or are they back to UHF P25?
Changes to the Code Plug and APXS000 HXE Portable Radio CODE PLUG CHANGES:
UMETRO 3 & 4 removed.
City Wide Fire frequency changing 470 to 460.
Removed the Direct Zone.
Removed PDD zone (CPD non-encrypted channels)
Old dispatch channels (470) becoming Back Up channels. Three new zones were added for Back Up Channels, Back UP FD, Back UP SE, and Back UP EMS.
New dispatch channels are being developed for our dispatch channels. FD, SE, and EMS zones will be the new channels on 460 frequencies.
UMETRO 1 & 2 now in UTAC Zone.
No confirmed information on new frequencies. Since the "new" 460 frequencies are in "development", how can the radios be reprogrammed? Why would the city invest in replacing apparatus radios with APX8500's tri band radios if they have no intention to utilize the 800 trunking system? Something seems a little off here.
Here you go..This information was sent out to the field due to an issue discovered on the newly programmed radios. The orange emergency button is "locking up" the Fireground channel when it's inadvertently being pushed. Since they didn't receive any "formal training", this radio information is being sent out, including how to reset it if you happen to be the "button pusher".
Based on what I've read, the UMETRO 3 & 4 ("old EMS North & South/460.600 & 460.625) have been eliminated from the radio code plugs. Also moving UMETRO 1 & 2 (453.750/453.950 ) to a UTAC Zone, would lead me to believe those frequencies won't be used for dispatching operations. The city has renewed licenses for frequencies in the 460 Mhz. range, so any one of them could be used.
As far as why I'm posting this under this thread, I would suspect alot of work needs to be done to add these new frequencies? Each transmit and receive site would need to be programmed. Testing would have to be a large part of this to gain confidence that the same interference issues will not return. If it is still problematic, the entire thing could be scrapped since they have a working radio system and the 800 trunking system doesn't appear to have any of the problems the 470 Mhz. system did, I would suspect the 800 trunking system will be in use for awhile. The "original" plan that I heard mentioned, was EMS to be switched over first...the continuation the proverbial "let Mikey try it"
I saw these submissions today:
Have these been verified on Site-3 (ORD-Site)? As far as I know, all above departments are using the TETRA system: Chicago O'Hare Airport TETRA Trunking System, Chicago, Illinois
The "original plan" was to have all these on the 800 trunking system.
Have these talkgroup text tags been confirmed? Since three of them are encrypted, just curious how this was verified? The talkgroups labeled as Event channels, I haven't heard anything during testing identifying them. What did I miss?
| 2513 | 9d1 | T | ORD SEC | Security | Security |
| 2514 | 9d2 | T | ORD TMA | Traffic Management Authority (TMA) | Law Tac |
| 2515 | 9d3 | T | ORD AMC | Association Management Center (AMC) | Business |
| 2516 | 9d4 | T | ORD MECH | Mechanics | Public Works |
Have these been verified on Site-3 (ORD-Site)? As far as I know, all above departments are using the TETRA system: Chicago O'Hare Airport TETRA Trunking System, Chicago, Illinois
The "original plan" was to have all these on the 800 trunking system.
| 1014 | 3f6 | DE | CMDSEC 14 | CMDSEC | Fire-Tac |
| 1015 | 3f7 | DE | CMDSEC 15 | CMDSEC | Fire-Tac |
| 1016 | 3f8 | DE | CMDSEC 16 | CMDSEC | Fire-Tac |
| 1017 | 3f9 | D | FD EVENT 1 | Fire Event 1 | Fire-Tac |
| 1018 | 3fa | T | FD EVENT 2 | Fire Event 2 | Fire-Tac |
Have these talkgroup text tags been confirmed? Since three of them are encrypted, just curious how this was verified? The talkgroups labeled as Event channels, I haven't heard anything during testing identifying them. What did I miss?
Last edited:
I don't believe I heard any of these O'Hare talkgroups above on the Citywide Simulcast unless it's just only being used on the ORD site itself.
Um...I don't seem to have this issue if I'm monitoring the site(s) within range and don't have too much scanning at the same time.
But...to get back to my question about submissions, if this was an "anonymous submission" as it was suggested to me, then the database administrator that took the submission might reach out and ask the "source" of the information. Since it's been documented O'Hare is also running a TETRA system, and a contributor confirmed Aviation Security is actively using a talkgroup and many others "unidentified in the WiKi", I would suspect this submission wasn't verified as it's been required.
On the CFD submissions, I have posted previously activity on the talkgroups, but since some of the talkgroups are encrypted, and unless the "source" is not from actual listening, it also isn't verified information. Encrypted 1011 isn't verified, but based on the radio ID's, I was able to narrow down the user(s).
@werinshades The new TGs were from anonymous source with the info coming direct from a radio codeplug.
So not "confirmed to be in use"? The CFD ones I could see, but the O'Hare talkgroups are not in use since they're using the TETRA system. Those talkgroups were "scheduled" to be used and a list is probably floating around still, but since the Department of Aviation likes to do things their way up there, they purchased their own radio system and opted not to use the city's 800 trunking system for those departments.
FWIW, I went airside at ORD in June 2022, and both Aviation Security and Airfield Ops had Motorola TETRA portables. I realize that things can change alot in a year, but none of those ORD talkgroups have come up during ID search on the OEMC 800 any time that I've been up there since.
I am in range of the ORD System (not the City simulcast system) and have been monitoring the above 4 ORD talkgroups all day. Not one bit of traffic on any of them.
Similar threads
- Locked
- Locked
