Brampton Connect Plus

[mtindor]

Below would be a sample of how you would disambiguate between two or more S1 systems.

​

Notes.txt from DSDPlus FastLane

​

Network ID prefixes can be used to disambiguate TIII networks that use the same network ID.​

Prefix values should be in the range 1 to 4095. We recommend using the first three or four​

digits of the page number of the Radioreference.com database entry for a given network.​

Brampton T3 is System ID 13213 in the DB (not to be confused with System IDs reported by trunked systems)

 https://www.radioreference.com/db/sid/13213

So, use something like 132 or 1321 as the disambiguation. In this example I'll use the first four of 1321 (since it's limited to 4095).

So "S1" in the files turns into "S1321:1"

DSDPlus.networks
; Brampton T3 - S1
TIIInonStd,S1321:1,"Brampton T3"

DSDPlus.sites
; Brampton T3 - S1
TIIInonStd,S1321:1,1,"2100 Bovaird Drive East"
TIIInonStd,S1321:1,2,"100 County Court Boulevard"

DSDPlus.frequencies
; Brampton T3 - S1
; I'm assuming those LSNs / CH IDs are correct
TIIInonStd,S1321:1,1,213,939.25,0.0,0
TIIInonStd,S1321:1,2,409,938.525,0.0,0
TIIInonStd,S1321:1,2,413,938.55,0.0,0

 

[mtindor]

@mciupa : add the S1 Network model / Network ID to the Brampton T3 system when you get a chance please.

That way the DSDPlus downloads for that system under the "Downloads" section will be accurate.

tnx

Mike

 

[VA3ADP]

I think DSDPlus is going to presume TIII Standard until it receiver either an MFID (manufacturer ID) or some other clue that tells it that it's something like a CAPMAX (MOT) system. So quite often, if you are hitting a new site for which you don't have anything in your DSDplus.* files, a CAPMAX system will initially show as TIIIStandard. And of course, if you have a week signal or one with interference on it, that will delay any detection of it being TIIInonStandard MOT aka CAPMAX.

I'd bet the Air Canada site in the DB (also listed as TIII Non-Standard is probably also going to be a MOT CAPMAX system, but I haven't seen screenshots of it). When you see MOT and TIII, it's CAPMAX period.

Those of you who have multiple S1 systems (or any x# T3 systems like L10, etc where there are more than one system with the same Network model and Network ID) are going to have to get proficient with using the disambiguation method that Slicerwizard mentioned in a further down post.

I Agree with you, regardless of what DSD+ is indicating they are more than likely CapMax systems.

Below would be a sample of how you would disambiguate between two or more S1 systems.

​

Notes.txt from DSDPlus FastLane

​

Network ID prefixes can be used to disambiguate TIII networks that use the same network ID.​

Prefix values should be in the range 1 to 4095. We recommend using the first three or four​

digits of the page number of the Radioreference.com database entry for a given network.​

Brampton T3 is System ID 13213 in the DB (not to be confused with System IDs reported by trunked systems)

 https://www.radioreference.com/db/sid/13213

So, use something like 132 or 1321 as the disambiguation. In this example I'll use the first four of 1321 (since it's limited to 4095).

So "S1" in the files turns into "S1321:1"

DSDPlus.networks
; Brampton T3 - S1
TIIInonStd,S1321:1,"Brampton T3"

DSDPlus.sites
; Brampton T3 - S1
TIIInonStd,S1321:1,1,"2100 Bovaird Drive East"
TIIInonStd,S1321:1,2,"100 County Court Boulevard"

DSDPlus.frequencies
; Brampton T3 - S1
; I'm assuming those LSNs / CH IDs are correct
TIIInonStd,S1321:1,1,213,939.25,0.0,0
TIIInonStd,S1321:1,2,409,938.525,0.0,0
TIIInonStd,S1321:1,2,413,938.55,0.0,0

Your calculations worked perfectly! this is what I am currently seeing on DSD+. I will. let it run for a few minutes and make sure it doesn't default back overnight. I am seeing a few Registration/Authentication Checks with some RID's. I am not sure why Tier III systems do that. I am assuming its just a digital handshake to see if the radio is still affiliated to the system.

 

[mtindor]

Your calculations worked perfectly! this is what I am currently seeing on DSD+. I will. let it run for a few minutes and make sure it doesn't default back overnight. I am seeing a few Registration/Authentication Checks with some RID's. I am not sure why Tier III systems do that. I am assuming its just a digital handshake to see if the radio is still affiliated to the system.

Thanks for the screenshot. Glad it is working. Even more important though, when you see a bunch of private or group calls and they are displayed in the Event window (main DSDPlus screen like above), please also take a screenshot of the channel activity window. This is only useful if (a) you've been sitting on that site for a while without moving and (b) there have been private or group calls. If you have data for this site on your screen but you've since moved to another site/system, then the channel activity window would be wrong for this system and the screenshot would not be useful.

Can anybody pick up both sites 1 an 2?

If you can pick up both with DSDPlus, please report what it says for the neighbor CC=

check Site 2 - 100 County Court Boulevard? See if it's still using 938.525 as the CC as of this morning?

VA3ADP's screenshot (presumably from overnight) while monitoring Site 1 shows that Site 2's CC is LSN/CH ID 411 (which would be the 411/412 pair)

S1321:1-1 neighbor: Site S1321:1-2; CC=411  100 County Court Boulevard

On the actual trunked system in the DB, there are 409/410 and 413/414. There is no 411/412 listed.

If Site one still shows Site 2 CC=411, and you tune to 938.525 and pick up site 2, then 938.525 is 411/412 rather than 409/410

Thanks
Mike

 

[mciupa]

I read your post, changed my frequency folder in site 2 to ch 411 and 412 and see this:



I was getting talkgroups still populating in 409 and 410.


This is site 1 I am getting voice on 937.125 for Brampton, maybe the voice channel for Site 1. A lot of transit talk on there.

 

[mtindor]

I read your post, changed my frequency folder in site 2 to ch 411 and 412 and see this:

View attachment 191805

I was getting talkgroups still populating in 409 and 410.


This is site 1 I am getting voice on 937.125 for Brampton, maybe the voice channel for Site 1. A lot of transit talk on there.

View attachment 191806

So in the first screenshot you were monitoring site 2 and were tuned to 938.525? If so, then that looks right. Looks like there is one CC and at least two active channels for site 2 in that case.

Since you can tune to both sites, would you tune to site 2, wait for it show all of the system details, and then get a screenshot of the Event window for site 2?

 

[mciupa]

Here you go, I notice that Private Calls utilize channels 409 and 410. Buses are showing aliases. Their bus numbers radio id's show with a leading 88, so Bus 8824 is radio 888824. Some of the channels used in this CAP MAX were last used in 2018 as part of the LTR system.




On an adjacent frequency, 939.225 I am getting tons of LLRP. I was getting a blank channel on 216 in the channel window.


(If I don't respond timely, I will be out at a retirement party in the afternoon. Will check replies later.)

 

[mtindor]

Here you go, I notice that Private Calls utilize channels 409 and 410. Buses are showing aliases. Their bus numbers radio id's show with a leading 88, so Bus 8824 is radio 888824. Some of the channels used in this CAP MAX were last used in 2018 as part of the LTR system.

View attachment 191809

Thanks.

Your screenshot for Site 1 shows:
S1321:1.1 neighbor: Site S1321:1.2; CC=411 (which according to your screenshot is 938.525)
- so Site 2 938.525 should be LCN 205 / CHID 411/412

Your screenshot for Site 2 shows:
S1321:1.2 neighbor: Site S1321:1.1; CC=213 (which according to you is currently 939.25)

So the DB for Site 2 should be updated to reflect that the LCN for 938.525 is 411
205 411 938.525
206 411 938.525

And your DSDPlus.frequencies file for Site 1 should be updated to show:
TIIInonStd,S1321:1,1,213,939.25,0.0,0

Mike