azblackbird
Pattern Altitude
Saw this on the news yesterday. Anyone have any idea of what's causing the contamination of their oxygen systems?
Mechanical things break, and there are failure modes that pop up over time that engineers don't foresee when they're designing and building stuff...
Really? How long have you been an engineer?Since OBOGS is a system that generates O2 using a mechanical process that filters bleed air, there are any number of reasons why the system might not be producing enough (or good-enough) oxygen.
Mechanical things break, and there are failure modes that pop up over time that engineers don't foresee when they're designing and building stuff...
Really? How long have you been an engineer?
Attack? No, it was asking for your credentials to make a claim like that.Rather than an ad hominem attack, what is your counterpoint to what I posted?
Attack? No, it was asking for your credentials to make a claim like that.
OK, so not an engineer and not been in product meetings where the engineer points to many reasons why the thing shouldn't be launched because of cost/schedule compromises or outright flaws in the design and then being overruled by the suits. And getting that "Nervous Nelly Naysayer" reputation is great for promotions.I wasn't aware that I had to have been an engineer to make a claim that the people who design and build things are not omniscient and cannot foresee every possible potential failure mode over time.
I'm an engineer and I spend quite a bit of time trying to break things for this purpose.Engineers are very interested in how things break. Thats how they learn to make them so they don't break.
I'm an engineer and I spend quite a bit of time trying to break things for this purpose.
Could it be a bleed air leak (bad O-rings possibly) in the filtration system and they're whiffing exhaust fumes?Since OBOGS is a system that generates O2 using a mechanical process that filters bleed air, there are any number of reasons why the system might not be producing enough (or good-enough) oxygen.
Mechanical things break, and there are failure modes that pop up over time that engineers don't foresee when they're designing and building stuff...
I didn't but I know who I'd call. I expect their lines are a little tied up right now.Nauga designed it...its his fault.
I'm an engineer and see little reason to wait for things to break. We take apart things that are perfectly functional to see how they work. Of course once that objective has been met there is little incentive to waste time putting anything back together again - nothing to be learned from that.
I think it started when I took apart the vacuum cleaner. I don't think Mom ever forgave me for leaving behind a pile of parts in the living room...
Seems like the engineers that design BMWs have that same exact mentality...
Engineer: "Sure, we can assemble it from scratch at the factory very easily"....
Other Guy: "But what about when you have to replace the water pump?".....
Engineer: "No, problem, I took it apart after it was assembled. You can get that part out just fine."
Other Guy: "What about putting it back together?"
Engineer: "Mehh, I didn't get that far..."
:-D
Engineers are very interested in how things break. Thats how they learn to make them so they don't break. We've all designed things that have broken. We've all broken things. Things do break. In fact, EVERYTHING put together sooner or later falls apart. Its a law of the universe.
You'll get over it.
Someone has never changed a water pump on a BMW. Easiest one I ever did, hands down.Seems like the engineers that design BMWs have that same exact mentality...
Engineer: "Sure, we can assemble it from scratch at the factory very easily"....
Other Guy: "But what about when you have to replace the water pump?".....
Engineer: "No, problem, I took it apart after it was assembled. You can get that part out just fine."
Other Guy: "What about putting it back together?"
Engineer: "Mehh, I didn't get that far..."
:-D
I find this to be very common with software/firmware. Lousy exception handling. Sloppy programming: "ship it now, fix it later."But I've also had plenty of things that happened in the field that I never anticipated.
Right, another non-engineer. Got it.Hacker, I agree with you. I think paflyer is a tad bit out of line.
I find this to be very common with software/firmware. Lousy exception handling. Sloppy programming: "ship it now, fix it later."
Logical fallacy. I think you've been infected by the POA "argue anything and everything" bug.Right, another non-engineer. Got it.
Come on folks. Engineers do not design things to break. That is pure nonsense! They just design things to be hard to replace when they do fail. I have scarred knuckles to prove it!
Thank you.Engineers do the best they can within the confines of time and fiscal constraints imposed upon them by management.
I agree, but that doesn't mean that there aren't thing that they don't/can't foresee while they are designing/building stuff. If it did, that would mean that nothing would ever have a "design flaw."Engineers do the best they can within the confines of time and fiscal constraints imposed upon them by management.
So the only reason I've had this experience is because I'm lousy at writing code? Really? I guess you're omniscient then...I find this to be very common with software/firmware. Lousy exception handling. Sloppy programming: "ship it now, fix it later."