I'm working on my first HP multi-stage, and could use some advise. It will be a 3" rocket, about 9 feet fall. ~3 foot booster with 54mm motor mount, most likely with a K and its own chute, then a dual deploy sustainer with a 54mm J or K. I'm hoping for a test launch at some METRA launch, and then a high altitude launch at LDRS next summer.
To couple the booster to sustainer I'm using about a 6" long piece of coupler tubing, with a bulk head on the bottom, and a very small ring of actual body tubing in the center. The bulk head will be attached to the recovery harness of the booster. The lower centering ring of the sustainer is sufficiently far up the body tube that the coupler fits up into the sustainer ~2" and bottoms out firmly on the centering ring. The timer to ignite the sustainer will be in the sustainer electronics bay, with a small SS tube getting the igniter wires down to the motor through the centering rings. The electronics bay includes an altimeter for dual deploy recovery, and a GPS with RF telemetry to find it!
My question is, what is the best way to insure good clean separation? A natural drag separation would be nice. Can I rely on this? If this doesn't happen, is it sufficient to allow the lighting of the second stage force off the coupler (which has a sealed bulk head in it)? In this case I should set the delay time on the booster eject charge sufficiently longer than the delay time on the timer electronics which will ignite the sustainer? Therefore the sustainer ignites first, then the eject charge in the booster.
Or, should I set the eject charge shorter on the booster, therefore forcing a separation prior to ignition of the sustainer? Or might this risk distorting the flight path of the sustainer prior to ignition?
Any thoughts on a test flight? I was thinking to fly it first with everything connected, except leave out the igniter in the sustainer. This would check the separation, and give me a feeling for stability, without risking a 2nd stage ignite in case it doesn't fly straight, or something else goes wrong.
Any comments/thoughts/suggestions are more than welcome.
Thanks - Adrian