How are the screens linked up on the 317/1s (using the screens fitted by Wagn in 2005/6) because they're doing some very odd things - besides the reading announcements backwards when not set up/reset properly (the common problem).
Tonight, the 1606 KGX to Cambridge service, 317340, had different information on different screens! This made me wonder if they're sent data wirelessly, and some were missing out. The clocks were about 8 minutes slow, and yet they're set by GPS! What a strange way to manage things if the clock data is stored on each individual screen unit.
As the train moved, having done the initial welcome/safety briefing properly, the clocks updated - but one was one minute behind. The system then tried to do the welcome bit again, but was stuttering the speech (screen text fine) and finished with a very high-pitched noise that lasted about half a second.
At Finsbury Park, the time on the platform was 1611, but the train screens near me said 1609 and 1610! One then froze until Potters Bar, where it must have been sent another announcement to display to say it was approaching the station.
The clocks were then jumping all over the place, and by the time it should have been speaking 'This train is now approaching Hatfield' to go with the text, it simply did the high-pitched squeal for the duration.. causing people on the train to cover their ears in agony.
Thank God I alighted before Cambridge, as I think there will be some people that will be hearing ringing in their ears for hours after!
I can only imagine the high-pitched noise must be corrupted audio data, but this needs to be fixed pronto!
Tonight, the 1606 KGX to Cambridge service, 317340, had different information on different screens! This made me wonder if they're sent data wirelessly, and some were missing out. The clocks were about 8 minutes slow, and yet they're set by GPS! What a strange way to manage things if the clock data is stored on each individual screen unit.
As the train moved, having done the initial welcome/safety briefing properly, the clocks updated - but one was one minute behind. The system then tried to do the welcome bit again, but was stuttering the speech (screen text fine) and finished with a very high-pitched noise that lasted about half a second.
At Finsbury Park, the time on the platform was 1611, but the train screens near me said 1609 and 1610! One then froze until Potters Bar, where it must have been sent another announcement to display to say it was approaching the station.
The clocks were then jumping all over the place, and by the time it should have been speaking 'This train is now approaching Hatfield' to go with the text, it simply did the high-pitched squeal for the duration.. causing people on the train to cover their ears in agony.
Thank God I alighted before Cambridge, as I think there will be some people that will be hearing ringing in their ears for hours after!
I can only imagine the high-pitched noise must be corrupted audio data, but this needs to be fixed pronto!