Gordon Bain <[email protected]> writes: > Can anyone tell me what I did wrong?
You set the 'flight state before' value to 'coast', which means that the igniter will not fire unless the rocket has not yet reached 'coast' state. In this case, I think the settings you'd want are 'after motor 1', 'tilt limit 20 degrees (for the sustainer ignition)', and 'delay after other conditions 1 or 2.5 seconds'. The 'state before' and 'state after' settings seem to be difficult for many people to get their heads around; 'state before' means that the rocket must have not yet reached the named state, 'state after' means that the rocket has reached the named state. By setting 'state before coast', you effectively require that the rocket still think that the motor is burning, or that the rocket has not yet reached 100m (that's as second condition on transitioning from boost to coast designed to avoid false triggering from a motor chuff). I have a plan to add some 'stock' configurations that will pre-configure settings for some common cases like this. I've also considered attempting to have some simulation mechanism so that you can see what the settings you've made will do. However, you'd want a wide range of possible simulations to check and make sure the settings work in a range of possible flights; there are usually many settings which work fine if the flight is nominal, but creating appropriate settings that fail safely when the flight doesn't go as planned means mapping out the whole failure tree. It turns out multi-staged flights are hard; it looks like your flight at least ended without damage, sorry you didn't get it to work correctly. -- -keith
signature.asc
Description: PGP signature
_______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
