|
|
#1 (permalink) |
|
FTA Newbie
![]() Join Date: Mar 2009
Posts: 6
Credits: 502.60
Thanks: 0
Thanked 2 Times in 2 Posts
|
Hauppauge IR Codes for Nfusion HD.. Success
This is not a request for assistance. Just hoping I can help out folks trying to set up any of Hauppauge products with the Nfusion HD...
After much trial and error, I have been able to get my HD-PVR to play with the nFusion HD and SageTV (though the IR codes have more to do with the HD-PVR & the nFusion than SageTV...).. I initially tried to find a compatible IR code set for the nFusion HD within Hauppauges Blaster Config application, but quickly gave up as it was not a listed device. From there I went through the "Learning" fucntionality within Blaster Config where you teach your remote codes to the Hauppauge device (in my case HD-PVR) so it can relay those through the IR Blaster to the nFusion HD. This was hit and miss. The codes relayed properly when tested in Blaster Config, but I'd get about 60% accuracy from within SageTV where it counts (SageTV has built in support for the HD-PVR which the IR Blaster is connected to). The error symptom would be that the IR commands sent by the IR Blaster would be received intermittently by the nFusion HD STB in broken patterns. For example, if I wanted to change the channel to 9432, despite all of my efforts to iron out kinks with Blaster Config tweaking of tuning, and inter-digit delays, and what not, the nFusion HD would sometimes pick up a "9".. followed by a brief pause at which point the "9" would be accepted by the nFusion HD and then a "432" at which point the nFusion HD would change channels to "432" assuming that was a valid channel. If not a valid channel, of course the nFusion HD would just sit on the current channel. This drove me up the wall. There have been a number of other folks with similar symptoms over the years (google), but no clear solution. I then resorted to what I thought was my last option. I uninstalled the HD-PVR device and reinstalled it with the latest beta drivers (in this case, 1.5.6) and uinstalled and reinstalled with the latest versions of Blaster Config and the IR Remote application (the little app that actually sends the signals). From there, I went through the Learning process again and this time, received even worse results. Despite, receiving "success" when learning each channel, the nFusion HD actually wouldn't read certain numbers at all... 7, 8, & 9 in this case. :-( Finally, I went back to testing pre-defined code sets.. really my last resort here... and came up up with a hit on code "627", which works perfectly.. about 95% of the time.. (nothings perfect).. but, much better than the "learned" codes... the WAF just went way, way up... So, if you're in this situation, make sure you've got your IR situated properly against the front of the STB and start your testing at, say, "623"... then, when the testing turns off the nFusion HD at "627", immediately hit the Stop button and save settings... then, commence to verifiying it works.. Hope this helps someone out there.. Last edited by jbmia; April 27th, 2009 at 10:21 AM. Reason: ..incomplete.. |
|
|
| The Following User Says Thank You to jbmia For This Useful Post: |
atabo40 (July 17th, 2009)
|
| Related Content | |
|
Cool Deals!
__________________
Cool Deals |
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|