<div>I second the JP-1 idea. You need build yourself a JP-1 cable (an old IDE cable works well) to program your remote with.</div>
<div> </div>
<div>Check out <a href="http://www.hifi-remote.com/jp1/">http://www.hifi-remote.com/jp1/</a> for more info.</div>
<div> </div>
<div>Here is what I did to get mine working with MythTV <a href="http://jason.sharonandjason.com/remote_mini_how_to.htm">http://jason.sharonandjason.com/remote_mini_how_to.htm</a></div>
<div> </div>
<div>Good luck...</div>
<div><br><br> </div>
<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="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">If you can get RC-5 working, then you can use the<br>receiver that came with your PVR-150. No extra<br>expense there. In order to get the extra buttons to
<br>work, you might need a different remote though. (But,<br>remotes can be cheap - the URC-6131 that I use is only<br>$20.)<br><br>It sounds like it's a problem with your receiver -<br>either the receiver is broken, or lirc isn't working
<br>with it.<br><br>By the way, if you want all of the buttons on your<br>remove to work, you either need to:<br>1. Find a mode where all of the buttons send IR<br>signals, and use that with your irman-like device<br>(because it won't work with the PVR-150 receiver), or
<br>2. Get a remote that supports key programming (like an<br>OneForAll remote, or something JP1 compatible) and<br>program the buttons that don't send IR codes to send<br>them.<br><br>Also, just so you know, the way I setup my irman with
<br>my universal remote (using RC-5) was to create a<br>config file with the irman tools, and then use a<br>script (I think it was included with lirc) to convert<br>the irman config file to a lirc config file. I've<br>never had much luck with irrecord.
<br><br>-- Joe<br><br>--- Michael Tiller <<a href="mailto:michael.tiller@gmail.com">michael.tiller@gmail.com</a>> wrote:<br><br>> My concern with this approach is that I will still<br>> see the code<br>> "fluxuations" with that device.
<br>><br>> I did a little more testing and all my remotes have<br>> this problem...even the<br>> RC-5 ones. It just turns out the RC-5 is much more<br>> robust.<br>><br>> Another interesting (strange?!?) thing I noticed is
<br>> that the "errors" don't<br>> seem to be related to which keys were pressed<br>> previously...they crop up when<br>> I change the position or orientation of the remote<br>> control! If I move the
<br>> remote around while holding a single button down,<br>> the variations correlate<br>> with the movement. WTF?!?<br>><br>> As such, investing in additional hardware is the<br>> last thing I really want to
<br>> do just now (although once the IR issue settles down<br>> I just might do it). Of<br>> course, buying more hardware reduces my WAF which<br>> I'm actively trying to<br>> raise at the moment. :-)<br>>
<br>> Thanks.<br>><br>> --<br>> Mike<br>><br>> On 8/28/05, Joe Votour <<a href="mailto:joevph@yahoo.com">joevph@yahoo.com</a>> wrote:<br>> ><br>> > This probably isn't what you want to hear, but
<br>> going<br>> > RC-5 and getting a programmable remote (like the<br>> > OneForAll series) is one of the easiest ways to<br>> go.<br>> > They have advanced key mapping capabilities which<br>> will
<br>> > allow you to use almost every button on the remote<br>> > control, and the RC-5 receiver in the Hauppauge<br>> will<br>> > work with it. (BTW, for RC-5 in my remote, I use<br>> 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<br>> (the<br>> > jack where it plugs into the card became loose),<br>> so<br>> > I'm using an irman again. Using RC-5 with the
<br>> irman<br>> > is also good, because it eliminated the conflicts<br>> with<br>> > my IR wireless keyboard.<br>> ><br>> > You're probably using your universal remote<br>> control<br>> > setup as a device which uses the changes in code
<br>> 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<br>> 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),<br>> and<br>> > on my URC-6131 remote control, I can use every
<br>> 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>><br>> wrote:<br>> ><br>> > > After getting my Myth box set up, I have been on<br>> a<br>> > > quest to improve the WAF<br>> > > for my system. There have been many tweaks, but
<br>> my<br>> > > "holy grail" has been to<br>> > > get all the functions (both media center + TV +<br>> ...)<br>> > > on to a single<br>> > > universal remote. I thought my objective was
<br>> 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<br>> card. I<br>> > > got the LIRC stuff<br>> > > going with the IR pickup that came with the<br>> card.<br>> > > But, it only works with
<br>> > > the Hauppauge supplied remote. I know in theory<br>> I<br>> > > could probably get it to<br>> > > work with other RC-5 remotes, but none of the<br>> 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<br>> <a href="http://www.home-electro.com">www.home-electro.com</a><<a href="http://www.home-electro.com">http://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<br>> work<br>> > > with the version of LIRC<br>> > > already installed on my machine (0.7.1). No<br>> 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,<br>> 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<br>> and<br>> > > libirman and tried to
<br>> > > sort things out.<br>> > ><br>> > > After a considerable amount of digging and<br>> 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<br>> protocol<br>> > > specifies 9600 baud, 8<br>> > > data bits, no partity, no flow control and 1
<br>> stop<br>> > > bit, the port<br>> > > initialization fails to actually specify one<br>> stop<br>> > > bit (although it doesn<br>> > > explicitly handle all the other parameters). I
<br>> added<br>> > > one line to the<br>> > > initialization routine in libirman (to set the<br>> stop<br>> > > bit to 1, something it<br>> > > should have already been doing even according to
<br>> 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<br>> .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<br>> presses.<br>> > > I went back into raw<br>> > > mode (using test_io in libirman to output the<br>> codes)<br>> > > and it turns out that
<br>> > > the stupid thing is spitting out multiple codes<br>> for<br>> > > the same key. I don't<br>> > > mean it repeats itself (which it does, but that<br>> is a<br>> > > different issue). I
<br>> > > mean it gives a different code sequence! God<br>> Damn<br>> > > IT!!!!<br>> > ><br>> > > The problem seems to be related to the history<br>> 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>><br>=== message truncated ===><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>Do You Yahoo!?<br>Tired of spam? Yahoo! Mail has the best spam protection around<br><a href="http://mail.yahoo.com">http://mail.yahoo.com</a><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>