[EMAIL PROTECTED] wrote: > > Assuming we don't find a clear cause of the baro failure, would it be > possible to have one timer 'enable' the baro sensor, with the electronic > provision that if the baro sensor already says 'fire' at that time, we > ignore it and fire a second or two later? I know we can do this with > some electronic modifications, but unsure if our stock system could. > > So, assuming the simulations show a max altitude at 25 seconds, we > set the first timer (baro enabler) at 23 seconds, and the backup timer > at 27 seconds. > > Dan > > In a message dated 11/13/2 10:22:37 AM, [EMAIL PROTECTED] writes: > > << Actually, there was just the one timer (the RDAS in timed > recovery mode) - the baro altimeter was simply disabled > (didn't connect an ejection charge or install a battery). >> > > _______________________________________________ > ERPS-list mailing list > [EMAIL PROTECTED] > http://lists.erps.org/mailman/listinfo/erps-list
The current system doesn't have that functionality. (There is the possibility to set a few seconds of "lockout" delay on the altimeter, but not to set up that kind of cross-coupled conditional logic between the two units.) -dave w _______________________________________________ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
