Windows Entertainment and Connected Home

How to organize, access and enjoy all of your media in and around your home

TSGH-IR01 - OEM (Beanbag) IR Remote, not working

  • rated by 0 users
  • This post has 9 Replies |
  • 4 Followers
Page 1 of 1 (10 items)
  •  
    Hello, everyone~

    HP is now bundling a remote and reciever (models: TSGH-IR01, TSGI-IR01) with their Vista media center desktops. I recently purchased their m8000n which came with this OEM remote/receiver, this is a standard eHome beanbag type receiver,  which should work with any MCE setup. The only difference is that it is an OEM device, and as such has a different Vendor ID. Editing the standard irbus INF file to add this VID allows me to install the device on MCE05.

    Now, the device is recognized, and is showing up in the USB devices, and the HID devices just as it should, but the remote is not actually functioning at all, no matter what I press the computer (and any programs, including Media Center) do not react at all.

    Any ideas?

    (Also, the remote and receiver both light their LEDs when I press anything on the remote, which means that the device is being recognized by Windows. Before installing the drivers, the receiver will not react to the remote's key presses at all.)

    EDIT:
    The remote is HP Part #5070-2583
    Remote control (Picasso) - For Windows Media Center PC and the paintbrush receiver (remote sensor)
    The receiver is HP Part #5070-2584
    Remote IR receiver (paintbrush) - For use with Picasso remote control


  •  

    Hi,

    I have the exact same problem.

    All looks good in Device Manager, and the leds are flashing on both remote and receiver.

    Any ideas?

  •  
    Xestrix:
    Hello, everyone~

    HP is now bundling a remote and reciever (models: TSGH-IR01, TSGI-IR01) with their Vista media center desktops. I recently purchased their m8000n which came with this OEM remote/receiver, this is a standard eHome beanbag type receiver,  which should work with any MCE setup. The only difference is that it is an OEM device, and as such has a different Vendor ID. Editing the standard irbus INF file to add this VID allows me to install the device on MCE05.

    Now, the device is recognized, and is showing up in the USB devices, and the HID devices just as it should, but the remote is not actually functioning at all, no matter what I press the computer (and any programs, including Media Center) do not react at all.

    Any ideas?

    (Also, the remote and receiver both light their LEDs when I press anything on the remote, which means that the device is being recognized by Windows. Before installing the drivers, the receiver will not react to the remote's key presses at all.)

    EDIT:
    The remote is HP Part #5070-2583
    Remote control (Picasso) - For Windows Media Center PC and the paintbrush receiver (remote sensor)
    The receiver is HP Part #5070-2584
    Remote IR receiver (paintbrush) - For use with Picasso remote control



    I thnk i have the same issue. can you please give detailed information on editing the INF file. Thank you.
  •  
    thought this was MCE 05 or older forum.  My bad, i'm in the wrong forum.  How embarassing.  Can any1 direct me to the right forum? TY
  •  

    Hello, i've been strugling with this for some time now but finaly found the solution.

    You not only have to edit the irbus.inf file, but also input.inf, keyboard.inf and  medctroc.inf  located in the windows inf folder.

    This are the lines i added to the files

    to input.inf

    [MICROSOFT_KBD]
    %IRBUS\VID_045E&PID_006D.DeviceDesc%=HIDIR_Inst, IRBUS\VID_1784&PID_0006 ; HP

    [HIDIR_Inst_DeviceID.Addreg.NT.HW]
    HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Remote Controls","HID\VID_1784&PID_0006&COL05",0x00000000,"" ; HP

    [strings]
    USB\VID_1784&PID_0006&Col01.DeviceDesc = "EHome Infraroodtransceiver"

    irbus.inf

    [MicrosoftHw]
    %USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_1784&PID_0006

    [ControlFlags]
    ExcludeFromSelect=USB\VID_1784&PID_0006

    [Strings]
    USB\VID_1784&PID_0006.DeviceDesc="eHome-infrared-receiver"

    keyboard.inf

    [MICROSOFT_KBD]
    %HID\VID_045E&PID_006D&COL05.DeviceDesc%=eHome_Keyboard_Inst,, HID\VID_1784&PID_0006&COL05 ; HP
    %HID\VID_045E&PID_006D&COL06.DeviceDesc%=eHome_Keyboard_Inst,, HID\VID_1784&PID_0006&COL06 ; HP
    %HID\VID_045E&PID_006D&COL07.DeviceDesc%=eHome_106_Keyboard_Inst,, HID\VID_1784&PID_0006&COL07 ; HP

    medctroc.inf

    ; List of MCE remote controls
    HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Remote Controls","HID\VID_1784&PID_0006",0x00000000,"" ; HP

    (only the black text has to be added)

    This seemed to do the trick and made the remote fuly functional.

    Let me know if it works for you.

    Grtz Wailer.

     

  •  

    :D   

    FINALLY SOLVED for me (on an HP 7655)

    The HP remote was my nightmare too – thanks Grtz Wailer for pointing me in the right direction.


    Having made the amends to the .inf files my remote started working. BUT on a reboot everything went back to no-go.


    Looking back into the inf folder you can see that each .inf file has an associated .PNF file. Apparently, these are created by Windows after the .inf file is accessed for the first time. Thereafter it is the .PNF file that is used and not the .inf file. If you make amends to the .inf file these are ignored because the .PNF file has been previously created. And the solution is to delete any .PNF files for which you want to amend the associated .inf file. Windows will then create new .PNFs from your amended .inf files when you reinstall the device(s).


    When I finally reconnected/reinstalled, the system went through a number of cycles of reinstall as it racked up the various different keyboards etc.


    The steps that made my remote work were:


    1.- uninstalled the device


    2. - amended the .inf files as suggested by Grtz Wailer (thanks again)


    3. - deleted the relevant .PNF files (irbus.PNF etc)


    4. - connected the remote; letting Windows install it automatically (accept the uncertified driver(s) throughout the process)

     

    :)  :D


    PHEW


    (The trouble starts (presumably) because HP has not included the device VID/PID refernces in the original .inf files - yet the refs work their way into the registry on (mis)installation the first time - but cannot be accessed by Windows without the correctly created .PNF files.)


    Anyone know a URL to download the remote user guide?


    Regards

    no3cat



  •  

    I have a question regarding this same Beanbag Reciever:

    My remote works, but it (catching) every 10 key strokes or so. It's like it kinda locks up for a second, and then forces all those strokes at once and it surges forward.

    I use my mouse and keyboard (bluetooth) it and works flawlessly. The remote is all snagged while using it.

    Any way to change the Timing of the signals? I usually build my own media centers, but decided to buy one from HP now. Everything is great, but this Remote issue.

     

    Origen H6 Silver / Abit AN8 Fatality Motherboard / AMD 64 X2 Dual Core 4200+ / 250GB Western Digital SATA Hard Drive / Asus X1600 256mb Silent Video Card / 2GB Corsair 400 Memory / WinTV-PVR-250MCE / Samsung DVD+RW / Vista Home Premium
  •  
    Have you done this on win7? i cant find irbus.inf? :S
  •  

    Has anyone gotten this to work in windows 7 yet?

  •  

     IBA KOKOT

    SA VIZNA NA TEJTO STANKE ☺☻☺☻CHOTE DO PIČE

Page 1 of 1 (10 items)