Page 1 of 4 123 ... LastLast
Results 1 to 10 of 32

Thread: Fintek MCEUSB Mythbuntu 12.04.02

  1. #1
    Join Date
    Mar 2008
    Beans
    14

    Post Fintek MCEUSB Mythbuntu 12.04.02

    I am trying to get the blaster to work. If i use irsend the blaster blinks....Once for everytime I run the command irsend SEND_STOP PaceDC50X KEY_5 I have no errors and if I watch the transmitter with a camera it blinks once. If I watch the original remote and press the button once it blinks multiple times. If I point the original remote at the receiver and use irw I get the correct buttons detected by the receiver. I have multiple OSs and it works fine in Windows and I hold the sensor in place on the DTA with velcro in the same place as in Windows...Anyone have any idea?


    Code:
    root@blackbox:~# ls /dev/lir*
    /dev/lirc0  /dev/lircd
    Gets one blink from the transmitter
    Code:
    irsend SEND_ONCE PaceDC50X KEY_5
    Code:
    # /etc/lirc/hardware.conf
    #
    #Chosen Remote Control
    REMOTE="Windows Media Center Transceivers/Remotes (all)"
    REMOTE_MODULES="lirc_dev mceusb"
    REMOTE_DRIVER=""
    REMOTE_DEVICE="/dev/lirc0"
    REMOTE_SOCKET=""
    REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb"
    REMOTE_LIRCD_ARGS=""
    
    #Chosen IR Transmitter
    TRANSMITTER="Microsoft Windows Media Center V2 (usb) : Motorola Cable box"
    TRANSMITTER_MODULES="lirc_dev mceusb"
    TRANSMITTER_DRIVER=""
    TRANSMITTER_DEVICE="/dev/lircd"
    TRANSMITTER_SOCKET=""
    TRANSMITTER_LIRCD_CONF="pace/pace.conf"
    TRANSMITTER_LIRCD_ARGS=""
    
    
    #Enable lircd
    START_LIRCD="true"
    
    #Don't start lircmd even if there seems to be a good config file
    #START_LIRCMD="false"
    
    #Try to load appropriate kernel modules
    LOAD_MODULES="true"
    
    # Default configuration files for your hardware if any
    LIRCMD_CONF=""
    
    #Forcing noninteractive reconfiguration
    #If lirc is to be reconfigured by an external application
    #that doesn't have a debconf frontend available, the noninteractive
    #frontend can be invoked and set to parse REMOTE and TRANSMITTER
    #It will then populate all other variables without any user input
    #If you would like to configure lirc via standard methods, be sure
    #to leave this set to "false"
    FORCE_NONINTERACTIVE_RECONFIGURATION="false"
    START_LIRCMD=""
    Code:
    root@blackbox:/etc/lirc/backup# cat lircd.conf
    #This configuration has been automatically generated via
    #the Ubuntu LIRC package maintainer scripts.
    #
    #It includes the default configuration for the remote and/or
    #transmitter that you have selected during package installation.
    #
    #Feel free to add any custom remotes to the configuration
    #via additional include directives or below the existing
    #Ubuntu include directives from your selected remote and/or
    #transmitter.
    
    #Configuration for the Windows Media Center Transceivers/Remotes (all) remote:
    include "/usr/share/lirc/remotes/mceusb/lircd.conf.mceusb"
    include "/usr/share/lirc/extras/transmitters/pace/pace.conf"
    Code:
    # Please make this file available to others
    #
    # this config file was automatically generated
    # using lirc-0.8.6-CVS(default) on Mon Jan 11 21:34:36 2010
    #
    # contributed by Kirk Bocek
    #
    # brand: Comcast Branded Motorola DTA100 and Pace DC50X
    # model no. of remote control: Unknown, Comcast Label
    # devices being controlled by this remote: Motorola DTA100 & Pace DC50X
    #
    # These are a couple of the cheap digital converters being provided by
    # Comcast as part of their analog shutdown. DTA100 information here:
    # http://www.motorola.com/Business/US-EN/Business+Product+and+Services/TV+Video+Distribution/Customer+Premises+Equipment+%28Set-tops%29# 
    # /All-Digital+QAM+Settops/DTA100_US-EN
    #
    # This remote also has power and volume buttons. You can program these
    # to control your TV. But these DTAs *do* have internal volume and mute
    # controls. The power button, however, is only for your TV and has no
    # effect on the DTA.
    #
    # Because this remote use the XMP protocol, this config requires
    # lirc 0.8.6 or later.
    #
    # Generated by starting with the generic XMP protocol configuration:
    # http://lirc.sourceforge.net/remotes/generic/XMP
    # and then using irrecord to add the keys.
    #
    # V.2 - Added Volume Up and Volume Down
    # V.3 - Confirmed operation with Pace DC50X. Changed strings to
    #       conform with standard strings used in lirc 0.8.6.
    #
    
    begin remote
    
       name PaceDC50X
       bits           24
       flags XMP
       eps            20
       aeps          300
    
       one             0   137
       zero          250   710
       ptrail        250
       pre_data_bits   32
       pre_data       0x170F443E
       post_data_bits  8
       post_data      0x0
       pre           250 12921
       gap          81698
       toggle_bit_mask 0x0
    
           begin codes
               KEY_1                       0x1E0001
               KEY_2                       0x1D0002
               KEY_3                       0x1C0003
               KEY_4                       0x1B0004
               KEY_5                       0x1A0005
               KEY_6                       0x190006
               KEY_7                       0x180007
               KEY_8                       0x170008
               KEY_9                       0x160009
               KEY_0                       0x1F0000
               KEY_CHANNELDOWN             0x11000E
               KEY_CHANNELUP               0x12000D
               KEY_MUTE                    0x13000C
               KEY_VOLUMEDOWN              0x14000B
               KEY_VOLUMEUP                0x15000A
               KEY_LANGUAGE                0x150082
               KEY_INFO                    0x170026
               KEY_ENTER                   0x180025
               KEY_LAST                    0x190051
           end codes
    
    end remote
    Code:
    root@blackbox:/etc/lirc# dmesg | grep mceusb
    [   18.884628] input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input3
    [   18.935328] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
    [   19.049704] mceusb 3-1:1.0: Registered FINTEK eHome Infrared Transceiver with mce emulator interface version 2
    [   19.049709] mceusb 3-1:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x0 active)
    [   19.049774] usbcore: registered new interface driver mceusb
    Last edited by betolley; March 17th, 2013 at 08:31 PM.

  2. #2
    Join Date
    Mar 2008
    Beans
    1,086

    Re: Fintek MCEUSB Mythbuntu 12.04.02

    With modern versions of LIRC starting with 0.8.6, I've only been able to get the Pace dc50x boxes to change channels by sending the raw codes from the blaster to the DTA, as are found in the conf file found in section 3.1 here: http://regx.dgswa.com/html/node/134 I continue to use this file with lirc 0.8.7; I suspect it should still be fine with the lirc 0.9.0 included with Mythbuntu 12.04

    Also what happens when you use the command "irsend send_once" rather than "irsend send_stop"?

  3. #3
    Join Date
    Mar 2008
    Beans
    14

    Re: Fintek MCEUSB Mythbuntu 12.04.02

    Sorry stupid typing mistake. I am doing SEND_ONCE.

    I change the config to the RAW format config instead of the xmpp. Still same problem. Except no flashing on the transmitter at all now.

    irsend LIST "" ""

    still shows DC50X


    Any other ideas?
    Last edited by betolley; March 17th, 2013 at 07:21 PM.

  4. #4
    Join Date
    Mar 2008
    Beans
    1,086

    Re: Fintek MCEUSB Mythbuntu 12.04.02

    Not really, other than to ask what feedback lircd is giving you, if any, when irsend fails. Easiest way would be to kill lircd and run it (sudo) from a terminal with the --nodaemon option. Then play with irsend in a second window. The lircd window may give you some clues.

  5. #5
    Join Date
    Mar 2008
    Beans
    14

    Re: Fintek MCEUSB Mythbuntu 12.04.02

    I ran with nodaemon I get the following output with irsend commands.
    Code:
    /usr/sbin/lircd --output=/var/run/lirc/lircd --device=/dev/lirc0 --nodaemon
    lircd-0.9.0[2811]: lircd(default) ready, using /var/run/lirc/lircd
    lircd-0.9.0[2811]: accepted new client on /var/run/lirc/lircd
    lircd-0.9.0[2811]: removed client
    lircd-0.9.0[2811]: accepted new client on /var/run/lirc/lircd
    lircd-0.9.0[2811]: removed client
    lircd-0.9.0[2811]: accepted new client on /var/run/lirc/lircd
    lircd-0.9.0[2811]: removed client
    but no channel changes.

  6. #6
    Join Date
    Mar 2008
    Beans
    1,086

    Re: Fintek MCEUSB Mythbuntu 12.04.02

    Then I believe the issue is likely the problematical mceusb driver itself, and how it's talking (or not) with your Fintek blaster.Though Fintek is, in theory, supposed to be supported by the mceusb driver, it's frequently fairly hit-or-miss as to whether any official "mceusb" device actually functions with the mceusb driver in any given installation.

    You can perhaps try the mceusb2 driver also, and in the likely event it fails for you, my only other recommendation might be to try a third-party blaster/receiver that supplies its own Linux non-kernel-level driver. After some frustration with LIRC and these Pace dc50x boxes, I went with the Iguanaworks blaster. Other than needing to recompile LIRC to include their iguana ir driver (since Ubuntu doesn't include the driver in their LIRC driver set) I've never had any particular issue with the devices over several years.

  7. #7
    Join Date
    Nov 2006
    Beans
    217

    Re: Fintek MCEUSB Mythbuntu 12.04.02

    I have tried to get 3 different IR Blasters to work with a MythTV computer(s)/setup, the first being the Rosewill RHRC-11001 MCE USB transceiver which registers as a Formosa21 eHome Infrared Remote Transceiver, with Vendor_:_Product ID 147a:e042, the second being a Hauppauge PVR-150 PCI card with built-in IR Transmitter, and the third (current effort) being an HP branded OEM MCE USB transceiver which registers as a Feature Integration Technology Inc. (Fintek) F71610A or F71612A with Vendor_:_Product ID 1934:5168. All three of these devices were able to receive IR from their respective included remotes, but only the HP/Fintek showed any sign of actually transmitting, in that I could see the IR LED (and the main box activity LED) blink when doing irsend. I am trying to transmit to a Motorola DTA100, which is (in theory) identical to the Pace DC50X, and the config file provided by lirc.org is the same for both units, however... the author of that config file (v 2.3), originally posted it with the following "zero" definition:

    zero 250 710

    whereas the current lirc.org file here: http://lirc.sourceforge.net/remotes/pace/DTA100 (and same for the motorola directory) has the "zero" as:

    zero 210 750

    The author Kirk Bocek documents that he started with a generic XMP file here: http://lirc.sourceforge.net/remotes/generic/XMP and added the various remote keys. This generic XMP config has the "zero" defined as 250 710. Note also that the DC50X/DTA100 has "bits" set to 24 versus 32 in the generic XMP config.

    Using the original (and geneirc XMP) "zero" 250 710 definition in the DC50X/DTA100 config I can see the HP MCE USB transmitter LED flash with irsend, but using the 210 750 it does not. Although I think there is a bigger overall problem/bug in the IR Transmit software of lirc 0.9.0, possibly in the mceusb driver, the question is why a relatively small change in those numbers would produce flash versus no flash. I suppose someone should mention the "error" to lirc.org, assuming it is one, but I don't remember seeing any flash when initially testing with the (unrelated) dctxxxx.conf file that the lirc installer used as the "Motorola Cable box", and that would suggest that the problem is bigger than the DC50X/DTA100 config per se.
    CPU: 80286 @ 10Mhz; FPU: n/a; RAM: 256K, HD: 20 Meg
    Graphics: Monochrome; Power Supply: 100 W; Case: Yes/Open

  8. #8
    Join Date
    Nov 2006
    Beans
    217

    Re: Fintek MCEUSB Mythbuntu 12.04.02

    Worth noting is that there are two IR connectors on the back of the HP MCE USB device, and the port to the right of the USB cable facing the back of the unit (and make sure the plug goes all the way into the connector as the last 1/8" was stubborn) is the only one that "works" in my testing. In theory the other is also a transmitter port (?) and might work by using irsend SET_TRANSMITTERS to 2,3,4 ? The mceusb driver logs (dmesg) 2 transmitters/ports:

    mceusb 6-2:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x0 active)
    CPU: 80286 @ 10Mhz; FPU: n/a; RAM: 256K, HD: 20 Meg
    Graphics: Monochrome; Power Supply: 100 W; Case: Yes/Open

  9. #9
    Join Date
    Mar 2008
    Beans
    14

    Re: Fintek MCEUSB Mythbuntu 12.04.02

    i tried several different distros. fedora would not work at all. I had the same issue as you if I used the pace config with xmpp in it I would get one flash every time I sent a signal. I should have gotten several. I would not get anything with the raw format. I restored a copy of win 7 and I am sadly using NPR.mit is working fine. Media center worked fine also.

  10. #10
    Join Date
    Nov 2006
    Beans
    217

    Re: Fintek MCEUSB Mythbuntu 12.04.02

    At least that proves that the problem is not the hardware, or hardware interaction issues like the distance between the IR blaster LED and the STB, or ambient IR light interference. I almost tried Fedora because I read that some of the IR devs were with Redhat, so that is also surprising. I am now wrestling with the option of going back to Ubuntu 10.04 as the last version with pre-0.9.0 lirc, or maybe 0.8.6/0.8.7 could be compiled from source and the kernel built-in mceusb blacklisted (?).
    CPU: 80286 @ 10Mhz; FPU: n/a; RAM: 256K, HD: 20 Meg
    Graphics: Monochrome; Power Supply: 100 W; Case: Yes/Open

Page 1 of 4 123 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •