Comments on: Infrared remote control receiver for Arduino

By: admin

admin — Fri, 19 Feb 2010 09:21:19 +0000

Thanks for sharing, Tom.
I’m Happy this could help.
Best regards
A.

By: tom

tom — Thu, 18 Feb 2010 16:57:21 +0000

THANKS! I’ve been smashing my head against a desk for 3 days trying to get an ATTiny13 to understand any remote codes at all, I’ve modified this one to work!

Again thanks!

By: admin

admin — Wed, 17 Feb 2010 13:24:40 +0000

You’re welcome. Thanks for sharing !
Best regards
A.

By: Veli

Veli — Sun, 14 Feb 2010 20:26:25 +0000

As a beginner I spent a lot of time with the rc5 stack from mikrocontroller.net triying to get it to work as an arduino sketch for a “quick” testing the TSOP4138 on Arduino Diecimila
With your script, at first no LED went on, no serial output, “It cannot be that easy”, I thought, the highlight came with the oldest of my three remote controls (for some generic TV). It works! Thanks a lot.

By: admin

admin — Sun, 14 Feb 2010 18:57:55 +0000

The IR receiver should be fine: to the datasheet your receiver is active low, not high. I mean : when 38kHz IR is received the output goes low. The same logic applies to the IR receivers I tried.
Please read the comments and check if any of them helps you, otherwise please return. At this stage I can’ t help.
Best regards

By: on4tux

on4tux — Sat, 13 Feb 2010 17:11:59 +0000

I’m a real newbie (got my board yesterday ) but already playing with RC5 on my mega board. The code is not working, but I’m not sure if it is due to my IR controller (IRM38bl) which is active high? Only if it receives IR, the pulses make it go low.

By: admin

admin — Sun, 24 Jan 2010 16:20:15 +0000

Mark,
Ah, great find ! I’m adding a few lines in the post. I’m not correcting the pde though because I can’t test it now. Still have to understand how it could work on my STK500-Arduino or work for a few interrupts on other reader’s platforms and the Arduino DK compile it regularly.
Again thank you a lot for sharing
A presto (talk to you soon)
Alessandro

By: Mark Arduino

Mark Arduino — Sun, 24 Jan 2010 12:06:37 +0000

Hi Alessandro,

Thanks for replying.
Been doing a little more digging and it seems that this may be a porting issue between the ATtiny24 and the ATmega168/328.

For the ATmega168/328, the timer compare vector is defined as “TIMER0_COMPA_vect” and not “TIM0_COMPA_vect”.

When an interrupt is received and no ISR can be found, the device will reset. I think this explains some of the issues others such as CaviaR and Matt Baker have been seeing.

Mark.

By: admin

admin — Sun, 24 Jan 2010 10:47:51 +0000

Ciao Mark,
great to know you solved the problem, thanks for sharing your solution also !
Your assumption at 1) is correct except that – I’m going by heart here – I’m masking the toggle bit which could be 1 or 0.
You are right also at 2). Just wanted to be the one to decide where and what should loop forever….
Best regards
Alessandro

By: Mark Arduino

Mark Arduino — Sat, 23 Jan 2010 20:31:01 +0000

Hi,

Thanks for all the replies.
I have figured out that the problem with the Arduino resetting is that instead of the “TIM0_COMPA_vect” ISR running when the timer match occurs the device was restetting – not sure why yet.

Adding the following line to the top of the code solves the problem :-

ISR_ALIAS(_vector_default, TIM0_COMPA_vect);

A few questions :-

1) Once you have 14 bits – why are you testing the data-word against 0×37C0? Is this to ensure that only RCU’s with address 0 will work? Why are you also masking the top bit of the command code?

2) why do you have the “for(;;)” in the main loop – “loop” is called continually – so do you really need this?

Mark.