If the barriers aren’t detected as being fully raised, the red roads lights will stay on. The road lights went out for a split second which would mean the interlocking initially saw them as all raised, and turned off the road lights, however if one of them was to bounce at the top of the movement, the “Up” detection would be lost and the road lights would come on again. The reason they didn’t come down again is because just losing the Up detection doesn’t start off the lowering sequence. This also explains why the amber light didn’t come on first, it just went straight to flashing red. The barriers each have a contact box in them where the contacts are made when a barrier has reached a certain point, usually 85 degrees, which indicates they are in the raised position. There are also motor contacts in there to drive any barriers back up to 85 degrees before the road lights come on, if they were to bounce. My guess would be these need tweaking.
I believe in emergency scenarios, such as a train approaching too quickly with the barriers raisde, most crossings are designed to skip that phase to convey a more 'urgent' instruction to stop, and that by the time said train reached the crossing with its brakes applied by the safety systems, enough time should have passed to have the crossing clear. I think it only did this here as it lost the 'raised' indication and thought the barriers were about to drop on someone.
Wow! That reminds me of that old video where the lights came on and the barriers stayed up for over 10 minutes. Seems odd it's done something similar again; great catch!!
Ah, I think I know what happened. I think the signaller pressed the wrong button. I think they pressed the middle red 'STOP' button instead of the 'LOWER' button.
Great video! My guess is that there's some kind of fail-safe built in the crossing somewhere, and, for whatever reason, one of the gate mechs doesn't raise all the way properly and causes the crossing to re-activate in the way it did. Kinda reminds me of that short malfunction some AHB crossings do when one of the gate arms doesn't raise as quickly as it should, except, of course, longer.
That is a possibility and would make sense, though I would say they all raised properly in that instance. Other than a button slip, I couldn't say for sure what I think caused it as the next train was quite a way away. Thanks by the way!
@@SouthEastLevelCrossings My guess would be there are electronic contacts inside the gate mechs (that determine when an arm is fully raised/lowered, for example), and at least one is either not adjusted properly or getting worn-out, causing it to not close/open when it should, causing the issue. I know older, pre-EGM gate mechs here in the US use contacts, and if those get messed-up they can cause issues (for example, I once saw a gate mech that refused to lower due to a messed-up contact in the gate mech, apparently preventing the hold-clear from releasing). My other guess would be a relay somewhere is getting worn-out and not operating properly or something.
@@SouthEastLevelCrossings if it was a button slip it would bring on the steady amber, then flashing red and then the barriers would start to lower as per the sequence. But it was just the flashing red which means the up indication was lost.
Great Videos and Crossing!👍🏻👍🏻
Thank you!
That is at New Lane, right beside the junction where trains either diverge to Petersfield, or the South Coast line.
Nice! Wow vehicle managed to get on the tracks and off as red lights were on around 10:41 nice
Numbers on the class 444 train: 044
I swear this crossing always malfunctions. Once, the train passed and it stayed down for another few minutes before raising.
Nice catch
Thank you very much!
Excellent video! Couldn’t the signaller override the activation?
Thanks very much! They can, and that's probably what they did when it eventually de-activated.
If the barriers aren’t detected as being fully raised, the red roads lights will stay on. The road lights went out for a split second which would mean the interlocking initially saw them as all raised, and turned off the road lights, however if one of them was to bounce at the top of the movement, the “Up” detection would be lost and the road lights would come on again. The reason they didn’t come down again is because just losing the Up detection doesn’t start off the lowering sequence. This also explains why the amber light didn’t come on first, it just went straight to flashing red. The barriers each have a contact box in them where the contacts are made when a barrier has reached a certain point, usually 85 degrees, which indicates they are in the raised position. There are also motor contacts in there to drive any barriers back up to 85 degrees before the road lights come on, if they were to bounce. My guess would be these need tweaking.
Interesting. Thanks for the insight!
There is a barrier fault. Also here is an one too fast alarm.
(7:53) It skipped the amber warning light.
I believe in emergency scenarios, such as a train approaching too quickly with the barriers raisde, most crossings are designed to skip that phase to convey a more 'urgent' instruction to stop, and that by the time said train reached the crossing with its brakes applied by the safety systems, enough time should have passed to have the crossing clear. I think it only did this here as it lost the 'raised' indication and thought the barriers were about to drop on someone.
Cool video
Cheers! 😁
Wow! That reminds me of that old video where the lights came on and the barriers stayed up for over 10 minutes. Seems odd it's done something similar again; great catch!!
It very much reminded me of that same video. The main difference this time was that it did deactivate rather than eventually lower. Thanks! 😁
Ah, I think I know what happened. I think the signaller pressed the wrong button. I think they pressed the middle red 'STOP' button instead of the 'LOWER' button.
Nice vid! Misuse 9:34
Thanks! Yeah...
Great video 👍
Thank you!
Barriers are horrible here. Nice video
They are in quite a state, for definite. Thanks!
Great video! My guess is that there's some kind of fail-safe built in the crossing somewhere, and, for whatever reason, one of the gate mechs doesn't raise all the way properly and causes the crossing to re-activate in the way it did. Kinda reminds me of that short malfunction some AHB crossings do when one of the gate arms doesn't raise as quickly as it should, except, of course, longer.
That is a possibility and would make sense, though I would say they all raised properly in that instance. Other than a button slip, I couldn't say for sure what I think caused it as the next train was quite a way away.
Thanks by the way!
@@SouthEastLevelCrossings My guess would be there are electronic contacts inside the gate mechs (that determine when an arm is fully raised/lowered, for example), and at least one is either not adjusted properly or getting worn-out, causing it to not close/open when it should, causing the issue. I know older, pre-EGM gate mechs here in the US use contacts, and if those get messed-up they can cause issues (for example, I once saw a gate mech that refused to lower due to a messed-up contact in the gate mech, apparently preventing the hold-clear from releasing).
My other guess would be a relay somewhere is getting worn-out and not operating properly or something.
@@SouthEastLevelCrossings if it was a button slip it would bring on the steady amber, then flashing red and then the barriers would start to lower as per the sequence. But it was just the flashing red which means the up indication was lost.
So people are ignoring the crossing being on