<div class="gmail_quote">On Sat, Jul 17, 2010 at 4:24 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com" target="_blank">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>On Sat, Jul 17, 2010 at 3:25 PM, Larry K <<a href="mailto:lunchtimelarry@gmail.com" target="_blank">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" target="_blank">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" target="_blank">lunchtimelarry@gmail.com</a>> 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 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 mythtv<br>
>> packages (<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 use<br>
>> mythchanger because it produced better debug for me to understand what was<br>
>> going on when I was attempting to record over the firewire. I since 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 with<br>
> the HD-PVR builtin IR blaster, since my STB can respond to IR commands, or<br>
> should I go with a channel changing script, which I assume requires a<br>
> firewire connection?<br>
<br>
</div>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>
<div><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 can<br>
> support commands to the HD-PVR as well. For instance, the HDHR I have 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>
</div>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>
<font color="#888888"><br>
<br>
--<br>
Jarod Wilson<br>
<a href="mailto:jarod@wilsonet.com" target="_blank">jarod@wilsonet.com</a><br>
</font><div><div></div><div>_______________________________________________<br>
</div></div></blockquote></div><br><div>This is all making sense. At first, I didn't make the connection that even for IR blasting, I need a channel change script. I had made a mental association of a channel change script with a wired connection like firewire or serial. I think what may have helped throw me off track was the wiki statement that goes something like "if you don't care about channel changes, then set it to /bin/true". Seems like that would never be the case for me or anyone else, unless there is a scenario I have not considered.</div>
<div><br></div><div>As for firewire, that sounds like a solid, reliable way to change channels, but my Asus M3N78-VM MoBo doesn't have native firewire support, and I'm not wild about adding a firewire card right now. </div>
<div><br></div><div>I've been using LIRC for years with my old PVR-250 to receive my remote control commands. It runs on /dev/lirc0. For IR blasting, I'll need to add another lirc daemon, I presume. Still trying to figure out how to spawn two lirc sockets, and know which one uses the lirc_i2c driver for IR receiving with which one uses lirc_zilog driver for blasting. Not quite sure how I explicitly bind one driver to lirc0 and the other to lirc1 or whatever. I keep getting the message "irsend: hardware does not support sending", regardless of which socket I point to with the -d switch. Anyway, I think I'm pretty close now. I've followed the wiki instructions, so I have the firmware, the /etc/lircd.conf changes. </div>
<div><br></div><div>irsend LIST "" "" shows this:</div><div><br></div><div>irsend: rs15-2116-vcr0081</div><div>irsend: Hauppauge</div><div>irsend: hauppauge_pvr</div><div>irsend: Hauppauge_350</div><div>
irsend: blaster</div><div><br></div><div>So, lirc knows about the "blaster" device. </div><div><br></div><div>My system had no hardware.conf file, so I added one at /etc/lirc. I am pointing this config to lirc1 since I am already using lirc0:</div>
<div><br></div><div><div>more /etc/lirc/hardware.conf</div><div>#Chosen IR Transmitter</div><div>TRANSMITTER="HD-PVR"</div><div>TRANSMITTER_MODULES="lirc_dev lirc_zilog"</div><div>TRANSMITTER_DRIVER=""</div>
<div>TRANSMITTER_DEVICE="/dev/lirc1"</div><div>TRANSMITTER_SOCKET=""</div><div>TRANSMITTER_LIRCD_CONF=""</div><div>TRANSMITTER_LIRCD_ARGS=""</div></div><div><br></div><div>Can anyone offer up their lirc configuration, where there are two daemons, one for receiving and one for blasting to the PVR? </div>