Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion RC5 IR remote decoder using 12 LEDs
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
David Eather  
View profile  
 More options Nov 12 2012, 11:21 am
Newsgroups: sci.electronics.basics
From: "David Eather" <eat...@tpg.com.au>
Date: Tue, 13 Nov 2012 02:21:36 +1000
Local: Mon, Nov 12 2012 11:21 am
Subject: Re: RC5 IR remote decoder using 12 LEDs
On Mon, 12 Nov 2012 13:57:46 +1000, Bill Bowden  

<bper...@bowdenshobbycircuits.info> wrote:
> On Nov 5, 1:12 am, Jasen Betts <ja...@xnet.co.nz> wrote:

>> On 2012-11-05, Bill Bowden <bper...@bowdenshobbycircuits.info> wrote:

>> > I'm attempting to construct an IR receiver circuit capable of
>> > receiving and displaying IR signals in binary format (using LEDs) from
>> > hand held IR remote controls. The protocol I'm interested in is the
>> > RC5 format originally developed by Phillips. The format consists of 2
>> > start bits followed by a toggle bit indicating a new key is pressed,
>> > followed by 5 address bits, and then 6 command bits for a total of 14
>> > bits. I plan to display the bits using 12 LEDs. The RC5 code uses a
>> > system where each bit is one cycle of equal time where a "1" is
>> > represented by the first half cycle
>> > being low followed by the second half cycle high and visa versa for a
>> > "0". This yields a weird waveform where the end of one bit may be the
>> > same level as the beginning of the next.

>> look up manchester code, because that's what you've got.

>> > What would be the best approach to decode the data using a couple
>> > shift registers and some sort of clock to sample the data at the  
>> right time?

>> esasiest decode is probably to rely on the state changing in the
>> missle of each bit and use that change to trigger your bit clock.

> Problem is, it's hard to see the middle of the bit when the levels may
> be changing at a 1.778 mS rate, or half that at a 889uS rate depending
> if the code is all ones or zeros, or alternating ones and zeros. Some
> of the clock edges may be missing, so it's hard to synchronize a
> clock. For example a code of all ones or zeros would be a series of
> narrow pulses, while a code of alternating ones and zeros would be a
> series of wider pulses. The total number of data edges is not
> constant. I think I might figure it out using a pic processor and
> measuring the time intervals between edges, but I thought there might
> be an easy hardware solution.

> Thanks,

> -Bill

PICAXE is a *very* easy solution to this problem. It is a micrprocesor  
running a interpreted basic and can be programed using  a usb port (+  
cable) or RS232 plus 3 resistors. It has built in commands to send and  
receive  Manchester codes

  http://www.picaxe.com/BASIC-Commands/Digital-InputOutput/infraout/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.