Rush University Medical Center Cap+ System

[kevino]

It appears that there is a MOTOTRBO Capacity Plus trunked system in use at Rush University Medical Center in Chicago. I was able to confirm one of the system repeaters on 461.7375 (CC1, LCN not confirmed), which is covered by callsign WQTA935. My guess is that other system repeaters are covered by this same callsign.

Security (300-series units) uses talkgroup 110, and an unknown user (500-series units) has been heard on talkgroup 113.

Does anyone have additional information (additional repeater frequencies, color codes, LCNs) for this system?

 

[kevino]

A quick update - 461.7375 (CC1) appears to be LCN 2 on this system.

 

[kevino]

A quick update - 461.7375 (CC1) appears to be LCN 2 on this system.

LCN 2 confirmed, still looking for additional system repeaters.

 

[ChicagoRadio736]

It appears that there is a MOTOTRBO Capacity Plus trunked system in use at Rush University Medical Center in Chicago. I was able to confirm one of the system repeaters on 461.7375 (CC1, LCN not confirmed), which is covered by callsign WQTA935. My guess is that other system repeaters are covered by this same callsign.

Security (300-series units) uses talkgroup 110, and an unknown user (500-series units) has been heard on talkgroup 113.

Does anyone have additional information (additional repeater frequencies, color codes, LCNs) for this system?

Do you have any more frequencies under that license? For some reason I can't look up the license, I will be by Rush tomorrow, and close call doesn't really work with DMR.

 

[kevino]

Do you have any more frequencies under that license? For some reason I can't look up the license, I will be by Rush tomorrow, and close call doesn't really work with DMR.

WQTA935 - best candidates appear to be 461.025, 461.125 and 461.200. There's a repeater at the same address on 464.9125, but the license shows a 7 watt erp. Two other repeaters (451.2875, 452.850) on the same license but located at another building. You might also check out 463.700, which was their "old" security repeater.

 

[kevino]

461.200 CC1 has been confirmed as LCN 1 for this system, with 461.7375 CC1 previously confirmed as LCN 2. I'll run LCN Finder again to see if there are any additional repeaters in use with this system.

I'll create the system in the Radio Reference database in the next day or so.

 

[werinshades]

Security (300-series units) uses talkgroup 110, and an unknown user (500-series units) has been heard on talkgroup 113.

113...edited:

This sounds like Maintenance of some kind. "You have a ticket" could be referring to a work order?"

 

[ChicagoRadio736]

463.7000 is confirmed LCN 3 trying to confirm the CC most likely 1

 

[That_Radio_Geek]

Here's the easiest way to figure this system out:
Go to the DB for WPXQ904 and input the whole system using only the frequencies marked with emission designator 7K60FXE (Digital Voice & Data) with class FB2, and run LCN finder. When you input the freqs, do it as a DMR One Frequency system. Let the radio do the work from there. Then run LCN finder.

FCC Callsign WPXQ904 (RUSH PRESBYTERIAN ST LUKES MEDICAL CNTR)

FCC Callsign WPXQ904 (RUSH PRESBYTERIAN ST LUKES MEDICAL CNTR)

www.radioreference.com

 

[werinshades]

Here's the easiest way to figure this system out:
Go to the DB for WPXQ904 and input the whole system using only the frequencies marked with emission designator 7K60FXE (Digital Voice & Data) with class FB2, and run LCN finder. When you input the freqs, do it as a DMR One Frequency system. Let the radio do the work from there. Then run LCN finder.

FCC Callsign WPXQ904 (RUSH PRESBYTERIAN ST LUKES MEDICAL CNTR)

FCC Callsign WPXQ904 (RUSH PRESBYTERIAN ST LUKES MEDICAL CNTR)

www.radioreference.com

I look forward to your updated findings, especially since you had an awakening as to how we've been doing this for years. But hey man, the floor is all yours and don't forget to submit "confirmed" information to the database.

 

[That_Radio_Geek]

I look forward to your updated findings, especially since you had an awakening as to how we've been doing this for years. But hey man, the floor is all yours and don't forget to submit "confirmed" information to the database.

Just trying to be helpful by giving all of you ideas. I love investigating radio systems and trying to figure out as much as I can. Maybe if I get time, I'll be able to help solve a part of this.

 

[werinshades]

Just trying to be helpful by giving all of you ideas. I love investigating radio systems and trying to figure out as much as I can. Maybe if I get time, I'll be able to help solve a part of this.

Since 3 LCN's have been identified and confirmed, I think they got this.

Here's the easiest way to figure this system out:
Go to the DB for WPXQ904 and input the whole system using only the frequencies marked with emission designator 7K60FXE (Digital Voice & Data) with class FB2, and run LCN finder. When you input the freqs, do it as a DMR One Frequency system. Let the radio do the work from there. Then run LCN finder.

FCC Callsign WPXQ904 (RUSH PRESBYTERIAN ST LUKES MEDICAL CNTR)

FCC Callsign WPXQ904 (RUSH PRESBYTERIAN ST LUKES MEDICAL CNTR)

www.radioreference.com

Have you had any Cap+ or Con+ systems that this method has worked on that you can point to? The only way to confirm LCN's is by self-programming the system as DMR Trunking, confirming the Color Codes, and listening for a long period of time so the scanner can detect radio traffic to determine it's LCN by running LCN Finder. We have many DMR Trunking systems in the metro area and can easily become confusing if you don't have the parameters set correctly and might be listening to another hospital/hotel thinking it's one and not the other. Listening for a day or a night is not enough time in most instances to confirm the user. By jumping from one or another can't submit confirmed information. This system is being monitored, and once more talk groups become active, additional LCN's can be confirmed. I'm not one of those who have this system on all the time, but based on the users and submissions, I have confidence it's being done correctly.

 

[That_Radio_Geek]

There is no single correct way to figure out a trunked system. There are multiple methods and techniques. And no, it doesn't take days or weeks to figure out who a user is or what their TGs are used for, it takes hours at best. The FCC is not going to issue a user a license for assigned frequencies while also assigning those same frequencies to another nearby system. I have an SDS-100 and use it daily. I use all the features. I have yet for my SDS to show me a user's LCN. It'll say one was found, but it won't show it because by law, it can't because LCNs are considered confidential. That's why the FCC never lists LCNs in a user's license. If WE find them, we can list them, but that's because we're civilians.
As I said, I was just trying to be helpful, not trying to tell people how to do things. The more people you have looking at a system, the better. But, I guess you just want you and your little clique to do this. I'll butt out and not try to help ever again. This is why I also don't make submissions, because I know it won't be accepted since it didn't come from a recognized member of your inner-circle.

 

[werinshades]

There is no single correct way to figure out a trunked system. There are multiple methods and techniques. And no, it doesn't take days or weeks to figure out who a user is or what their TGs are used for, it takes hours at best. The FCC is not going to issue a user a license for assigned frequencies while also assigning those same frequencies to another nearby system. I have an SDS-100 and use it daily. I use all the features. I have yet for my SDS to show me a user's LCN. It'll say one was found, but it won't show it because by law, it can't because LCNs are considered confidential. That's why the FCC never lists LCNs in a user's license. If WE find them, we can list them, but that's because we're civilians.

LOL...you're way off again. On Uniden scanners, once an LCN is found and it displays (1 of 5 Found for example), you can exit the LCN finder mode, you'll be prompted to save and if you press yes, it will be on the scanner. Then, you can Read from Scanner into Sentinel or go into the menu, find the Favorite List, drill down to the site, frequency and it will show you if an LCN has been assigned.

As far as mapping systems, yes it does take time and hurrying up and posting what you found without any confirmation is why the database get's messy. As I've said on the CTA Simulcast thread..slow down, give it some time and confirm before posting. Just because you're first, doesn't make it right.

The Chicago metro area has numerous users on the same frequencies because most hospitals/hotels are operating on low power. So that means, they shouldn't interfere with each other. So a hotel in downtown Chicago could be assigned the same frequency as a hotel in Oak Lawn, and depending on what your antenna system is, talk groups/LCN's might get jumbled up and talk group 101 is security in the downtown hotel and 201 might be the talk group for security in the Oak Lawn hotel. The color codes might be different, one might be on a Cap+ system, while the other is a DMR conventional system and needs time to decipher and confirm. I've been at this a long time, and have had it happen to me.

LCN's are confidential...not sure where you heard that one

 

[ChicagoRadio736]

There is no single correct way to figure out a trunked system. There are multiple methods and techniques. And no, it doesn't take days or weeks to figure out who a user is or what their TGs are used for, it takes hours at best. The FCC is not going to issue a user a license for assigned frequencies while also assigning those same frequencies to another nearby system. I have an SDS-100 and use it daily. I use all the features. I have yet for my SDS to show me a user's LCN. It'll say one was found, but it won't show it because by law, it can't because LCNs are considered confidential. That's why the FCC never lists LCNs in a user's license. If WE find them, we can list them, but that's because we're civilians.
As I said, I was just trying to be helpful, not trying to tell people how to do things. The more people you have looking at a system, the better. But, I guess you just want you and your little clique to do this. I'll butt out and not try to help ever again. This is why I also don't make submissions, because I know it won't be accepted since it didn't come from a recognized member of your inner-circle.

We got this bro thanks for your comments we have been doing this a long time. You have not provided us any new information! Enjoy your day were done here.