What isn't in the IR.zip file that is needed for communications?
JP1 - gwiopm.sys
Jp1.x - JP12serial.DLL
We used to need the delcom driver that came with our cable to run jp1.usb, is that superceded by the wpaIntel and wpaADM files found in the main system?
I have in my notes that I need USBIOds.sys, but that doesn't appear to be around any more, is that something that died away after IR7?
What isn't in the IR bundle?
Moderator: Moderators
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
What isn't in the IR bundle?
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
gwiopm.sys is the driver for eeprom remotes hooked to parallel port. Any old version does the job far as I recall & still use it.
don't know about jp12serial
May have been replaced by the FTDI drivers which work jp1.3 and eeprom if you have the little adapter
delcom, goodby forever for me, 3FG burried it
The current distribution provides WinUSB which takes care of the stuff. If your delcom driver worked for you, then I think WinUSB will see it and use it.
I'm not sure I answered your question
don't know about jp12serial
May have been replaced by the FTDI drivers which work jp1.3 and eeprom if you have the little adapter
delcom, goodby forever for me, 3FG burried it
I'm not sure I answered your question
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Let me try to be a little clearer
zipped in with IR are
gwiopm.sys
jp12serial.dll
That should be the flash and jp1 simple interface support.
Then in the Main Tools we have
USB JP1 (EEPROM) Cable Driver (10/19/2006)
USB JP1 (EEPROM) Cable Driver (2/12/2008)
USB JP1 (EEPROM) Cable Driver (3/3/2007)
I think Rob moved them there when we were trying to figure out why some people were having trouble with the delcom driver when we were running a poll to figure out where are problem was. Found out it was something in the way some windows were having USB, but are these still necessary? Should they be moved to the archived tools folder?
And then these are the replacement drivers for 32 and 64 bit drivers for the delcom drivers. (I don't understand what that means, since all I know is I have a serial JP1.x cable, a USB JP1 2/3 cable, and a SIMPLE interface and a USB JP1 cable, but how in the heck do I know what needs a delcom driver? I have absolutely no idea of what is actually in the cable.
WdpAMD.zip
WdpIntel.zip
So what does a newbie have to download to run IR to upload and download their remote?
zipped in with IR are
gwiopm.sys
jp12serial.dll
That should be the flash and jp1 simple interface support.
Then in the Main Tools we have
USB JP1 (EEPROM) Cable Driver (10/19/2006)
USB JP1 (EEPROM) Cable Driver (2/12/2008)
USB JP1 (EEPROM) Cable Driver (3/3/2007)
I think Rob moved them there when we were trying to figure out why some people were having trouble with the delcom driver when we were running a poll to figure out where are problem was. Found out it was something in the way some windows were having USB, but are these still necessary? Should they be moved to the archived tools folder?
And then these are the replacement drivers for 32 and 64 bit drivers for the delcom drivers. (I don't understand what that means, since all I know is I have a serial JP1.x cable, a USB JP1 2/3 cable, and a SIMPLE interface and a USB JP1 cable, but how in the heck do I know what needs a delcom driver? I have absolutely no idea of what is actually in the cable.
WdpAMD.zip
WdpIntel.zip
So what does a newbie have to download to run IR to upload and download their remote?
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
WdpAMD.zip is drivers for 64 bit computers
WdpIntel.zip is drivers for 32 bit computers
That's my understanding; 3FG can tell you more
I don't know the answer for the others except gwiopm.sys which I already covered.
WdpIntel.zip is drivers for 32 bit computers
That's my understanding; 3FG can tell you more
I don't know the answer for the others except gwiopm.sys which I already covered.
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
JP1 remotes employ a 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:
1) using a parallel port and some interface electronics to the 6 pin.
2) by using a serial port and some different interface electronics.
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.
3) 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; others should use WdpIntel (32 bit) or WdpAMD (64 bit) drivers.
4) By using 3) below combined with a JP1 adapter.
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:
1) 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.
2) 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.
3) 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/1.3 interface cable.)
I believe that the IR distribution includes JP12serial.DLL and gwiopm.sys. The user is responsible for recognizing that additional drivers may be needed and to obtain/install the drivers.
1) using a parallel port and some interface electronics to the 6 pin.
2) by using a serial port and some different interface electronics.
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.
3) 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; others should use WdpIntel (32 bit) or WdpAMD (64 bit) drivers.
4) By using 3) below combined with a JP1 adapter.
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:
1) 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.
2) 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.
3) 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/1.3 interface cable.)
I believe that the IR distribution includes JP12serial.DLL and gwiopm.sys. The user is responsible for recognizing that additional drivers may be needed and to obtain/install the drivers.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
First off, I'd like to make a suggestion. Could we rename these files towWdpAMD.zip is drivers for 64 bit computers
WdpIntel.zip is drivers for 32 bit computers
WdpADM64.zip
WdpIntel32.zip
That would make it so you didn't have to jump up and down a layer to figure out what you need.
Thanks Dave, that's quit informative. I have absolutely no electronics back ground, and actually have a 'hardware-phobia'. How I ever got caught up in JP1-itus, is a mystery to everyone I know.3FG wrote:JP1 remotes employ a 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:
1) using a parallel port and some interface electronics to the 6 pin.
2) by using a serial port and some different interface electronics.
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.
3) 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; others should use WdpIntel (32 bit) or WdpAMD (64 bit) drivers.
4) By using 3) below combined with a JP1 adapter.
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:
1) 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.
2) 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.
3) 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/1.3 interface cable.)
I believe that the IR distribution includes JP12serial.DLL and gwiopm.sys. The user is responsible for recognizing that additional drivers may be needed and to obtain/install the drivers.
So following what you are saying would it be fair to say that.
Users of the EEPROM JP1-USB interface, will need to download additional drivers to work with IR. If you bought your interface prior to 2010, you would have recieved instructions to download a delcom driver, but the official delcom drivers are incompatible with newer Windows operating systems, so you'll need to download and install drivers that were written specifically for JP1 USB remote communication.
And are there any specific instructions for people who have installed the delcom drivers and their JP1 remote is unrecognized? Do they need to remove the delcom drivers?
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.