shajoe44
Member
There has been no communication on this site as of now. I am running DSD constantly
Could it be that the system is actually a Cap Max instead of Cap Plus? I’m not sure what the difference is but it might be throwing it off due to their similarities.Can anyone tell me why it sees this new system as Network S2 at start up then shows it as S3 then gives me Forcing TIII network type then settles in as network S2?
It shows it as TIIInonStd (MOT) Site S2-2 DCC:0 RAS NL: 1 3 4
Thanks
2024/08/07 15:45:09 Freq=300.000000 Tuning to 453.387500; dwell time = 0.75 sec
2024/08/07 15:45:10 Freq=453.387500 DCC=0 RAS Found control channel
2024/08/07 15:45:10 Freq=453.387500 Current network: S2
2024/08/07 15:45:10 Freq=453.387500 Current site: S2-2
2024/08/07 15:45:10 Freq=453.387500 Current network: S3
2024/08/07 15:45:10 Freq=453.387500 Current site: S3-1.3
2024/08/07 15:45:10 Freq=453.387500 From .frequencies file, line 293: Forcing TIII network type; Setting network ID, site number.
2024/08/07 15:45:10 Freq=453.387500 Current network: S2
2024/08/07 15:45:11 Freq=453.387500 Current site: S2-2
2024/08/07 15:45:11 Freq=453.387500 DCC=0 RAS S2-2 neighbor: Site S2-4; CC=1
2024/08/07 15:45:11 Freq=453.387500 DCC=0 RAS S2-2 neighbor: Site S2-1; CC=1
2024/08/07 15:45:11 Freq=453.387500 DCC=0 RAS S2-2 neighbor: Site S2-3; CC=1
Can it be monitored with an XPR like Cap Plus?It's a Cap Max for sure
Actually EMS is using Fleettalk until the new system comes online. They simulcast on their VHF frequency. Sometimes on the weekend for unknown reasons the simulcast gets turned off.I did not kno
Can anyone tell me why it sees this new system as Network S2 at start up then shows it as S3 then gives me Forcing TIII network type then settles in as network S2?
It shows it as TIIInonStd (MOT) Site S2-2 DCC:0 RAS NL: 1 3 4
Thanks
2024/08/07 15:45:09 Freq=300.000000 Tuning to 453.387500; dwell time = 0.75 sec
2024/08/07 15:45:10 Freq=453.387500 DCC=0 RAS Found control channel
2024/08/07 15:45:10 Freq=453.387500 Current network: S2
2024/08/07 15:45:10 Freq=453.387500 Current site: S2-2
2024/08/07 15:45:10 Freq=453.387500 Current network: S3
2024/08/07 15:45:10 Freq=453.387500 Current site: S3-1.3
2024/08/07 15:45:10 Freq=453.387500 From .frequencies file, line 293: Forcing TIII network type; Setting network ID, site number.
2024/08/07 15:45:10 Freq=453.387500 Current network: S2
2024/08/07 15:45:11 Freq=453.387500 Current site: S2-2
2024/08/07 15:45:11 Freq=453.387500 DCC=0 RAS S2-2 neighbor: Site S2-4; CC=1
2024/08/07 15:45:11 Freq=453.387500 DCC=0 RAS S2-2 neighbor: Site S2-1; CC=1
2024/08/07 15:45:11 Freq=453.387500 DCC=0 RAS S2-2 neighbor: Site S2-3; CC=1
I was kind of figuring it might be something along those lines. The Edgefield site shows up perfectly. Not sure why this site, which is actually closer, is so weak. Maybe they are still working on it. ThanksUnless the signal is perfect, DSDPlus by default will detect a TIII system as TIIIstandard with different network model and #.# site numbers, until it "detects" certain information in the datastream that confirms it is CAPMAX. If the signal is weak it may never show MOT TIIInonStandard/CAPMAX, or it might take a while for it to show it.
you're welcome. Have fun sleuthing out the new system!I was kind of figuring it might be something along those lines. The Edgefield site shows up perfectly. Not sure why this site, which is actually closer, is so weak. Maybe they are still working on it. Thanks
you're welcome. Have fun sleuthing out the new system!
Yes the Edgefield site shows that information with CC=1 but this site does not show that information. ThanksI should also add that if you see neighbors with cc=1, that either means that the neighboring sites are not online OR that there is no connectivity between those sites and the site you are monitoring. You may have already known that, but I figured I'd throw it out there.