My concern with this approach is that I will still see the code "fluxuations" with that device.<br>
<br>
I did a little more testing and all my remotes have this problem...even
the RC-5 ones. It just turns out the RC-5 is much more robust.<br>
<br>
Another interesting (strange?!?) thing I noticed is that the "errors"
don't seem to be related to which keys were pressed previously...they
crop up when I change the position or orientation of the remote
control! If I move the remote around while holding a single
button down, the variations correlate with the movement. WTF?!?<br>
<br>
As such, investing in additional hardware is the last thing I really
want to do just now (although once the IR issue settles down I just
might do it). Of course, buying more hardware reduces my WAF
which I'm actively trying to raise at the moment. :-)<br>
<br>
Thanks.<br>
<br>
--<br>
Mike<br><br><div><span class="gmail_quote">On 8/28/05, <b class="gmail_sendername">Joe Votour</b> <<a href="mailto:joevph@yahoo.com">joevph@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This probably isn't what you want to hear, but going<br>RC-5 and getting a programmable remote (like the<br>OneForAll series) is one of the easiest ways to go.<br>They have advanced key mapping capabilities which will<br>
allow you to use almost every button on the remote<br>control, and the RC-5 receiver in the Hauppauge will<br>work with it. (BTW, for RC-5 in my remote, I use VCR<br>code 0081, which works with the Hauppauge card - I<br>
think that the VCR part is the key).<br><br>I don't use the Hauppauge receiver anymore myself (the<br>jack where it plugs into the card became loose), so<br>I'm using an irman again. Using RC-5 with the irman<br>is also good, because it eliminated the conflicts with
<br>my IR wireless keyboard.<br><br>You're probably using your universal remote control<br>setup as a device which uses the changes in code to<br>mean something specific to that device.<br><br>To summarize: If you're not attached to your
<br>particular remote, get an OneForAll remote (or a<br>similar Radio Shack remote), and use the button<br>programming functions to assign extended RC-5 codes to<br>the extra buttons you wish to use. It doesn't take<br>long (it only took me a couple of hours to setup), and
<br>on my URC-6131 remote control, I can use every button<br>with MythTV, except for SET and the buttons that<br>select devices.<br><br>-- Joe<br><br>--- Michael Tiller <<a href="mailto:michael.tiller@gmail.com">michael.tiller@gmail.com
</a>> wrote:<br><br>> After getting my Myth box set up, I have been on a<br>> quest to improve the WAF<br>> for my system. There have been many tweaks, but my<br>> "holy grail" has been to<br>> get all the functions (both media center + TV + ...)
<br>> on to a single<br>> universal remote. I thought my objective was within<br>> my grasp, but I've been<br>> thwarted once again and I'm hoping somebody can<br>> provide me with a solution<br>> to my latest problem.
<br>><br>> First, a bit of background. I have a PVR-150 card. I<br>> got the LIRC stuff<br>> going with the IR pickup that came with the card.<br>> But, it only works with<br>> the Hauppauge supplied remote. I know in theory I
<br>> could probably get it to<br>> work with other RC-5 remotes, but none of the codes<br>> I tried on my universal<br>> remote seemed to work.<br>><br>> I tried making my own, but the voltages weren't<br>
> right and I just didn't have<br>> the time to iterate on that thing.<br>><br>> So I bought an IRA-3 from <a href="http://www.home-electro.com">www.home-electro.com</a><br>> <<a href="http://www.home-electro.com">
http://www.home-electro.com</a>>thinking my days of<br>> screwing around were<br>> over. Sadly, I was wrong. The IRA-3<br>> uses the IRMAN protocol, BTW.<br>><br>> I hooked the thing up and tried to get it to work
<br>> with the version of LIRC<br>> already installed on my machine (0.7.1). No dice. I<br>> couldn't seem to get<br>> anything. It kept giving me an error in<br>> irman_init(). Crap. So I got the<br>> source to LIRC and tried building it. No dice, same
<br>> error. Because I could<br>> initialize the device on my Windows machine, I<br>> didn't understand what the<br>> problem was. I got the latest versions of LIRC and<br>> libirman and tried to<br>> sort things out.
<br>><br>> After a considerable amount of digging and learning<br>> far more about IRMAN,<br>> IR, LIRC and serial ports than I ever wanted to<br>> learn, I eventually managed<br>> to narrow down the problem. While the IRMAN protocol
<br>> specifies 9600 baud, 8<br>> data bits, no partity, no flow control and 1 stop<br>> bit, the port<br>> initialization fails to actually specify one stop<br>> bit (although it doesn<br>> explicitly handle all the other parameters). I added
<br>> one line to the<br>> initialization routine in libirman (to set the stop<br>> bit to 1, something it<br>> should have already been doing even according to the<br>> comments in the code)<br>> and low and behold...it worked!!! My IRA-3
<br>> initialized and I started getting<br>> data from it in the expected 6 byte chunks.<br>> Hooray!!!<br>><br>> At this point, I thought I had finally conquered<br>> this stupid issue. I<br>> rebuilt libirman and LIRC using the new
<br>> initialization code and I was well<br>> on my after running irrecord and building up a .conf<br>> file for my remote.<br>><br>> Then...disaster struck. After trying to use Myth<br>> with the new remote it
<br>> seemed like it was ignoring some of the key presses.<br>> I went back into raw<br>> mode (using test_io in libirman to output the codes)<br>> and it turns out that<br>> the stupid thing is spitting out multiple codes for
<br>> the same key. I don't<br>> mean it repeats itself (which it does, but that is a<br>> different issue). I<br>> mean it gives a different code sequence! God Damn<br>> IT!!!!<br>><br>> The problem seems to be related to the history of
<br>> key presses. As I said, a<br>> single keypress send a duplicated code but that<br>> doesn't seem to cause any<br>> problem. The real problem is when the codes change.<br>> For example, running<br>> 'test_io', these sequences are for the same key:
<br>><br>> [29][14][7d][f7][5f][ff]<br>> [29][14][7d][f7][5f][ff]<br>> [2a][e8][4e][f7][5f][3f]<br>> [2a][e8][4e][f7][5f][3f]<br>> [29][14][7d][f7][5f][ff]<br>> [29][14][7d][f7][5f][ff]<br>><br>> WTF? I find that if I hit the same key repeatedly I
<br>> pretty much get<br>> consistent codes. But, if I jump around (e.g. LEFT,<br>> RIGHT, Channel-UP, LEFT)<br>> that the same key (e.g. LEFT) will have different<br>> codes.<br>><br>> My hope is that somebody has some simple remedy
<br>> (e.g. something simple like<br>> turning on flow or changing the parity or<br>> something). By the way, the<br>> Hauppauge remote works fine. But it only send 2<br>> bytes?!?<br>><br>> Any suggestions?!? I was so close. After having
<br>> hacked may way through all<br>> this to have it fail to read remote key signals<br>> reliably is so<br>> aggravating!!!!!<br>><br>> Any help would be greatly, greatly appreciated.<br>><br>> --
<br>> Mike<br>> > _______________________________________________<br>> mythtv-users mailing list<br>> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>><br><br><br><br><br>____________________________________________________<br>Start your day with Yahoo! - make it your home page<br><a href="http://www.yahoo.com/r/hs">
http://www.yahoo.com/r/hs</a><br><br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div><br>