kabsonline
Best SSL Train: S Stock Best Tube Train: 92 Stock
Posts: 686
|
Post by kabsonline on Nov 8, 2012 19:35:55 GMT
Hi all It was reported today in my local newspaper (Bucks Examiner) that the S Stock digital voice announcements and displays have a "technical glitch" with them with 5% of Met line trains going to Amersham actually displaying and announcing Chesham as its destination, causing some commuters to end up in Amersham instead of Chesham. According to the article this is one of the main reasons as to why the S Stock are being returned to Derby to have this problem altered. Now is this just the newspaper exaggerating with maybe a couple of drivers accidentally selecting Chesham instead of Amersham when setting up the train for operation or is it a genuine problem? Now my theory is that if it is a genuine problem, then Chesham/Amersham cannot be the only Met destinations affected. Other S Stocks going to other destinations such as Watford and Uxbridge must also have 5% of trains displaying and announcing other destinations instead. I remember back when they first came out I was on a Watford bound train when we arrived at Finchley Road and the announcements and displays showed that we had arrived at Hillingdon and we were on a train to Uxbridge. It also did this at Wembley Park where the driver I assume switched the system off. I thought that there must have been a fault with that particular train. Surely though if this was a problem the DVAs and displays would be switched off until the problem was resolved. That is however the only S Stock that I have been on and the displays and announcements have been wrong and I do travel on the Met a fair bit. What is everybody else's experiences and thoughts ? Kabsonline  |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 8, 2012 20:36:26 GMT
I did report a incident of this nature, a little while ago, where a southbound train entering service arrived at finchley road showing baker street when infact it was heading to aldgate. I think it would be very difficult to say either way (if its a fault or not) as you can always blame the driver. (sorry drivers)
|
|
rincew1nd
Administrator
Junior Under-wizzard of quiz
Posts: 10,286 
|
Post by rincew1nd on Nov 8, 2012 20:58:49 GMT
I remember when the class 333s were introduced in Aire and Wharfdale, they would often pull up in Saltaire then proudly announce "Welcome to the Leeds Train; the next station is, Salt... The next station is, Shipley." They learnt, eventually. |
|
|
|
Post by t697 on Nov 9, 2012 6:12:35 GMT
Hi all According to the article this is one of the main reasons as to why the S Stock are being returned to Derby to have this problem altered. What is everybody else's experiences and thoughts ? Kabsonline Whilst the system hasn't been trouble free, it isn't a contributor to trains going to Derby for a mods programme. The improvements to the Customer Information System are software upgrades that can be implemented to the train pretty well anywhere. |
|
kabsonline
Best SSL Train: S Stock Best Tube Train: 92 Stock
Posts: 686
|
Post by kabsonline on Nov 10, 2012 11:29:23 GMT
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 23, 2012 21:52:18 GMT
Mr Bartlett thinks the drivers should do more to warn commuters if the destination has changed.What does he suggest? We tell each passenger personally? Face to face? How about the passengers that are wearing headphones?  He added: “I think if the drivers can’t really rely on the boards they should be making announcements manually until they are sure the glitch has been fixed.”We bend over backwards to tell the passengers if the destination has been changed. Then i suggest you try a little harder. ;D  |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 23, 2012 21:55:03 GMT
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 23, 2012 22:19:38 GMT
The worst CIS fault I have seen was a train bleating on about going to Aldgate as it went through Finchley road northbound. !!!!It carried on right until ...WEMBLEY PARK. Deary me ;D    I have witnessed worse, Met Moorgate reversers, if you enter a NB destination with Aldgate as a starting destination, (because Moorgate is not an option) the train announces "Liverpool Street" as the next station.  (You are in the bay road, btw.)  |
|
|
|
Post by chrisvandenkieboom on Nov 23, 2012 22:37:09 GMT
Wait, the PIS can't be told to just start at Moorgate?
|
|
|
|
Post by causton on Nov 23, 2012 23:25:33 GMT
Haha, oh dear! Is there not a manual 'next station' button (I presume the next station announcements are done by wheel revolutions underground?)
|
|
Chris M
Global Moderator
Forum Quizmaster
Always happy to receive quiz ideas and pictures by email or PM
Posts: 19,770
|
Post by Chris M on Nov 24, 2012 0:33:51 GMT
None of those PIS faults beat the Class 350 I was on that thought it was travelling from Liverpool to Birmingham when in fact it was doing the exact opposite. At least one person got on the train, heard the DVA and then scurried off again thinking they had the wrong train - iirc the next train was an hour away.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 24, 2012 8:14:31 GMT
Mr Bartlett thinks the drivers should do more to warn commuters if the destination has changed.What does he suggest? We tell each passenger personally? Face to face? How about the passengers that are wearing headphones? He added: “I think if the drivers can’t really rely on the boards they should be making announcements manually until they are sure the glitch has been fixed.”We bend over backwards to tell the passengers if the destination has been changed. Think the point here is that LU should make drivers aware of the issue. Obviously, most drivers do what they can but this followed an incident at Chalfont where someone thought they were on an Amersham train because of the auto-announcements, and got taken to Chesham. No manual announcement was made which may well have been because the driver was unaware of the problem. |
|
|
|
Post by norbitonflyer on Nov 24, 2012 12:14:35 GMT
....... thought it was travelling from Liverpool to Birmingham when in fact it was doing the exact opposite. We get this occasionally on the Kingston rounders, which get confused about whether they are coming or going, so that they think they are heading out of Waterloo when they are actually on the way back in. They only call at Queenstown Road inbound when going clockwise, or outbound when going anticlockwise, this can lead to outbound leading to announcements like "The next stop is Queenstown Road, please mind the gap when leaving the train" - when not only is the train passing through non-stop, but there is no platform on the track the train is travelling so the "gap" is the width of three or four tracks! |
|
|
|
Post by t697 on Nov 24, 2012 15:22:33 GMT
The worst CIS fault I have seen was a train bleating on about going to Aldgate as it went through Finchley road northbound. !!!!It carried on right until ...WEMBLEY PARK. Deary me ;D I have witnessed worse, Met Moorgate reversers, if you enter a NB destination with Aldgate as a starting destination, (because Moorgate is not an option) the train announces "Liverpool Street" as the next station. (You are in the bay road, btw.) Have you actually witnessed this in the last few weeks since the most recent upgrade? I haven't, yet it or variations of the problem used to be common with trains reversing at the bay roads at Baker Street |
|
a60
I will make the 8100 Class DART my new A Stock.
Posts: 745
|
Post by a60 on Nov 24, 2012 15:51:08 GMT
It must be taking the PIS (Sorry had to get that one in). But on serious note, isn't there little software update that can applied to get Moorgate in and the like?
|
|
|
|
Post by andypurk on Nov 24, 2012 16:03:50 GMT
[ Have you actually witnessed this in the last few weeks since the most recent upgrade? I haven't, yet it or variations of the problem used to be common with trains reversing at the bay roads at Baker Street Last time I had this problem was an Uxbridge service, starting from Harrow-on-the-Hill, during the engineering work on the 3rd November. It claimed that the next stop was Moorgate (not West Harrow). The system corrected itself at West Harrow. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 24, 2012 16:08:32 GMT
A very confusing change of destination announcement is slow to fast and vice versa. Example, on an all-stations Amersham: "The destination of this train has changed. This is now a Metropolitan line train to Amersham." Passengers now look at each other thinking what the f***, and make comments about stupid trains and technology. This has happened to me several times when there are delays. How difficult would it be to programme "This is now a fast Metropolitan line train to Amersham".
|
|
|
|
Post by Alight on Nov 24, 2012 16:18:31 GMT
This has happened to me at Baker Street where an Aldgate-bound train changed its destination to Watford, but the doors closed immediately so that none of us - those who were listening to the DVA that is - could leave! Completely defeated the object of playing that announcement and meant that I found myself travelling up to Finchley Road when I just wanted to get to King's Cross St. Pancras!
|
|
|
|
Post by t697 on Nov 24, 2012 19:07:00 GMT
[ Have you actually witnessed this in the last few weeks since the most recent upgrade? I haven't, yet it or variations of the problem used to be common with trains reversing at the bay roads at Baker Street Last time I had this problem was an Uxbridge service, starting from Harrow-on-the-Hill, during the engineering work on the 3rd November. It claimed that the next stop was Moorgate (not West Harrow). The system corrected itself at West Harrow. Hmm, interesting. Will pass on! |
|
|
|
Post by t697 on Nov 24, 2012 19:09:28 GMT
It must be taking the PIS (Sorry had to get that one in). But on serious note, isn't there little software update that can applied to get Moorgate in and the like? The principle is that the train knows where it is when berthed in the platform so the T/Op doesn't need to select the starting point, just the route, destination and on the Met, stopping pattern. |
|
|
|
Post by t697 on Nov 24, 2012 19:17:43 GMT
This has happened to me at Baker Street where an Aldgate-bound train changed its destination to Watford, but the doors closed immediately so that none of us - those who were listening to the DVA that is - could leave! Completely defeated the object of playing that announcement and meant that I found myself travelling up to Finchley Road when I just wanted to get to King's Cross St. Pancras! Sounds like a service disruption reversal? Must have been in platforms 1, 2 or 4 none of which normally have Aldgate trains since you can no longer reverse in platform 3. Since I recognise you are a regular LU user, I'm guessing the train was in platform 2 since the other two are terminals and you wouldn't even expect an Aldgate train there? |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 25, 2012 15:17:53 GMT
Wait, the PIS can't be told to just start at Moorgate? No. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 25, 2012 15:18:45 GMT
Haha, oh dear! Is there not a manual 'next station' button (I presume the next station announcements are done by wheel revolutions underground?) No. |
|
