- Joined
- Jul 23, 2012
- Messages
- 1,899
- Reaction score
- 873
I've been following kjkcolorado's thread with some interest https://www.rocketryforum.com/showthread.php?133199-Just-torched-my-new-RRC2-what-did-I-do-wrong and I wanted to chime in here about a concept touched on, but not really fleshed out, in that discussion.
"Why do you want to connect two matches to one altimeter output, anyway? What's the point?"
The short answer, I believe, is you never want to do that.
What are you trying to achieve? Redundancy in case one match has a problem? If you're putting both matches into the same deployment charge that seems the only possible goal. But as the other conversation pointed out well, you're just swapping potential failure modes around. You are not making the list of potential failure modes any shorter! It really doesn't look like a clear win can be had, containing new benefits but no new risks.
Besides, this level of redundancy isn't deep, given all the other things that remain as single points of failure:
1- The shared altimeter output channel (as kjkcolorado sadly found out - thank goodness it was on the ground)
2- The programming of that shared output channel (what if you set it up wrong?)
3- The rest of the single altimeter
4- The single battery
5- And the shared wiring harness from battery --> altimeter --> deployment charge
I think a far better answer is this: "Always one match per output channel. Always." Followed with the corollary "Make all items on the single point of failure list truly redundant"
Sounds kinda familiar, doesn't it? Level three regs. The requirements for level 3 certification are true and full redundancy. It's a mandate. Two altimeters sharing nothing - no common wiring, no common battery. Primary and backup charges for apogee, and also primary and backup charges for main. I think this rule exists for a good reason, and I think it is the right way to go for ALL birds above a certain size/weight/complexity level.
I'm interested to hear what others think about this. Feel free to tell me I'm crazy, or to point out some special case where 2 matches on a single output actually make sense. Me? I don't see it.
Be safe out there, everybody!
"Why do you want to connect two matches to one altimeter output, anyway? What's the point?"
The short answer, I believe, is you never want to do that.
What are you trying to achieve? Redundancy in case one match has a problem? If you're putting both matches into the same deployment charge that seems the only possible goal. But as the other conversation pointed out well, you're just swapping potential failure modes around. You are not making the list of potential failure modes any shorter! It really doesn't look like a clear win can be had, containing new benefits but no new risks.
Besides, this level of redundancy isn't deep, given all the other things that remain as single points of failure:
1- The shared altimeter output channel (as kjkcolorado sadly found out - thank goodness it was on the ground)
2- The programming of that shared output channel (what if you set it up wrong?)
3- The rest of the single altimeter
4- The single battery
5- And the shared wiring harness from battery --> altimeter --> deployment charge
I think a far better answer is this: "Always one match per output channel. Always." Followed with the corollary "Make all items on the single point of failure list truly redundant"
Sounds kinda familiar, doesn't it? Level three regs. The requirements for level 3 certification are true and full redundancy. It's a mandate. Two altimeters sharing nothing - no common wiring, no common battery. Primary and backup charges for apogee, and also primary and backup charges for main. I think this rule exists for a good reason, and I think it is the right way to go for ALL birds above a certain size/weight/complexity level.
I'm interested to hear what others think about this. Feel free to tell me I'm crazy, or to point out some special case where 2 matches on a single output actually make sense. Me? I don't see it.
Be safe out there, everybody!