Twlighting
Member
Anyone else listening to the current Metro Red Line system? I've recently discovered it's a great way to pass the time on the train while void of cell service. Also had the pleasure of overhearing a conversation indicating one train's speedometer was inoperable while in motion. Fun!
I'm trying to sort out exactly kind of system they're running down there. As the DB indicates, they've moved to some variety of NXDN/IDAS. I'm unsure as to whether it's a trunked system or a multi-site conventional. Here's what I've noted so far:
There are two pairs of frequencies active at any given location on the route. Only one of these two pairs is active at any given time.
Pair A: 160.5125
161.1375
Pair B: 160.7125
161.1625
When the system is idle, both frequencies of the the active pair pulse every every few seconds with a rest /beacon burst. When a voice call occurs, one of the two frequencies carries the voice traffic while the other continues to pulse regularly.
Here's what I've identified as far as active pairs go along the route:
North Hollywood: A
Universal City: B
Hollywood/Highland: A
Hollywood/Vine: B
Hollywood/Western: B
Vermont/Sunset: A
Vermont/Santa Monica: A
Vermont/Beverly: A
Wilshire/Vermont: B
Westlake/MacArtur: A
7th St/Metro Center: B
Pershing Square: ?
Civic Center: ?
Union Station: ?
The handoff between pairs occurs at some point between stations.
DSD+ identifies this as a Nexedge48 System and always indicates TG 00001 for all voices calls. Haven't seen any channel identifiers pop up.
Have identified two RANs:
10 - Maintenance
20 - Rail Operations
Would anyone be able to expand upon what they have going on down there?
I'm trying to sort out exactly kind of system they're running down there. As the DB indicates, they've moved to some variety of NXDN/IDAS. I'm unsure as to whether it's a trunked system or a multi-site conventional. Here's what I've noted so far:
There are two pairs of frequencies active at any given location on the route. Only one of these two pairs is active at any given time.
Pair A: 160.5125
161.1375
Pair B: 160.7125
161.1625
When the system is idle, both frequencies of the the active pair pulse every every few seconds with a rest /beacon burst. When a voice call occurs, one of the two frequencies carries the voice traffic while the other continues to pulse regularly.
Here's what I've identified as far as active pairs go along the route:
North Hollywood: A
Universal City: B
Hollywood/Highland: A
Hollywood/Vine: B
Hollywood/Western: B
Vermont/Sunset: A
Vermont/Santa Monica: A
Vermont/Beverly: A
Wilshire/Vermont: B
Westlake/MacArtur: A
7th St/Metro Center: B
Pershing Square: ?
Civic Center: ?
Union Station: ?
The handoff between pairs occurs at some point between stations.
DSD+ identifies this as a Nexedge48 System and always indicates TG 00001 for all voices calls. Haven't seen any channel identifiers pop up.
Have identified two RANs:
10 - Maintenance
20 - Rail Operations
Would anyone be able to expand upon what they have going on down there?
