|
|
Post by dodidi on Mar 11, 2020 20:08:07 GMT
Yesterday whilst travelling eastbound on the Central Line I witnessed an unusual occurrence which I didn't think was possible. The station announcements were correct however at each station the train was announcing that it was terminating at Ealing Broadway, even though we were travelling in the complete opposite direction through Central London towards Hainault.
Understand that the system could potentially have been programmed incorrectly however what is unusual is that the stations were correctly announced in their correct Eastbound order however the actual destination being announced was on the West End of the line. Is this possible on the DVA System or could this be a glitch specific to one unit?
|
|
Chris M
Global Moderator
Forum Quizmaster
Always happy to receive quiz ideas and pictures by email or PM
Posts: 19,772
|
Post by Chris M on Mar 11, 2020 20:47:25 GMT
I experienced exactly the same thing a few years ago, but on Class 350 from Birmingham to Liverpool. One person getting on (possibly at Stafford) actually hurried off again when hearing the announcement thinking they'd boarded the wrong train on a 1 or 2 tph service. Unfortunately I was too far away to alert them that it was the train that was wrong.
I don't recall hearing about it happening on the tube before though.
|
|
|
|
Post by antharro on Mar 11, 2020 20:58:25 GMT
I've had this on a Northern Line train and an a 444 on a trip up from Weymouth to London.
|
|
|
|
Post by johnb2 on Mar 11, 2020 21:28:59 GMT
I had a similar experience at Northampton when a 350 coupled up to another. From Stafford to N'ton all was fine but after coupling up it was wrong (going to Birmingham) but had sorted itself out by the time we got to MK. Worried a couple of people though.
|
|
|
|
Post by countryman on Mar 11, 2020 22:05:30 GMT
I was on one of the stopping services in the Eltham area a while ago, and the DVA was one station out (can't remember if it was one late or one early), but it was in the right direction.
|
|
|
|
Post by norbitonflyer on Mar 11, 2020 22:11:16 GMT
We get that a lot on the SWR "rounders", where the train gets confused as to whether it is on the outward leg or the inward one and announces the previous station instead of the next one. (That is, it knows where it is but not which way it's going). Occasionally also happens on "Real Time Trains" where the train is shown as being at two different stages of its journey simultaneously.
|
|
|
|
Post by countryman on Mar 12, 2020 8:04:39 GMT
We get that a lot on the SWR "rounders", where the train gets confused as to whether it is on the outward leg or the inward one and announces the previous station instead of the next one. (That is, it knows where it is but not which way it's going). Occasionally also happens on "Real Time Trains" where the train is shown as being at two different stages of its journey simultaneously. In my case it knew which way it was going but not where it was. |
|
|
|
Post by aslefshrugged on Mar 12, 2020 8:52:05 GMT
Yesterday whilst travelling eastbound on the Central Line I witnessed an unusual occurrence which I didn't think was possible. The station announcements were correct however at each station the train was announcing that it was terminating at Ealing Broadway, even though we were travelling in the complete opposite direction through Central London towards Hainault. Understand that the system could potentially have been programmed incorrectly however what is unusual is that the stations were correctly announced in their correct Eastbound order however the actual destination being announced was on the West End of the line. Is this possible on the DVA System or could this be a glitch specific to one unit? No great mystery, the station announcements and dot matrix boards are tied into the signalling system at Wood Lane while those on the trains are manually input by the driver when they change ends (you can also change the train number and duty number on the same panel). The on-train "next station" announcements are uploaded when a train stops at the previous station. All that happened here was that either the driver forgot to change the destination when they changed ends, there is a fault on the train and the driver input the new destination but hasn't noticed that it hasn't changed or someone had activated the "not in service" button in the rear cab which will stop changes to destination input in the front cab. Last night I got as far as Notting Hill Gate before I noticed that my train was still advertising itself as a White City when it should have been Ealing Broadway (and I was running with the wrong duty number). |
|
