-
Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!
Met line - Northwick Park announcement at Neasden
- Thread starter Railguy1
- Start date
- Status
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R
RailUK Forums
bluegoblin7
Established Member
Likewise, I’ve never heard this.
DLRnotDave
Member
Can concor, happens an all the Southbound fasts I've been on since CBTC reached Preston Road
Might be if you had a disability and was very dependent on the announcements?
NoddyMaccy
Member
I did the route today and didn’t hear this?
DLRnotDave
Member
Anecdotally, I think all the ones I've been on recently have been switched to fasts at last minute HOTH due to disruption, not sure if the destination change makes a difference
bluegoblin7
Established Member
This would actually make a lot of sense - and probably is therefore a CBTC bug. Drivers don't necessarily change the CIS code from an 'All Stations' code to a '(Semi-)Fast' one when they get a last minute diversion from Harrow. This should get corrected automatically when the train next passes over a track-based tag, or it can be overridden/set automatically by the CBTC system. I suspect there is some kind of mis-match that is recognising the train doesn't stop at Wembley, and so won't trigger any announcements there, but does when on the approach to Finchley Road. However, as it still 'thinks' the next station is Northwick Park, that is the announcement playing, then corrected automatically once an 'Accurate Stop' (AS) occurs at Finchley Road.
I'll see if I can confirm/deny this theory later in the week... and then I can absolutely pass it on to the CIS team too (albeit it is likely to be a short lived bug around SMA8/9 interfaces so may not get changed!).
In my experince the westbound indicator at Northwick Park can give odd information with trains sometimes dropping off (or did ,I've not noticed recently). I don't know if its to do with being on the signalling migration border. The announcements could have something to do with this and be a bug.
bluegoblin7
Established Member
Westbound? I assume you mean Northbound (the Met is a north/south railway throughout).
Entirely separate and unrelated issue with the interface between CBTC and the legacy signalling.
Entirely separate and unrelated issue with the interface between CBTC and the legacy signalling.
You are correct it is officially Northbound. However, the trains to Uxbridge are going westbound. I wonder if many people get confused at Ruislip Manor where the indicators show Northbound & Southbound or am I being pedantic?
bluegoblin7
Established Member
You're being pedantic. The Met is a north/south railway and is signed as such throughout. Across LUL all line directions are (generally) derived from how the line passes through Central London, the Met's of course pre-dating the all-day service to Aldgate.
To be equally pedantic, at Northwick Park trains are still northbound even if they then go on towards Uxbridge.
To be equally pedantic, at Northwick Park trains are still northbound even if they then go on towards Uxbridge.
I was under the impression that the stations Great portland street - Aldgate are Eastbound/Westbound?
The Met main being Northbound/Southbound makes sense, irrespective of the all day running to Aldgate, as it follows a North/South ish sort of alignment, from Baker Street onwards.
The Met main being Northbound/Southbound makes sense, irrespective of the all day running to Aldgate, as it follows a North/South ish sort of alignment, from Baker Street onwards.
bluegoblin7
Established Member
Signed east/west but operationally are outer rail/inner rail.
Again this is a historical anomaly for the Met.
LondonMitch
Member
- Joined
- 17 Jan 2016
- Messages
- 9
As fast/semi-fast trains pass Neasden, CBTC switches it's destination code to an all stations one and prompts the driver to do the same on the train.
If the driver confirms the change before Finchley Road, it'll trigger the Northwick Park message because of a software bug
If the driver confirms the change before Finchley Road, it'll trigger the Northwick Park message because of a software bug
So just quickly on this point, if the Met did not have this "historical anomaly", how would it be sign posted?
Itsjustesh
On Moderation
Have they fixed it as of yet?
DLRnotDave
Member
LondonMitch
Member
- Joined
- 17 Jan 2016
- Messages
- 9
No, I suspect it'll be an issue for a while.
You won't hear it all the time though, because it depends on the driver accepting the change of destination code before the train reaches Finchley Road
S Stock still have bugs in 2026?
I was kidding but from my experience yes, but minor bugs such as internal door lights not switching off sometimes. If I could remember. Sometimes the external amber lights at stop don’t all light up if I can remember or the white light would show instead. However maybe this is normal for trains but because the s stock and 09 stock use much more light indication than former stock it’s very noticeable. Also the door chimes probably can sound milliseconds out of sync with each other. I think older stock probably just use one door chime for all the doors???
Last edited:
- Status