Also 20006 saw some activity. RIDs in the 2199xxx range (mostly 21991xx.)Going through recordings and found some *interesting* patches on FiRST off/on the past two days.
Patches of Prince George's Fire Dispatch talkgroup were found on FiRST Talkgroups 20188, 20022, & 20102. Heard on the Anne Arundel Site. This is the same talkgroup range that was heard many years ago when they were doing ISSI with the PG system.
Interesting to see AACo so low in the FIRST tg ranges.8889-8900 should be the Anne Arundel County Backup Zone. I have previously seen AA RID's log on but haven't previously heard any activity on them.
8893 - AA Engine 131 calling Fire Alarm. No response. Then they logged on AA Alpha Talkgroup doing a radio check.
I notice a couple different units logging into 8893 on Sunday; one channel grant at 1607 - I assume that is E131?8889-8900 should be the Anne Arundel County Backup Zone. I have previously seen AA RID's log on but haven't previously heard any activity on them.
8893 - AA Engine 131 calling Fire Alarm. No response. Then they logged on AA Alpha Talkgroup doing a radio check.
It seems that it is "protocol" for Howard to use a FiRST MD Tac channel whenever they are responding to a call in Patapsco Valley State Park because coverage is better. Carroll County & Baltimore County have also used FiRST tac channels for operations in the PVSP area.
A while ago (year or so?), they did a field radio exercise testing radio coverage on Howard, Anne Arundel, Baltimore County, FiRST and I believe CMARC in various PVSP locations. It seemed that FiRST had some of the better coverage in a lot of the areas.
My guess is that the exercise is somewhere in the Avalon, Orange Grove, Glen Artney areas since most of the PVSP radio id's active on the talkgroup are from those areas.
Yesterday it was on MD Tac 5, in the Sykesville area.Howard County is again exercising in PVSP, today using MD Tac 4. Comms are sounding really good, particularly using a SDRTrunk / Airspy Mini combo in my office. Better that any other Phase 2 SDR solution out there right now IMO - blows DSD away, and bests OP25 (not easy.) Very clear and satisfyingly non-warblely.)
There is a new tg posted for the Hagerstown Police on FIRST, and it is listed as T and not TE. Since local police in Washington County tend to be fully encrypted, this seems to be an anomaly. Can anyone verify its use?
Pretty much confirms what I suspected - it didn't make sense that Hagerstown Police would leave their comms open when they have been pretty much addicted to encryption porn for years.This is what I see using DSDPlus, I haven't been recording audio as I usually just look for new stuff, maybe sometimes it is in the clear --
View attachment 114039
13595 isn't ENC and 13600 is ENC so the db is correct for those two.
TBH, I don't remember if that tg was already in the rrdb. Right now it is marked as T which doesn't seem correct since all their tgs on the Washington County UHF system are encrypted. Add that @BM82557 has a DSD log showing it as ENC suggests the the rrdb is incorrect.Somewhere along the way I had that TGID labeled as:
13596 Hagerstown PD (Patch of TG 13557) ENC
Is it no longer a patched TGID? Are they moving to FIRST?
Not that it matters.. Just curious..