HIP surgery needed

[mjfoxtrot]

Hi,

This is a HIP problem, but I'm hoping somebody out there may have come across this issue and found a solution. I have two Hauppauge WinTV PVR USB2 devices that I operate with a PVR150 Model 1062/232 remote. The beanbag has two ports (#1 and #2) and I'm running both Windows MCE 2005 and GBPVR. Under Windows MCE 2005, I get seemless performance -- I have both blaster ports working perfectly, each controlling a Comcast Scientific Atlanta digital cable box.

However, GBPVR is a different story. I'm close to a perfect setup, but yet so far away. The problem is that no matter what I try, HIP doesn't seem to be able to fire IR codes out of blaster port #1 on the beanbag. I followed the HIP setup WIKI on the GBPVR site, which is very well detailed. In GBPVR's settings, I have the ehome driver loaded in device manager, but still have HIPs output device set to use 'MCE' (HipMCE.DLL). This configuration works fine for one STB - the IR codes are the same for each box, and I have HIP sending the proper codes through HIPsend. This works as long as I have the blaster connected to port #2. If I connect through port #1, it never sends a flash.

I investigated further and used the HIP configuration utility (I'm running the latest version of HIP) . . . I tried to send a "Test IR" command to port #1, and I never get anything. Using the same command on port #2, it works perfectly and sends the right flash every time. If I swith the blaster cables, I still get the same results -- #2 port works and #1 port doesn't.

Since both ports #1 and #2 work in MCE 2005, I know there's nothing wrong with the hardware. For some reason, HIP just refuses to recognize port #1. Is there anything I can try to get it to work?

Thanks very much in advance.

[ricklous]

Im not sure if HIPs fully compatible with that specific remote, i think ive seen similar posts from folk in the past.

ALthough i dont have the same remote myself, the wiki page says the same:

http://gbpvr.com/pmwiki/pmwiki.php/Hardware/MCERemotes

[mjfoxtrot]

I think you're right, it seems to be that HIP just recognizes one of the blasters.

Bummer. Now I've got to abandon HIP. You suppose girder will work fine with it? I've never tried girder but it would seem to be my only option at this point, other than to get a new remote.

[ricklous]

Sorry ive no idea, ive never used Girder.

Theres also EventGhost which could be work looking at, seems to be developing fast, although again, ive never used it myself.

[zehd]

Hi,

This is a HIP problem, but I'm hoping somebody out there may have come across this issue and found a solution. I have two Hauppauge WinTV PVR USB2 devices that I operate with a PVR150 Model 1062/232 remote. The beanbag has two ports (#1 and #2) and I'm running both Windows MCE 2005 and GBPVR. Under Windows MCE 2005, I get seemless performance -- I have both blaster ports working perfectly, each controlling a Comcast Scientific Atlanta digital cable box.

However, GBPVR is a different story. I'm close to a perfect setup, but yet so far away. The problem is that no matter what I try, HIP doesn't seem to be able to fire IR codes out of blaster port #1 on the beanbag. I followed the HIP setup WIKI on the GBPVR site, which is very well detailed. In GBPVR's settings, I have the ehome driver loaded in device manager, but still have HIPs output device set to use 'MCE' (HipMCE.DLL). This configuration works fine for one STB - the IR codes are the same for each box, and I have HIP sending the proper codes through HIPsend. This works as long as I have the blaster connected to port #2. If I connect through port #1, it never sends a flash.

I investigated further and used the HIP configuration utility (I'm running the latest version of HIP) . . . I tried to send a "Test IR" command to port #1, and I never get anything. Using the same command on port #2, it works perfectly and sends the right flash every time. If I swith the blaster cables, I still get the same results -- #2 port works and #1 port doesn't.

Since both ports #1 and #2 work in MCE 2005, I know there's nothing wrong with the hardware. For some reason, HIP just refuses to recognize port #1. Is there anything I can try to get it to work?

Thanks very much in advance.

I have had this problem before, and swapped the hardware and the problem went away. I know it doesn't make sense, if it worked with MCE...

I should tell you that you should always use the alternate driver. If I understand correctly, you won't get separated individual control if you don't...

[zehd]

Sorry ive no idea, ive never used Girder.

Theres also EventGhost which could be work looking at, seems to be developing fast, although again, ive never used it myself.

EventGhost isn't at the stage where it will use the blasters...

[mjfoxtrot]

Yep, I figure I'll probably have to replace the hardware if I want to get GBPVR to work. It's too bad, though, because the particular beanbag and remote I have work perfectly with both MCE and in GBPVR -- the latter of course with the limitation that I can only use one blaster. I wonder why HIP can't make it work. Oh well . . .

Zehd, as far as your comment that I should always use the replacement driver . . . see the link below to see why I (and others) have opted to stick with the ehome infrared driver. If it's set up under the right conditions, it works very well and solves some problems that the replacement driver causes in MCE.

http://forums.nextpvr.com/showthread.php?t=15656

[zehd]

Yep, I figure I'll probably have to replace the hardware if I want to get GBPVR to work. It's too bad, though, because the particular beanbag and remote I have work perfectly with both MCE and in GBPVR -- the latter of course with the limitation that I can only use one blaster. I wonder why HIP can't make it work. Oh well . . .

Zehd, as far as your comment that I should always use the replacement driver . . . see the link below to see why I (and others) have opted to stick with the ehome infrared driver. If it's set up under the right conditions, it works very well and solves some problems that the replacement driver causes in MCE.

http://forums.nextpvr.com/showthread.php?t=15656

I see why you want the ehome driver. Personally, I don't need the headache. As high as I want the WAF to be, it's easier to say to her, "it's one or the other, honey..." (as in me or the mailman)

Maybe that's why I'm going through my second divorce. But then I do have a kick ass PVR setup...

[mjfoxtrot]

Well said. I personally am bound to the ehome driver by the bonds of matrimony.