Re: ir receiver and transmitter[UPDATE]

[Neil on L. <nei...@re...>]

Ok guys, 

here is what I did. I modified /etc/lircd.conf so the name directive is set 
to mitsubishi. I also added frequency 38000. 

I restarted lircd --device=/dev/lirc0 

I executed this command while looking at my digital camera:
irsend send_once mitsubishi one one one 

I saw the infrared lit up. For me, that was already a nice test. 

I shutdowned my linux box and brought it over near the Mitsubishi set. I 
connected my homebrew ir transmitter to com1. I cleaned up my serial using 

setserial /dev/ttyS0 uart none
depmod -a
modprobe lirc_serial 

Now, when I run the last line, I'm getting a message "Badness on 
sleep_on_timeout in kernel/sched.c 

But when i lsmod it, I can see the module get loaded. 

I remove the ir transmitter again, and connect my receiver and rmmod it and 
modprobe it again. I still see the Badness.......I fired up lircd 
 --device=/dev/lirc0 to check if ir receiver will work since I saw those 
messages. I ran mode2 and I saw the scrolling pulses. 

Anyways, when I was running modprobe lirc_serial before, the screen was 
clean. Do you have any idea what happened? 

And lastly, the real point of my email. How come, I am not able to change 
the channel using this command: 

irsend send_once mitsubishi channelup 

in /var/log/messages, it says, new client found and on the next line, client 
removed. Something like this.... 

Any help will be appreciated. 

Thanks, 

Neil 


Neil on Lirc writes: 

> hey guys,  
> 
> just finished building my ir receiver and ir transmitter. I also built FC3 
> last night. So far, my ir receiver has been working great. I have used 
> mode2 and xmode2 and all 5 different remote controls at home are working.  
> 
> Now, is the recorded data via irrecord enough to be used by my ir 
> transmitter to send signals to my devices such as satellite receiver(DISH 
> Network)? How should I use irsend using those recorded signals/pulses? Is 
> there a need to modify the .conf file?  
> 
> Please let me know.  
> 
> Thanks,  
> 
> Neil 
>