Metrolinx Simulcast sites

[mciupa]

I certainly hope you guys are not like me and rely on control channel only.

The primary control channel for simulcast of 410.0625 was not working.

I put the scanner in SEARCH and found that 410.3375 was spitting out the data and now I'm hearing GO Transit again.

I'll submit 410.3375 as an alternate cc

 

[mciupa]

Tonight, 410.0625 is the primary control channel for 1-001 (Simulcast Zone)

The strange thing is that if you notice, 410.3375 is also emitting a control channel signal at 48% on my scanner but is not telling me a tower affiliation, which I always presumed was for 1-001.

 

[mciupa]

Something interesting this morning between 11 and 11:30 am.

A new control channel was chugging away on 410.2125.

This was also in the Simulcast area of 1-001, however a new WACN was displayed with a readout of BEE11 and not BEE00.

At this time, it is silent.

 

[xml]

Coverage is amazing out here in Halton.

They are using CQPSK on Site 2...

This looks like a brand new system. It is using the existing talkgroups - but there is no traffic but random a console test every so often.

 

[mciupa]

Coverage is amazing out here in Halton.

They are using CQPSK on Site 2...

This looks like a brand new system. It is using the existing talkgroups - but there is no traffic but random a console test every so often.

Thanks, so I am not alone hearing it. :lol:

I was parked on it this morning, but I have not yet seen a talkgroup appear.

It comes and goes for me in Toronto, I must be on the fringe.
Best decodes on my Pro-2096 were in the 68% to 70% range.

 

[exkalibur]

Andy and I went for a spin...

There is certainly nothing very impressive in the Halton area on 410.2125. Certainly NOT "excellent".

410.2125 is chugging away from the CN Tower, the same site as the 410.0625 channel from the Simulcast Zone.

What's this new CC for? Who knows. My bet goes for testing. By changing the WACN, they're able to make it "live" without worrying about system radios roaming over to it accidentally. Much easier to reprogram a controller than all the radios!

It'll be curious to see what they end up doing with it.

 

[xml]

Andy and I went for a spin...

There is certainly nothing very impressive in the Halton area on 410.2125. Certainly NOT "excellent".

410.2125 is chugging away from the CN Tower, the same site as the 410.0625 channel from the Simulcast Zone.

Not Site 1... Site 2 (WACN BEE11). It was buzzing away on 411.0375 on Friday and Saturday. It's offline again.

From looking at the IC site - it looks like they are going to simulcast their existing multicast sites. There are new sites in Niagara Falls, Kitchener, and Sunderland showing as well.

Techs are doing testing on talkgroup 1002. Mix of encryption.

 

[mikewazowski]

410.2125Mhz Site 1 was also buzzing away from Churchill.

Forgot to mention, from my notes, the current system is CQPSK.

 

[mciupa]

Tonight we see 410.2125 as the primary control channel for site 1-001 displaying a WACN of BEE00. My 2096 displays it as Site 101 rather than 201.
The usual 410.0625 cc is in the rotation as a voice channel.

 

[Forts]

Perhaps the coming expansion out to the KW area has something to do with all this?

 

[terryg1]

The Niagara Falls site is up.... good signal in Niagara now.

 

[Saint]

Niagara Falls Site

The Niagara Falls site is up.... good signal in Niagara now.

Still not picking up any control channel down hear in Fort Erie, I thought when they got the Niagara Falls Site up the control channel would be booming in hear.
Steve