On Mon, Feb 13, 2012 at 10:25 PM, Keith Packard <[email protected]> wrote:
> Yeah, it's like your board doesn't have the fix installed; once we stuck > a cap across the LDO input, we couldn't cause *any* kind of voltage drop > on the 3.3V rail. > I see where the cap was added, and it looks solid. I didn't think I could solder a surface mount part to the regulator leads without going off coffee for a week. :) But if Bdale thinks it wise, I could easily tack a new cap to the pyro batt terminals. I've thought about this. I coded up bits of it a few months ago; of > course, it would require talking to the TM board over USB, which makes > it less than ideal from an electrical perspective. > Rather than the manually-triggered Raven approach, I was thinking about a dongle-initiated transition that reset the TM and replayed a hard-coded list of dummy sensor values/times into the logic -- just enough to walk through the state machine over a few seconds. That way, we'd see it fire igniters and tx without USB confusing matters. Maybe this isn't realistic, given the space constraints. Sounds really clean. Let's see if Bdale has any other suggestions on how > to test stuff; if I had the board in hand, I'd hook up a meter to the > 3.3V rail and then take a high power transmitter (like a regular HT) and > see if I could get it to drop at all by holding it near sensitive bits > of the TM. That's how we diagnosed the missing capacitor issue... > I can borrow a scope at work, and I've got a 5W HT I can key up next to it... Maybe later this week. Thanks for the thoughts, Casey
_______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
