The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


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

IR Transceiver data structure


  • To: <ukha_d@xxxxxxx>
  • Subject: IR Transceiver data structure
  • From: "Ian B" <Ian@xxxxxxx>
  • Date: Thu, 8 Aug 2002 20:15:06 +0100
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

Hi Steve

These are extracts from the header of my program. One gives you the
structure of the 15 bytes as it stands at the moment. For this to make any
sense you have to understand how I am analysing the IR signal. Here is
another extract from the program giving a little more detail.

Don't forget though that I intend to wrap all this data up in a SNAP packet
(www.hth.com). The DLL to strip this packet from my 15 bytes is available
>from is liable to change so don't go writing to much yet. I will let folks know
when things settle down. We are getting closer though I am pleased to say.

Extracts.............

; During the commentary here I am talking about 'bits' a lot. This is NOT a
bit represented in IR
; by a high and low IR pulse but a length of time that the IR pulse is
EITHER high or low for.
; Bits are represented in the data byte by a 0 or 1 to represent their
length. This has nothing
; to do with their actual value
;               --------      ----      --------      ----
;           1T    2T   1T 1T 1T    2T   1T 1T
;          ----          ----      ----          ----
; would be 01000100 where 0 is a short time period (T) and a 1 is a long one
(2T). In all the IR
; signals I have analysed the start bit has been of varying length but all
further bits can
; be represented by one of the two time periods present in the same signal.
This includes PWM
; as found in Sony etc., Space coded as in my Sanyo telly and RC5 in a lot
of Phillips kit.
; A typical signal is around 24 bits using this coding method. I have 74
available in the packet
; Byte 7 bit 1 is always an on period after the start bits. It then goes
off/on/off/on/off etc.


; Byte1      ; Command Byte. First four bits for repeat
            counter if packet inbound to PIC (bits 7-4)
; Byte1      ; Command Byte. Next two bits for number of
            start bit ON timeouts (long start bits) (bits 3 & 2)
; Byte1      ; Command Byte. Next two bits for number of
            start bit OFF timeouts (long start bits) (bits 1 & 0)
; Byte2      ; # of data bits in packet where a bit is an on or off time
; Byte3      ; Start bit ON duration
; Byte4      ; Start bit OFF duration
; Byte5      ; '0' duration
; Byte6      ; '1' duration
; Byte7      ; Data byte
; Byte8      ; Data byte
; Byte9      ; Data byte
; Byte10      ; Data byte
; Byte11      ; Data byte
; Byte12      ; Data byte
; Byte13      ; Data byte
; Byte14      ; Data byte
; Byte15      ; Data byte

Ian B



>-----Original Message-----
>From: Steve D [mailto:steve@xxxxxxx]
>Sent: 08 August 2002 14:41
>To: ukha_d@xxxxxxx >Subject: Re: [ukha_d] Re: Hv Multizone Update(IR MESSENGER)
>
>
>Ian,
>you coulsnt send me a copy of this data could you?
>I'd love to help write some PC software for logic and controlling of your
>units :)
>I will probably be one of your first customers for these units!
>----- Original Message -----
>From: "ianwbird" <Ian@xxxxxxx>
>To: <ukha_d@xxxxxxx>
>Sent: Thursday, August 08, 2002 1:47 PM
>Subject: [ukha_d] Re: Hv Multizone Update(IR MESSENGER)
>
>
>> Yep, all my versions of the PCB's etc. and the bits soldered on in
>> strange and wonderful places are all part of the prototyping stage.
>> Once I have the schematic correct then the PCB is fine, it's just the
>> bit in the middle. If you are prototyping on vero board you are a
>> better man than I. All I managed to do was short things out and get
>> very confused that way.
>>
>> Ian B
>>
>> p.s. I managed to get my IR units talking to each other last night.
>> There was simplex comms accross 485 and the IR controlled unit at the
>> other end actually did something depending on the button pressed on
>> the remote. Cool!! ;-) Just as icing on the cake I had the PC
>> evesdropping on the data using the 485 to serial converter ;-)))
>
>
>
>For more information: http://www.automatedhome.co.uk
>Post message: ukha_d@xxxxxxx >Subscribe:  ukha_d-subscribe@xxxxxxx >Unsubscribe:  ukha_d-unsubscribe@xxxxxxx >List owner:  ukha_d-owner@xxxxxxx >
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>


Yahoo! Groups Sponsor
ADVERTISEMENT

For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

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.