Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 3, 2018 11:38:06 GMT
Hello
Today I was on a Met train to Harrow from Uxbridge and the PA system had done something I’ve never seen before.
The screens did show the destination but it was like this “The next station is ... , this is a blank train to Aldgate” there was no All stations Metropolitan on the screen.
And finally every next station stop was delayed till the train was almost to a stop.
Regards
Philsam123 (59stock)
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 3, 2018 17:00:57 GMT
I don't know the stock too well, but maybe the train had no idea where it was until it picks up a signal at a station?
|
|
|
|
Post by t697 on Sept 3, 2018 18:34:13 GMT
Any car number or train running number noted?
|
|
|
|
Post by goldenarrow on Sept 3, 2018 20:57:34 GMT
That most likely sounds like a defect with the trains data exchange equipment that feeds the Passenger Information System (PIS). Sometimes an irregular destination code (incorrect line for example) can cause fragmented announcements or rid them entirely but that's a bit hit and miss.
|
|
|
|
Post by met on Sept 5, 2018 21:07:28 GMT
Noticed this today on train 21045/21046 running number 451. All outside destination displays were blank, only the running number was shown. I've seen the outside displays to be blank before but never experienced the odd format of the announcements like this. Inside displays were working, but the format was unusual indeed. For example: 'The next station is Baker Street. This is a <BLANK> line train to Uxbridge'. There also appeared to be a double space between the words 'a' and 'line'. But, the voice announcements (when the doors were opened) did not say the word 'line', just 'This is Baker Street. The next station is Finchley Road. This is a train to Uxbridge.' Also seemed not to be any announcements on the approach to any of the stations either and the displays didn't refresh and go blank until doors open like it usually does on approach. Managed to get a picture of the display for clarity: i.imgur.com/0DKwGUO.jpg |
|
|
|
Post by goldenarrow on Sept 5, 2018 22:03:56 GMT
Noticed this today on train 21045/21046 running number 451. All outside destination displays were blank, only the running number was shown. I've seen the outside displays to be blank before but never experienced the odd format of the announcements like this. Inside displays were working, but the format was unusual indeed. For example: 'The next station is Baker Street. This is a <BLANK> line train to Uxbridge'. There also appeared to be a double space between the words 'a' and 'line'. But, the voice announcements (when the doors were opened) did not say the word 'line', just 'This is Baker Street. The next station is Finchley Road. This is a train to Uxbridge.' Also seemed not to be any announcements on the approach to any of the stations either and the displays didn't refresh and go blank until doors open like it usually does on approach. Managed to get a picture of the display for clarity: i.imgur.com/0DKwGUO.jpgIf you haven’t already, I would suggest giving the Met line twitter account a PM for the service number and timings. It’s a fairly well known issue for the leading cab not to display the external destination/calling pattern sometimes However, this is now the fourth incident I’ve read about recent days which makes wonder weather it could be a bug or some form of wider interference affecting the PIS (Pax Info Screens). Unless by some extraordinary happening we are all pondering over just one unit in which case the time continuum would also need to come in for check up. |
|
|
|
Post by MoreToJack on Sept 5, 2018 23:54:49 GMT
Noticed this today on train 21045/21046 running number 451. All outside destination displays were blank, only the running number was shown. I've seen the outside displays to be blank before but never experienced the odd format of the announcements like this. Inside displays were working, but the format was unusual indeed. For example: 'The next station is Baker Street. This is a <BLANK> line train to Uxbridge'. There also appeared to be a double space between the words 'a' and 'line'. But, the voice announcements (when the doors were opened) did not say the word 'line', just 'This is Baker Street. The next station is Finchley Road. This is a train to Uxbridge.' Also seemed not to be any announcements on the approach to any of the stations either and the displays didn't refresh and go blank until doors open like it usually does on approach. Managed to get a picture of the display for clarity: i.imgur.com/0DKwGUO.jpgIf you haven’t already, I would suggest giving the Met line twitter account a PM for the service number and timings. It’s a fairly well known issue for the leading cab not to display the external destination/calling pattern sometimes However, this is now the fourth incident I’ve read about recent days which makes wonder weather it could be a bug or some form of wider interference affecting the PIS (Pax Info Screens). Unless by some extraordinary happening we are all pondering over just one unit in which case the time continuum would also need to come in for check up. I'd say with a fair amount of certainty that this will be an issue introduced in the latest software drop. It has been causing huge issues with the CIS over the last few months and is causing a lot of grief (including the issue of no external displays). Definitely still worth reporting, however. |
|
|
|
Post by firestorm on Sept 10, 2018 15:50:00 GMT
If you haven’t already, I would suggest giving the Met line twitter account a PM for the service number and timings. It’s a fairly well known issue for the leading cab not to display the external destination/calling pattern sometimes However, this is now the fourth incident I’ve read about recent days which makes wonder weather it could be a bug or some form of wider interference affecting the PIS (Pax Info Screens). Unless by some extraordinary happening we are all pondering over just one unit in which case the time continuum would also need to come in for check up. I'd say with a fair amount of certainty that this will be an issue introduced in the latest software drop. It has been causing huge issues with the CIS over the last few months and is causing a lot of grief (including the issue of no external displays). Definitely still worth reporting, however. It is like you said a known software issue and is being looked at. |
|
|
|
Post by t697 on Sept 13, 2018 17:19:16 GMT
21045/21046 now believed fixed. Anyone ridden it recently?
|
|
|
|
Post by bearbin on Sept 18, 2018 18:37:20 GMT
I encountered this issue on a District line S7 today, perhaps it is spreading? The train number was 21393, running as 023
|
|
