[mythtv-users] lirc transmitting and pvr150
Peter Abplanalp
pta-myth at psaconsultants.com
Sat Jul 17 21:50:48 UTC 2010
On Sat, Jul 17, 2010 at 2:48 PM, Peter Abplanalp
<pta-myth at psaconsultants.com> wrote:
> On Sat, Jul 17, 2010 at 2:19 PM, Jarod Wilson <jarod at wilsonet.com> wrote:
>> On Sat, Jul 17, 2010 at 1:08 PM, Peter Abplanalp
>> <pta-myth at psaconsultants.com> wrote:
>>> all,
>>>
>>> research has suggested to me that the "correct" way to use a pvr150
>>> blaster these days is to use the lirc_zilog module. is that correct?
>>
>> Yes.
>>
>>> assuming it is, i'm trying to verify with a mythdora live cd which
>>> supposedly has everything in it to make the zilog driver work. my
>>> issue is that when i try an irsend, i get the following message:
>>>
>>> lirc_zilog: failed to get data for code 0, key 9036 -- check lircd.conf entries
>>
>> Huh. That's a completely new one to me.
>>
>>> afaik, the lircd.conf file is correct. i have a hauppage remote
>>> section at the top and a dctxxxx section on the bottom. i've searched
>>> the web for that particular error message with no luck on an answer.
>>>
>>> it looks to me like everything loads correctly, here is the output of
>>> dmesg|grep zilog:
>>>
>>> lirc_zilog: Zilog/Hauppauge IR driver initializing
>>> lirc_zilog: chip found with RX and TX
>>> i2c i2c-0: lirc_dev: driver lirc_zilog registered at minor = 0
>>> lirc_zilog: Zilog/Hauppauge IR blaster firmware version 1.3.0 loaded
>>> lirc_zilog: initialization complete
>>> lirc_zilog: failed to get data for code 0, key 9036 -- check lircd.conf entries
>>> lirc_zilog: failed to get data for code 0, key 9036 -- check lircd.conf entries
>>> lirc_zilog: failed to get data for code 0, key 9036 -- check lircd.conf entries
>>>
>>> can anyone point me in the correct direction?
>>
>> dmesg does look sane there (prior to the failures, anyway). What
>> exactly is the irsend command you're using that is failing?
>
> irsend send_once blaster 9
>
> 'blaster' matches the remote name in lircd.conf and '9' matches the
> button '9' in lircd.conf.
got a little more info. i rebooted the system to try again and this
time i found that the /etc/lircd.conf file was mangled. it had the
correct remote block for the remote (hauppage) and then the correct
block for the blaster (motorola dct6200) but then it had a ton more
remote blocks, the last of which was incomplete. i removed everything
but the first 2 blocks and restarted lirc.
the dmesg output now looks like this:
lirc_zilog: Zilog/Hauppauge IR driver initializing
lirc_zilog: chip found with RX and TX
i2c i2c-0: lirc_dev: driver lirc_zilog registered at minor = 0
lirc_zilog: Zilog/Hauppauge IR blaster firmware version 1.3.0 loaded
lirc_zilog: initialization complete
it seems to be missing the 'failed to get data' messages from the last
time. i also checked the messages file this time and found the
following:
Jul 17 17:40:46 masterbed lircd-0.8.6[4462]: accepted new client on
/var/run/lirc/lircd
Jul 17 17:40:46 masterbed lircd-0.8.6[4462]: invalid send buffer
Jul 17 17:40:46 masterbed lircd-0.8.6[4462]: this remote configuration
cannot be used to transmit
Jul 17 17:40:46 masterbed lircd-0.8.6[4462]: error processing command:
SEND_ONCE Motorola_DCT6200 3
Jul 17 17:40:46 masterbed lircd-0.8.6[4462]: transmission failed
i get this output when i run irsend a la:
[root at localhost ~]# irsend SEND_ONCE Motorola_DCT6200 3
irsend: command failed: SEND_ONCE Motorola_DCT6200 3
irsend: transmission failed
what does the messages output mean?
quoting your other message:
> Hm. There is no '9' in the 'blaster' section of the stock lircd.conf
> for lirc_zilog (http://www.blushingpenguin.com/mark/lmilk/lircd.conf).
> Please show your lircd.conf, it sounds to me like you might not be
> using the right one...
i copied over a dctxxx config file from another box due to the mangled
lircd.conf file and appended it to the hauppage config the first time.
this time i left the 2 blocks i needed and removed all the rest.
the dct6200 block looks like this now and is what i got after running
the web config tool:
begin remote
name Motorola_DCT6200
bits 48
eps 30
aeps 100
one 0 0
zero 0 0
pre_data_bits 16
pre_data 0xFFFF
gap 209929
min_repeat 1
toggle_bit 0
begin codes
rew 0x8914DDDF5FFF
play 0x8914DD7F5FFF
ff 0x8914DDF75FFF
stop 0x8914DD5F5FFF
rec 0x145415EC0100
pgdn 0x145515FC0100
up 0x29147DF75FFF
down 0x29147DD75FFF
left 0x29147D575FFF
right 0x29147D775FFF
select 0x29147D7D5FFF
guide 0x29147D7F5FFF
menu 0xA914FDFF5FFF
info 0x105515F80100
exit 0x09145DDF5FFF
help 0x105415E80100
last 0x09145D5F5FFF
vup 0x238C7DDD5D55
vdn 0x23847DD55D55
chup 0x29147DD55FFF
chdn 0x29147D555FFF
mute 0x23AE7DFF5D55
fav 0x105555D80300
1 0x8914DDFD5FFF
2 0x8914DD7D5FFF
3 0x8914DDDD5FFF
4 0x8914DD5D5FFF
5 0x8914DDF55FFF
6 0x8914DD755FFF
7 0x8914DDD55FFF
8 0x8914DD555FFF
9 0x09145DFF5FFF
input 0x29147D7F5FFF
0 0x09145D7F5FFF
enter 0x09145D5F5FFF
end codes
end remote
thanks!
-peter
More information about the mythtv-users
mailing list