Goosetown/Triangle Communications Tier 3 System

[seagravebuff60]

Picking up fairly strong , IDing as NT3/DT3, so this is likely One Voice Max. Site 96 DCC07 Control Channel on 472.2625

We have a very strong UHF opening to the South West from here (Bristol County, Mass), and I am getting it stronger on my South West UHF antenna. UHF Band is open well into New York City.

Nice catch! I'm not picking up anything from here. Site ID, Network ID, DCC, and Frequency line up with current other OneVoice MAX sites. Did you happen to pick up a Neighbor list? Was the channel ID 2869? I couldn't find 472.2625 specifically licensed in NYS, CT, or MA

 

[pro92b]

WPSH994 472.2625 Glen Oaks Queens

This was listed as LCN 4 in 171-007. Site 96 fits in OneVoice MAX if that is a hex site number. The decimal numbers go up from 100. LSN should be 2871.

 

[seagravebuff60]

Weird, I'm not receiving it here in Westchester on two separate geographical computers, yet I receive the Glen Oaks Con+ Site well at both.

 

[u2brent]

Has anyone noticed the system has changed ID's from L3 to H3? Or this an issue with DSD+


Disregard.. LOL.
Hmm, too much coffee?? Or awoke from a coma.

 

[seagravebuff60]

Has anyone noticed the system has changed ID's from L3 to H3? Or this an issue with DSD+
View attachment 172439

Disregard.. LOL.
Hmm, too much coffee?? Or awoke from a coma.

Yeah, I noticed the same thing back in March

 

[W1KNE]

Picking up fairly strong , IDing as NT3/DT3, so this is likely One Voice Max. Site 96 DCC07 Control Channel on 472.2625

We have a very strong UHF opening to the South West from here (Bristol County, Mass), and I am getting it stronger on my South West UHF antenna. UHF Band is open well into New York City.

So it turns out, this kept coming in regardless of the "RF conditions". Research done today (on site) has determined this is Chopmist Hill in Scituate Rhode Island. WPPU889 , licensed to "Jason Garabedian", but highly likely leased out to Goosetown. Based on the "Net 03" ID, I am adding it to the trunk.

 

[DaveNF2G]

Monitoring from Latham, NY. No LCN/LSN info or voice traffic seen yet.

464.0625 TIIIStd CC7 Site H4-16.6 Neighbors 17.4, 17.7, 19.8 (Austerlitz site)

17.4 CC 397
17.7 CC 2141
19.8 CC 397

Other licensed freqs for this site: 464.3625, 464.6125

 

[pro92b]

It's part of OneVoice MAX. Set to TIII nonstd to get the right site designation. The neighbors are Woodstock, Esopus, and Mt Tom sites. Thanks for finding this site.

 

[DaveNF2G]

It's part of OneVoice MAX. Set to TIII nonstd to get the right site designation. The neighbors are Woodstock, Esopus, and Mt Tom sites. Thanks for finding this site.

I'm glad my mistake was at least useful. Thanks for the advice on settings.

 

[DaveNF2G]

OK, I went back through this topic looking for the part about DSD+ giving incorrect data, then being corrected.

I am using version 2.509. I selected Force NonStd in the drop down menu and it worked, until the next beacon, when DSD+ reverted to TIIIStd. According to the Notes.txt file, the menu is the only way to do this. It also says that DSD+ uses the information transmitted by the system to determine Std vs NonStd.

So, is DSD+ still misprogrammed for dealing with TIII systems?

 

[GTR8000]

You force DSD+ to recognize OneVoice MAX as non-standard by using the TIIInonStd prefix in your files....specifically TIIInonStd,H3,

 

[DaveNF2G]

Thanks. Actually, I finally realized that RR could solve this problem. I downloaded the DSD formatted files for this system and all is well.

 

[cg]

There could be something with DSDPlus not properly changing. I do have to manually change to non-standard the ones I monitor.

 

[seagravebuff60]

Ive never had that problem with DSD+. It's been working for me since 2.457+. Ensure all your DSD files (.networks, .sites, .siteloader & .frequencies) use "TIIInonStd", not just one file.

 

[DaveNF2G]

Ive never had that problem with DSD+. It's been working for me since 2.457+. Ensure all your DSD files (.networks, .sites, .siteloader & .frequencies) use "TIIInonStd", not just one file.

The files were the issue. However, when trying to analyze a new system or site that does not appear in any of the support files yet, I would consider the ephemerality of using the menu selection to be a bug.

 

[cg]

They are all set up properly and once I manually change them they stay that way for the duration of the session. Anyway, Dave has started another thread on it, so that is a good place for me to throw out an idea

 

[DaveNF2G]

I just updated the RRDB with Sentinel and it shows 18 sites for OneVoice MAX. The RRDB itself lists 39 sites. I presume that's because it is broken up by state. However, Site 125 (Austerlitz, NY) is not in the Sentinel update.

 

[dave3825]

How did you update? 39 show in my Sentinel. Maybe only 18 are visible and you need to scroll down?

 

[seagravebuff60]

They are all set up properly and once I manually change them they stay that way for the duration of the session. Anyway, Dave has started another thread on it, so that is a good place for me to throw out an idea

From the DSD+ .notes file around line 300.

For non-standard TIII systems that DSD+ does not correctly classify, such as those made by Selex ES, the DSD+ Control menu provides a mechanism to force the system type to "TIIInonStd", or back to "TIIIStd", if desired.

The proper method to force the use of the correct TIII system type by DSD+ is to feed signals to DSD+ via an FMPx direct link or TCP link and to load the DSDPlus.frequencies file with accurate system type, system ID and site frequency data for every monitored TIII site. If this is done, DSD+ will use the data to reliably select TIII system types. Also, the DSDPlus.frequencies file data will override the TIII system type selection option in the DSD+ Control menu.

My understanding is that if you are locked to a new site of OneVoice MAX that is not in any of the DSD+ files yet, like discovering it for the first time, DSD+ will automatically think it is a Standard system (denoted by "(Auto)" shown below) and the way to change that is to force it each time manually or "Code" the information into the DSD files and then once the correct information is in the files it will always recognize the system type in the future as the information in the files will always override any manual input.

So the next time you lock on to the site, either via the site loader or by manually finding it in FMPx, the info will be correct, and DSD will automatically detect that OneVoice MAX is a DMR TIII Non-standard system in the future.

Oh, and if any forgot, OneVoice MAX is using Selex Hardware.

 

[DaveNF2G]

I figured out my mistake. The first time I attached the system to my DMR Trunked Favorite List, I selected the location at the red arrow, which only gave me part of the system.

The second time, I moved up to the County Systems subfolder and selected the location at the green arrow, which gave me the full system.