12-19-2018, 06:36 PM
I was by the University crossing this evening and had a chance to watch the warning system in operation again.
It worked well, but as the poster with the video mentioned, they come down awfully early (before a train has even departed University of Waterloo station, heading SB). They raised promptly after the train passed (514, I believe), and the lights turned green after about ~5 seconds delay.
I think the problem must be with when a pedestrian crosswalk request is made - that just completely garbles the whole sequence and it has no idea how to recover. I've seen the condition exactly as described in the video, and from memory, I think it has always occurred when there's a large throng of people waiting to cross (meaning: someone's likely pushed the button). Foot traffic was absent in the area (except for the guy who decided to cross diagonally through the barriers, bells and lights flashing, because WTF, the rules don't apply to me!) so that's likely why the cycle operated perfectly.
It worked well, but as the poster with the video mentioned, they come down awfully early (before a train has even departed University of Waterloo station, heading SB). They raised promptly after the train passed (514, I believe), and the lights turned green after about ~5 seconds delay.
I think the problem must be with when a pedestrian crosswalk request is made - that just completely garbles the whole sequence and it has no idea how to recover. I've seen the condition exactly as described in the video, and from memory, I think it has always occurred when there's a large throng of people waiting to cross (meaning: someone's likely pushed the button). Foot traffic was absent in the area (except for the guy who decided to cross diagonally through the barriers, bells and lights flashing, because WTF, the rules don't apply to me!) so that's likely why the cycle operated perfectly.