Lumo 803 fault?

[cambsy]

I was on the 12.18 King Cross-Edinburgh Lumo service, Weds 19th Jan, whIch shortly, after departure from Stevenage, came to a stand on the fast lines, for about 7-8 mins, before setting off again, after rectifying the fault. We then made up the delay by Darlington, and arrived Edinburgh bang on time, which got me thinking what type of fault it could have been? My first thought was TPWS grid activation or similar, as the fault seemed to have gone, and not reoccur again.

If not a TPWS. Fault, what other faults on the 800’s, can be fixed quickly, and are unlikely to occur again? Thanks for any info from drivers, on here.

 

[Class15]

No idea, seems strange

 

[Wyrleybart]

Loads of potential faults - even as simple as something like the driver missing the TPWS or vigilance, although that wouldn't take 7 or 8 minutes to reset.

 

[cambsy]

Wyrleybart, the train ambassador, came over the PA, and said we had a fault, then pretty quickly, we just set off again, with no more problems, did seem strange to me too, but was good we made up the delay and had no more problems.

 

[fgwrich]

Loads of potential faults - even as simple as something like the driver missing the TPWS or vigilance, although that wouldn't take 7 or 8 minutes to reset.

Possibly the rheostatic braking system? It caused delay to my LNER service back last summer, the driver having to reset the unit at Dunbar and continue our journey southwards (losing time in the process) on Diesel. Of course the LUMO unit's cant do this but presumably may have involved a reset or two.

 

[northernbelle]

I was on the 12.18 King Cross-Edinburgh Lumo service, Weds 19th Jan, whIch shortly, after departure from Stevenage, came to a stand on the fast lines, for about 7-8 mins, before setting off again, after rectifying the fault. We then made up the delay by Darlington, and arrived Edinburgh bang on time, which got me thinking what type of fault it could have been? My first thought was TPWS grid activation or similar, as the fault seemed to have gone, and not reoccur again.

If not a TPWS. Fault, what other faults on the 800’s, can be fixed quickly, and are unlikely to occur again? Thanks for any info from drivers, on here.

An emergency door egress was activated and the time you waited would have been for the driver to check the door involved and reset the alarm. There would also have been some time spent communicating with the signaller/control centre to advise on the unscheduled stop, its reason and its rectification.

 

[cambsy]

fgwrich, once we set off again,after rectifying the fault, we made up the delay, pretty quickly, due to good running and timetable padding, and ran non stop, to Newcastle, as booked, so doubt anymore resets were needed.

== Doublepost prevention - post automatically merged: 21 Jan 2022 ==

northerbelle, thanks for info, is an emergency door egress a handle pulled or a sensor playing up? And do u work for Lumo etc? Just out of interest, thats all.

 

[Towers]

fgwrich, once we set off again,after rectifying the fault, we made up the delay, pretty quickly, due to good running and timetable padding, and ran non stop, to Newcastle, as booked, so doubt anymore resets were needed.

== Doublepost prevention - post automatically merged: 21 Jan 2022 ==

northerbelle, thanks for info, is an emergency door egress a handle pulled or a sensor playing up? And do u work for Lumo etc? Just out of interest, thats all.

It's the emergency door release lever, essentially. One pull will apply brakes, second pull releases the door. Somebody (I've no idea what the on-board staff are competent to do on there, I understand it's some sort of DOO effort) would have reset it manually at whatever location it was operated before the train continued on its way.

 

[cambsy]

Towers, it was announced as a fault with the train, so if it was someone pulling a door release lever, would’nt the Amnassador have said, passenger has pulled an emergency door lever, so we have to wait while driver resets it, rather than stating. a fault With train has caused the stop.

 

[DownFast]

Loads of potential faults - even as simple as something like the driver missing the TPWS or vigilance, although that wouldn't take 7 or 8 minutes to reset.

AWS, not TPWS. Whatever the cause, the stop out of course must be reported to the signaller (Rule Book Module TW1 sec 40), which can take a few minutes, especially if it's not immediately clear what the cause is, and the signaller needs to be sure that's it's not a TPWS brake demand before authorising the driver to continue. Could also have been a signalling irregularity that requires reporting to the signaller immediately, and an RT3185 completed, which also takes a few minutes.

edit: seems that's not the case here, as northernbelle has explained

 

[tpjm]

Towers, it was announced as a fault with the train, so if it was someone pulling a door release lever, would’nt the Amnassador have said, passenger has pulled an emergency door lever, so we have to wait while driver resets it, rather than stating. a fault With train has caused the stop.

Unless it was a spurious 'door open in traffic' alarm and upon inspection the door was confirmed as not being open. Wouldn't be the first time on an 80x.

 

[Towers]

Unless it was a spurious 'door open in traffic' alarm and upon inspection the door was confirmed as not being open. Wouldn't be the first time on an 80x.

Yes that's entirely possible!

 

[Lewlew]

Towers, it was announced as a fault with the train, so if it was someone pulling a door release lever, would’nt the Amnassador have said, passenger has pulled an emergency door lever, so we have to wait while driver resets it, rather than stating. a fault With train has caused the stop.

The ambassador might not have known. The driver may simply have quickly called them and said something like "got a door problem, bare with me, I'll keep you posted".

 

[D365]

”Train fault” announcements are deliberately vague.