Register or Login to Hide This Ad for Free!
Status
Not open for further replies.
Here’s the thing, it would make sense for BGW to open it either early May, or early july to not interfere with veloci. But that might not be possible to do in May, so who knows
 
My understanding is that when a ride is turned over to the park the ops do everything they can to force faults such as hitting all the buttons on the control panel at once, etc. Is that even close to correct?
That's usually during the programming time. Usually the programmer will run the ride alone until 2 train ops, then have park ops come and operate the ride. This is when they do anything they can to cause a fault, valley, or otherwise break the system. This reduces downtime after opening.
 
On another note tho don't be surprised when this ride doesn’t have much downtime, from people i’ve talked to hagrids served as the testing grounds for this switch and they may have perfected it, only thing i’m worried about is the newer lsm’s this ride uses, haven’t seen many like them this extreme so, we will see
 
Don’t worry I’m sure we’ll get the special intamin maintenance treatment of half off half off
 
  • Like
Reactions: Le Moose
My understanding is that when a ride is turned over to the park the ops do everything they can to force faults such as hitting all the buttons on the control panel at once, etc. Is that even close to correct?

I'm not going to say all the details, but a ride that I helped commission, I was talking with the engineer from the manufacturer. Basically, he wanted me to "break the ride." We pressed every button there was and then he basically told me to kick the operator gate with the ride in motion to see if it engaged the e-stop. Needless to say, I kicked the gate open and the ride did NOT e-stop. So we hit the e-stop. But the programmer got frustrated at us because he "disabled" that safety feature for testing purposes (they hadn't handed the ride over to operations yet). After that, the gate sensor was enabled again because there was basically no reason for it to be disabled at that point in testing.

But I'm sure the programmers have ridden the ride already like ControlsEE mentioned. They get to ride before anyone else. If I can find the comment, I'll link it, but on Irvine Ondrey Engineering they mentioned that they get frustrated when higher ups wish to ride before they have the ride dialed in.
 
I mean it makes sense - I'd assume the manufacturer's main concerns are getting things dialed in and getting it ready to hand over to the park; operations would be more concerned with figuring out and testing all the ways an op or guest could to fault the ride systems while the manufacturer is still around so they can resolve anything that comes up.
 
  • Like
Reactions: Twisted_Airtime
Still doo-doo brown... but it blends well (naturally) with the environment.
Still wish it had one more post-top hat element... but the 3-time launch bunny hop will be fantastic.
 
My understanding is that when a ride is turned over to the park the ops do everything they can to force faults such as hitting all the buttons on the control panel at once, etc. Is that even close to correct?

"OP1 Ride start is stucked." That was a legit fault at Volcano. If you held down any button at board for more than 60 seconds the ride would fault out and require a maintenance reset. Always a fun one to explain to 690.

I'm not going to say all the details, but a ride that I helped commission, I was talking with the engineer from the manufacturer. Basically, he wanted me to "break the ride." We pressed every button there was and then he basically told me to kick the operator gate with the ride in motion to see if it engaged the e-stop. Needless to say, I kicked the gate open and the ride did NOT e-stop. So we hit the e-stop. But the programmer got frustrated at us because he "disabled" that safety feature for testing purposes (they hadn't handed the ride over to operations yet). After that, the gate sensor was enabled again because there was basically no reason for it to be disabled at that point in testing.

But I'm sure the programmers have ridden the ride already like ControlsEE mentioned. They get to ride before anyone else. If I can find the comment, I'll link it, but on Irvine Ondrey Engineering they mentioned that they get frustrated when higher ups wish to ride before they have the ride dialed in.

I remember being able to pull a restraint all the way up during a ride commissioning, the board was still registering it as down. One of the Park Managers had literally just gotten off from a test ride in that exact same seat too. I'll never forget that look on his face.
 
"OP1 Ride start is stucked." That was a legit fault at Volcano. If you held down any button at board for more than 60 seconds the ride would fault out and require a maintenance reset. Always a fun one to explain to 690.



I remember being able to pull a restraint all the way up during a ride commissioning, the board was still registering it as down. One of the Park Managers had literally just gotten off from a test ride in that exact same seat too. I'll never forget that look on his face.

As a former rides sup from KD, can confirm that all forms of chicanery can happen. Doesn't mean the ride is completely unsafe, there are fail safes on fail safes designed for most situations.
 
Status
Not open for further replies.
Consider Donating to Hide This Ad