MCEUSB transmit not working. Same codes send as receive. Hardware working fine.
Mark <[email protected]>
| Newsgroups | gmane.comp.hardware.lirc |
|---|---|
| Message-ID | <[email protected]> |
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. ---------------------------- 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: [ 1072.293862] usb 1-7: new full-speed USB device number 9 using xhci_hcd [ 1072.464347] usb 1-7: New USB device found, idVendor=03ee, idProduct=2501 [ 1072.464352] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1072.464355] usb 1-7: Product: eHome Infrared Transceiver [ 1072.464357] usb 1-7: Manufacturer: Mitsumi [ 1072.464360] usb 1-7: SerialNumber: MI001nxT [ 1072.465713] Registered IR keymap rc-rc6-mce [ 1072.465906] input: 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/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) LIRC config: [root@ratty lircd.conf.d]# cat mce.lircd.conf # Please make this file available to others # by sending it to <[email protected]> # # this config file was automatically generated # using lirc-0.9.0(default) on Mon Mar 20 14:57:23 2017 # # contributed by # # brand: own_remote.conf.conf # model no. of remote control: # devices being controlled by this remote: # 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_VOLUMEUP 0x0C 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 LIRC OPTIONS file: [root@ratty lirc]# cat lirc_options.conf # Generated by lirc-setup [lircd] nodaemon = False driver = default device = /dev/lirc0 output = /var/run/lirc/lircd pidfile = /var/run/lirc/lircd.pid plugindir = /usr/lib64/lirc/plugins permission = 666 allow-simulate = No repeat-max = 600 effective-user = lirc lircd_conf = mce.lircd.conf [lircmd] uinput = False nodaemon = False [modinit] code = echo lirc > /sys/class/rc/rc0/protocols ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot