Discussion:
Misleading messages
(too old to reply)
Recliner
2020-01-18 11:30:35 UTC
Permalink
Yesterday, I wanted to catch the 14.14 Bloxwich to Cannock, about 14.05
an announcement was made the train was cancelled, so I caught the bus
instead. When I got back home, I checked Realtime Trains website, and
found that the train I wanted did actually run it got to Bloxwich 7 mins
late. Why do NR annonuce a train is cancelled when it just running late?
That was partially cancelled, terminated at Hednesford and did not call
at Rugely Town or Rugely Trent Valley. It was delayed at Walsall for 7 minutes.
Possibly at Walsall it was cancelled then partially reinstated on the
departures boards, but the Bloxwich announcer (or announcement robot)
updated at just the wrong time, announced the cancellation but didn't
pick up the subsequent reinstatement.
I was recently on a Metropolitan line train heading for Aldgate. As we
approached Finchley Road, the train first announced, as usual, that the
next station was Finchley Road, and that this train was for Aldgate. Then,
as we stopped, it announced that the train was terminating here, and "all
change, all change".

Everyone looked up, puzzled, but few actually got up. The doors then closed
as normal, and off we went. It happened again at a couple more stations,
confusing those who'd got on after the first announcement. The driver made
no manual announcements, so I don't know if the erroneous announcements
were his fault or the train's.
b***@nowhere.org
2020-01-18 12:26:41 UTC
Permalink
On Sat, 18 Jan 2020 11:30:35 -0000 (UTC)
Yesterday, I wanted to catch the 14.14 Bloxwich to Cannock, about 14.05
an announcement was made the train was cancelled, so I caught the bus
instead. When I got back home, I checked Realtime Trains website, and
found that the train I wanted did actually run it got to Bloxwich 7 mins
late. Why do NR annonuce a train is cancelled when it just running late?
That was partially cancelled, terminated at Hednesford and did not call
at Rugely Town or Rugely Trent Valley. It was delayed at Walsall for 7
minutes.
Possibly at Walsall it was cancelled then partially reinstated on the
departures boards, but the Bloxwich announcer (or announcement robot)
updated at just the wrong time, announced the cancellation but didn't
pick up the subsequent reinstatement.
I was recently on a Metropolitan line train heading for Aldgate. As we
approached Finchley Road, the train first announced, as usual, that the
next station was Finchley Road, and that this train was for Aldgate. Then,
as we stopped, it announced that the train was terminating here, and "all
change, all change".
Everyone looked up, puzzled, but few actually got up. The doors then closed
as normal, and off we went. It happened again at a couple more stations,
confusing those who'd got on after the first announcement. The driver made
no manual announcements, so I don't know if the erroneous announcements
were his fault or the train's.
Probably the trains. It wouldn't be the first time an automated announcing
system gets confused and even forgets where it is. No doubt the driver was
fully well aware that the system was playing up as he can certainly hear it
from the cab but presumably his measly 60K salary isn't enough for him to
bother to make a corrective announcement.
Charles Ellson
2020-01-19 01:28:37 UTC
Permalink
Post by b***@nowhere.org
On Sat, 18 Jan 2020 11:30:35 -0000 (UTC)
Yesterday, I wanted to catch the 14.14 Bloxwich to Cannock, about 14.05
an announcement was made the train was cancelled, so I caught the bus
instead. When I got back home, I checked Realtime Trains website, and
found that the train I wanted did actually run it got to Bloxwich 7 mins
late. Why do NR annonuce a train is cancelled when it just running late?
That was partially cancelled, terminated at Hednesford and did not call
at Rugely Town or Rugely Trent Valley. It was delayed at Walsall for 7
minutes.
Possibly at Walsall it was cancelled then partially reinstated on the
departures boards, but the Bloxwich announcer (or announcement robot)
updated at just the wrong time, announced the cancellation but didn't
pick up the subsequent reinstatement.
I was recently on a Metropolitan line train heading for Aldgate. As we
approached Finchley Road, the train first announced, as usual, that the
next station was Finchley Road, and that this train was for Aldgate. Then,
as we stopped, it announced that the train was terminating here, and "all
change, all change".
Everyone looked up, puzzled, but few actually got up. The doors then closed
as normal, and off we went. It happened again at a couple more stations,
confusing those who'd got on after the first announcement. The driver made
no manual announcements, so I don't know if the erroneous announcements
were his fault or the train's.
Probably the trains. It wouldn't be the first time an automated announcing
system gets confused and even forgets where it is.
That happens on NR as well. I've had Thameslink trains going in one
direction while the PIS thought it was going in the opposite
direction.
Post by b***@nowhere.org
No doubt the driver was
fully well aware that the system was playing up as he can certainly hear it
from the cab but presumably his measly 60K salary isn't enough for him to
bother to make a corrective announcement.
Martin Smith
2020-01-26 17:03:28 UTC
Permalink
Post by Charles Ellson
Post by b***@nowhere.org
On Sat, 18 Jan 2020 11:30:35 -0000 (UTC)
Yesterday, I wanted to catch the 14.14 Bloxwich to Cannock, about 14.05
an announcement was made the train was cancelled, so I caught the bus
instead. When I got back home, I checked Realtime Trains website, and
found that the train I wanted did actually run it got to Bloxwich 7 mins
late. Why do NR annonuce a train is cancelled when it just running late?
That was partially cancelled, terminated at Hednesford and did not call
at Rugely Town or Rugely Trent Valley. It was delayed at Walsall for 7
minutes.
Possibly at Walsall it was cancelled then partially reinstated on the
departures boards, but the Bloxwich announcer (or announcement robot)
updated at just the wrong time, announced the cancellation but didn't
pick up the subsequent reinstatement.
I was recently on a Metropolitan line train heading for Aldgate. As we
approached Finchley Road, the train first announced, as usual, that the
next station was Finchley Road, and that this train was for Aldgate. Then,
as we stopped, it announced that the train was terminating here, and "all
change, all change".
Everyone looked up, puzzled, but few actually got up. The doors then closed
as normal, and off we went. It happened again at a couple more stations,
confusing those who'd got on after the first announcement. The driver made
no manual announcements, so I don't know if the erroneous announcements
were his fault or the train's.
Probably the trains. It wouldn't be the first time an automated announcing
system gets confused and even forgets where it is.
That happens on NR as well. I've had Thameslink trains going in one
direction while the PIS thought it was going in the opposite
direction.
I was on one a few weeks ago that was announced on the PIS as out of
service, but was full of passengers and the inside information screen
also claimed it was out of service... that was Thameslink from
Loughborough Junction to the elephant
Post by Charles Ellson
Post by b***@nowhere.org
No doubt the driver was
fully well aware that the system was playing up as he can certainly hear it
from the cab but presumably his measly 60K salary isn't enough for him to
bother to make a corrective announcement.
--
Martin
Loading...