JP1 or JP1x
Back to IR Help
Our tools only work with some of the many remotes manufactured by Universal Electronics (UEI). These remotes have a 6-pin connector or a space for 6-pin connector on the circuit board. Prior to 2004, if you opened up that battery compartment and saw that 6-pin connector, that was all you needed to know. It's not that simple any more. Prior to about 2004, all remotes used a separate memory chip (EEPROM) for programmable data. We have always called these JP1 remotes because that was the original designation of the 6-pin connector marked on the PCB. Remotes currently manufactured use newer technology, flash microcomputers. These omit the EEPROM in favor of using part of the flash RAM to store programmable data.
There is a tendency to refer to the entire population of remotes we deal with as JP1 remotes, which can be quite misleading. Only EEPROM remotes are JP1 remotes. Flash remotes are either JP1.1, JP1.2, JP1.3. That is an important distinction because not all interfaces will talk to all UEI remotes. Communications with a FLASH chip is very different than communications with an EEPROM and requires a different type of interface.
Determining which type of remote you have can be quite difficult. Just because the PCB might say JP1, doesn't mean you have a JP1 EEPROM remote. There are plenty of JP1.2 and JP1.3 remotes that say JP1 on the PCB. However if it says JP1.1, JP1.2 or JP1.3 you probably have a flash remote. JP1.1 remotes have very limited support, and have very special communications needs, so you might be better off picking another remote.
Before you buy or make an interface you should determine which type of remote you have. If you are not sure what type of remote you have, try looking it up in the Chart of Remotes. If you can’t find your model in the chart, post a question on the forum.
JP1 remotes employ an EEPROM memory, which uses the I2C protocol for reading and writing. The remote microprocessor is not involved when IR.exe communicates with the EEPROM. The computer generates and receives I2C data by:
- using a parallel port and some interface electronics to the 6-pin.
- by using a serial port and some different interface electronics.
- by using a Delcom microprocessor (and interface electronics) connected to the computer by a USB port. The Delcom micro translates USB packets to the I2C protocol. A device driver is needed for IR.exe to communicate with the Delcom micro. Computers running 32 bit Windows with a UHCI USB host controller can typically use the Delcom supplied driver should use WdpIntel (32 bit) or WdpAMD (64 bit) drivers.
- By using 3) below combined with a JP1 adapter.
For both 1) and 2) (simple interfaces), gwiopm.sys is used to allow IR.exe to send/receive the I2C protocol by directly manipulating the pins of the port.
JP1.2/1.3 remotes use flash memory. IR.exe interacts with the microprocessor in the remote which does the actual read/write of the flash memory. Communication with the remote's micro employs a serial protocol similar to the ubiquitous RS-232.
IR can use:
- a serial port with some interface electronics to the 6-pin. Hardware built into the serial port generates the bit streams in the correct format, and the driver is included in the OS.
- A USB port equipped with a USB to Serial converter, which may require a driver, or it may be included in the OS. The converter formats the bits. Interface 1) plugs into the converter.
- A USB to Serial converter with additional interface electronics to the 6-pin. The converter formats the bits. A driver may be required, or included in the OS.
For all of the 1.2/1.3 scenarios, IR.exe thinks it is communicating via a serial port, and it uses JP12serial.DLL to do that. I believe that IR.exe requires that both JP12serial.DLL and gwiopm.sys are present even if they won't be used.
Besides those, drivers may be required to support the Delcom interface (only used with JP1) or to support a USB to Serial converter (JP1.2/1.3 only), or for an integrated USB to Serial converter and interface electronics (e.g. Tommy Tyler's JP1.2/3 interface cable.)
