It sounds like Waco is taking back the freqs they contributed to TxWARN for their own system but the freqs haven't been dropped from the TxWARN site, yet. Very interesting.
I finally got through listening to the recordings off my HomePatrol. Very interesting and enlightening! (and thanks!)
I'm going to submit the data from my data-gathering now.
As mentioned, there are several frequencies, specifically in the control channel section of the system(s), which are assigned to both systems. I've never seen this before and it definitely will cause problems for scanner users if they have the active CC for one system in the programming for the other.
How I've solved this for myself is to remove 859.2125 from the Waco 572 entry in my HP's favorites list, and remove 858.2125 from TxWARN site 002-030. These removed frequencies are the opposite system's current control channel (that is, 858.2125 is the current Waco 572 channel).
If you don't do this, then your scanner is likely to pick up the control channel from the "wrong" system. This is because the scanner will happily decode whatever control channel it first finds, regardless of whether it's for the system you've named the entry as or not. Professional radios get around this by requiring the control channel data to be validated against the system programming. If our scanners were designed so that they only accepted a control channel broadcasting sysid 1A7 when you were scanning TxWARN, you (nor I) would never learn about sys 572.
I did submit a bunch of talkgroup IDs but the admins haven't gotten around to it yet. I have very little experience with the radio systems in this area but I think you'll find the channel structure is laid out much like the Waco public works channels on TxWARN. I heard plenty of "Go to B" and "Go back to channel A" from various users, which seem to correspond to some channel allocations on TxWARN.
Also, I'm not assisting in West. I had some extra time after being at the races at Circuit of the Americas last week, and as the FD I work for at home in Canada seems to be very similar in composition and area served to West FD, I wanted to stop by, take a look at the town and area, and pay my respects. I also just got back from the Czech Stop where I put a donation in the bucket on the counter. (I wish I'd had the forethought to bring a T-shirt or shoulder patch from my department to contribute to the display outside the firehall.)
I'm heading back to Alberta Saturday morning, but the last 10 days have been excellent in all aspects (except for when I tripped over a curb at a rest stop and wrenched my ankle). So I'm sure I'll be back eventually. Thanks for the warm welcome and support here in the forums.
You will remember (from your stint) that we can move submissions from system to system or county to county as needed. I think he mistakenly moved it to TxWARN instead of the new one when he grabbed it.Interesting - that last submission was submitted to a new system, as you can see from the text auto-added by RR at the bottom of the submission, but the submission got attached to TxWARN somehow.
I think the belief is that the TxWARN site will disappear once the 572 system is operational.
Everything has been submitted and will be in the DB shortly.
If I recall correctly almost all modern scanners manage P25 systems using the Control Channel Only function, which means that all you really need is the current CC in order to track a system. So all you need for TxWARN 002-030 is 859.2125, and all you need for 572's site is 858.2125. Disregard the rest of the frequencies (and hopefully the CC of either site doesn't roll again).