From: Luc G. <llg...@en...> - 2005-09-30 13:11:05
|
Hello Vlad and other LIRC goers, I also had the same question as you, so I put together a software remote that sends the proper UDP packet to LIRC. There is one catch though, and it is that I modified the UDP driver into my own, which would accept the UDP packet with a specific code inside of it. I found that the LIRC software is exactly what it claims to be, for IR remotes. So, it was very hard to find exactly what to send to the UDP packets, so I just hard coded the functionality right into it. The other catch is that I modified one of the LIRC source code files to return a certain parameter to my UPD driver, so that needs to be compiled as well. If you are interested in getting a patch, ple>ase let me know. Thanks, Luc Gallant > Hello, > I was wondering if someone could help me with the UDP driver. My goal > is to write a simple "software remote" that emulates a real remote. > When a user clicks "send mute event" in the program, a custom UDP > packet is sent to the LIRC daemon, which recognizes the packet as a > mute button press. > In the hw_udp.c file, I learned that the UDP driver listens on port > 8765 and that: > * Received UDP packets consist of some number of LE 16-bit integers. > * The high bit signifies whether the received signal was high or low; > * the low 15 bits specify the number of 1/16384-second intervals the > * signal lasted. > I have noticed that sending UDP packets will prevent irrecord from > timing out, but none of the UDP packets I tried are registered by > irrecord as key presses. I tried 2, 4, and 8 byte packets with > varying signal high and repetitions values, with no luck. > I think I"m on the right track but I don"t know what to actually put > into the UDP packets :) > If anyone could point me into the right direction, it would be > greatly appreciated. > -Vlad ---------------------------------------- This mail sent through www.mywaterloo.ca |