Welcome Guest!
In order to take advantage of all the great features that Waterloo Region Connected has to offer, including participating in the lively discussions below, you're going to have to register. The good news is that it'll take less than a minute and you can get started enjoying Waterloo Region's best online community right away.
or Create an Account




Thread Rating:
  • 16 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ION - Waterloo Region's Light Rail Transit
(11-27-2020, 07:50 PM)dtkvictim Wrote: If I'm not mistaken, a big part of why we chose the vehicles we did was to piggy-back on Toronto's order. Perhaps ironically, Toronto has ordered some of the same vehicles as Ottawa now because they fear Bombardier won't fulfill their order in time.

Even more ironically, Metrolinx had a whole lot to do with the delays, as they turned uncooperative once they were fighting BBD in court.
Reply


(11-27-2020, 07:17 PM)ac3r Wrote: Also, maybe this disaster that we call the ION could...you know...NOT use Bombardier for anything going forward?

"Disaster" is an unnecessarily hyperbolic mischaracterisation of ION.

Yes, Bombardier being so late on delivery was very frustrating, but once we had the working trams Keolis had things up and running in short order, and they have been reliable ever since. The problems with the EasyGO fare card system were also frustrating, but I am of the opinion that at least some of the problems were with users not paying attention and using the system incorrectly. Presto has had far more problems on almost every one of their installs. The TTC for example, has been having problems with their implementation for more than 5 years.

Frustrating? Sure. A disaster? Hardly.

(11-27-2020, 07:17 PM)ac3r Wrote: When is the last time you ever read anything about them that wasn't bad news? They're a terrible company.

I'm guessing that you don't follow rail news, like, at all? Alstom, Siemens, Kinki Sharyo, they've all had their problems at one time or another. Alstom's clusterfuck with the Citadis Spirit for Ottawa. Siemens was forbidden from bidding on contracts for the London Underground for more than a decade from the early 2000s because a previous delivery was just as bad as Ottawa's from Alstom.

Prior to mid 2013 or so, well after Waterloo Region had decided to join the contract with Metrolinx, Bombardier Transportation was one of the top three largest rail manufacturers and had a highly respected reputation, 180° from Bombardier Air's. That had produced literally tens of thousands of locomotives and cars for the previous 40+ years, include more than 3,000 LRT trams. Unless you were expecting the Regional Council to have been psychic and able to tell the future, there were some very good reasons to go with Bombardier.

(11-27-2020, 07:17 PM)ac3r Wrote: I think we only went with them because we or they or someone got some breaks if we bought Canadian, but that turned out to be a complete waste of time and money.

One of those good reasons was cost. The only other manufacturers who reportedly showed any interest in supplying trams for the ION were Alstom, Siemens and Kinki Sharyo, and if you go and google their contracts for the five to ten years prior to 2012 that got mentioned in the news, you'll quickly see that we probably would have paid close to twice as much for trams from one of them, based on those other known contracts. Even with the extra $20-25M in other costs caused by Bombardier being so late, we are still cheaper than what those three would have been.

(11-27-2020, 07:17 PM)ac3r Wrote: Alstom may have had some wonky doors on the newest Otrain line, but at least they got trains in time - not 2-3 years later, incomplete with no APT and welding that was cracking after a few weeks.

If you think Ottawa only had a few problems with "wonky doors" then you weren't paying attention to what happened there.

They also had problems with control system integration the required 20+ minute reboots, various problems with the electrical systems which caused the trams to stop working in inclement weather, and issues persisted into January of this year when on one day they were short 5 trams due to recurring mechanical and electrical issues. They are supposed to have 13 trams on during peak, and 8 the rest of the day. And a whole bunch more.

Now contrast that to our trams. Bombardier may have been very late, but once we got all of them Keolis had the system up and running in short order and it has been reliable ever since.

So twice the price and all those problems? No thank you!
Reply
(11-27-2020, 07:17 PM)ac3r Wrote:
(11-27-2020, 01:24 PM)Bytor Wrote: after 2041?
For the sake of everyone in WR, I hope we build a second line before 2041...it shouldn't take a region of over 600'000 roughly half a century to simply build two "rapid" transit lines. eyerollemoji

Not if there isn't the ridership to make it warranted.

None of the remaining iXpress routes have riderships of more than 1,500 per day, pre-covid. Only the 201 was that high, the rest were at about 1,000/day. At 7% per year average annual growth that will take a minimum of ~18 years before the 201 reaches the lower end of the range where LRTs start to have a comparable operating cost per ride to a bus route, and ~23 years to the middle of the range. So we are, realistically, looking at 2038 to 2043 before Stage 3 would be warranted based purely on operational cost. None of the numbers that I have gotten over the years from the GRT has suggested that the other iXpress routes ever had growth rates above system average like the 200/302 has had.
Reply
Lots of unknowns in predicting the future: will more people work from home, how many people will live in the downtowns, will there be less parking available for cars, will more people walk or use bicycles, and more. Very hard to know.

And, whatever the actual numbers, we should remember that the LRT was built not only to carry people but also to promote intensification along its route. Building a stage 3 should mean building it wherever we expect the next stage of intensification to be. And at the moment we still have a lot of capacity to intensify along the current stage 1 route, so that urgency is not there yet. 10+ years before we start going down this path, I expect, subject to change of course! Big Grin
Reply
(11-27-2020, 10:28 PM)ijmorlan Wrote: I read an article which said that any train with a door that wouldn’t close would be locked out by the ATP (automatic train protection) and could only be moved under old-school procedures essentially involving written authorization to use sections of track.

Total engineering fail; ATP has no business absolutely preventing a train from operating just because of door problems. There should be a procedure to inform the system that the door has failed, possibly install a temporary barrier, and continue on, even in service if appropriate.

What horrors lurk in the design away from areas where I can confidently assert the designers screwed up?

I hope this isn’t the way of the future: software industry practices applied to other industries. By this I mean products which, while technically meeting the spec, fail to operate in the way which anybody who actually thought about the problem for a few minutes would realize they should operate. The customer should not be responsible for thinking of all the obvious, goes-without-saying, features and putting them explicitly in the spec.

1. I think you are mixing up ATP with ATC. ATP is just a signaling system that compares train speed with permitted speed and signals the train control computer for brake activation if the train speed is above the permitted speed. ATC takes control over acceleration and braking and works in conjunction with ATP to operate the train safely.

2. That's not an engineering fail at all. All modern passenger trains have a door interlock braking system. When the doors are open, the brakes are activated. When the doors close properly the brakes are then deactivated. If the doors do not close properly, the door interlock brake stays active. ATC is a completely separate hardware module that simply sends commands to and receives data inputs from the train control computer. ATC doesn't get a signal as to why the brakes are active. All ATC gets from the train control computer is basically: "Brakes: Active, Position: Service-50%, Locked: True". ATC would operate in the same fashion if the operator hit the emergency stop switch on the control panel. All ATC would know from that is: "Brakes: Active, Position: Emergency, Locked: True". ATC can only control the train if the controls aren't locked out by another module with higher control priority, like the emergency stop switch or door interlock brake.
Reply
(11-29-2020, 07:10 PM)trainspotter139 Wrote: 1. I think you are mixing up ATP with ATC. ATP is just a signaling system that compares train speed with permitted speed and signals the train control computer for brake activation if the train speed is above the permitted speed. ATC takes control over acceleration and braking and works in conjunction with ATP to operate the train safely.

I think you’re right. It’s been a while since I read the article; most likely it referred to ATC.

Quote:2. That's not an engineering fail at all. All modern passenger trains have a door interlock braking system. When the doors are open, the brakes are activated. When the doors close properly the brakes are then deactivated. If the doors do not close properly, the door interlock brake stays active. ATC is a completely separate hardware module that simply sends commands to and receives data inputs from the train control computer. ATC doesn't get a signal as to why the brakes are active. All ATC gets from the train control computer is basically: "Brakes: Active, Position: Service-50%, Locked: True". ATC would operate in the same fashion if the operator hit the emergency stop switch on the control panel. All ATC would know from that is: "Brakes: Active, Position: Emergency, Locked: True". ATC can only control the train if the controls aren't locked out by another module with higher control priority, like the emergency stop switch or door interlock brake.

It is an engineering fail for a door problem to absolutely prevent operation of the train.

To be clear, there are multiple possible scenarios. Say the door is stuck and won’t close; either at all or completely. Depending on the exact situation, either the vehicle should be evacuated and then driven to the OMSF, or kept in service until the end of the line (or wherever) with a temporary barrier across the door (and the door excluded from normal open/close operation). In either scenario, there needs to be a procedure to inform ATC that the door is locked out and to ignore what it is saying.

Another possible scenario is the door closes fine, but the device which detects the state of the door has failed and always reports that it is open. In this scenario especially it is obviously totally absurd for the vehicle not to be able to operate.

Even with the current malengineered situation, the train can be operated; it just needs written track authority. So presumably there is a way of disengaging the brakes even while the door is still reporting that it is open (I don’t think typical train motive power is capable of moving the train against a fully-applied brake, even if the control system would allow an attempt). Again, a door problem is not a legitimate reason to require going back to 1800s technology. In fact, I can’t think of much that would; besides the obvious failure of part of the ATC itself, something like total brake failure maybe; except that then the vehicle would have to be towed or pushed, and in that case it would be nice if ATC could still be able to operate the helper vehicle.

This is not the first time I have heard of clearly wrong design related to doors. My understanding is that some subway trains, I think including the TTC’s Toronto Rockets, have the following procedure when an obstruction prevents a door from closing: all doors re-open and repeat the closing sequence. If they fail 3 times, the train is out of service. This is totally absurd. What should happen is that only the obstructed door should re-open. This means instead of requiring 24 doors to successfully close simultaneously, maybe 23 close on the first try and the remaining one re-opens and then closes. So right away this would eliminate most of the problems. Next, the basic idea of 3 failures requiring taking the train out of service is OK; if there is an equipment failure, at some point it needs to be dealt with. But if the reason is identified as “some idiot kept sticking their foot in the door”, then there is no equipment failure (not even a suspicion of a failure) and no point in taking the train out of service. What, they’ll take it back to the yard, and do … what? It’s fine; there was just somebody blocking it.

I think safety engineers need to step back more often and consider whether the behaviour they are creating is reasonable. I’m not asking for them to design unsafe systems, but the above examples just don’t pass the smell test.
Reply
(11-29-2020, 09:45 PM)ijmorlan Wrote: This is not the first time I have heard of clearly wrong design related to doors. My understanding is that some subway trains, I think including the TTC’s Toronto Rockets, have the following procedure when an obstruction prevents a door from closing: all doors re-open and repeat the closing sequence. If they fail 3 times, the train is out of service. This is totally absurd. What should happen is that only the obstructed door should re-open. This means instead of requiring 24 doors to successfully close simultaneously, maybe 23 close on the first try and the remaining one re-opens and then closes. So right away this would eliminate most of the problems.

This is the way every urban train (that I can think of) works: all the doors open and close in unison. One won't close? All doors will reopen and attempt to close again.

I am not an expert in this, though, so I don't know why this logic is used.
Reply


(11-29-2020, 09:58 PM)tomh009 Wrote:
(11-29-2020, 09:45 PM)ijmorlan Wrote: This is not the first time I have heard of clearly wrong design related to doors. My understanding is that some subway trains, I think including the TTC’s Toronto Rockets, have the following procedure when an obstruction prevents a door from closing: all doors re-open and repeat the closing sequence. If they fail 3 times, the train is out of service. This is totally absurd. What should happen is that only the obstructed door should re-open. This means instead of requiring 24 doors to successfully close simultaneously, maybe 23 close on the first try and the remaining one re-opens and then closes. So right away this would eliminate most of the problems.

This is the way every urban train (that I can think of) works: all the doors open and close in unison. One won't close? All doors will reopen and attempt to close again.

I am not an expert in this, though, so I don't know why this logic is used.

It's standard for any system where the doors opening/closing is automatic for obvious reasons. ION is an example that clearly shows that train manufacturers already have the technology to individually control the doors. You end up trading one problem for another, though. Instead of a simpler system where all doors operate simultaneously, you have a more complicated system that could now fail in some other way.
Reply
(11-30-2020, 07:41 AM)jamincan Wrote: It's standard for any system where the doors opening/closing is automatic for obvious reasons. ION is an example that clearly shows that train manufacturers already have the technology to individually control the doors. You end up trading one problem for another, though. Instead of a simpler system where all doors operate simultaneously, you have a more complicated system that could now fail in some other way.

I assume it’s inertia. At one time, it would have been a substantial undertaking to build any sort of independent control into the door system. First you need a way of getting per-door signals from the cabs to the doors; and next unless the individual operation is entirely automatic you need some way of providing controls for each door. But now, with everything computerized, it’s much easier to push all the complexity into software. This doesn’t make the problem disappear entirely, but providing the individual control becomes a coding problem, rather than a whole bunch of additional hardware.

One thing I’d like to know: does the cab display show the status of each door individually? I don’t actually know.

Although it occurs to me that if the open/close cycle were localized to each door then the overall train could simply have a single open/close command for all doors, even while individual doors can retry on their own. There is no need for a door that won’t close to immediately tell the rest of the train about it — until it’s given up on retrying, it can just signal that it’s still closing and so it will appear as a very slow closing door to the rest of the system. But I’m less sure about this part because I don’t know where the logic to re-open and then try closing again actually is — in the door mechanism or in a central control point. In a modern system it doesn’t matter though.
Reply
The mention of ION reminds me of another door-related example of maldesign: when the LRT is sitting in station with the doors in “open when button pressed” mode, each door chimes when it closes after letting somebody on or off. This leads to an utterly pointless cacophony. Instead they should close silently. The chime is only useful when the reason the doors are closing is because they are changing to “closed, ready to move” mode. Arguably the chime should also sound just before the doors switch from “ open when button pressed” mode to “closed, ready to move” mode.

Additionally, the doors should have different re-opening policies depending on why they’re closing: if they’re closing because enough time has elapsed since the button was pushed, they should re-open like an elevator door: essentially, prioritize letting people through. Only once the doors have been informed to close in preparation for departure should they switch to the more aggressive subway train policy which prioritizes getting the train under way (and then, of course, see previous discussion on allowing each door to have more independence).
Reply
(11-30-2020, 08:52 AM)ijmorlan Wrote: The mention of ION reminds me of another door-related example of maldesign: when the LRT is sitting in station with the doors in “open when button pressed” mode, each door chimes when it closes after letting somebody on or off. This leads to an utterly pointless cacophony. Instead they should close silently. The chime is only useful when the reason the doors are closing is because they are changing to “closed, ready to move” mode. Arguably the chime should also sound just before the doors switch from “ open when button pressed” mode to “closed, ready to move” mode.

Additionally, the doors should have different re-opening policies depending on why they’re closing: if they’re closing because enough time has elapsed since the button was pushed, they should re-open like an elevator door: essentially, prioritize letting people through. Only once the doors have been informed to close in preparation for departure should they switch to the more aggressive subway train policy which prioritizes getting the train under way (and then, of course, see previous discussion on allowing each door to have more independence).

Is this not an accessibility feature to let all people know that the door is closing?  I.e., it is about the door closing, not the train departing.
Reply
Indeed, its primary purpose is to assist the visually impaired so they don't get caught in a closing door.
Reply
(11-30-2020, 03:14 PM)KevinL Wrote: Indeed, its primary purpose is to assist the visually impaired so they don't get caught in a closing door.

And yet somehow elevators get by without it. Or, now that I think about it, do elevators have a closing chime? Even if so, however, it’s not as loud and obtrusive as the LRT chime. The LRT chime is totally fine for departure, it’s just the repeating of it over and over while the LRT is parked which I find to be excessive.
Reply


(11-30-2020, 05:52 PM)ijmorlan Wrote:
(11-30-2020, 03:14 PM)KevinL Wrote: Indeed, its primary purpose is to assist the visually impaired so they don't get caught in a closing door.

And yet somehow elevators get by without it. Or, now that I think about it, do elevators have a closing chime? Even if so, however, it’s not as loud and obtrusive as the LRT chime. The LRT chime is totally fine for departure, it’s just the repeating of it over and over while the LRT is parked which I find to be excessive.

Could that possibly be resolved by using the button to open if necessary but control the close from the cab? (Kinda a hybrid of what they do now?)
Reply
(11-29-2020, 09:45 PM)ijmorlan Wrote: Even with the current malengineered situation, the train can be operated; it just needs written track authority. So presumably there is a way of disengaging the brakes even while the door is still reporting that it is open (I don’t think typical train motive power is capable of moving the train against a fully-applied brake, even if the control system would allow an attempt). Again, a door problem is not a legitimate reason to require going back to 1800s technology. In fact, I can’t think of much that would; besides the obvious failure of part of the ATC itself, something like total brake failure maybe; except that then the vehicle would have to be towed or pushed, and in that case it would be nice if ATC could still be able to operate the helper vehicle.

There's certainly a way to disable the door interlock to move or tow a vehicle back to the yard for repairs, but it would never be engaged with passengers on board for obvious reasons.

You'd never be able or want to tow or operated a train or any other vehicle with its brakes engaged. Brakes are designed purposefully to be much more powerful. But there will also be some mechanism or master switch to manually disengage the emergency or parking brake.
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 9 Guest(s)

About Waterloo Region Connected

Launched in August 2014, Waterloo Region Connected is an online community that brings together all the things that make Waterloo Region great. Waterloo Region Connected provides user-driven content fueled by a lively discussion forum covering topics like urban development, transportation projects, heritage issues, businesses and other issues of interest to those in Kitchener, Waterloo, Cambridge and the four Townships - North Dumfries, Wellesley, Wilmot, and Woolwich.

              User Links