Goosetown/Triangle Communications Tier 3 System

[cg]

Another new site in southern New England is active. Still trying to determine the exact location as the license for the other channels in the 171 system show 2 sites. 171 shows the site name as "Stonington" but is really in North Stonington. The other licensed location is 15 miles away in Montville CT. Anyway...

2024/12/18 11:30:35 Freq=454.200000 Current network: H3 OneVoice Tier III
2024/12/18 11:30:35 Freq=454.200000 Current site: H3-102 Montville/N Stonington?
2024/12/18 11:31:03 Freq=454.200000 DCC=7 H3-102 neighbor: Site H3-96; CC=2871 472.26250 Chopmist Hill
2024/12/18 11:31:09 Freq=454.200000 DCC=7 H3-102 neighbor: Site H3-101; CC=2439 454.23125 Hartford

Also, found because it showed as neighbors to new site 96...
2024/12/18 11:14:14 Freq=472.262500 Current network: H3 OneVoice Tier III
2024/12/18 11:14:14 Freq=472.262500 Current site: H3-96 Chopmist Hill
2024/12/18 11:14:42 Freq=472.262500 DCC=7 H3-96 neighbor: Site H3-153; CC=2233 463.93750 Barnstable
2024/12/18 11:15:48 Freq=472.262500 DCC=7 H3-96 neighbor: Site H3-102; CC=675 454.20000 Montville/N Stonington?

 

[cg]

Site 101 is sending more Neighbors now but I ran into a couple issues.

First is a minor typo in the site download list, 101 should be 2439 rather than 2440. Shouldn't matter but it messed up the Neighbor list lining up wrong freqs with the location names. Changing to 2439 fixed it.

Second item is that Site 101 is showing Site 103 as a Neighbor using Ch 2769 / 471.6250. That frequency shows as Site 130 in Putnam Valley NY which would not be unreasonable as a Neighbor. If anyone monitors that site or another that may be a Neighbor to it, can they verify which is correct?

 

[pro92b]

Site 121 lists site 130 as a neighbor using Ch 2769 471.625 as the control channel. Reusing an RF frequency is not unusual if there is some distance between the sites.

I don't understand the issue with ch 2439 and 2440. Those channels are the same RF frequency and DSD+ should be able to use either one in its frequency file.

 

[GTR8000]

Site 101 is sending more Neighbors now but I ran into a couple issues.

First is a minor typo in the site download list, 101 should be 2439 rather than 2440. Shouldn't matter but it messed up the Neighbor list lining up wrong freqs with the location names. Changing to 2439 fixed it.

Second item is that Site 101 is showing Site 103 as a Neighbor using Ch 2769 / 471.6250. That frequency shows as Site 130 in Putnam Valley NY which would not be unreasonable as a Neighbor. If anyone monitors that site or another that may be a Neighbor to it, can they verify which is correct?

The LSN for Site 101 are already 2439 (slot 1)/2440 (slot 2) as listed in the site details: OneVoice MAX Site: Hartford

Assuming you're referring to the "Download DSD Formatted Frequencies Data File", it could be a weird bug with that LSN. All of the LSN's for this system in that file should end in an odd digit, not an even digit. I'll pass this along to Lindsay.

Anyway, 102 should be Montville and 103 should be Glastonbury. Putnam Valley 130 is not going to be a peer of sites near Hartford.

 

[cg]

Sorry, yes the file for downloads.
This is what is confusing me. These are the reported Neighbors on 2 separate setups. Channel/frequencies of Neighbors do not match up with known channels of sites. Bloomfield and Glastonbury are not T Band (in Hartford CT area). If I delete all of the other sites and frequencies for OV Max except Hartford (Farmington), I get the same Site and channel matchup.



Using latest 2.509 version, etc.
Perhaps since the system is still being built out, someone just pushed out info for testing

 

[GTR8000]

@blantonl fixed the bug with the DSDPlus.frequencies file download, should be good to go now.

 

[seagravebuff60]

101 is not showing up in the NL for 130


For this system, the NL is transmitted over the air as well as that neighbor's LSN (or CC=). Nothing else. The DSD+ user configures the actual frequency of the site, like 471.625, and the site's name in the necessary files.

To get DSD+ to show the actual frequency and the site name, the site must be programmed correctly in your .frequencies file to match the NL that the site that DSD+ is showing.


Similarly, if you want it only to show the site's name, make sure that the site is programmed into your .sites file.


For me, all the NY/CT/NJ/MA/RI sites are listed in my .sites file so that I can see the name of any site that shows up in the NL; I have only the sites I can pick up programmed into the .freqencies file. Not all DMR systems behave like this so that you may see different manufacture-based results.

To answer your question, it is common to see different sites reuse frequencies. I can't pick up 101 from here yet, but I'm assuming it's just there for testing or someone overlooked something. This system is not anywhere near being complete. Since you might be closer, could u pick up anything on 471.625?

 

[cg]

Thanks for your help and for verifying that site.
There is no T band in the Greater Hartford area as it is not allowed here (and nothing seen except during good skip). I can get Paxton if I go mobile but as of this morning there were no neighbors showing there (which is consistant with previous loggings)
Not a problem in the files, showing the same CC info before I added any info except the single site/CC freq and network to the new install.
Then I was using the RR download with only a couple site names changed. Looks like the site is transmitting the wrong info for the neighbors. I will check back after the first week of January to see if it is corrected.

 

[cg]

Two new OneVoice Max sites online. Glastonbury CT & Exeter RI. One from me and one from a SE CT monitor.

Exeter, RI, 266 Nooseneck Hill Rd
WPNX774, ULS License - Industrial/Business Pool, Trunked License - WPNX774 - GARABEDIAN JR, LAWRENCE
H3-97
463.5625, LCN 1087, LSN 2173/4
DCC 7

Glastonbury, CT, Birch Hill Rd
WQWN437, ULS License - Industrial/Business Pool, Trunked License - WQWN437 - REPEATER NETWORK LLC
H3-103
464.0375, LCN 1087, LCN 2173/4
DCC 7

 

[seagravebuff60]

Exeter, RI, 266 Nooseneck Hill Rd
WPNX774, ULS License - Industrial/Business Pool, Trunked License - WPNX774 - GARABEDIAN JR, LAWRENCE
H3-97
463.5625, LCN 1087, LSN 2173/4
DCC 7

Glastonbury, CT, Birch Hill Rd
WQWN437, ULS License - Industrial/Business Pool, Trunked License - WQWN437 - REPEATER NETWORK LLC
H3-103
464.0375, LCN 1087, LCN 2173/4
DCC 7

How can the LCN be the same if they are 2 different frequencies? The LCN for Site 103 should be 1124 (LSN 2249) calculated from 464.0375

 

[pro92b]

LCN for 464.0375 calculates to 1086.

Are there neighbor sites for 097 and 103?

 

[seagravebuff60]

LCN for 464.0375 calculates to 1086.

Math is hard.

 

[pro92b]

My error, should be 463.5625 is LCN 1086

 

[cg]

Sorry, too much copy and paste and too little previewing.
97 uses 2173 and 103 uses 2249

97 Neighbors are 96, 102, 103, 153
103 Neighbors are 96, 97, 101, 102, 151, 152

All the Neighbors show properly now for all the sites I can monitor, the hiccup is fixed now.
Site 104 (Bloomfield) is shut off again. This is typical behavior for that site when new sites are installed.

 

[seagravebuff60]

Wiki updated. OneVoice MAX Sites - The RadioReference Wiki

 

[cg]

Some interesting behavior to watch for during the changeover...
Site H3-101, "Hartford", is running 454.23125 as the CC and 454.21875 as a voice channel. However, that voice frequency is also the CON+ system 171-26 control channel. So the behavior appears to be that the Tier III uses the second slot for voice with the CON+ CC on slot 1.
DSDPlus does rapidly scroll the CON+ Neighbors as TIII Neighbors. This continues until voice traffic ends:
2025/02/11 10:25:07 Freq=454.218750 DCC=7 H3-101 neighbor: Site H3-8
2025/02/11 10:25:07 Freq=454.218750 DCC=7 H3-101 neighbor: Site H3-9
2025/02/11 10:25:07 Freq=454.218750 DCC=7 H3-101 neighbor: Site H3-15
2025/02/11 10:25:07 Freq=454.218750 DCC=7 H3-101 neighbor: Site H3-50
When the voice traffic ends, the TIII Neighbors show back up.
2025/02/11 10:25:12 Freq=454.231250 DCC=7 H3-101 neighbor: Site H3-102; CC=675 454.20000 Montville, CT
2025/02/11 10:25:18 Freq=454.231250 DCC=7 H3-101 neighbor: Site H3-151; CC=397 452.46250 Holyoke, MA
2025/02/11 10:25:24 Freq=454.231250 DCC=7 H3-101 neighbor: Site H3-152; CC=2603 470.58750 Paxton, MA
2025/02/11 10:25:30 Freq=454.231250 DCC=7 H3-101 neighbor: Site H3-115; CC=2765 471.60000 North Salem, NY
2025/02/11 10:25:36 Freq=454.231250 DCC=7 H3-101 neighbor: Site H3-103; CC=2249 464.03750 Glastonbury, CT

Not a real common issue but raw recording going to DSDPlus email.

 

[BM82557]

Site 210 is a neighbor to site 195 --



Any ideas on it's location?

 

[Whiskey3JMC]

Site 210 is a neighbor to site 195 -- Any ideas on it's location?

Wiki says Newport, Perry County PA: WQSK899

 

[BM82557]

I forgot about the info in the wiki, thanks