Easy Mega Staging Setup - Balls 2015

Kip_Daugirdas said:

My thought is that the "flight state before" and "after" might be the culprit. Should have I not selected those!?

Click to expand...

Zebedee said:

This question came up looking at Jim's configuration. If you have an altitude check and also a "delay after other conditions" check selected - Does it wait to start the delay after the rocket exceeds the altitude value?

If so, is there a way to make it wait for the delay number of seconds after burn out and then check the altitude to verify that the rocket is high enough (e.g. it did not weathercock/lay over during the delay) before lighting the next stage?

Click to expand...

keithp said:

Yup. You should have just used 'After Motor Number' and selected '1'. Selecting 'flight state before Fast' means that the motor ignition was inhibited because you were in state 'fast' or 'coast' after burnout.

We spent a while brainstorming at Airfest over Labor day and I think the best idea we came up with was to add a menu of 'normal' configurations that would pre-set the usual options for various uses of the extra pyro channels. That and a bit of memory for the 'tilt angle' setting so that a rapidly rotating airframe wouldn't accidentally hit the right tilt angle just as the test was made. Right now, the tilt angle is checked during the 'delay after other conditions' phase, but if you set that to zero, then it doesn't check the angle more than once.

A 'normal' sustainer ignition setting for a two stage flight should be 'after motor number 1', 'tilt angle less than 20' and 'delay after other conditions 2' -- that'll light the motor two seconds after the booster burns out. You could use a longer coast if you want to go higher, but of course that might mean tilting over too far.

Click to expand...

Kip_Daugirdas said:

I don't think a normal menu is super necessary. Instead some explicit examples in the documentation would help for common flight scenarios.

Click to expand...