Might be useful to have a list of general settings for standard configs.
The only people who get this are list subscribers. There wasn't even any 
mention of the list in the manual.  So helpful as this config you have provided 
is...
A it's after the event.  Which I'll assume was expensive for the rocket owner.
B Should have been part of a standard config list disseminated with the manual. 
 Preventing A


Norman McGeoch
TRA12957
Mob 0451 463 961



-------- Original message --------
From: [email protected]
Date: 21/03/2018 5:00 AM (GMT+10:00)
To: [email protected]
Subject: altusmetrum Digest, Vol 81, Issue 6


Send altusmetrum mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.gag.com/mailman/listinfo/altusmetrum
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of altusmetrum digest..."


Today's Topics:

   1. Re: Fwd: Help with TeleMega setting for two stages (Keith Packard)


----------------------------------------------------------------------

Message: 1
Date: Mon, 19 Mar 2018 23:27:26 -0600
From: "Keith Packard" <[email protected]>
To: Gordon Bain <[email protected]>, [email protected]
Subject: Re: [altusmetrum] Fwd: Help with TeleMega setting for two
        stages
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: 
<http://lists.gag.com/pipermail/altusmetrum/attachments/20180319/627b7c56/attachment-0001.sig>

------------------------------

Subject: Digest Footer

_______________________________________________
altusmetrum mailing list
[email protected]
http://lists.gag.com/mailman/listinfo/altusmetrum


------------------------------

End of altusmetrum Digest, Vol 81, Issue 6
******************************************
_______________________________________________
altusmetrum mailing list
[email protected]
http://lists.gag.com/mailman/listinfo/altusmetrum

Reply via email to