I was monitoring them fine on TRX-1 DMR untill about 6 months ago and now nothing?
Has Evergy disappeared in Kansas City Metro?
- Thread starter kctracker1
- Start date
- Status
Which system are you monitoring? the VHF or 900MHz system?
They have been building out the 900MHz system the last few years, and there are several sites in and around KC Metro. While I haven't been in the region since December, I would suspect with the recent storms the activity would mostly be on the 900MHz by now.
Evergy VHF Trunking System, Kansas City, Multi-State
Evergy VHF Trunking System Profile
www.radioreference.com
Evergy (DMR T3) Trunking System, Various, Multi-State
Evergy (DMR T3) Trunking System Profile
www.radioreference.com
They have been building out the 900MHz system the last few years, and there are several sites in and around KC Metro. While I haven't been in the region since December, I would suspect with the recent storms the activity would mostly be on the 900MHz by now.
I had them on the VHF system that tait built them:
forums.radioreference.com
As far as I can figure out the 900 system is at powerplants and is used for meter reading and switch control. Just can see them droping the VHF with all the investment made in 2020. I can get a couple control channels but cant get a system to work in my SDS-100. I have seen articles on the new broadband and PLTE network they have installed with Erricson and 20 Sites. So maybe they are moving the fleet over to LTE and we will never again here them. It is a 5g system. Glad my rates are going up to pay for all this.
Here's the link to the article:
Evergy (KCP&L - Westar Energy)
What I've learned so far about the DMR TIII System Built by Tait Communications TN9300 network TP9300 Portables TM 9300 Mobiles 23 sites associated with the system Crews work out of the various service centers Talk Groups 6200 Johnson County Service Center 108th and Renner...
Here's the link to the article:
I can see where the confusion is, so let me help to clarify (full disclosure, I am a former employee of Aquila, one of the three predecessor companies that make up Evergy, and still hold stock in Evergy).
When KCP&L merged with Aquila (formerly Missouri Public Service or Utilicorp/United) they became Great Plains Energy. The Tait system was contracted to be built, with the intent of replacing KCP&L's Motorola Analog system, and Aquila's non-trunked repeater network. Likewise, Westar Energy had a separate 900MHz Motorola Analog system covering its operating territory and had started working with Motorola to build out a large Capacity Max system to replace their aging system. When Great Plains and Westar merged to form Evergy, the decision was to finish building out the respective systems, but at some point, consolidate into a single system. The Capacity Max system was chosen, and so they have started building additional sites to cover the old KCP&L (what is now called the "Metro" Division) and Aquila (now called the "Missouri West" Division) service areas.
Much of what you see in RRDB was collected by me over 4 trips in November/December of 2021-2022 (I've got another trip slated for September plus my November/December trips this year, and hope to get a day or two on the road each trip to survey more), and I can tell you that, especially the sites in the Metro area, were not online in 2021, but then showed up in 2022, and there are likely more sites online now in Missouri. I have a lot of detail in the Wiki for the system, including a map showing all the licenses for the 900 MHz system (there's over 100 sites with licensees or pending applications, I probably should check with the FCC to see if any more have been granted).
The 900 MHz system will serve as packet data (data terminals in truck, although cellular LTE might be their primary means for faster bandwidth), location data ("LRRP"), as well as voice communications for the entire network. This includes some power plant operations, but also their crews in the field. The one exception to this is Wolf Creek Generating Station at Burlington, which has a separate 2-site Tier 3 system (not yet in RRDB, since I don't have enough data on it, but the information I had is in the Wiki).
The Ericsson LTE system is only slated for remote meter reading as well as some "remote control" equipment control and monitoring but will not be carrying voice traffic. aka the "Smart Grid" network.
Based on your location you show in your messages, I presume that you are in Prairie Village. You likely should be picking up the Shawnee Site, as well as the Kansas City, MO site on the 900MHz system, if not also the Downtown Kansas City site (I didn't get it confirmed so it's not in RRDB but there is also a site in that area - see the Wiki). Be sure to set your SDS100 to ID Search (in Sentinel it will be under the "Options" for the system), as there most likely is a lot more than the 2 talkgroups listed in RRDB being used.
I hope this helps, but don't hesitate to ask if you have any more questions.
When KCP&L merged with Aquila (formerly Missouri Public Service or Utilicorp/United) they became Great Plains Energy. The Tait system was contracted to be built, with the intent of replacing KCP&L's Motorola Analog system, and Aquila's non-trunked repeater network. Likewise, Westar Energy had a separate 900MHz Motorola Analog system covering its operating territory and had started working with Motorola to build out a large Capacity Max system to replace their aging system. When Great Plains and Westar merged to form Evergy, the decision was to finish building out the respective systems, but at some point, consolidate into a single system. The Capacity Max system was chosen, and so they have started building additional sites to cover the old KCP&L (what is now called the "Metro" Division) and Aquila (now called the "Missouri West" Division) service areas.
Much of what you see in RRDB was collected by me over 4 trips in November/December of 2021-2022 (I've got another trip slated for September plus my November/December trips this year, and hope to get a day or two on the road each trip to survey more), and I can tell you that, especially the sites in the Metro area, were not online in 2021, but then showed up in 2022, and there are likely more sites online now in Missouri. I have a lot of detail in the Wiki for the system, including a map showing all the licenses for the 900 MHz system (there's over 100 sites with licensees or pending applications, I probably should check with the FCC to see if any more have been granted).
The 900 MHz system will serve as packet data (data terminals in truck, although cellular LTE might be their primary means for faster bandwidth), location data ("LRRP"), as well as voice communications for the entire network. This includes some power plant operations, but also their crews in the field. The one exception to this is Wolf Creek Generating Station at Burlington, which has a separate 2-site Tier 3 system (not yet in RRDB, since I don't have enough data on it, but the information I had is in the Wiki).
The Ericsson LTE system is only slated for remote meter reading as well as some "remote control" equipment control and monitoring but will not be carrying voice traffic. aka the "Smart Grid" network.
Based on your location you show in your messages, I presume that you are in Prairie Village. You likely should be picking up the Shawnee Site, as well as the Kansas City, MO site on the 900MHz system, if not also the Downtown Kansas City site (I didn't get it confirmed so it's not in RRDB but there is also a site in that area - see the Wiki). Be sure to set your SDS100 to ID Search (in Sentinel it will be under the "Options" for the system), as there most likely is a lot more than the 2 talkgroups listed in RRDB being used.
I hope this helps, but don't hesitate to ask if you have any more questions.
Thanks MW I knew about the changes with the merger and spent lots of time on DSD plus in 2020 finding the freqs and system that tait installed.. I didn't know about the reuse of the 900 system. So far cant seem to get Shawnee or Kansas City locations to work still trying. I did find this:
www.fiercewireless.com
Communications will be on LTE to allow easy comms between companies.
Anterix scores $30M lease with Evergy for 900 MHz spectrum
Anterix is building steam with utility companies, notching a third long-term lease for use of its 900 MHz spectrum in a 20-year $30 million agreement with power company E | Anterix is gaining momentum in the utility sector, securing a $30 million long-term lease with Evergy for 900 MHz spectrum...
Anterix hoped to have built out their LTE network, but I can tell you it is still very much a work in progress (in the Dallas area where I'm located they've still got their legacy DMR radios on the air in that frequency range, so they haven't even started installing the LTE network here), since they have to get existing users off of it (936.5 MHz to 939.5 MHz). Likewise, to quote the article you linked:
That again points to the LTE network being used for "command and control" functions, what is commonly referred to as "system operations", as a part of the Smart Grid. It does not mention anything about "Voice over LTE", similar to what AT&T FirstNet is offering (and I currently don't know of any public safety agencies that are using FirstNet for primary dispatch communications).
The quote about interoperabilty was the CEO of Anterix, and while it may be a pie-in-the-sky type dream, their platform is not anywhere near ready for that, and won't be for years. Also, while there is Voice over LTE equipment on the market, being that this is a new band for many of them, I don't know if any of the manufacturers will work with Anterix yet, when they do become operational. I suspect companies like Ameren UE, Evergy, Oncor and Reliant will stick to their proven radio systems for voice until the equipment reaches the end of its lifecycle at minimum, before looking at something like a Voice over LTE system, at which point it might be more mature to support such functionality.
That again points to the LTE network being used for "command and control" functions, what is commonly referred to as "system operations", as a part of the Smart Grid. It does not mention anything about "Voice over LTE", similar to what AT&T FirstNet is offering (and I currently don't know of any public safety agencies that are using FirstNet for primary dispatch communications).
The quote about interoperabilty was the CEO of Anterix, and while it may be a pie-in-the-sky type dream, their platform is not anywhere near ready for that, and won't be for years. Also, while there is Voice over LTE equipment on the market, being that this is a new band for many of them, I don't know if any of the manufacturers will work with Anterix yet, when they do become operational. I suspect companies like Ameren UE, Evergy, Oncor and Reliant will stick to their proven radio systems for voice until the equipment reaches the end of its lifecycle at minimum, before looking at something like a Voice over LTE system, at which point it might be more mature to support such functionality.
Thanks, understood. Any idea why the SDS-100 wont pick up any of these coms? Maybe a different antenna other than the oem?
It worked on my SDS100 when I was on my road trips, but most of the data gathering was via DSDPlus. If I was to render a guess, one of two things is happening - either the SDS100 is getting hung on the LRRP channel (one channel of the site is a constant stream of location data for the various trucks) - it shouldn't but that's a possibility, or there is other frequencies not in RRDB (and thus not in your scanner) that are being used - a distinct possibility, as I show in my notes 4 additional frequencies potentially for Shawnee, and a similar amount for Kansas City Missouri. I would have to look at it with DSDPlus to see what is on the control channel to determine what's going on.
nd5y
Member
Search the whole band 935-940 MHz in 12.5 kHz steps in analog mode with the squelch at the lowest possible setting and see how many DMR control channels you find. It helps if you know what a control channel sounds like. Then determine what FCC licenses they belong to. Then analyze them with the SDS100 or whatever software you have.
Already did that only getting three so far and only one with color code 15 relates to kcmo and kck locations. Gonna set DSD plus back up see whats happening here. Thanks gang..
Wanted to provide you with an update. I may have found the reason your SDS100 was deaf on the 900MHz system - almost all of the sites listed in RRDB have the incorrect LCN values (the value showing as LCN is actually the Channel ID or LSN), which means the trunk tracking is not working as intended. SDS100's use the LCN value, while DSDPlus uses the LSN/Channel ID value. Since I built Evergy from scratch using my own data, I compensated for it, thus why mine worked - but when I submitted the data, I submitted the LSN values, and they didn't catch that (although some sites I didn't touch also had the same error). I've since updated my submission template to compensate for that (I know the RRDB database maintainers have a default of LCN when inputting into the database, so my template now sends them both, just so it's clear)
I just submitted a massive update to all of the affected sites to get it corrected, so you should see the updates post in the next few days. If you want to fix it sooner, the values shown should be -1 (make it an even number, since they will always be odd), then divide by 2.
So, here's what the corrected sites will look like:
Shawnee:
Kansas City, Kansas
Kansas City, Missouri (63rd Street)
Let me know if this gets your SDS100 to working with the system.
I just submitted a massive update to all of the affected sites to get it corrected, so you should see the updates post in the next few days. If you want to fix it sooner, the values shown should be -1 (make it an even number, since they will always be odd), then divide by 2.
So, here's what the corrected sites will look like:
Shawnee:
| LCN | LSNs or CH IDs | Frequency | Color Code | |
|---|---|---|---|---|
| 23 | 47/48 | 935.275 | 13 | Control Channel |
| 35 | 71/72 | 935.425 | 13 | Control Channel |
| 47 | 95/96 | 935.575 | 13 | |
| 70 | 141/142 | 935.8625 | 13 |
Kansas City, Kansas
| LCN | LSNs or CH IDs | Frequency | Color Code | |
|---|---|---|---|---|
| 84 | 169/170 | 936.0375 | 15 | Control Channel |
| 102 | 205/206 | 936.2625 | 15 | Control Channel |
| 114 | 229/230 | 936.4125 | 15 |
Kansas City, Missouri (63rd Street)
| LCN | LSNs or CH IDs | Frequency | Color Code | |
|---|---|---|---|---|
| 27 | 55/56 | 935.325 | 15 | |
| 51 | 103/104 | 935.625 | 15 | Control Channel |
| 64 | 129/130 | 935.7875 | 15 |
Let me know if this gets your SDS100 to working with the system.
Thanks, I was still having trouble with the system working with tye SDS -100. However I ran accross a post of yours from some time back about a small program to change the LSN and LCN. Basically halved the channels listed and entered those numbers and off it went. Sorry I was going to contact you, but was so neat to have the scanner working I forgot. I did get the Remtronix antenna from Zip. What a difference that made. I'm getting KCMO site the best, and inside the house, clear as a bell.
Here is what I have found so far.
KCMO 63rd street
LCN CH ID FREQUENCY COLOR CODE
27 55/56 935.325 15
*39 79/80 935.475 15
51 103/104 935.625 15
64 129/130 935.7875 15
*77 155/156 935.950 15 CONTROL CHANNEL
Now I'm trying to make sense of the TG ID's.
110 Shows up occasionally for service trucks
210 is showing up for calls here in JoCo and Metro
216 is showing up for metro calls
219 is showing up a lot for service calls Metro wide
So I am assuming somehow the TG's will relate to the current Evergy service areas below.
Still a work in progress, and thanks for your help sofar. Much appreciated.
mwjonesMember
Premium Subscriber
JoinedApr 8, 2003Messages477LocationVan Alstyne, TX
Most Tier 3 systems, including Motorola's Capacity Max do use a bandplan of sorts, but it sounds like you're already ahead of that with the data from your SDS100/200. The LCN's identified there can be turned into LSN's for DSDPlus with a bit of simple math:
Multiply the LCN times 2 and add 1, so for example LCN 485:
485 x 2 = 970 + 1 = 971
So 971 is what you'd put in your DSDPlus.frequencies file.
You can also use the DMR Frequency Calculator to construct the bandplan (see the below message for the link to the latest version):
LCN to Frequency calculator for DMR TIII
Thanks for the reply, @Kazzaw. It's the OrionMax network in NSW. I haven't forgotten about you, I just haven't had a chance to make it near a computer today to see what I have logged for around NSW. I'll have a look tomorrow and get back to you
forums.radioreference.com
Here is what I have found so far.
KCMO 63rd street
LCN CH ID FREQUENCY COLOR CODE
27 55/56 935.325 15
*39 79/80 935.475 15
51 103/104 935.625 15
64 129/130 935.7875 15
*77 155/156 935.950 15 CONTROL CHANNEL
Now I'm trying to make sense of the TG ID's.
110 Shows up occasionally for service trucks
210 is showing up for calls here in JoCo and Metro
216 is showing up for metro calls
219 is showing up a lot for service calls Metro wide
So I am assuming somehow the TG's will relate to the current Evergy service areas below.
Still a work in progress, and thanks for your help sofar. Much appreciated.
Glad you were able to sort the LCN's out. The two additional frequencies you identified for 63rd Street were in my master list, but had not been verified, so I would say those are likely correct (be sure to submit them as an update to RRDB)Thanks, I was still having trouble with the system working with tye SDS -100. However I ran accross a post of yours from some time back about a small program to change the LSN and LCN. Basically halved the channels listed and entered those numbers and off it went. Sorry I was going to contact you, but was so neat to have the scanner working I forgot. I did get the Remtronix antenna from Zip. What a difference that made. I'm getting KCMO site the best, and inside the house, clear as a bell.
Here is what I have found so far.
KCMO 63rd street
LCN CH ID FREQUENCY COLOR CODE
27 55/56 935.325 15
*39 79/80 935.475 15
51 103/104 935.625 15
64 129/130 935.7875 15
*77 155/156 935.950 15 CONTROL CHANNEL
Now I'm trying to make sense of the TG ID's.
110 Shows up occasionally for service trucks
210 is showing up for calls here in JoCo and Metro
216 is showing up for metro calls
219 is showing up a lot for service calls Metro wide
So I am assuming somehow the TG's will relate to the current Evergy service areas below.
Still a work in progress, and thanks for your help sofar. Much appreciated.
The service areas aligning with the talkgroups would likely be correct, as the three divisions don't really overlap (What they show Kansas and Missouri Metros are one division, but they separate them for the employee benefit of not having to pay taxes in both states like I did when I worked for Utilicorp - now Missouri West - and lived in Kansas).
Honestly, I find identifying the talkgroups the hardest part of any system, unless you have inside information, you pretty much have to be patient and listen to a lot of traffic. Granted the newer scanners and SDR radio applications make it easier, but it's still tough work.
Updated from massive submission, thanks @mwjones, and added KC 63rd st 2 additional freqs, thanks @kctracker1 - if you can verify the TGs please submit them - thanks!
Wally through the use of DSD+ and my SDS-100 The following Talk Groups are active in the KC Metro area:
110 Has not be seen so far in Kc Metro area.
??? Kansas Central
210 Kansas Metro (Johnson County) [Don't believe it has any thing to do with Lawrence Power Plant.]
216 Missouri Metro
219 Missouri West
Still trying to nail down a few others that have appeared less than 10 times so far. More to follow.
Thanks for your efforts, I did Admin here in the early 2000's.
Wrapping up my road trip to Kansas and will be heading back to Texas soon. Covered a lot of miles, and will have a bunch of updates to the system coming (double digit count of new sites). In Kansas City, the Downtown KCMO Site is online (site 61) and site 56 is likely Gardner. Still got a lot of logs to parse, lots of data to sort, so it will be a few days before I can get them submitted (fair warning @wbloss, sorry).
Plenty of other mysteries discovered through the course of this, and that information will be making an appearance in an update to the Wiki page. Will be planning for what I'm going to target during my next trip into the region in November.
Stay tuned...
Plenty of other mysteries discovered through the course of this, and that information will be making an appearance in an update to the Wiki page. Will be planning for what I'm going to target during my next trip into the region in November.
Stay tuned...
All of the new sites and additional frequencies to existing sites etc. have been added to the database: Evergy (DMR T3) Trunking System, Various, Multi-State
Now we need locals to ferret out talk groups - there are many!
ALSO, @mwjones found a whole stand-alone system at the Wolf Creek generation plant that is fairly busy. Need more Talkgroup-finding there also.
Now we need locals to ferret out talk groups - there are many!
ALSO, @mwjones found a whole stand-alone system at the Wolf Creek generation plant that is fairly busy. Need more Talkgroup-finding there also.
I want to say Thank You to @wbloss for putting up with the massive dumps of information I submit. When I do a road trip I may generate tons of data, and once I return home, I can filter it out and sort it into something that is usable by the admins. Sadly, it ends up being a massive submission each time (I probably should split it up, but there's pros and cons to each). Wally has been my sanity check validating a lot of my data (yes, I make errors translating the date from one source to another, so having someone that catches my errors helps to make sure the RRDB is as accurate as we can make it), and that is much appreciated.
I track all the changes that I submit in a document file, and in 3 years, Evergy has produced 9 submissions and 62 pages in that file since the first submission I made to it on December 4, 2021 (and that's not counting the VHF system, nor the new submission for Wolf Creek).
Not bad for someone who lives over 400 miles from the majority of the system and only gets up there 2-3 times a year. The September trip was approximately 2,500 miles, including the drive up there and back, most of which was collecting data.
My opportunities to get out there to capture more data during the November and December planned trips may not be as fruitful as this one, but will try and expand more on what is already out there (when visiting, my base of operations is Ottawa, and this trip finally identified Gardner, and I suspect I have the site number for LaCygne - details in the Wiki - but that will be one of my targets for those trips, along with covering the former Missouri Public Service/Utilicorp service area, where there's a lot of holes remaining).
I track all the changes that I submit in a document file, and in 3 years, Evergy has produced 9 submissions and 62 pages in that file since the first submission I made to it on December 4, 2021 (and that's not counting the VHF system, nor the new submission for Wolf Creek).
Not bad for someone who lives over 400 miles from the majority of the system and only gets up there 2-3 times a year. The September trip was approximately 2,500 miles, including the drive up there and back, most of which was collecting data.
My opportunities to get out there to capture more data during the November and December planned trips may not be as fruitful as this one, but will try and expand more on what is already out there (when visiting, my base of operations is Ottawa, and this trip finally identified Gardner, and I suspect I have the site number for LaCygne - details in the Wiki - but that will be one of my targets for those trips, along with covering the former Missouri Public Service/Utilicorp service area, where there's a lot of holes remaining).
- Status
Similar threads
