Brampton transitioning systems

[VA3ADP]

Hello everyone. I've noticed one of the Brampton Con+ sites now appears to be transmitting a DT3 Signal with a colour code of 0. I thought this was bleed over from something else but my SDS200 with the analyze feature is showing this as well while scanning. Not sure if they are migrating over?

 

[mciupa]

I thought I saw that last week. I parked my 536 on the system this morning and I am getting CON traffic on Corporate Security, By-law Officers and Brampton Transit.

 

[Forts]

It's certainly sensible... Connect+ was dropped a while back, so any further upgrades would have to be CapacityMax/Tier III.

 

[VA3ADP]

I thought I saw that last week. I parked my 536 on the system this morning and I am getting CON traffic on Corporate Security, By-law Officers and Brampton Transit.

I checked my 536 also just for comparison and it's also showing DT3 for the Bovaird site

 

[mciupa]

Currently seeing CON on Parks Maintenance, Corporate Security and Brampton Transit on both sites. I believe you about DT3 as I saw the same thing last week, just not this week. Maybe one day soon they will convert.

 

[mciupa]

Reopening this thread from 2023.
I am only seeing 938.525 and 939.250 as DT3 signals. It is showing as TIIInonStd [Auto] (MOT) Site S:1-1 DCC:0 RAS NL:2

I can remove those frequencies from the Con+ Sys: 521 system if we can get more details like CH ID etc.

 

[VA3ADP]

Reopening this thread from 2023.
I am only seeing 938.525 and 939.250 as DT3 signals. It is showing as TIIInonStd [Auto] (MOT) Site S:1-1 DCC:0 RAS NL:2

I can remove those frequencies from the Con+ Sys: 521 system if we can get more details like CH ID etc.

View attachment 176720

I've seen the Bovaird drive site spitting out TIII emissions for almost two years now. I imagined back then they were testing it, they must have that site coverted to TIII now.

 

[mciupa]

It looks like a two site TIIInonStd system.
939.250 is Site 1-1 and 938.525 is Site 1-2

Database updated. Removed two freq. from Connect Plus Sys ID 521 and created this:

Brampton TIII Trunking System, Brampton, Ontario

Brampton TIII Trunking System Profile

www.radioreference.com

 

[VA3ADP]

It looks like a two site TIIInonStd system.
939.250 is Site 1-1 and 938.525 is Site 1-2

Database updated. Removed two freq. from Connect Plus Sys ID 521 and created this:

Brampton TIII Trunking System, Brampton, Ontario

Brampton TIII Trunking System Profile

www.radioreference.com

Great thanks! Hopefully they will be using the same TG's.

 

[mciupa]

Great thanks! Hopefully they will be using the same TG's.

This is from this morning while I was monitoring


TIIInonStd,S1, 106, 50, Normal, 6, 2025/01/21 10:23, "East Roads 1"
TIIInonStd,S1, 109, 50, Normal, 4, 2025/01/21 9:52, "West Roads 1"
TIIInonStd,S1, 138, 50, Normal, 1, 2025/01/21 9:29, "Brampton Transit Control 2"
TIIInonStd,S1, 150, 50, Normal, 7, 2025/01/21 10:40, "Brampton Transit Fallback"

But, are these also on Sys Id 521 Connect+ ?

 

[VA3ADP]

This is from this morning while I was monitoring


TIIInonStd,S1, 106, 50, Normal, 6, 2025/01/21 10:23, "East Roads 1"
TIIInonStd,S1, 109, 50, Normal, 4, 2025/01/21 9:52, "West Roads 1"
TIIInonStd,S1, 138, 50, Normal, 1, 2025/01/21 9:29, "Brampton Transit Control 2"
TIIInonStd,S1, 150, 50, Normal, 7, 2025/01/21 10:40, "Brampton Transit Fallback"

But, are these also on Sys Id 521 Connect+ ?

I wonder if they are simulcasting?

 

[VA3ADP]

Well, It would appear that site 2 is back online. I was monitoring the current Connect Plus system the other day and only hearing transmissions from security. Not a peep out of bylaw or transit who is often very busy on the system. I am not going to jump the gun on this one and say users have switched over just yet.

On another note DSD+ can't seem to make up its mind if its a TIII standerd or non standard system. The info from the RRDB seems to be invalid on the DSD+ side of things. I don't think I've configured the system correctly.

 

[mciupa]

This is how Site 2 comes up for me. I took the NETWORK name off Brampton as it would come up as Air Canada TIII and the talk groups would pull the AC aliases.




Something odd I noticed is that the channel listing will pull all my TIIInonStd channels because they are all S1. You see Hamilton Street Railway, both Brampton sites and Air Canada.

 

[gary123]

I have noticed in the DSD frequencies files that if the scanner hits a CC on a frequency it will act as if its hearing the first one in the frequency list. I do not think there is any way around this as the systems do not have an imbedded SID. Therefore DSD just looks for the first match it sees and then uses that user assigned system and matching groups and sites data.

I have not tried placing all the frequencies into one frequency file as you have posted.

 

[VA3ADP]

This is how Site 2 comes up for me. I took the NETWORK name off Brampton as it would come up as Air Canada TIII and the talk groups would pull the AC aliases.


View attachment 191685

Something odd I noticed is that the channel listing will pull all my TIIInonStd channels because they are all S1. You see Hamilton Street Railway, both Brampton sites and Air Canada.
View attachment 191682

That is quite odd. I tried running mine as well and it kept pulling back onto Alectra's system

 

[mciupa]

I have not tried placing all the frequencies into one frequency file as you have posted.

I didn't intentionally do that. I had walked away and came back later to that monster. I have everything separated into proper frequency and system groupings in their pertinent files.

 

[slicerwizard]

Something odd I noticed is that the channel listing will pull all my TIIInonStd channels because they are all S1. You see Hamilton Street Railway, both Brampton sites and Air Canada.

Because you're not using network prefixes to disambiguate systems that share a common network ID?

 

[mciupa]

Thanks. Time to re-read my Notes text doc.

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.

 

[mtindor]

It looks like a two site TIIInonStd system.
939.250 is Site 1-1 and 938.525 is Site 1-2

Database updated. Removed two freq. from Connect Plus Sys ID 521 and created this:

Brampton TIII Trunking System, Brampton, Ontario

Brampton TIII Trunking System Profile

www.radioreference.com

That should be set as a Capacity Max system. DSDPlus says its TIIInonStd with a [MOT] indication, which is the indicator for CAPMAX.

 

[mtindor]

On another note DSD+ can't seem to make up its mind if its a TIII standerd or non standard system. The info from the RRDB seems to be invalid on the DSD+ side of things. I don't think I've configured the system correctly.

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.