JP1 Remotes

I have a new interface arrived and downloaded the D2XX USB Drivers from 'the Robman's link but am having trouble installing the drivers and getting the thing to work with my URC7960. I have tried the installation process and I have also tried pointing Windows device to the driver location both in XP then WIndows 7 to no avail.
Can anyone help please?

Please post a link to the cable you bought. If it's an FTDI, you don't need to load any drivers since they're built-in to the OS. If it's a Prolific or TIAO like DIYGadget sells, you need the Prolific or TIAO drivers from their site. If the driver loads but RMIR doesn't work, then you picked the wrong interface in RMIR. If all the above is correct, you may have low batteries or have the cable plugged in upside down. If all that fails, you may have a hardware problem.

Thanks, I purchased this
http://www.ebay.co.uk/itm/221268958900? ... 1439.l2649

Earlier Windows 8 on my laptop installed drivers for it but it still isn't working as I get a 'JP12 read failed 0' message if I try to download from the remote. If I do an interface check it says 'the remote interface check succeeded!

Windows XP on my desktop doesn't install the driver and I have to do it manually.

I cant see an RDF for that remote either.

Regards

Sounds like you may have the wrong version of RM. Make sure you get 2.02a.

For the RDF/Map/Image, get this first: https://www.hifi-remote.com/forums/dload ... e_id=10761

Then overwrite with this: https://www.hifi-remote.com/forums/dload ... e_id=10759

Thanks mdavej but I have tried that and still get the same '...read failed' message. What else could be wrong?

Your first post mentions D2XX drivers from "Rob's link". D2XX drivers are intended for FTDI chips, but they aren't the correct drivers for our software. Instead our software needs VCP drivers. But Win8 should already have the correct drivers built-in for FTDI chips. If not, the latest and best FTDI drivers are at http://www.ftdichip.com/FTDrivers.htm. If you have actually installed D2XX drivers, these need to be uninstalled first.

So what chipset do you have? In XP, ControlPanel/System/Hardware/Device Manager/Ports/Properties should tell you if the chip has been recognized and who makes it.

Once it looks like you have a functioning USB to RS-232 interface. check its operation using Tommy's instructions on how to identify a remote. If the remote doesn't respond correctly, probably the interface cable is bad.

Just noticed there is a error in the device list against that item. It is 'Prolific USB-to-Serial Comm Port (COM3)' with error 'The device cannot start. (Code 10). A device which does not exist was specified.

This is on the Windows 8 laptop where I didn't manually install any drivers but allowed Windows to do it.

Tried different USB ports but its the same

This means you have the wrong drivers. You need to find some Prolific drivers. Ask the cable vendor what drivers to use.

Thanks mate. I eventually found that the drivers had windows 8 issues so I switched to a windows 7 system and the drivers show fine. I have the correct RDFs and latest IR and though the remote flashes I still have the same 'JP12 read failed 0'.
Is there anything else that could be wrong?

IIRC, some of those Prolific cables don't work with JP1.2 remotes. If I were you, I'd get an FTDI cable. They're usually about $8 US shipped worldwide and proven to work.

Any links please?

The one in this post is a good one:
https://www.hifi-remote.com/forums/viewt ... 649#p108649

I have contacted the seller of my current cable and he indicates that it works with JP1.2 and 1.3 so Im foxed as to what can be wrong.

Did you you check the interface using Tommy's instructions as I mentioned a week ago? If manipulating the RTS line makes the remote go in and out of programming mode, but it doesn't provide the correct identification, then the interface cable itself is defective.

Ube_Astard wrote:I have contacted the seller of my current cable and he indicates that it works with JP1.2 and 1.3 so Im foxed as to what can be wrong.

Sorry, I meant to say JP1.4/JP2. That's what your remote is, not JP1.2/JP1.3. Ask your vendor again. Also try 3FG's suggestion.

Do you have any JP1.3 remotes you could try?