|
patch38
|
 |
« on: November 25, 2019, 16:03:59 » |
|
I'm not sure I've heard about this happening berfore... I'm on 1G47 - the 15:36 service from PAD» to CNM» . It was late to the platform but all avaiable evidence was that it was going to be P1. An IET▸ pulled in and cleaning and catering crews busied themselves. I ambled slowly towards the front. The destination indicators on coaches K and L were still showing 'London PAD' from the inbound service. When I got to J, they changed to '15:36 Cheltenham'. Excellent; I had beaten the system! I got to D and the indicator said 'Penzance'. B*gger - I hadn't beaten the system: they were obviously about to announce 1G47 as departing from some other patform. I walked back up the platform and the indicator on the next coach said 'Cheltenham'. Back to D - 'Penzance'. Forward to C - 'Cheltenham'. At that point the platform announcements fired up and confirmed it as the 15:36 to Cheltenham. Anyone else seen that happen? Or does coach D surreptitiously peel off at Reading and freewheel down the B&H▸ to the Land of the Pasty?  |
|
|
|
|
Logged
|
|
|
|
|
IndustryInsider
|
|
« Reply #1 on: November 25, 2019, 16:08:35 » |
|
It's not unknown for a rogue external and internal display to show a previous train and destination to what the rest show.
|
|
|
|
|
Logged
|
To view my GWML▸ Electrification cab video 'before and after' video comparison, as well as other videos of the new layout at Reading and 'before and after' comparisons of the Cotswold Line Redoubling scheme, see: http://www.dailymotion.com/user/IndustryInsider/ |
|
|
|
didcotdean
|
|
« Reply #2 on: November 25, 2019, 17:05:19 » |
|
Carriage lettering can also sometimes be wrong, which can be a problem when trying to find seat reservations and your carriage appears to be missing.
|
|
|
|
|
Logged
|
|
|
|
|
stuving
|
|
« Reply #3 on: November 25, 2019, 17:11:20 » |
|
S*******
|
|
|
|
|
Logged
|
|
|
|
|
patch38
|
|
« Reply #4 on: November 25, 2019, 18:17:03 » |
|
It's not unknown for a rogue external and internal display to show a previous train and destination to what the rest show.
It was definitely a single rogue display: it was still showing Penzance when I got off and I also noticed that the one at the other end of the same carriage was showing correctly. |
|
|
|
|
Logged
|
|
|
|
|
CyclingSid
|
|
« Reply #5 on: November 26, 2019, 06:58:12 » |
|
This raises a question I was going to ask. Are visual and audible information on trains from the same source, which my simple mind thinks they would be.
A few weeks ago I was on a GWR▸ service where visual was "saying" one thing but audible was saying something else. Was corrected very quickly.
On Saturday I was on a Thameslink service from Gatwick to Brighton, which as I sat down I noticed displayed this station is Kings Lynn, but audibly it said this is Gatwick. Visual stayed stuck at Kings Lynn all the way to Brighton, but the audible knew where it was.
|
|
|
|
|
Logged
|
|
|
|
|
ChrisB
|
|
« Reply #6 on: November 26, 2019, 09:33:29 » |
|
I thionk the verbal announcements are connected to GPS, hence the train 'knowing' where it is/approaching and thus states corectly the station calls.The visuals used to be set by the driver using a Train ID system that they enter before leaving the originating station - each ID having the calling stations loaded, sop the display can show the calling stations etc
|
|
|
|
|
Logged
|
|
|
|
|
IndustryInsider
|
|
« Reply #7 on: November 26, 2019, 11:14:01 » |
|
I thionk the verbal announcements are connected to GPS, hence the train 'knowing' where it is/approaching and thus states corectly the station calls.The visuals used to be set by the driver using a Train ID system that they enter before leaving the originating station - each ID having the calling stations loaded, sop the display can show the calling stations etc
Both audio and visual are controlled by the same system on (all?) trains GWR▸ use. The problem you sometimes get is that a display doesn't receive the signal from the master computer leading to the odd rogue display here and there on occasions. Sometimes the GPS link fails as well which can lead to the wrong station being announced - it should still work as it recognises the doors have been opened, but occasionally that gets misses - though that largely seems to only affect older train retrofitted. |
|
|
|
|
Logged
|
To view my GWML▸ Electrification cab video 'before and after' video comparison, as well as other videos of the new layout at Reading and 'before and after' comparisons of the Cotswold Line Redoubling scheme, see: http://www.dailymotion.com/user/IndustryInsider/ |
|
|
|
bobm
|
|
« Reply #8 on: November 26, 2019, 12:39:05 » |
|
800 023 had an unusual fault yesterday. Displays were correct but the bit which puts the announcements together was clearly awry. A different voice reeled off a string of numbers when each announcement was due. It seems "Station 1000" may be London Paddington.
|
|
|
|
|
Logged
|
|
|
|
|
tomL
|
|
« Reply #9 on: November 26, 2019, 15:25:55 » |
|
800 023 had an unusual fault yesterday. Displays were correct but the bit which puts the announcements together was clearly awry. A different voice reeled off a string of numbers when each announcement was due. It seems "Station 1000" may be London Paddington.
Sounds like some sort of debug mode perhaps.  |
|
|
|
|
Logged
|
|
|
|
|
grahame
|
|
« Reply #10 on: November 26, 2019, 15:58:34 » |
|
800 023 had an unusual fault yesterday. Displays were correct but the bit which puts the announcements together was clearly awry. A different voice reeled off a string of numbers when each announcement was due. It seems "Station 1000" may be London Paddington.
Sounds like some sort of debug mode perhaps. Come across all sorts of code for Paddington, but no "1000". (Added some other examples of these codes). | . | CRS | NLC▸ | TIPLOC | STANME | STANOX | | Paddington | PAD» | 308700 | PADTON | PADDINGTN | 73000 | | Melksham | MKM» | 334600 | MELKSHM | MELKSHAM | 75361 | | Melksham Market Place Bus Stop | XBO | 334601 | MELKMAR | . | . |
NLC codes often abbreviate to first 4 digits - so Paddington is 3087 See http://www.railwaycodes.org.uk/crs/CRSp.shtm |
|
|
|
« Last Edit: November 26, 2019, 16:04:09 by grahame »
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
|
tomL
|
|
« Reply #11 on: November 27, 2019, 12:08:18 » |
|
800 023 had an unusual fault yesterday. Displays were correct but the bit which puts the announcements together was clearly awry. A different voice reeled off a string of numbers when each announcement was due. It seems "Station 1000" may be London Paddington.
Sounds like some sort of debug mode perhaps. Come across all sorts of code for Paddington, but no "1000". (Added some other examples of these codes). | . | CRS | NLC▸ | TIPLOC | STANME | STANOX | | Paddington | PAD» | 308700 | PADTON | PADDINGTN | 73000 | | Melksham | MKM» | 334600 | MELKSHM | MELKSHAM | 75361 | | Melksham Market Place Bus Stop | XBO | 334601 | MELKMAR | . | . |
NLC codes often abbreviate to first 4 digits - so Paddington is 3087 See http://www.railwaycodes.org.uk/crs/CRSp.shtmSoftware integration being the day job, it’s interesting they appear to not have chosen to use the plethora of existing codes for the new on board systems.  |
|
|
|
|
Logged
|
|
|
|
|
stuving
|
|
« Reply #12 on: November 27, 2019, 12:17:10 » |
|
Software integration being the day job, it’s interesting they appear to not have chosen to use the plethora of existing codes for the new on board systems. ...unless it's a set of voice samples preloaded so the functionality can be tested through to audio at the factory, with no route or station data loaded? |
|
|
|
|
Logged
|
|
|
|
|
Click on the map to explore geographics
