![philips ehome infrared receiver philips ehome infrared receiver](https://blog.turboturbo.net/wp-content/uploads/2016/09/gbheader.png)
- #Philips ehome infrared receiver install#
- #Philips ehome infrared receiver update#
- #Philips ehome infrared receiver software#
- #Philips ehome infrared receiver windows 7#
- #Philips ehome infrared receiver windows#
I set “Power On Delay”, “Inter-key Delay”, “Input Delay” and “Inter-Device Delay” to 0. Now back on the Devices tab choose the “Settings” option for your remote and then the “Adjust the delays (speed settings)” option. So I would scroll up once and it would actually scroll up twice. Using values of 4 or 5 meant that it would jump to many times. Again though, don’t bother disconnecting it yet. Run through the “Update Device” procedure to get it onto the actual Harmony Remote. Select the “Troubleshoot” option for your remote control, then “Server responds to some commands either too many times or only occasionally.” on the next page. We do this before changing the delays as a side-effect of changing the repeat value is that the Harmony app automatically adjusts the delays without telling you. Now it’s time to adjust the repeat value. By learning these keys myself I know for a fact that they are correct. Later it suddenly decides it does recognise it and you are supposed to trust that it will pick the best profile.
#Philips ehome infrared receiver software#
The way I see it is that at the start the software said it did not recognise the remote. Once that has completed just ok your way through all the confirmation screens, leave the remote connected. On the next page scroll down to DirectionLeft, DirectionRight, DirectionUp and DirectionDown, tick them all and then choose to re-learn them. So on the Devices tab click Settings on your remotes tile menu. I read that if you do RAW learning then you will have an extra delay added onto the command that you can do nothing about. In XBMC you will be using up and down a lot to navigate. The first step after the initial setup is complete is to re-learn the directional buttons. It took quite a bit of testing to get something workable, around 4 hours went into this and a lot of running up and down stairs! On top of that it adds several user configurable delays as well as a repeat frequency. I’ve done a bunch of searching and it seems the Harmony One remote has a few short comings, one of these is that it has a minimum duration of 300ms for each transmission. Tweaking the Aim RC6 RC118 remote settings for the Harmony One In the MCE plugin settings for IR Suite I told it to override the hardcoded buttons as without this the number pad and directional controls would not work. You can test the remote out by using IR Server Suites debug client utility and it’s Listen then Learn options. It auto-detected that I had an MCE remote hooked up. I got around that by using MediaPortals IR Server Suite. You will now have the device installed on the system.Īll is still not well though as for me, nothing would happen when I’d press the remote buttons whilst XBMC was loaded.
#Philips ehome infrared receiver install#
Now when you connect the MCE receiver and it prompts you to install drivers just point it to that directory and let it install the uncertified drivers. Inside there is a directory called SP2QPE, copy that to your desktop. That is the temp one used by the eHome installer. You will see a directory with a long alpha-numeric title. Instead open My Computer and go to your C: drive. Run the installer again and when you get the error popup, don’t click OK. The simple fix is to cheat and manually grab the drivers out of the installers temp directory.
#Philips ehome infrared receiver windows#
After unpacking the files it would close saying that I had the wrong version of Windows as it was looking for the Media Center edition.
#Philips ehome infrared receiver update#
I downloaded the Update Rollup 2 for eHome Infrared Receiver for Windows XP Media Center Edition 2005 (KB912024) and tried to install that.
#Philips ehome infrared receiver windows 7#
Out of the box the receiver works fine with Vista and Windows 7 as it is supported natively. To be honest Windows XP actually hated the AIM remote receiver and refused to install it. I thought I’d cover what I did here so others can try it out. I’ve tweaked it as much as I can and have reached a point where I am moderately happy with it. It would take 3-4 button presses to get a response.
![philips ehome infrared receiver philips ehome infrared receiver](https://blog.turboturbo.net/wp-content/uploads/2016/09/IRPowerOnATtiny.png)
When I tested it though the remote was extremely sluggish slow. After about 4-5 buttons it then said it knew the rest already and that was it. The Harmony software didn’t recognise it at first and asked me to input a few buttons from the original remote. I tried to set it up on my Harmony One remote as I have with other remotes but this one was undetected. Bought an AIM RC118 MCE remote from Maplins that works fine with the system. I switched from using a crappy D-Link WDTV-Live to using HDMI over ethernet with IR pass through so that I could use XBMC.