[mythtv-users] Controlling STB with Lirc

[Erik Sejr]

On 5/20/2013 11:40 PM, Erik Sejr wrote:
> On 5/20/2013 11:07 PM, aaron wrote:
>>
>> Hi,
>>
>> This might be a bit off-topic, and I might not have described properly
>> in the subject, but hopefully it will make sense...
>>
>> I had been happily using analog cable with two PVR-250 capture cards
>> since 2005 (which is when I bought the capture cards. Before that I
>> was relatively happily using it with a BT8x8 card since 2002).
>> Everything worked great, I just plugged the cable directly into both
>> cards and away I went.
>>
>> Just recently, I moved into a new house, and rather than migrate my
>> analog Rogers service, I decided to try the new Bell Fibe service.
>> Which, of course, requires a box. While the PVR software offered with
>> Fibe is leaps and bounds ahead of the pitiful offering of Bell's
>> ExpressVu service, it's still pretty pathetic compared to Myth. So
>> naturally I would like to capture the output on my Myth box.
>>
>> So I set about connecting the composite out of the Fibe box (I lost my
>> SVideo cable in the move :( ) and I was able to successfully capture
>> video and audio. yay!
>>
>> But the sticking point is trying to control the Fibe box (to change
>> channels). I bought a USB-UIRT device, which seems to work (I was able
>> to successfully turn the TV off with it. Baby steps. :) )
>>
>> I wasn't able to find any ready-made remote configuration files for
>> the Fibe box that I have (...which I would have to look up later as I
>> forgot to write it down. I remember it's a Motorola something-or-other).
>>
>> I figured I could use irrecord to learn the remote's codes and then
>> point the transmitter at the box and use that config file to blast
>> using irsend.
>>
>> After a fair bit of trial and error, I was able to get irrecord to
>> learn the codes for Power, Select, and 0--9. Which I think will  be
>> all I need, but I can deal with that later.
>>
>> Then I turned the blaster around, pointing at the Fibe box, and issued:
>> $ irsend SEND_ONCE Fibe BTN_POWER
>> to send the "Power" button command
>>
>> ...and... nothing happened. I saw the light on the blaster blink,
>> indicating it did something, but the box didn't respond. I tried again
>> with other codes, but none of them had any effect.
>>
>> Is there some other trick needed to program the transmitter codes? Is
>> this box/remote using some frequency/code/language/whatever that the
>> USB-UIRT isn't able to recognize? Has anyone else tried to control
>> such a box? I found precious little information on trying to connect
>> Fibe to a PVR system, or control the box with a blaster.
>>
>> Any input would be appreciated. And I'm happy to provide more details,
>> just it's late right now and I'm not near the Myth box, and not sure
>> which details might be helpful.
>>
>> aaron
>>
> Aaron,
> This is certainly not off-topic for the users list. I don't have a Fibe
> Box (I assume we're talking Bell here?) but the process is the same
> regardless.
> 
> It sounds to me like you have the transmitter working OK - which is
> good, we'll skip that part.
> 
> The remote definitions are usually stored in /etc/lircd.conf, if you're
> using a remote to control your myth frontend on the same machine you may
> have defs for both the incoming and outgoing signals. If you're just
> using it for the IR blaster then you just need the defs in there to
> control your Fibe box.
> 
> To get those you have a couple options:
> 
> 1. Look though the Lirc remote database at
> http://lirc.sourceforge.net/remotes/ and try some you think might work
> based on the model and manufacturer of your box.
> 
> 2. Put a large database of remotes in your lircd.conf and write a script
> to go though all of them trying to toggle the power on your STB while
> watching the STB. Wait until the power toggles, and presto! You'll know
> at least one of the codesets supported by your STB
> 
> 3. Create your own lircd.conf by using irrecord (this is a lot of work
> for you and probably a last resort). This is almost certainly not
> required, pretty much every codeset imaginable is out there somewhere.
> 
> Let me know if I can help further
> 
> Erik
> 
It is late and I really should read your message twice before I reply
with half the stuff you said you already did. But still, I'd try the
other two options - I doubt the problem is your IR hardware though I
have never used that particular device.

Erik