CLMRN (was CSERN)

[WoodburyMan]

I was able to briefly map a few sites today, Troop C, D, and K as well as Middletown's and Wallingford's P25 system while driving along I-84 as a passenger.

Middletown (BEE00.954-1.01) is officially linked to the following CLMRN sites:
Neighbor: BEE00.3A9-1.27 ; Troop F Simulcast
Neighbor: BEE00.3A9-1.28 ; Troop H Simulcast
Neighbor: BEE00.3A9-1.29 ; Troop I Simulcast
Neighbor: BEE00.3A9-1.30 ; Troop K Simulcast

Also Mapped Wallingford (BEE00.9EF-1.01) and they are linked to the following sites:
Neighbor: BEE00.3A9-1.27 ; Troop F Simulcast
Neighbor: BEE00.3A9-1.29 ; Troop I Simulcast


I also submitted and added 3 new frequencies for Troop D Simulcast.

 

[RESQ766]

I was able to briefly map a few sites today, Troop C, D, and K as well as Middletown's and Wallingford's P25 system while driving along I-84 as a passenger.

Middletown (BEE00.954-1.01) is officially linked to the following CLMRN sites:
Neighbor: BEE00.3A9-1.27 ; Troop F Simulcast
Neighbor: BEE00.3A9-1.28 ; Troop H Simulcast
Neighbor: BEE00.3A9-1.29 ; Troop I Simulcast
Neighbor: BEE00.3A9-1.30 ; Troop K Simulcast

Also Mapped Wallingford (BEE00.9EF-1.01) and they are linked to the following sites:
Neighbor: BEE00.3A9-1.27 ; Troop F Simulcast
Neighbor: BEE00.3A9-1.29 ; Troop I Simulcast


I also submitted and added 3 new frequencies for Troop D Simulcast.

Great work!

 

[WoodburyMan]

Mapped site 34 today, ERV. (I call this site ERV2). It appears to use the same Interop Frequencies ERV1 Site 33 uses, just different CC and ACC's. Submitted to database.

I did this from Lover's Leap Overlook on Route 67 in New Milford / Bridgewater line. (41.556745, -73.387786) Signal with my directional Yagi showed it coming from ESE or WNW. It also only had Troop A Dispatch traffic for the 20 minutes I monitored it, no other TG's. Very weak there as well. I'm thinking its positioned somewhere in the Sherman area, as I couldn't pick the signal up in Roxbury/Woodbury line at a MUCH higher elevation earlier. Sherman area makes sense since it's Troop A territory and covers NM and Sherman area where it may not have coverage from hills.

Basic plot of where it might be. There's some small hills just north of that spot that may be causing some scattering as well.

    Site: 1.34   NAC=3A0    ; Emergency Response Vehicle ERV2

    Neighbor: BEE00.3A9-1.22     ; Troop A Simulcast
    Neighbor: BEE00.3A9-1.31     ; Troop L Simulcast

    Channel 1-1180:   769.38125             VOICE
    Channel 1-1236:   769.73125        SCC
    Channel 1-1260:   769.88125    CC
    Channel 1-2058:   774.86875             VOICE

 

[WoodburyMan]

It seems Litchfield County Dispatch is getting onboard CLMRN.

Extensive testing and such last 3-4 days. 1801 is LCD District 1 which includes Torrington. Getting lots of 1431xxxx ID's on it and some patches. I assume District 1 is Torrington for LCD. I saw some 1802 quick tests but nothing in the TX's that advertise what it is.

I can find anything on Torrington switching to CLMRN, so I'm assuming it's LCD itself getting onboard.

 

[cg]

Torrington FD (at least) is moving over, they did the agreement last year. I heard the fire chief and the district chief testing over this past week.
TFD could be on a 243xx talkgroup but I would expect that LCD would get a range of TGs at some point if there was any amount of interest in moving the regional operation over to the P25 TRS.

chris

 

[scanner1]

Does this new system have Private Call like the old 800 system. I think the T/G used to be 700000 for private call. If so any idea how to enter it into scanner?

 

[WoodburyMan]

Does this new system have Private Call like the old 800 system. I think the T/G used to be 700000 for private call. If so any idea how to enter it into scanner?

They do have private calls. I have picked up and recorded some of them with my SDS200. The only way I've been able to catch them is on my SDS200 having "Search ID" on in System Options. Unsure how Uniden handles private calls if I didn't have that on. They didn't show as a TG, but as Radio ID to Radio ID They are far and few between on Troop L Simulcast, I've seen a few more monitoring Troop A Simulcast and Troop I Simulcast. A few I had seemed to be between CT Transit ID's. Which tracks since Troop L Simulcast rejects most CTT TalkGroups.

 

[Mr_Boh]

Right, and the reason they were in the 700000 range is that is to the Type II system what all subscriber IDs actually start with. Systems with SmartX you actually see an ID that used to be, for example, "123" as 700123 for a Radio ID - probably why they appeared that way in the old system. So a private call would have likely been (in plain english) "700123" to "700321", whereas talkgroups started with 8, so at a system level a radio calling a talkgroup would be "700123" to "800100" if the radio was talking on TG 100.

 

[scanner1]

So maybe we use a subscriber Id (radio Id) and enter a wildcard xx000?

 

[cg]

Uniden scanners get .0 for the I-Call wildcard
The system is pretty much locked to Console to subscriber unit only. No subscriber to subscriber I-Calls.

chris

 

[cg]

New Britain appears to now be part of the system. The were supposed to change to using the State P25 switch and that seems to have happened.

All of New Britain's TGIDs and RIDs on their own system are changed to the CLMRN/CT Statewide standard. (189xx talkgroups, 89xxxx IDs)

chris

 

[gofasters4]

New Britain appears to now be part of the system. The were supposed to change to using the State P25 switch and that seems to have happened.

All of New Britain's TGIDs and RIDs on their own system are changed to the CLMRN/CT Statewide standard. (189xx talkgroups, 89xxxx IDs)

chris

From the Trp F site, can you confirm that TG 18901 sounds encrypted; and TG 18921 sounds like fire dispatch?

 

[cg]

I can't do it from the Troop F site but 18901-18910 are NB PD and are all secure.
18921-27 are FD
others are still being worked out but they all seem to line up with the pattern of the old NB system groups.

chris

 

[55engine]

Are they going to go off the old system

 

[cg]

The old NB P25 system ID is going away. However, the same frequencies are now in use as Site 1 of CLMRN which is New Britain Simulcast.
856.2125 is CC
855.9625 is SCC
Neighbors - Site 28, 33 (Isolated), 41

Old talkgroup IDs and radio IDs are no longer valid.

chris

 

[55engine]

OK so should I take those frequencies and put them on the statewide system or keep everything the same and just change the radio IDs

 

[55engine]

And do we know why they switched over

 

[cg]

Either way will work. I find it easier to program the entire system as just that, a single system. If I had my home setup and lived near New Britain, I would have one scanner set up for New Britain (and perhaps other municipalities) and a different one set up for CSP traffic.

The why I don't know for a fact but I have heard it has to do with the Motorola system they purchased being discounted because that particular system could not be upgraded to the newer versions of P25 software/firmware. They saved money purchasing it back then but to get the benefit of the latest P25 technology, they needed to buy a new P25 switch or move onto the state system. There may also be a benefit with a service contract that goes with the State system for the hardware.

chris

 

[MFCJR]

I set it up by putting the new talkgroups in the old New Britain system. At first I had them in the Hartford Simulcast site because that is how I found them after they switched over. Later in the day they went dead on the Hartford site. I also get a stronger signal on the New Britain site.

 

[gofasters4]

Does anyone know the range of 65xxx numbers that are used for dynamic talkgroups on CLMRN? I think I've only seen 653xx-655xx.
Is this range system/manufacturer defined or administratively defined?
Also I very rarely see radio ID's on these TG's.