<div class="gmail_quote">On Sun, Jul 18, 2010 at 10:10 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Sun, Jul 18, 2010 at 9:53 AM, Larry K <<a href="mailto:lunchtimelarry@gmail.com">lunchtimelarry@gmail.com</a>> wrote:<br>
> On Sat, Jul 17, 2010 at 4:24 PM, Jarod Wilson <<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>> wrote:<br>
>><br>
>> On Sat, Jul 17, 2010 at 3:25 PM, Larry K <<a href="mailto:lunchtimelarry@gmail.com">lunchtimelarry@gmail.com</a>> wrote:<br>
>> > On Sat, Jul 17, 2010 at 11:22 AM, Kenneth Emerson<br>
>> > <<a href="mailto:kenneth.emerson@gmail.com">kenneth.emerson@gmail.com</a>> wrote:<br>
>> >><br>
>> >><br>
>> >> On Sat, Jul 17, 2010 at 7:50 AM, Larry K <<a href="mailto:lunchtimelarry@gmail.com">lunchtimelarry@gmail.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> Since Comcast hosed pretty much all my unencrypted QAM (except the<br>
>> >>> networks, of course), I just picked up an HD-PVR, another STB, and<br>
>> >>> have been<br>
>> >>> reading through all the materials I can find.<br>
>> >>> On this wiki -> <a href="http://www.mythtv.org/wiki/Hauppauge_HD-PVR" target="_blank">http://www.mythtv.org/wiki/Hauppauge_HD-PVR</a><br>
>> >>><br>
>> >>> Larry:<br>
>> >><br>
>> >> A lot depends on what STB Comcast gave you.<br>
>> ><br>
>> > I have the Motorola DCX3200 HD box. It comes with an IR remote.<br>
>> ><br>
>> >><br>
>> >> People on this list seem to have had good luck using firewire to change<br>
>> >> channels on STB's (as do I). If your STB has a firewire port AND it is<br>
>> >> enabled I'd suggest you look at 6200ch which AFAIK is included in the<br>
>> >> mythtv<br>
>> >> packages<br>
>> >> (<a href="https://help.ubuntu.com/community/MythTV_External_Channel_Changer" target="_blank">https://help.ubuntu.com/community/MythTV_External_Channel_Changer</a>)<br>
>> >> or try mythchanger (<a href="https://wiki.ubuntu.com/majoridiot" target="_blank">https://wiki.ubuntu.com/majoridiot</a>). Personally I<br>
>> >> use<br>
>> >> mythchanger because it produced better debug for me to understand what<br>
>> >> was<br>
>> >> going on when I was attempting to record over the firewire. I since<br>
>> >> gave up<br>
>> >> that goal and purchased an HDPVR, as you did.<br>
>> ><br>
>> > I guess my question is, given my STB, should I pursue channel changing<br>
>> > with<br>
>> > the HD-PVR builtin IR blaster, since my STB can respond to IR commands,<br>
>> > or<br>
>> > should I go with a channel changing script, which I assume requires a<br>
>> > firewire connection?<br>
>><br>
>> No. Channel change scripts are just scripts you point mythtv-setup at.<br>
>> Its pretty much completely arbitrary what you put inside them. But<br>
>> generally speaking, you're going to put calls to another program in<br>
>> there, such as irsend, to do IR blasting, calls to 6200ch or<br>
>> mythchanger or whatever to send AVC commands over firewire, etc.<br>
>><br>
>> > It's not clear to me if the myth - HD-PVR USB<br>
>> > connection is just to receive content, or if that is bi-directional and<br>
>> > can<br>
>> > support commands to the HD-PVR as well. For instance, the HDHR I have<br>
>> > uses<br>
>> > the Ethernet connection bidirectionally, both to receive channel change<br>
>> > commands, and to dump content back on the wire for myth to pick up.<br>
>><br>
>> Well, the usb connection to the hd-pvr is what's used to send<br>
>> instructions to the zilog z8 chip on the hd-pvr, which in turn acts<br>
>> upon those instructions to send the appropriate raw IR signals out the<br>
>> blaster port. But you need lirc_zilog binding to the thing first.<br>
>><br>
</div></div><div class="im">>> _______________________________________________<br>
><br>
> This is all making sense. At first, I didn't make the connection that even<br>
> for IR blasting, I need a channel change script. I had made a mental<br>
> association of a channel change script with a wired connection like firewire<br>
> or serial. I think what may have helped throw me off track was the wiki<br>
> statement that goes something like "if you don't care about channel changes,<br>
> then set it to /bin/true". Seems like that would never be the case for me<br>
> or anyone else, unless there is a scenario I have not considered.<br>
> As for firewire, that sounds like a solid, reliable way to change channels,<br>
> but my Asus M3N78-VM MoBo doesn't have native firewire support, and I'm not<br>
> wild about adding a firewire card right now.<br>
> I've been using LIRC for years with my old PVR-250 to receive my remote<br>
> control commands. It runs on /dev/lirc0. For IR blasting, I'll need to add<br>
> another lirc daemon, I presume. Still trying to figure out how to spawn two<br>
> lirc sockets, and know which one uses the lirc_i2c driver for IR receiving<br>
> with which one uses lirc_zilog driver for blasting. Not quite sure how I<br>
> explicitly bind one driver to lirc0 and the other to lirc1 or whatever.<br>
<br>
</div>There's no particularly good way to do so, other than loading the<br>
drivers manually (or by script) in the desired order.<br>
<div class="im"><br>
> I<br>
> keep getting the message "irsend: hardware does not support sending",<br>
> regardless of which socket I point to with the -d switch. Anyway, I think<br>
> I'm pretty close now. I've followed the wiki instructions, so I have the<br>
> firmware, the /etc/lircd.conf changes.<br>
> irsend LIST "" "" shows this:<br>
> irsend: rs15-2116-vcr0081<br>
> irsend: Hauppauge<br>
> irsend: hauppauge_pvr<br>
> irsend: Hauppauge_350<br>
> irsend: blaster<br>
> So, lirc knows about the "blaster" device.<br>
> My system had no hardware.conf file, so I added one at /etc/lirc.<br>
<br>
</div>Well, hardware.conf is a debian and ubuntu thing, it gets consulted by<br>
the debian/ubuntu lirc initscript. If you're running a different<br>
distribution, adding that file isn't going to do a thing. Fedora has<br>
similar-ish functionality provided by /etc/sysconfig/lirc, but has no<br>
automagic (and utterly broken in way too many cases) secondary lircd<br>
instance support at this time. Not sure what exactly you're running<br>
though.<br>
<br></blockquote><div>Jarod, I'm running FC12: </div><div><br></div><div>2.6.32.14-127.fc12.i686 #1 SMP Fri May 28 05:04:10 UTC 2010 i686 athlon i386 GNU/Linux</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
One thought: why use both lirc_i2c and lirc_zilog, why not load *only*<br>
lirc_zilog, since its got receiver support too? Should support all of<br>
the mentioned remotes just fine, and save the complication of running<br>
a second lircd.<br></blockquote><div><br></div><div>Good to know. I've been running lirc_i2c for years, and didn't realize that lirc_zilog alone is enough. I just figured one lircd instance for IR in, and another for IR out. I'll ditch lirc_i2c and see what I can get with one lircd instance. BTW, when I modprobe lirc_zilog debug=1, I think I am supposed to see something like this, as was pasted by another user somewhere:</div>
<div><div><br></div><div><span style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12px; border-collapse: collapse; line-height: 17px; ">lirc_zilog: ivtv i2c driver #0: no devices found<br>lirc_zilog: chip found with RX and TX<br>
lirc_dev: lirc_register_driver: sample_rate: 0<br>firmware: requesting haup-ir-blaster.bin<br>lirc_zilog: firmware of size 258140 loaded<br>lirc_zilog: 654 codesets loaded<br>lirc_zilog: Zilog/Hauppauge IR blaster: firmware version 2.1.0</span><br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
</blockquote></div><br></div><div>But I don't anything near that verbose. All I get is this:</div><div><br></div><div><div>lirc_zilog: Zilog/Hauppauge IR driver initializing</div><div>lirc_zilog: initialization complete</div>
</div><div><br></div><div>Makes me wonder if something is amiss since I see no mention of the firmware in my debug messages.</div><div><br></div><div>Thanks for the reply. Your help is much appreciated. :) </div></div><div>
<br></div></div>