Wrong announcement, not corrected

[RGM654]

I was on 9G32 today, Euston to Birmingham New St. When we were in Kilsby tunnel there came an automated announcement that the next stop would be Birmingham International. The information screen (not the high up scrolling one) likewise declared Birmingham International as the next stop, displayed some connections from there, and continued to do so for some time, I think until we were arriving at Rugby. Presumably the train lost GPS while in the tunnel, but why would it assume a location where it was not due to be until some time later? I thought the train manager might make an announcement reassuring us that the next stop would be Rugby, but no such announcement followed.

 

[tcm1106]

This seems to be an Evero feature…

I’ve been on 807 services both today and yesterday that did exactly the same thing in Kilsby Tunnel.
One corrected by the TM, the other not.

 

[webbfan]

This seems to be an Evero feature…

I’ve been on 807 services both today and yesterday that did exactly the same thing in Kilsby Tunnel.
One corrected by the TM, the other not.

Interesting bug this, and repeatable. Losing GPS like that should not cause it to progress down the route, that should only happen in response to new GPS values or whatever the PIS uses to progress without GPS (assuming it does ). Losing GPS then jumping a stop and announcing approach to the next stop is a bit weird. Some programmer has got a bit of a job on to fix that and hide their red face.

 

[a_c_skinner]

Interesting bug this, and repeatable. Losing GPS like that should not cause it to progress down the route, that should only happen in response to new GPS values or whatever the PIS uses to progress without GPS (assuming it does ). Losing GPS then jumping a stop and announcing approach to the next stop is a bit weird. Some programmer has got a bit of a job on to fix that and hide their red face.

Had I written the program (they don't ask retired anaesthetists of course, though perhaps they could do worse), knowing where we were going, I'd have programmed in the elapsed distance or at worst time since the GPS was lost.

 

[webbfan]

You cannot estimate or guess where the train is. If position isn't known then don't announce anything, leave it to manual announcement. Do you know where the train is going, if lose GPS then most likely lost all communications so wouldn't know about any any potential route changes - although if it's only been a few seconds is fair to assume no change.

 

[Fenchurch SP]

Interesting bug this, and repeatable. Losing GPS like that should not cause it to progress down the route, that should only happen in response to new GPS values or whatever the PIS uses to progress without GPS (assuming it does ). Losing GPS then jumping a stop and announcing approach to the next stop is a bit weird. Some programmer has got a bit of a job on to fix that and hide their red face.

This also often happens through the Thameslink Core, eg announcing the next stop as East Croydon when we are between Blackfriars and London Bridge.

 

[Merle Haggard]

The Every trains displays have a number of shortcomings. When running late they persist in giving the arrival time of stations in advance as the timetabled one, even though this time for at least the next station might have already passed and the train is far short of reaching it.
A bizarre one is that the rolling screen of connections gives the departures one hour after the timetabled arrival - so a train arriving at 13.52 shows departures from 14.53 onwards. I've noticed this alighting at Rugby and New St. Perhaps it's connected with GMT/BST. but 1352 today, BST, would be 1252 GMT.