johnr57
Member
- Joined
- 29 Mar 2013
- Messages
- 270
It appears the issue was on a freight train.Seen at York this morning - any ideas what happened?
No, nothing at all like that... If you don't really have a clue probably best not commenting something completely wrong!probably the driver pressed the uncouple button by accident
i've re-worded it slightly.No, nothing at all like that... If you don't really have a clue probably best not commenting something completely wrong!
So what was the issue then?It appears the issue was on a freight train.
No, nothing at all like that... If you don't really have a clue probably best not commenting something completely wrong!
A freight train divided, I don't know how or why so I won't speculate on that.So what was the issue then?
You don't just press the uncouple button 'by accident'. To accidentally uncouple you'd need to go into the coupled cab, key in, cancel the AWS, set the desk up correctly and then press the uncouple button (and on modern units such as 195s and I suspect 80x the train will automatically recouple if not moved apart a certain amount of time since they were uncoupled). You don't just accidentally push a button from the front cab and leave a unit behind on the move!i've re-worded it slightly.
Thanks for the clarification. I was definitely told they recouple but not to let it happen as it upsets the computer... either way you're not accidentally leaving coaches behind!On a 195 once the button is pressed even if the trains stay together they won't move again (together) till the full recoupling process has been completed. Computer says no.![]()
thanks for letting me know, as i’m not in the railway industry, i had no idea that was how (my only idea was from an Old wessex traind training video fpr 153s uploaded onto youtube)You don't just press the uncouple button 'by accident'. To accidentally uncouple you'd need to go into the coupled cab, key in, cancel the AWS, set the desk up correctly and then press the uncouple button (and on modern units such as 195s and I suspect 80x the train will automatically recouple if not moved apart a certain amount of time since they were uncoupled). You don't just accidentally push a button from the front cab and leave a unit behind on the move!
It’s likely an auto-populated reason. The full reason would be too long to include.So whoever updates the PIS thinks freight trains consist of coaches![]()
Poor excuse.It’s likely an auto-populated reason. The full reason would be too long to include.
But I don’t know if that’s one of the auto-populated reasons available to whoever is operating that PIS. It might not be their fault. It’s still better than “operational incident”!Poor excuse.
"a freight train becoming uncoupled" (for example) is no longer.
If it isn't, it should be - I would think a freight train uncoupling is a more likely occurrence than a passenger train doing so.But I don’t know if that’s one of the auto-populated reasons available to whoever is operating that PIS. It might not be their fault. It’s still better than “operational incident”!
The delay code will probably be something like 'train divided', because fundamentally from an operational POV there's no real difference between a passenger or a freight train dividing.If it isn't, it should be - I would think a freight train uncoupling is a more likely occurrence than a passenger train doing so.
In which case, Train becoming divided (or uncoupled) would be fine as an accurate reason on the PISThe delay code will probably be something like 'train divided', because fundamentally from an operational POV there's no real difference between a passenger or a freight train dividing.
Indeed, but in this case the PIS was set (whether manually or by default) to replace it with a message that sounds potentially a little less dramatic.In which case, Train becoming divided (or uncoupled) would be fine as an accurate reason on the PIS
In a past era, especially with unfitted freights, hearing the bell code for "train divided" would be bad news enough for a signaller, but not as alarming as " train running away on right line", or worse still "train running away on wrong line". Not something which would have been made known to the travelling public I'd guess, even if there had been a system which was capable of doing so.The delay code will probably be something like 'train divided', because fundamentally from an operational POV there's no real difference between a passenger or a freight train dividing.
More options means more work to find the right one, it's a balance.If it isn't, it should be - I would think a freight train uncoupling is a more likely occurrence than a passenger train doing so.
“Poor excuse”Poor excuse.
"a freight train becoming uncoupled" (for example) is no longer.
Did that take a few goes to get the timing exactly right, or is it from a video?honourable mention
That one will be ‘an unusually large passenger flow’, it’s just the word ‘flow’ has been cut off.Did that take a few goes to get the timing exactly right, or is it from a video?![]()
Exactly. I was just wondering if the capture of the scrolling message was skill or luck…That one will be ‘an unusually large passenger flow’, it’s just the word ‘flow’ has been cut off.
found it elsewhere, not mineDid that take a few goes to get the timing exactly right, or is it from a video?![]()