<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jun 25, 2014 at 12:45 PM, Hika van den Hoven <span dir="ltr"><<a href="mailto:hikavdh@gmail.com" target="_blank">hikavdh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hoi Jon,<br>
<div class=""><br>
Wednesday, June 25, 2014, 7:25:29 PM, you wrote:<br>
<br>
</div><div><div class="h5">> On Wed, Jun 25, 2014 at 11:41 AM, Hika van den Hoven <<a href="mailto:hikavdh@gmail.com">hikavdh@gmail.com</a>>wrote:<br>
<br>
> Hoi Jon,<br>
><br>
<br>
> Wednesday, June 25, 2014, 5:59:07 PM, you wrote:<br>
><br>
>> Hey,<br>
><br>
><br>
><br>
>> I have 2 HD-PVRs and yesterday decided to move the one that has<br>
>> been on slave backend to my master backend that has a HD-PVR<br>
>> already. I can get everything to work but can only seem to get one<br>
>> blaster to work at a time. I end up with.<br>
>><br>
>> [ 377.424068] lirc_zilog: i2c_master_send failed with -5<br>
>> [ 377.424084] lirc_zilog: sending to the IR transmitter chip failed, trying reset<br>
>> [ 378.082019] lirc_zilog: Zilog/Hauppauge IR blaster firmware version 2.1.0 loaded<br>
>><br>
>> Has anyone ran into this or have a successful 2 blaster setup they can share?<br>
><br>
>> Thanks,<br>
><br>
>> Jon<br>
><br>
><br>
<br>
> Basically you have to run two separate instances of lircd under a<br>
> different name. So you have to copy your lircd configuration and start<br>
> script to for instance lircd1 and adjust this configuration to the<br>
> second blaster.<br>
> Do you get two lirc instances in /dev/ or /dev/input ?<br>
<br>
> I do get 2 /dev/lirc instances.<br>
<br>
> I've tried to have 2 individual /dev/lircd and to use the<br>
> listen/connect to connect a second lirc a single /dev/lircd <br>
><br>
> Would it be possible to share your startup scripts? I must be doing something dumb.<br>
<br>
> Jon<br>
<br>
</div></div>If you post your current two lircd scripts/configurations, I can look<br>
at it. Also on the wiki you can find examples for udev rules. For you<br>
also might want to distinguish the rest of the two cards.</blockquote><div><br></div><div>I was using a udev already for the single one and have the second added.</div><div><br></div><div>For the most basic version running from the cli.</div>
<div><br></div><div><div>lircd --output=/dev/lircd --device=/dev/hdpvr_ir -P /var/run/lirc/lircd.pid /etc/lirc/lircd.conf</div><div>lircd --output=/dev/lircd2 --device=/dev/hdpvr2_ir -P /var/run/lirc/lircd2.pid /etc/lirc2/lircd.conf</div>
</div><div><br></div><div>With the lircd.confs linking to a blaster and a blaster2 setting defined.</div><div><br></div><div><div>$ irsend -d /dev/lircd SEND_ONCE blaster select</div></div><div>$ irsend -d /dev/lircd2 SEND_ONCE blaster2 select<br>
</div><div><br></div><div>Sometimes the blaster 2 will work a time or two but it eventually fails. I'm not sure it having on going recordings effects it or not.</div><div><br></div><div>Has anyone had issues with a "failing" power adapter and the blaster maybe? I can leave it recording for a long time no problem. I had not used this hdpvr in a while.</div>
<div><br></div><div>Jon</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div></div></div>