Metrolinx Rail Traffic Control

slicerwizard

Member
Joined
Sep 19, 2002
Messages
7,643
Location
Toronto, Ontario
Typically, NXDN48 signals have nice smooth audio that produces decent eye patterns in DSD+ and good decoding levels:

OnQ NXDN48 Signal.png


This signal on 160.6275 isn't as good, but has a visible eye pattern and solid decoding. RID 1 dead keying on talkgroup 0, no OTA alias text:

160p6275 NXDN48 Signal.png


And this signal on 160.92 looks terrible and DSD+ decodes are full of errors. I get the impression that someone doesn't know how to properly set up NXDN48 transmitters:

160p92 NXDN48 Signal.png
 

mjf

Member
Premium Subscriber
Joined
Dec 19, 2002
Messages
56
Location
Toronto, Ontario
I noticed in my area (west end Toronto) that the transmitter on 161.160 is quite strong but is very scratchy sounding when monitored on an analog radio and will not decode on DSD+. I see the same kind of spikey pattern vs the usual smooth on the DSD+ source audio window. If I move to a location about 5 kms west of home, it comes in nice and clean and decodes fine. Are we seeing simulcast distortion of some sort? I've read that NXDN does indeed support simulcast. 160.920 is too weak here for me to look at.
 

mjf

Member
Premium Subscriber
Joined
Dec 19, 2002
Messages
56
Location
Toronto, Ontario
You can add 161.1625 RAN 1 TG 0 RID 1

That should be 161.160. 161.1625 isn't a valid 7.5 KHz spaced frequency. I can get it here exactly on 161.160 on the SDR.

I see on Google Streetview that there is a similar tower at Streetsville to the one at Judson Rd here in Etobicoke.
 

VA3ADP

Member
Premium Subscriber
Joined
Mar 27, 2015
Messages
759
Location
Mississauga, Ontatrio Canada
That should be 161.160. 161.1625 isn't a valid 7.5 KHz spaced frequency. I can get it here exactly on 161.160 on the SDR.

I see on Google Streetview that there is a similar tower at Streetsville to the one at Judson Rd here in Etobicoke.

Also got 161.3125. just a data stream outside Oakville Go Station today also. I'm assuming that is going to be 161.310?
 

mjf

Member
Premium Subscriber
Joined
Dec 19, 2002
Messages
56
Location
Toronto, Ontario
The normal, analog railway frequencies are 15 KHz apart, so for example, 161.160 161.175 161.190 etc. These new, narrowband digital channels are in-between the 15 KHz channels so the spacing between valid frequencies becomes 7.5 KHz.

Here is where the two channels you found fit in:

161.1600
161.1675
161.1750
161.1825
161.1900
161.1975
161.2050
161.2125
161.2200
161.2275
161.2350
161.2425
161.2500
161.2575
161.2650
161.2725
161.2800
161.2875
161.2950
161.3025
161.3100
161.3175
161.3250

You can use Excel to easily generate a list of all the valid railway channels between 160.215 and 161.565. Be aware that not all radios can tune in 7.5 KHz steps.

More details: Railroads Scanner Frequencies and Radio Frequency Reference
 
Last edited:

mciupa

Member
Moderator
Joined
Nov 5, 2002
Messages
8,342
Since the signal is great at Willowbrook Maintenance Yard, I wonder if the system user is Bombardier Transportation?

Apparently Bombardier Transportation currently has a 5-year contract with two options of five years each to maintain the trains at Willowbrook and I would assume GO other locations.

So channels so far are:

AAR 317 160.29
AAR 325 160.35
AAR 362 160.6275
AAR 377 160.74
AAR 425 161.10
AAR 433 161.16
AAR 454 161.3175
AAR 481 161.52
AAR 485 161.55

I receive all but AAR 454 and AAR 481 from Toronto.
 

exkalibur

Member
Premium Subscriber
Joined
Aug 15, 2006
Messages
2,781
Location
York, Ontario
I don't think the system would be Bombardier specific. Rather, it could be a GO/Metrolinx system that is just being used by Bombardier. It seems odd, since they already have the UHF system.
 

mikewazowski

Forums Manager/Global DB Admin
Staff member
Forums Manager
Joined
Jun 26, 2001
Messages
13,516
Location
Oot and Aboot
I wondered if the trains would migrate from UHF to VHF and only have to have one radio?
 

ATCTech

Active Member
Joined
Aug 13, 2002
Messages
1,857
That makes sense Mike, leave the UHF system for public road vehicles and keep rail integrated with existing RF infrastructure.
 

mciupa

Member
Moderator
Joined
Nov 5, 2002
Messages
8,342
Some documentation from Metrolinx may give a clue as to what is going on.

Full doc is 86 pages but the gist of my post is below page 31/86)

(NOC=Network Operation Control)

The second phase of the NOC development will start in late 2019 and continue through 2021as the RTC will transfer from CN to Metrolinx. This will occur alongside the implementation of the new Transit Control System (TCS) for signals and switches along our corridor. The NOC will also host the coordination of day-to-day rail track, signals, switching and communication first line help desk. In order to smoothly transition the takeover of the RTC, we have established a program team that monitors related capital projects and ensures that staffing, training and compliance are ready for the transition in 2020.

I've heard CN Mainline communicating with Metrolinx RTC on CN 001.
 

Aurora

Member
Joined
Dec 19, 2002
Messages
136
That makes sense Mike, leave the UHF system for public road vehicles and keep rail integrated with existing RF infrastructure.
I could see the counter argument that the UHF be kept for operational comms so the VHF would remain dedicated to wayside activity. Whether VHF/UHF or VHF/VHF I could see a two radio system remaining.
 

VA3ADP

Member
Premium Subscriber
Joined
Mar 27, 2015
Messages
759
Location
Mississauga, Ontatrio Canada
Wonder why they didnt just use the GoTrbo network its nxdn UHF and next to nobody uses it anyway :D
Being sarcastic as I know there are not many towers around etc. Didnt there use to be a toronto tower? Its even still in the Toronto frequency page.

The CN Tower site Its been offline for a while. At least a year or two now. I have no idea why I still have it in my scanners. I agree Kris GOTRBO or even Fleetcom would of been a better move.
 
Top