Re: Hey, no responses (not EVEN from Jerry)

No. I was going to respond that you were making it too complicated but I held my tongue. (err, fingers) I had no idea that RMR collectively would do so as well. :-)

You don't need a deadman switch, just someone at the switch. Tell them "Push and hold until the rocket moves".

bit eimer wrote:

Does this mean my message (below) didn't make it past my own news server? >
Reply to
David Schultz
Loading thread data ...

I tried to respond, bit, but never did see what I wrote either. I'm not as anal as #&@d and didn't repost. What I had to say was basically, "it be a bad idea". That's what the count down if for. Once you reach one and say "launch", you've made a point of no return decision. Hold the button until the rocket has left the pad.

stve

Reply to
default

Mea culpa - as I realized from your response (and the two others), I did not make it clear that 1) this controller is a wireless system and 2) it includes multiple launch capability (not just clustered but also sequenced). Thus (if one reads and follows Stine's book), deadman functionality is pretty much a given.

What I was struggling with (and your post helped me crystalize - thanks) is whether to "cut short" a launch when the current to the igniter has already started flowing. This question is especially problematic for clustered launches as I already described. But I've decided that once the current starts, the launch of THAT particular unit should continue to completion, whereas any others (sequentially thereafter) would be not be permitted to start.

Reply to
bit eimer

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.