The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: RE: Belkin Wemo


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Development] IREDS


  • To: <ukha_d@xxxxxxx>
  • Subject: RE: [Development] IREDS
  • From: "Keith Doxey" <ukha.diyha@xxxxxxx>
  • Date: Sun, 20 May 2001 19:55:40 +0100
  • Delivered-to: rich@xxxxxxx
  • Delivered-to: mailing list ukha_d@xxxxxxx
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

Not enough pins.

Only 13.

an 8 to 3 encoder wouldnt work. They are PRIORITY encoders. Once something
with a higher priority is connected the lower pins are ignored. They also
dont indicate change of state just tell you the highest priority input that
is in the Low/High state depending on the Encoder used. Also its another
chip. Better to use a PIC with more pins.

Dont use an oscillator, make the PIC do the work. Waggle the output line on
and off 38000 times per second. That way you can accomodate different
carrier frequencies on different pins and it would be programmable.

Keith

> -----Original Message-----
> From: Ian Lowe [mailto:ian@xxxxxxx]
> Sent: 20 May 2001 17:43
> To: ukha_d@xxxxxxx
> Subject: [ukha_d] [Development] IREDS
>
>
> Thats a neat idea!
>
> Would there be enough I/O Pins to do this with a 16F84 or similar?
>
> You would need one pin for the input from the local TSOP for IR RX,
three
> pins for the bits to read from an 8 bit encoder for the state of each
> channel (we could use the B port pins with Interrupt on change, to
detect
> emitters being inserted/removed whilst the unit was on), another
> three pins
> to drive the outputs, then presumably at least two pins for
> talking back to
> the upstream controller. Is there a Dallas one-wire component that
could
> help in this?
>
> Could you use a single 38Khx oscillator a-la-nigel, pipe it into
something
> like an 8-way analog switch IC, then just switch the particular line
on or
> off as requried to produce the pulses, or would you need a
> seperate version
> of Nigel's IRTX circuit for each channel?
>
> Ian.
>
>
> ----- Original Message -----
> From: "Jon Whiten" <jon@xxxxxxx>
> To: <ukha_d@xxxxxxx>
> Sent: Sunday, May 20, 2001 4:04 PM
> Subject: RE: [ukha_d] [Project] IREDS
>
>
> > How's about:-
> >
> > 7 (+ 1) Channels
> >
> > CH #1 IR LED on-board
> > CH #2 - #7 Plug-in emitters
> > CH #8 Virtual Channel for Broadcasting to all emitters at this
node.
> >
> > To keep things simple, arrange it so that the plug-in emitters
> use, say a
> > Mono 3.5mm jack plug and Stereo Skt.  Plugging in an emitter also
shorts
> > Ring-to-screen which could be used to detect "Emitter
Present" - No
> > Dip-switches to set.
> >
> > ??????
> >
> > Regards,
> >
> > Jon
> > +--------------Personal------------+----------Work-----------+
> >  Jon Whiten        Church Gresley   D.G. Controls Limited
> >                        Derbyshire  Beacon Lamp Specialists
> >  jon@xxxxxxx         England      mail@xxxxxxx
> >  http://www.whiten.co.uk/
          http://www.deegee.com
> > +----------------------------------+-------------------------+
> >
> >
> >
> > > -----Original Message-----
> > > From: Ian Lowe [mailto:ian@xxxxxxx]
> > > Sent: 20 May 2001 15:45
> > > To: ukha_d@xxxxxxx
> > > Subject: Re: [ukha_d] [Project] IREDS
> > >
> > >
> > >
> > > So, your Controller would need to be able to interrogate the
zone
> > > boxes for
> > > something like dip settings, to figure out what
channels/zones
> > > were in use,
> > > and would provide an interface onto the Ethernet.
> > >
> > >
> >
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
> >
> >
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.