AeroElectric-List Digest Archive

Fri 12/15/06


Total Messages Posted: 3



Today's Message Index:
----------------------
 
     1. 08:14 AM - Re: Heat shrink labelling (Joe & Jan Connell)
     2. 07:39 PM - Re: Annunciator Panel Update? (Alan K. Adamson)
     3. 08:37 PM - Re: Annunciator Panel Update? (Doug Windhorn)
 
 
 


Message 1


  • INDEX
  • Back to Main INDEX
  • NEXT
  • Skip to NEXT Message
  • LIST
  • Reply to LIST Regarding this Message
  • SENDER
  • Reply to SENDER Regarding this Message
    Time: 08:14:20 AM PST US
    From: "Joe & Jan Connell" <jconnell@rconnect.com>
    Subject: Heat shrink labelling
    I used Microsoft Word to print all my labels using a 6 pitch font. Rather than a numbering scheme, I used full text describing the wire. Examples below: (3) DYNON D10A GROUND (1) DYNON D10A TO ESSENTIAL BUSS 12V + (2) DYNON D10A KEEP ALIVE POWER With this format I know the pin number, the purpose, and the destination. I cut the label, lay it on the wire, slide a piece of heat shrink over the two, and heat briefly. For hard-to- read locations I use two labels (one reversed.) It's a bit time consuming but works well... Joe Connell RV-9A N95JJ


    Message 2


  • INDEX
  • Back to Main INDEX
  • PREVIOUS
  • Skip to PREVIOUS Message
  • NEXT
  • Skip to NEXT Message
  • LIST
  • Reply to LIST Regarding this Message
  • SENDER
  • Reply to SENDER Regarding this Message
    Time: 07:39:30 PM PST US
    From: "Alan K. Adamson" <aadamson@highrf.com>
    Subject: Annunciator Panel Update?
    Ok, I've been doing a bit more thinking about this widget.... I'm really trying to avoid designing the kitchen sink into it, and also I don't want the complexity of multiple modules that all have to be interfaced. I'm applying the KISS principle if at all possible. I've nailed down a feature list a bit further. This is just major features and is broken out by Hardware, and Hardware/Software. I've also included a "future additions" section to keep those in perspective. *If* we were to do a little virtual design here. Maybe we could nail down a final V1 feature set, work up a prospective component list. From there we could scratch out a schematic and then obviously, we could get some prototypes done and build a couple and see how they work. Single sided, or at the most double sided would be preferred. Concerns that we'll have to watch for is RFI/EMI and how to keep that to a minimum. Hardening this device should not be in the cards just yet, unless that can be done easily. At this point, we should work to a prototype. Ok, so here's my feature list. Feel free to comment on it and if there are questions, let me know. One note, this should be designed to work in both metal and composite airplanes (that means we'll have to make sure grounding is available and adequate. Since the original round, I did think of a couple of nice to haves. Rick's ideas muting and was a good one, that lead me to thing about priorities and overrides. These can be handled in software. Dimming was another good idea and the inclusion of some PWM for driving led's etc. (we'll really have to watch EMI/RFI from those!) This should be designed with PC tools that the average joe can afford if we are to work in a collaborative environment with and around this. So, what do ya think? Hardware a) 8 control inputs (can be active hi, active lo, or strobed) b) 8 control outputs (can be active hi, active lo, or strobed) c) microprocessor control d) flash memory (perhaps processor embedded) e) serial port output (output strings for external usage - e.g. Engine monitor display, EFIS display, etc) f) serial port input (command processor for configuration, s/w upload, etc) g) 8 low level audio inputs h) 3 low level audio outputs i) audio tone generator j) 9-32v DC power supply Hardware/Software a) test circuitry (lights, processor, logic, etc) b) smart mute circuitry (mute until remedy, then re-arm, etc) c) smart dimming circuitry (PWM for LEDs, ambient light sensor, for auto adjust, etc) d) event priorities for both control outputs and audio outputs (can be linked or combined via configuration) e) queued events with queue clearing logic (would need to integrate with event priorities) Future additions a) recorded or recordable voice messages in place of tone generated sounds b) ethernet or some other form of faster interface technology Obviously, the number of inputs and outputs (gazintas and gazoutas) are arbitrary, but 8 is a nice micro number :) Alan - wanna be designer at large ;> -----Original Message----- From: owner-aeroelectric-list-server@matronics.com [mailto:owner-aeroelectric-list-server@matronics.com] On Behalf Of rtitsworth Sent: Thursday, December 14, 2006 4:24 PM Subject: RE: AeroElectric-List: Annunciator Panel Update? --> <rtitsworth@mindspring.com> Alan, It would also be nice if the audio output could be manually muted (i.e. until the input conditions was fixed at which point it would auto re-arm) unless/until another input generated a second warning which would trigger a subsequent audio signal. This is better than shutting off the audio as you could forget to turn it back on/up. It would also be nice to have the visual intensity dimmable (perhaps external to the board) as it would be nice to have the annunciations "very" bright during the day, but not blinding at night. If it were LED based, it would be nice to be able to configure/switch the LED colors (red, yellow, green, etc) during assembly. Some thoughts on the test function/circuit... 1) It could be designed to only test the lights by suppling power directly to the lights (bypassing the processor) - simple and software independent but a rather weak "test". 2) It could be designed into the processor/code (ie. a manually activated "all on" mode). 3) It could be designed to be a circuit "in-front" of the processor (i.e. pulling all selected inputs high or low - thereby testing the processor/coding as well) which is the most complex. If option #2 (above) it might be nice if the "test" were automatically performed at startup such that all the lights would initially come on automatically and then hitting the test (or mute) button would extinguish them. Thereafter, you would hold the momentary "test" button to test again. Perhaps "holding" the mute button (>1 sec) would function as the test button (saving a button). Of course, following a "test" event, any prior illuminated warnings should still be illuminated. .02 Rick -----Original Message----- From: owner-aeroelectric-list-server@matronics.com [mailto:owner-aeroelectric-list-server@matronics.com] On Behalf Of Alan K. Adamson Sent: Thursday, December 14, 2006 12:27 PM Subject: RE: AeroElectric-List: Annunciator Panel Update? <aadamson@highrf.com> Well, I'll throw my hat in the ring as at least a paper designer. I've been toying with a simple microprocessor based application that could take either active hi, or active low, and maybe alternating types of inputs. It could then generate either active hi, or active low, or flashing outputs, along with an associated audio notification event. This would all be configurable from a simple serial port based device and some windows or other software. It would obviously support a "test" mode and would be configurable for audio volume. Second generation would allow recorded voice instead of simple tones. Most likely, I'd center it around low power incandescent or LED annunciation lights. Because IO on micros *isnt* unlimited, perhaps looking at 8 gazintas, and 8 gazoutas as a start. Power would be 9-32v and regulated on the board. I'd look for something the size of a pack of gum or maybe just a smidge large to stay in thru hole parts and allow it to be available in Kit form. Would there be much interest in the above? I'm most likely going to do the Honeywell type lights, which are LED based and has been what is driving my desire for the above. Alan -----Original Message----- From: owner-aeroelectric-list-server@matronics.com [mailto:owner-aeroelectric-list-server@matronics.com] On Behalf Of Robert L. Nuckolls, III Sent: Thursday, December 14, 2006 9:49 AM Subject: Re: AeroElectric-List: Annunciator Panel Update? --> <nuckollsr@cox.net> At 05:30 PM 12/13/2006 -0800, you wrote: ><bob.condrey@baesystems.com> > >Anybody got an update on the potential annunciator panel that was being >discussed several months ago? > >Thanks > >Bob That topic was one of several being massaged around plates of tacos at the el Mexico cafe but it seems to have died out. None of the pepper-heads present has demonstrated an interest in stepping up to the project. Bob . . . --------------------------------------------------------- < What is so wonderful about scientific truth...is that > < the authority which determines whether there can be > < debate or not does not reside in some fraternity of > < scientists; nor is it divine. The authority rests > < with experiment. > < --Lawrence M. Krauss > ---------------------------------------------------------


    Message 3


  • INDEX
  • Back to Main INDEX
  • PREVIOUS
  • Skip to PREVIOUS Message
  • NEXT
  • Skip to NEXT Message
  • LIST
  • Reply to LIST Regarding this Message
  • SENDER
  • Reply to SENDER Regarding this Message
    Time: 08:37:46 PM PST US
    From: "Doug Windhorn" <N1DeltaWhiskey@comcast.net>
    Subject: Re: Annunciator Panel Update?
    Alan, Thanks for looking into this a bit further. I have been trying to locate a row of enunciators to let me know when some defined parameter is out of normal/desired ranges (row of idiot lights if you will, with some additional features such as audio alert via the headphones. After reading over your list, not sure how KISS your proposal is, but will leave that conversation to those that might have a better idea of what they are talking about. I am not sure what all the "features" do, or are supposed to do, or how I would use them. I am wondering, though, if dimming wouldn't be better performed by simple light sensitive resistive circuitry (could be paralleled with user adjustable) rather than PWM. I am assuming that the enunciator panel is for the purpose of displaying fault/attention needed events and would not be lit continuously (not sure what I would want continuously lit on such a panel). If true, then it is doubtful that any meaningful power savings could be had by going to the complication of PWM. Just some thoughts. Hope you can produce a well engineered design/product (e.g., competitive costs are factored in). Regards, Doug Windhorn ----- Original Message ----- From: "Alan K. Adamson" <aadamson@highrf.com> Sent: Friday, 15 December, 2006 19:36 Subject: RE: AeroElectric-List: Annunciator Panel Update? > <aadamson@highrf.com> > > Ok, I've been doing a bit more thinking about this widget.... I'm really > trying to avoid designing the kitchen sink into it, and also I don't want > the complexity of multiple modules that all have to be interfaced. > > I'm applying the KISS principle if at all possible. > > I've nailed down a feature list a bit further. This is just major > features > and is broken out by Hardware, and Hardware/Software. I've also included > a > "future additions" section to keep those in perspective. > > *If* we were to do a little virtual design here. Maybe we could nail down > a > final V1 feature set, work up a prospective component list. From there we > could scratch out a schematic and then obviously, we could get some > prototypes done and build a couple and see how they work. > > Single sided, or at the most double sided would be preferred. Concerns > that > we'll have to watch for is RFI/EMI and how to keep that to a minimum. > Hardening this device should not be in the cards just yet, unless that can > be done easily. > > At this point, we should work to a prototype. > > Ok, so here's my feature list. Feel free to comment on it and if there > are > questions, let me know. One note, this should be designed to work in both > metal and composite airplanes (that means we'll have to make sure > grounding > is available and adequate. > > Since the original round, I did think of a couple of nice to haves. > > Rick's ideas muting and was a good one, that lead me to thing about > priorities and overrides. These can be handled in software. > > Dimming was another good idea and the inclusion of some PWM for driving > led's etc. (we'll really have to watch EMI/RFI from those!) > > This should be designed with PC tools that the average joe can afford if > we > are to work in a collaborative environment with and around this. > > So, what do ya think? > > Hardware > a) 8 control inputs (can be active hi, active lo, or strobed) > b) 8 control outputs (can be active hi, active lo, or strobed) > c) microprocessor control > d) flash memory (perhaps processor embedded) > e) serial port output (output strings for external usage - e.g. Engine > monitor display, EFIS display, etc) > f) serial port input (command processor for configuration, s/w upload, > etc) > g) 8 low level audio inputs > h) 3 low level audio outputs > i) audio tone generator > j) 9-32v DC power supply > > Hardware/Software > a) test circuitry (lights, processor, logic, etc) > b) smart mute circuitry (mute until remedy, then re-arm, etc) > c) smart dimming circuitry (PWM for LEDs, ambient light sensor, for auto > adjust, etc) > d) event priorities for both control outputs and audio outputs (can be > linked or combined via configuration) > e) queued events with queue clearing logic (would need to integrate with > event priorities) > > > Future additions > a) recorded or recordable voice messages in place of tone generated sounds > b) ethernet or some other form of faster interface technology > > Obviously, the number of inputs and outputs (gazintas and gazoutas) are > arbitrary, but 8 is a nice micro number :) > > Alan - wanna be designer at large ;> > > -----Original Message----- > From: owner-aeroelectric-list-server@matronics.com > [mailto:owner-aeroelectric-list-server@matronics.com] On Behalf Of > rtitsworth > Sent: Thursday, December 14, 2006 4:24 PM > To: aeroelectric-list@matronics.com > Subject: RE: AeroElectric-List: Annunciator Panel Update? > > --> <rtitsworth@mindspring.com> > > Alan, > > It would also be nice if the audio output could be manually muted (i.e. > until the input conditions was fixed at which point it would auto re-arm) > unless/until another input generated a second warning which would trigger > a > subsequent audio signal. This is better than shutting off the audio as > you > could forget to turn it back on/up. > > It would also be nice to have the visual intensity dimmable (perhaps > external to the board) as it would be nice to have the annunciations > "very" > bright during the day, but not blinding at night. > > If it were LED based, it would be nice to be able to configure/switch the > LED colors (red, yellow, green, etc) during assembly. > > Some thoughts on the test function/circuit... > 1) It could be designed to only test the lights by suppling power directly > to the lights (bypassing the processor) - simple and software independent > but a rather weak "test". > 2) It could be designed into the processor/code (ie. a manually activated > "all on" mode). > 3) It could be designed to be a circuit "in-front" of the processor (i.e. > pulling all selected inputs high or low - thereby testing the > processor/coding as well) which is the most complex. > > If option #2 (above) it might be nice if the "test" were automatically > performed at startup such that all the lights would initially come on > automatically and then hitting the test (or mute) button would extinguish > them. Thereafter, you would hold the momentary "test" button to test > again. > Perhaps "holding" the mute button (>1 sec) would function as the test > button > (saving a button). > > Of course, following a "test" event, any prior illuminated warnings should > still be illuminated. > > .02 > Rick > > > -----Original Message----- > From: owner-aeroelectric-list-server@matronics.com > [mailto:owner-aeroelectric-list-server@matronics.com] On Behalf Of Alan K. > Adamson > Sent: Thursday, December 14, 2006 12:27 PM > To: aeroelectric-list@matronics.com > Subject: RE: AeroElectric-List: Annunciator Panel Update? > > <aadamson@highrf.com> > > Well, I'll throw my hat in the ring as at least a paper designer. > > I've been toying with a simple microprocessor based application that could > take either active hi, or active low, and maybe alternating types of > inputs. > It could then generate either active hi, or active low, or flashing > outputs, > along with an associated audio notification event. This would all be > configurable from a simple serial port based device and some windows or > other software. It would obviously support a "test" mode and would be > configurable for audio volume. Second generation would allow recorded > voice > instead of simple tones. Most likely, I'd center it around low power > incandescent or LED annunciation lights. > > Because IO on micros *isnt* unlimited, perhaps looking at 8 gazintas, and > 8 > gazoutas as a start. Power would be 9-32v and regulated on the board. > I'd > look for something the size of a pack of gum or maybe just a smidge large > to > stay in thru hole parts and allow it to be available in Kit form. > > Would there be much interest in the above? I'm most likely going to do > the > Honeywell type lights, which are LED based and has been what is driving my > desire for the above. > > Alan > > -----Original Message----- > From: owner-aeroelectric-list-server@matronics.com > [mailto:owner-aeroelectric-list-server@matronics.com] On Behalf Of Robert > L. > Nuckolls, III > Sent: Thursday, December 14, 2006 9:49 AM > To: aeroelectric-list@matronics.com > Subject: Re: AeroElectric-List: Annunciator Panel Update? > > --> <nuckollsr@cox.net> > > At 05:30 PM 12/13/2006 -0800, you wrote: > >><bob.condrey@baesystems.com> >> >>Anybody got an update on the potential annunciator panel that was being >>discussed several months ago? >> >>Thanks >> >>Bob > > That topic was one of several being massaged around > plates of tacos at the el Mexico cafe but it seems > to have died out. None of the pepper-heads present > has demonstrated an interest in stepping up to the > project. > > Bob . . . > > --------------------------------------------------------- > < What is so wonderful about scientific truth...is that > > < the authority which determines whether there can be > > < debate or not does not reside in some fraternity of > > < scientists; nor is it divine. The authority rests > > < with experiment. > > < --Lawrence M. Krauss > > --------------------------------------------------------- > > >




    Other Matronics Email List Services

  • Post A New Message
  •   aeroelectric-list@matronics.com
  • UN/SUBSCRIBE
  •   http://www.matronics.com/subscription
  • List FAQ
  •   http://www.matronics.com/FAQ/AeroElectric-List.htm
  • Web Forum Interface To Lists
  •   http://forums.matronics.com
  • Matronics List Wiki
  •   http://wiki.matronics.com
  • 7-Day List Browse
  •   http://www.matronics.com/browse/aeroelectric-list
  • Browse AeroElectric-List Digests
  •   http://www.matronics.com/digest/aeroelectric-list
  • Browse Other Lists
  •   http://www.matronics.com/browse
  • Live Online Chat!
  •   http://www.matronics.com/chat
  • Archive Downloading
  •   http://www.matronics.com/archives
  • Photo Share
  •   http://www.matronics.com/photoshare
  • Other Email Lists
  •   http://www.matronics.com/emaillists
  • Contributions
  •   http://www.matronics.com/contribution

    These Email List Services are sponsored solely by Matronics and through the generous Contributions of its members.

    -- Please support this service by making your Contribution today! --