Re: [mythtv-users] MCEUSB transmit not working. Same codes send as receive. Hardware working fine.
Mark <[email protected]>
| Newsgroups | gmane.comp.hardware.lirc |
|---|---|
| Message-ID | <[email protected]> |
On 23/03/17 08:51 AM, Alec Leamas wrote:
>
> On 23/03/17 15:17, Mark wrote:
>> Hello,
>>
>> I am really close to getting this. Just need some help to finish this
>> up please.
>>
>> A short description of what I am trying to do. I just need to change
>> channels in MythTV on a new device.
>>
>> Essentially, I am transmitting, but nothing is working and codes are not
>> activating device.
> You are cross-posting to both lirc-list and mythtv-devel. Cross-posting
> in on of those things which from time to time creates a mess...
>
>> To do this, I have:
>>
>> I have an IPTV box called a technicolor IPV5050 ( same codes as Cisco
>> IPN330HD ) that there are no known codes for. So I used IRRecord to
>> build a config from the remote that came with the IPV5050.
>>
>> The receive portion of this works perfectly. As the codes that are
>> setup to receive are also the same ones that I want to send, I am
>> thinking I should only have one device config.
>>
>> When I try to irsend, the command ( irsend SEND_ONCE mce KEY_OK ) is
>> accepted fine, and I can see the pulse on a camera coming out, but no
>> action on the IPTV box, or with another box listening with IRW. ( I have
>> two computer with the same config and receivers set up to test this )
>>
>> Here are the configs and hardware info. Any thoughts or advice greatly
>> appreciated.
>>
>> Fedora 25 and lirc 0.9.4C
>>
>> Hardware is an HP MCEUSB IR Receiver with the plug in transmitter cable
>> on the back. I can see pulses when I try to transmit.
>>
>> --------------------------
>>
>> DMESG:
>>
>>
>> /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/rc/rc0/input25
>> [ 1072.466061] rc rc0: Media Center Ed. eHome Infrared Remote
>> Transceiver (03ee:2501) as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/rc/rc0
>> [ 1072.466249] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb)
>> registered at minor = 0
>> [ 1072.621897] mceusb 1-7:1.0: Registered Mitsumi eHome Infrared
>> Transceiver with mce emulator interface version 1
>> [ 1072.621901] mceusb 1-7:1.0: 2 tx ports (0x1 cabled) and 2 rx sensors
>> (0x1 active)
> 'oK, all looks good. The driver seems to be able to send data
>
>> LIRC config:
>> min_repeat 1
>> suppress_repeat 2
> It might as simple as the TV requiring the code to be repeated - it
> seems like the remote repeats each code at least twice
> (suppress_repeat). You can raise min_repeat to repeat each code; see
> lircd.conf(5).
>
>
>> LIRC OPTIONS file:
>> permission = 666 <--- testing only, right? Should be 660
> If you still are stuck, please post the lircd logs obtained as described
> in [1]
>
>
> Cheers!
>
> --alec
>
> [1] https://sourceforge.net/p/lirc/mailman/message/35742509/
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Hello,
in debug mode, here is the command and the output. Also, the config
file below with repeat etc... commented out. ( I just added these
manually earlier as I thought they were needed )
irsend SEND_ONCE blaster KEY_OK
[root@ratty lircd.conf.d]# journalctl -b0 /usr/sbin/lircd | tail -30
Mar 23 10:03:23 ratty.opisop.ca lircd-0.9.4c[5391]: Notice:
lircd(default) ready, using /var/run/lirc/lircd
Mar 23 10:03:29 ratty.opisop.ca lircd[5391]: lircd-0.9.4c[5391]: Notice:
accepted new client on /var/run/lirc/lircd
Mar 23 10:03:29 ratty.opisop.ca lircd[5391]: lircd-0.9.4c[5391]: Info:
[lirc] protocol is enabled
Mar 23 10:03:29 ratty.opisop.ca lircd-0.9.4c[5391]: Notice: accepted new
client on /var/run/lirc/lircd
Mar 23 10:03:29 ratty.opisop.ca lircd-0.9.4c[5391]: Info: [lirc]
protocol is enabled
Mar 23 10:03:29 ratty.opisop.ca lircd[5391]: lircd-0.9.4c[5391]: Info:
removed client
Mar 23 10:03:29 ratty.opisop.ca lircd-0.9.4c[5391]: Info: removed client
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Info: lircd: Opening
log, level: Info
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Info: Initial
device: /dev/lirc0
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Info: [lirc]
protocol is enabled
Mar 23 10:04:52 ratty.opisop.ca lircd[5419]: lircd-0.9.4c[5419]: Info:
lircd: Opening log, level: Info
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Info: Initial
device: /dev/lirc0
Mar 23 10:04:52 ratty.opisop.ca lircd[5419]: lircd-0.9.4c[5419]: Notice:
Running as user lirc
Mar 23 10:04:52 ratty.opisop.ca lircd[5419]: lircd-0.9.4c[5419]: Info:
Using remote: mce.
Mar 23 10:04:52 ratty.opisop.ca lircd[5419]: lircd-0.9.4c[5419]: Info:
Using remote: blaster.
Mar 23 10:04:52 ratty.opisop.ca lircd[5419]: lircd-0.9.4c[5419]: Info:
Using remote: ser1.
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Info: [lirc]
protocol is enabled
Mar 23 10:04:52 ratty.opisop.ca lircd[5419]: lircd-0.9.4c[5419]: Notice:
lircd(default) ready, using /var/run/lirc/lircd
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Info: lircd: Opening
log, level: Info
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Notice: Running as
user lirc
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Info: Using remote: mce.
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Info: Using remote:
blaster.
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Info: Using remote:
ser1.
Mar 23 10:04:52 ratty.opisop.ca lircd-0.9.4c[5419]: Notice:
lircd(default) ready, using /var/run/lirc/lircd
Mar 23 10:04:59 ratty.opisop.ca lircd[5419]: lircd-0.9.4c[5419]: Notice:
accepted new client on /var/run/lirc/lircd
Mar 23 10:04:59 ratty.opisop.ca lircd[5419]: lircd-0.9.4c[5419]: Info:
[lirc] protocol is enabled
Mar 23 10:04:59 ratty.opisop.ca lircd-0.9.4c[5419]: Notice: accepted new
client on /var/run/lirc/lircd
Mar 23 10:04:59 ratty.opisop.ca lircd-0.9.4c[5419]: Info: [lirc]
protocol is enabled
Mar 23 10:04:59 ratty.opisop.ca lircd[5419]: lircd-0.9.4c[5419]: Info:
removed client
Mar 23 10:04:59 ratty.opisop.ca lircd-0.9.4c[5419]: Info: removed client
FYI. In this config, the name OK ( raw code section ) works. Thats the
only key that works.
begin remote
name mce
bits 8
flags RCMM|CONST_LENGTH
eps 18
aeps 100
header 417 278
three 167 778
two 167 611
one 167 444
zero 167 278
ptrail 167
pre_data_bits 24
pre_data 0x248026
gap 99817
min_repeat 1
suppress_repeat 2
toggle_bit_mask 0x8000
begin codes
KEY_1 0x01
KEY_2 0x02
KEY_3 0x03
KEY_4 0x04
KEY_5 0x05
KEY_6 0x06
KEY_7 0x07
KEY_8 0x08
KEY_9 0x09
KEY_0 0x00
KEY_POWER 0x0C
KEY_REWIND 0x29
KEY_STOP 0x31
KEY_FASTFORWARD 0x28
KEY_PAUSE 0x2C
KEY_OK 0x5C
KEY_CHANNELUP 0x20
KEY_CHANNELDOWN 0x21
end codes
end remote
# This is configuration is for the Motorola VIP 1200
#
<http://broadband.motorola.com/catalog/productdetail.asp?ProductID=441> and
# VIP 1216
# <http://broadband.motorola.com/catalog/productdetail.asp?ProductID=443>
# STB provided by AT&T for their U-verse IPTV service
begin remote
name blaster
bits 8
flags RCMM|CONST_LENGTH
eps 18
aeps 100
header 417 278
three 167 778
two 167 611
one 167 444
zero 167 278
ptrail 167
pre_data_bits 24
pre_data 0x248026
gap 99817
# min_repeat 4
# suppress_repeat 2
toggle_bit_mask 0x8000
begin codes
KEY_1 0x01
KEY_2 0x02
KEY_3 0x03
KEY_4 0x04
KEY_5 0x05
KEY_6 0x06
KEY_7 0x07
KEY_8 0x08
KEY_9 0x09
KEY_0 0x00
KEY_POWER 0x0C
KEY_REWIND 0x29
KEY_STOP 0x31
KEY_FASTFORWARD 0x28
KEY_PAUSE 0x2C
KEY_OK 0x5C
KEY_CHANNELUP 0x20
KEY_CHANNELDOWN 0x21
end codes
end remote
begin remote
name ser1
flags RAW_CODES|CONST_LENGTH
eps 30
aeps 100
ptrail 0
repeat 0 0
gap 96946
begin raw_codes
name 1
450 150 300 200 200 600
200 200 250 700 250 350
250 200 250 200 250 200
250 200 200 550 200 400
250 550 200 250 250 200
200 250 150 450 200
name 2
500 150 300 150 250 550
250 200 200 750 200 400
200 250 200 200 250 200
250 550 200 600 200 400
150 600 200 250 200 250
200 250 200 550 200
name ok
500 200 200 250 200 550
250 200 150 800 250 350
250 200 250 200 150 300
200 250 200 550 200 400
200 600 200 400 200 400
200 750 200 250 200
end raw_codes
end remote
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot