JP1 Remotes

I have posted IR 8.03 Beta 5. This is the first public Beta version of IR 8.03, the earlier betas were privately distributed for testing during development. Its main new features are:

* Improved support for JP1 (as distinct from JP1.x) remotes, including support for 64-bit versions of Windows.

* Ability to import and export learned signals in Pronto format,

* A new Analysis display on the learned signals page, which shows the signal in IRP notation. This is derived directly from the signal. No look-up is involved, so it should work with a wide variety of protocols even if they are not recognised by DecodeIR.

The import, export and analysis features are provided by ExchangeIR.dll. This is a new DLL that is now included in the IR.exe distribution. The current version is v0.05.

The improved support for JP1 remotes comes in two forms. First, the package includes version 0.16 of jp12serial.dll. This version supports the JP1 EEPROM Programming Adapter that enables uploads and downloads of JP1 remotes to be performed with JP1.x interfaces and software. Secondly, the library routines that support the JP1 interface have been substantially rewritten by Dave Reed (3FG). The interface cables for these remotes use a Delcom chip and need an installed driver. The Delcom drivers have proved not to be very reliable and they do not support 64-bit versions of Windows. The new library routines compensate for some of the problems of the Delcom driver when used with 32-bit systems and they also support a WinUSB driver for the Delcom chip that does work with 64-bit systems. The initial development of these new routines is discussed here, but the work has continued and is now ready for the wider testing that its inclusion in this Beta should provide.

Import of signals in Pronto format is available through the Add and Edit buttons of the Learned Signals page. The dialog that then opens now has radio buttons to choose between UEI Learned and Pronto formats, UEI Learned being the standard learned format of UEI remotes. Switching the format has no effect on the data in the Add/Edit window. Instead, it tells the import software how this data is to be interpreted when the OK button is pressed.

Pronto export is available through a new Export Pronto button on the Learned Signals page. Pressing this button will append the Pronto format of each signal selected in the left-hand pane (multiple selections are allowed) to a text file called ExportedPronto.txt. This file is created if it does not exist. The directory for this file can be set by a new entry, Set Export Path, on the File/Set Directory menu.

Information about the Analysis feature can be found in the thread Automated analysis of IR protocols where it is illustrated in the context of IRScope 2.01 Beta 3, which was the first program to make use of this new feature.
_________________
Graham

If you wish to try IR8.03 Beta 5 with WinUSB drivers, the installation instructions are a short download. The WinUSB driver is about 7 Mbytes, and there are 32 bit and 64 bit versions. [I've revised the link names in response to later posts in this thread.]
Note that the drivers were posted here in January 2010, and the drivers have not changed since then, so users who already downloaded the drivers need not download again. The instructions and supporting information have been considerably streamlined and are the only content that has changed.

Here’s the text of the FAQ (also available in the instructions download):

Why use the WinUSB driver?
There are two situations in which the WinUSB driver may help.
1. The Delcom-provided drivers can't be installed, typically because the target computer is running 64bit Windows.
2. The Delcom driver is installed, but gives errors, typically because the computer has a OHCI type USB host controller rather than UHCI.

Is it safe to install the WinUSB driver?
The WinUSB driver was written by Microsoft, and is supposed to work with Windows 7, Vista, and XP (32 bit only) with Service Pack 2 or better.
The JP1 community has generated the necessary inf and cat files to allow associating the WinUSB driver with the Delcom interface.

The WinUSB download is 7 MBytes! How much room does the driver take?
Less than 50 KBytes. The installation package is big because it provides different drivers for each version of the operating system, the bit size of the CPU and OS, and other variations.

What's OHCI and UHCI and why should I care?
Open Host Controller Interface and Universal Host Controller Interface are competing hardware implementations of USB host controllers. In principle, any USB device should work with either, but apparently the Delcom interface has a firmware bug which gives frequent errors when the computer reads data from some OHCI-based hubs. Most of the work to make IR.exe work with WinUSB has been spent trying to tame the OHCI related problems.

If your computer has an UHCI hub (or both, but you plug into a port which is serviced by an UHCI hub) then you should expect error free performance. Actually, a Delcom driver should also work if it can be properly installed. If your computer has an OHCI hub, then probably IR.exe will work with infrequent errors. However, we know that for some circumstances, it may not work. At this point little is known about the behavior for EEPROMs smaller or larger than 2K Bytes.

Do I have OHCI or UHCI?
Click Windows Start. Type devmgmt.msc in the Search Box (use Run in XP) and press Enter.
Click the plus sign next to Universal Serial Bus Controllers. Ignore the entries which say Enhanced Controller and look for either Open Host or Universal Host.

I have the Delcom driver already installed. Do I need to remove it?
No. In fact you can switch between the Delcom driver and the WinUSB driver by starting at instruction 3 in the file WinUSB Installation Instructions.rtf. The WinUSB driver is called "Delcom Proxy", and the Delcom driver is called "Delcom USB IO Driver".

I'm trying to test this new beta out but am running into issues. First, when I edit a learned signal or try to add one, the Pronto radio button is not selectable. Secondly, when I look at a learned signal, it's says "Analyzer: Not available" and "N/A" on the IRP form line.

Am I doing something wrong?

Btw, I'm testing this on a WinXP Pro box (version 5.1, SP3) without admin rights.

The Robman wrote:I'm trying to test this new beta out but am running into issues. First, when I edit a learned signal or try to add one, the Pronto radio button is not selectable. Secondly, when I look at a learned signal, it's says "Analyzer: Not available" and "N/A" on the IRP form line.

These symptoms all mean that ExchangeIR.dll has not been loaded. I presume you have this in the same folder as IR.exe, so it appears to be the same issue that Calisoto encountered with IRScope, reported on this page. He also found the solution (same page):

calisoto wrote:I have found that, in order to load all the dlls, the Microsoft C++ Runtime Library 2008 vcredist_x86.exe is required.

I don't understand this, as it is compiled with the same compiler and options as DecodeIR.dll. Also, it doesn't seem to be a problem running the DLL, but with loading it. I suppose it has to be some feature of Visual C++ that I am using that isn't used in DecodeIR, but I can't understand how that can stop the DLL from actually loading. I meant to investigate further, but haven't yet got round to it. I hoped it was a rare problem, as no-one else who has tested IRScope has encountered it.
_______________
Graham

Unfortunately, I can't install vcredist_x86.exe on this computer as I don't have admin rights (work PC) so I'll have to test it at home.

3FG wrote:If you wish to try IR8.03 Beta 5 with WinUSB drivers, the installation instructions are a short download. The WinUSB driver is about 7 Mbytes, and there are Intel and AMD versions.
Note that the drivers were posted here in January 2010, and the drivers have not changed since then, so users who already downloaded the drivers need not download again. The instructions and supporting information have been considerably streamlined and are the only content that has changed.

3FG: I am following the installation instructions for the WdpIntel delcom proxy driver exactly, and cannot get it to install. Following the directions in your installation guide all goes pretty well up until:

9. Install From Disk dialog box appears. Click the Browse... button.
a. Navigate to the location of WdpAMD or WdpIntel.
b. Click on "JP1del.inf" and click on the Open button.
c. Click on OK in the Install From Disk window.

10. Click on Delcom Proxy and click on Next.

11. The Delcom Proxy Driver has not passed Logo Testing. Click Continue anyway or Yes.

After step 10, I get this message:

which is not addressed in your step 11 (or subsequently). There is no "continue" or "Yes" option available. Just "Close".

I have a Intel (R) Core (TM)2 Duo CPU T6400 @2.00GHz;
I am running Windows 7 Ultimate (64-bit)

What am I doing wrong?

Well, taking the message at face value, perhaps a file is missing. I'm not at the correct computer, but I believe the directory should contain the files jp1del.inf and jp1del.cat, besides the 2 rtf text files. It should also contain the subdirectory X86.
Is that what you have?

Capn Trips wrote:After step 10, I get this message: ... which is not addressed in your step 11 (or subsequently). There is no "continue" or "Yes" option available. Just "Close".

I have a Intel (R) Core (TM)2 Duo CPU T6400 @2.00GHz;
I am running Windows 7 Ultimate (64-bit)

What am I doing wrong?

Probably nothing other than UAC issue. Have you figured a way to install as Administrator?
Is there, somewhere in the windows directory a file called setupAPI.log or .txt? Try to find it. Likely what windows is objecting to might be listed there in a very non-plain English such as this nightmare from Windows XP (I hightlighted few files and things that happen)

[2010/03/28 16:09:01 424.2]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line: rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{2750431D-E3DF-4208-A5B0-A927631881F8}
#I060 Set selected driver.
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_0010,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device.
#I060 Set selected driver.
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_0010,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_0010,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#I022 Found "USB\VID_0FC5&PID_1222" in s:\jp1\winusb\trydistintel\JP1Del.inf; Device: "Delcom Proxy"; Driver: "Delcom Proxy"; Provider: "hifi-remote.com"; Mfg: "hifi-remote.com"; Section name: "USB_Install".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [USB_Install]. Rank: 0x00008001. Effective driver date: 01/11/2010.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [USB_Install] in "s:\jp1\winusb\trydistintel\jp1del.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "USB\VID_0FC5&PID_1222\5&2122BCE5&0&2".
#E366 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\jp1del.cat" for driver "Delcom Proxy" will be installed (Policy=Warn, user said ok). Error 0x800b0100: No signature was present in the subject.
#W187 Install failed, attempting to restore original files.
#E362 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\jp1del.cat" for driver "Delcom Proxy" will be installed (Policy=Warn). Error 0x800b0100: No signature was present in the subject.
#-024 Copying file "s:\jp1\winusb\trydistintel\x86\WinUSBCoInstaller2.dll" to "C:\WINDOWS\system32\WinUSBCoInstaller2.dll".
#E362 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\x86\WinUSBCoInstaller2.dll" for driver "Delcom Proxy" will be installed (Policy=Warn). Error 0x800b0100: No signature was present in the subject.
#-336 Copying file "s:\jp1\winusb\trydistintel\x86\WdfCoInstaller01009.dll" to "C:\WINDOWS\system32\WdfCoInstaller01009.dll" via temporary file "C:\WINDOWS\system32\SET18D.tmp".
#E362 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\x86\WdfCoInstaller01009.dll" for driver "Delcom Proxy" will be installed (Policy=Warn). Error 0x800b0100: No signature was present in the subject.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [USB_Install.Interfaces] from "s:\jp1\winusb\trydistintel\jp1del.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0FC5&PID_1222\5&2122BCE5&0&2".
#E362 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\JP1Del.cat" for driver "Delcom Proxy" will be installed (Policy=Warn).
Error 0x800b0100: No signature was present in the subject.
#I121 Device install of "USB\VID_0FC5&PID_1222\5&2122BCE5&0&2" finished successfully.

3FG wrote:Well, taking the message at face value, perhaps a file is missing. I'm not at the correct computer, but I believe the directory should contain the files jp1del.inf and jp1del.cat, besides the 2 rtf text files. It should also contain the subdirectory X86.

Code: Select all

01/12/2010  10:58 PM             2,637 jp1del.cat
01/12/2010  10:58 PM             1,912 JP1Del.inf
05/02/2010  11:01 PM             2,926 WinUSB FAQ.rtf
05/02/2010  11:22 PM             7,678 WinUSB Installation Instructions.rtf
05/05/2010  01:16 PM    <DIR>          x86


There should be 6 files in X86:
07/14/2009  01:27 PM         1,461,992 WdfCoInstaller01009.dll
07/14/2009  11:49 AM           824,040 WdfCoInstaller01009_chk.dll
07/14/2009  07:25 AM           851,176 winusbcoinstaller2.dll
07/14/2009  07:20 AM           685,288 winusbcoinstaller2_chk.dll
07/14/2009  01:21 PM         1,837,296 WUDFUpdate_01009.dll
07/14/2009  11:43 AM         1,128,176 WUDFUpdate_01009_chk.dll

Is that what you have?

Got 'em all.

ElizabethD wrote:

Capn Trips wrote:After step 10, I get this message: ... which is not addressed in your step 11 (or subsequently). There is no "continue" or "Yes" option available. Just "Close".

I have a Intel (R) Core (TM)2 Duo CPU T6400 @2.00GHz;
I am running Windows 7 Ultimate (64-bit)

What am I doing wrong?

Probably nothing other than UAC issue. Have you figured a way to install as Administrator?
Is there, somewhere in the windows directory a file called setupAPI.log or .txt? Try to find it. Likely what windows is objecting to might be listed there in a very non-plain English such as this nightmare from Windows XP (I hightlighted few files and things that happen)

[2010/03/28 16:09:01 424.2]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line: rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{2750431D-E3DF-4208-A5B0-A927631881F8}
#I060 Set selected driver.
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_0010,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device.
#I060 Set selected driver.
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_0010,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_0010,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#I022 Found "USB\VID_0FC5&PID_1222" in s:\jp1\winusb\trydistintel\JP1Del.inf; Device: "Delcom Proxy"; Driver: "Delcom Proxy"; Provider: "hifi-remote.com"; Mfg: "hifi-remote.com"; Section name: "USB_Install".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [USB_Install]. Rank: 0x00008001. Effective driver date: 01/11/2010.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [USB_Install] in "s:\jp1\winusb\trydistintel\jp1del.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "USB\VID_0FC5&PID_1222\5&2122BCE5&0&2".
#E366 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\jp1del.cat" for driver "Delcom Proxy" will be installed (Policy=Warn, user said ok). Error 0x800b0100: No signature was present in the subject.
#W187 Install failed, attempting to restore original files.
#E362 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\jp1del.cat" for driver "Delcom Proxy" will be installed (Policy=Warn). Error 0x800b0100: No signature was present in the subject.
#-024 Copying file "s:\jp1\winusb\trydistintel\x86\WinUSBCoInstaller2.dll" to "C:\WINDOWS\system32\WinUSBCoInstaller2.dll".
#E362 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\x86\WinUSBCoInstaller2.dll" for driver "Delcom Proxy" will be installed (Policy=Warn). Error 0x800b0100: No signature was present in the subject.
#-336 Copying file "s:\jp1\winusb\trydistintel\x86\WdfCoInstaller01009.dll" to "C:\WINDOWS\system32\WdfCoInstaller01009.dll" via temporary file "C:\WINDOWS\system32\SET18D.tmp".
#E362 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\x86\WdfCoInstaller01009.dll" for driver "Delcom Proxy" will be installed (Policy=Warn). Error 0x800b0100: No signature was present in the subject.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [USB_Install.Interfaces] from "s:\jp1\winusb\trydistintel\jp1del.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0FC5&PID_1222\5&2122BCE5&0&2".
#E362 An unsigned or incorrectly signed file "s:\jp1\winusb\trydistintel\JP1Del.cat" for driver "Delcom Proxy" will be installed (Policy=Warn).
Error 0x800b0100: No signature was present in the subject.
#I121 Device install of "USB\VID_0FC5&PID_1222\5&2122BCE5&0&2" finished successfully.

I'm logged in as Admin. Tried to right-click at every step to select "Run as Admin" options, but none were ever available.

No SetupAPI.* file is present.

I believe that for both Vista and Win7 the logs are:

• Setupapi.dev.log. This file contains logging information from Device Management and Installation (DMI) components specific to device installs. This is the primary log that should be used for most troubleshooting investigations.
• Setupapi.app.log. This file contains legacy Setupapi logging information unrelated to device installs, such as associated application events.

These files are simple ANSI text logs that are written to the %windir%\inf directory.

So typically, C:\Windows\inf\setupapi.dev.log.

Capn Trips wrote:I am following the installation instructions for the WdpIntel delcom proxy driver exactly, and cannot get it to install. Following the directions in your installation guide all goes pretty well up until........

I have a Intel (R) Core (TM)2 Duo CPU T6400 @2.00GHz;
I am running Windows 7 Ultimate (64-bit)

What am I doing wrong?

Intel = 32 bit drivers
AMD = 64 bit drivers

You are running Windows 7 64 bit, so use the AMD driver package.

3FG wrote:What's OHCI and UHCI and why should I care?
Open Host Controller Interface and Universal Host Controller Interface are competing hardware implementations of USB host controllers. In principle, any USB device should work with either, but apparently the Delcom interface has a firmware bug which gives frequent errors when the computer reads data from some OHCI-based hubs. Most of the work to make IR.exe work with WinUSB has been spent trying to tame the OHCI related problems.

Using a high speed hub may fix problems with OHCI contollers. The hub will communicate with the computer's EHCI (high speed) controller and communicate with the Delcom chip using the low speed protocol. The hub may work better than the OHCI controller in the computer. It could also be worse or not significanly different. The only way know it to try it.

The hub must be high speed (marketed as "USB 2.0") and the computer must have a high speed (EHCI) controller.

Kevin Timmerman wrote:

Capn Trips wrote:I am following the installation instructions for the WdpIntel delcom proxy driver exactly, and cannot get it to install. Following the directions in your installation guide all goes pretty well up until........

I have a Intel (R) Core (TM)2 Duo CPU T6400 @2.00GHz;
I am running Windows 7 Ultimate (64-bit)

What am I doing wrong?

Intel = 32 bit drivers
AMD = 64 bit drivers

You are running Windows 7 64 bit, so use the AMD driver package.

SUCCESS!

Except the instructions need to be updated and/or zipfiles renamed to preclude the confusion I had. I have an Intel processor, but the AMD driver zip file works for me.

Thanks to all for the marvelous work! Now my ultra-sleek Tommy Tyler JP1 USB cable can continue doing great service for me on my new laptop.

Well, I'm glad that you got it installed. It's my confusion, not yours--in fact, I'm still confused. The original installation package was built with both AMD64 and X86 subdirectories, and I split them apart to try to reduce the size of the download. Maybe that was the wrong thing to do.

But the bigger question is: Does your JP1 interface work? And please look to see if you have UHCI or OHCI. I'd also like to know the EEPROM size.

Thanks.