DSD+ and Tier 3 systems

[pro92b]

Please list every file that is involved. I used new base files as listed in the screenshot. These files are all empty. What do you clean out to avoid picking up old data? I just don't know what I am missing.

 

[seagravebuff60]

Please list every file that is involved. I used new base files as listed in the screenshot. These files are all empty. What do you clean out to avoid picking up old data? I just don't know what I am missing.

Sure. , I just added a leading semi-colon to my current records in the .networks, .sites, .siteloader, and .frequencies files.

So originally they looked like this:
.networks
TIII, 13, "13 East MTN Trunk"

.sites
TIII, 13, 1.8, "East MTN Trunk - 1.8 Tinker Hill"

.siteloader
TIII, 13, 1.8, "East MTN Trunk - 1.8 Tinker Hill"

.frequencies
TIII, 13, 1.8, 1763, 461.000, 0.0, 0
TIII, 13, 1.8, 1855, 461.575, 0.0, 0
TIII, 13, 1.8, 2353, 464.6875, 0.0, 0

Then after adding a leading semicolon, my files looked like this
.networks
;TIII, 13, "13 East MTN Trunk"

.sites
;TIII, 13, 1.8, "East MTN Trunk - 1.8 Tinker Hill"

.siteloader
;TIII, 13, 1.8, "East MTN Trunk - 1.8 Tinker Hill"

.frequencies
;TIII, 13, 1.8, 1763, 461.000, 0.0, 0
;TIII, 13, 1.8, 1855, 461.575, 0.0, 0
;TIII, 13, 1.8, 2353, 464.6875, 0.0, 0

Then after all those files are saved. Close DSD+, wait for a few minutes, and then reopen it. Then, with FMPx or whatever you use to tune the signal. Tune to the active Control Channel of the site you want to monitor (Example: 461.575 for Tinker Hill), Then that should display System ID 12, and the Site ID as an integer value, as DSD+ is getting that information Over The Air rather than from the DSDPlus.xxx files.



Hope this helps.

 

[pro92b]

Every file you mentioned is part of the base files list. When I put the base files in the DSD+ folder it changes nothing here. The base files are confirmed to be empty of any system information. Still DSD+ reports L13 here and L12 for you. We haven't found the cause yet. Does anyone know which is the real system number, 12 or 13?

I haven't sent a message to the DSD+ author yet. I don't want to waste his time if I am doing something stupid so I'm trying to get more understanding of what the cause might be before contacting the author. I did record the control channel for one minute and can post that file here if anyone has the ability to analyze it. Ultimately it will go to the DSD+ author if this remains intractable.

 

[pro92b]

One thing I forgot to mention is that in your screen shot for site L12-7 there is a line of red text "Blocking network ID change from 12 to 13". For some reason DSD+ is not allowing the ID change. I never get that message and for me the ID does change to 13.

 

[seagravebuff60]

Does anyone know which is the real system number, 12 or 13?

I believe the SysID is 12. DSD+, SDRTrunk and my SDS200 confirm this.

One thing I forgot to mention is that in your screen shot for site L12-7 there is a line of red text "Blocking network ID change from 12 to 13". For some reason DSD+ is not allowing the ID change. I never get that message and for me the ID does change to 13.

Im not exactly sure what thats about, maybe someone more knowledgeable can chime in on that? Also, it may sound like a stupid question but is your DSD updated to 2.448?

 

[pro92b]

I am using 2.448. It's specified in the first line of the screen shot in post 10.

 

[scottjpalmer]

I've lost track of who is seeing what but I wouldn't be changing any data files permanently if your DSD+FL is behaving differently on 2.448 than it did previously. Just wait it out, it is likely the next version will sort it.

 

[seagravebuff60]

I am using 2.448. It's specified in the first line of the screen shot in post 10.

Oh, ok, I must have missed that.

As far as the "Blocking ID Change" in red, ive seen it before on some other TIII Systems (Esp when goosetown was testing other hardware), but I don't recall what it means. The bottom line is that when all of my files are virtually blank from any past East Mountian Records, I tune in to the active control channel of the Tinker Hill site, and it displays SysID 12. Why you are seeing System ID 13 I don't have any explanation except that there is something in the files, but there isn't. So im as confused as you are.

I've lost track of who is seeing what

It's really not that hard; if you just reread this thread, it will tell you what I am seeing vs. what @pro92b is seeing.

 

[ak716]

The one online TIII system here (Tesla) is still the same....

The ones not in the DB due to the lack of information:
The Saia TIII sites are now SysID 5
The suspected NYSEG TIII system is still SysID 6

 

[GTR8000]

I fired up a virgin copy of 2.448 a little while ago and checked as many T3 sites as I could pull in with the Airspy. My findings mirror @pro92b as far as the East Mountain system...nothing has changed, still L13 with x.x Site ID's

Also discovered that the Pleasant Valley (Dutchess) (460.925) site which was previously part of its own system L1 Site 2.4 is now part of the primary East Mountain system L13 Site 2.2

 

[DaveNF2G]

The one online TIII system here (Tesla) is still the same....

The ones not in the DB due to the lack of information:
The Saia TIII sites are now SysID 5
The suspected NYSEG TIII system is still SysID 6

Is that the one I posted as SysID 7?

 

[seagravebuff60]

Just installed a brand new install of DSD+. I don't get it. This is East Mountain Communications, Tinker Hill
Edit: Even after i left the system running after a while, it still showed a system ID 12, Site 7.

 

[pro92b]

The critical line is "Blocking network ID change from 12 to 13". I don't know what triggers that in DSD+ but I never see it. Best I can tell the correct ID is 12 and not 13. The binary string in verbose console output indicates that. My BCD536HP also shows 12.

To add to the confusion, 460.925 still shows L1-2.4 DCC 11 here this morning.

Yesterday I installed fresh DSD+ on a different computer and nothing changed here. The fresh installation consisted of unzipping all base files and adding DSDPlus.exe version 2.448.

 

[seagravebuff60]

For some odd reason, When i changed my DSD to "CC Monitor" it changed the System ID to 13. Now it is staying to show system ID 13. Dont know why. I also adjusted my PPM and Gain values that virtually did nothing. Anyway, sorry for the confusion folks.

To add to the confusion, 460.925 still shows L1-2.4 DCC 11 here this morning.

I believe that was an error on the system Techs Part. Makes no scene why they would have 2 TIII Networks with 2 different IDs

 

[pro92b]

There are two East Mountain licenses for 460.925.
WROT344 Chesnut Hill (Pleasant Valley, Dutchess)
WRKA693 Thunder Hill (Grahamsville, Sullivan)
It's possible we are receiving different sites.

East Mountain has three licenses for 461.000
WRPE926 Catskill (This is the control channel I receive)
WROY824 Pine Plains (This is reported as the control channel in site L13-1.4 (12-3) neighbors list)
WPAP250 WRFV413 Tinker Hill (Putnam Valley) (I think this was monitored with 461.000 in the channel rotation at one time)

Anyway East Mountain seems to use a frequency at more than one site.

 

[GTR8000]

I was just advised that there were TWO versions of 2.448 released. The original 2.448 DSDPlus.exe was created on Dec 5 @ 01:46, and the second 2.448 DSDPlus.exe was created on Dec 6 @ 01:03. So for some inexplicable reason, the author decided it would be a good idea to release two versions of the same release number, instead of making the later one 2.449 or whatever.

Why does this matter? Because the later version once again breaks the Goosetown/Triangle (Selex) Network and Site numbering. That's right, all of this is moot because we're right back to L6 with site numbers like 26.2

 

[pro92b]

Not cool! I already modified DSD+ files to work with 2.448 old version so that's where I stay until a numbered new version comes out. Investigation of DSD+ anomalies is suspended until next version.

 

[GTR8000]

Yeah, it's frustrating, and there is no guarantee that the "fix" we saw for the Selex T3 systems will come back. Apparently it was an unintended change and broke stuff with other brand T3 systems, maybe. At this point I'm kind of throwing my arms up with the whole thing. Hate to be that way, but I don't want to get more agita than I already have over it.

 

[scottjpalmer]

The author is working on it and acknowledges 2.448 "is a mess". I stand by by what I said earlier, leave your data files as they were on 2.444 and wait for the next version.

 

[ak716]

Is that the one I posted as SysID 7?

Yes