I have it included in an "interop" group in for each site along with all the PTACs, LTACs, etc. I hear traffic on it once in a while but not very often.It is part on Zone 1 Interoperability Metro Talk-groups, so I have it in each of my Metro Tower systems. Dakota, Washington Mpls etc, so it is off of the CC for each tower site.
If I am doing it wrong, let me know.
METCOM is designed to be used within the Metro area and is only allowed in consoles and not in field units. Some exceptions for programming into field units for back-up radios and such has been approved in the past.
For what it's worth, McLeod County's Fire fleetmap lists METCOM in one of the Interop zones in their radios.
I had a hunch that METCOM was 31500, based on watching the way a few radios were affiliating, seemingly hitting each zone in the same order as the fleetmap.
I would agree with this. I think what is now happening is the Metro may be preparing to start the change process to come in line with the rest of the state's regional pool talkgroup concept . Just my thoughts and observations.mmtstc said:In the metro, the only radios i have seen Metcom in are consoles and supervisor units. Our dispatchers portables don't even have it in them IIRC.
i have never seen it in a police or fire radio in either Anoka or Hennepin county.
In my UniTrunker database, i have only seen about 40 non-console ID's affiliate with Metcom in 4 years of running UniTrunker. (i have about 32000 radios logged)