Randall Clague wrote: > ... required upgrade, to meet a CSFM regulatory requirement. My > bust last year for not keeping up, as RegAff, with KISS design > details...but I probably would have deferred it until now anyway, just > to get the thing flying. Having gotten it flying, we need to cross > the rest of the t's and dot the rest of the i's, to the extent that we > safely can (the requirement to fuel the rocket 100 feet from the > launch pad, for example, is stupid and dangerous for a liquid fuel > rocket). > > I thought we had discussed this?
We have indeed. I've already been looking into circuit possibilities. (Hence my prior comments on issues with circuitry...) I've been expecting to include the capability in the "next generation" avionics/recovery system (with a radio transmitter for data output and locator beacon, and possible dual deployment), which we'll need once we start increasing vehicle performance beyond the current KISS level to where "find rocket" would start becoming the slow part of our turnaround sequence. I figure we can develop the "second generation" system with HPR flights (similar to the KISS-beta runs) while we still have the "first generation" system to use for operations at current impulse levels. Retrofitting "remote disarm" into the "first generation" system could be a bit of a kluge... I'd rather keep that hardware operable as is and include the feature into the "second generation" system, than carve it up for a "retrofit". As for anyone "dropping the ball", as far as I remember the history of the situation is that we were originally planning to fly at Black Rock; I don't think the plan to fly at Mojave took concrete form until considerably later (well after the original unit had flown on KISS-beta). -dave w _______________________________________________ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
