Re: Launch controller work-in-porgress

bit: whats the range? I want one but for only one pad..... can you interface a strobe light and or loud small beeper for a pad unit.....to warn people its getting ready to go off? You going to publish the schematic at some future point?

shockie B)

Pad unit will likely have both a strobe and a speaker, as they are planned for. I haven't yet done the schematics for those two little circuits, but not a big deal. Control unit will also have a speaker.

This design is about a factor of 7992x overkill for what you want - even the minimum configuration is for 8 pads. Actually, the reason I started this is that I wanted a good cluster launcher, one that could independently test all igniters for continuity and shorts. So if you were to do clustering or drag-racing, the min config might still be appropriate.

Range is unknown as of yet. So much depends on antenna selection, location on the box, etc. Will just have to wait for field testing.

As to schematic publishing, I will consider. I still haven't written any code for the PICs yet, so this project is likely several months from completion (especially given that I've got 2-3 trips planned for the near-midterm)

BTW, 2nd half of second line under "Control Unit Features" should read just "Keyed lock-out switch"

So did you use a LINX TX / RX module? I built a hybrid launch controller, in the near turm I installed a cable between the lauch controller and pad box. It worked great last weekend when I fired my Hypertek hybrid from it. It is PIC based 16F628, with built in UART.

Yes, Linx TX/RX; I have a back-up RS232 link designed (and built) in, but mostly to support debug during code dev. Don't want to have to worry about the RF channel reliability at that time. This also allows me to emulate the Pad Unit with the PC while debugging the Control Unit and vice versa.

Using 16F877s -20MHz (but only 'cause I don't know yet what performance I actually need).