JP1.x USB cable (Prolific) on Windows 10

DDE12 · Post by **DDE12** » Sat Apr 30, 2016 6:09 pm

I recently upgraded from XP to Windows 10 64 bit and have lost the ability to communicate with my OCAP 5 remote. I am not entirely sure what cable I have, so I will describe my setup to hopefully avoid misidentification and going down the wrong solution path. The cable is a 6 pin female at one end and USB at the other. There are no LED lights. I have a Silver Atlas OCAP 5 (1056B01). When I plug the cable into USB port, Windows device manager shows it under Ports (COM & LPT) as Prolific USB-to-serial Port (COM3). This gives Code 10 (device cannot start). I tried the procedure described in the Wpd64bit.zip but I do not have a USB IO Controller listed under Universal Serial Bus controllers. I would greatly appreciate some guidance in sorting this out so that I can communicate with my remote in IR again.

3FG · Post by **3FG** » Sat Apr 30, 2016 7:30 pm

WPD64bit.zip is only intended for use with the very old Delcom interface to JP1 remotes. You have a flash remote and a USB to Serial interface, so please don't try to use wpd64bit. It cannot help and might mess things up.

This is a driver issue associated with Prolific (or more likely fake Prolific) chips. Googling "prolific usb to serial code 10" generates lots of hits.
http://www.prolific.com.tw/US/ShowProdu ... 25&pcid=41
It may be that you have an older chip which is no longer supported, or a counterfeit. If eventually it turns out that you need to replace your interface, I strongly recommend that you get a genuine FTDI chip.

doctorwizz · Post by **doctorwizz** » Sat May 07, 2016 6:31 pm

You just need the 3.2.0.0 from 2007 version of the driver. The version that win 8 and win 10 installs does not work.
Use this and don't update it. If it updates, roll back.
http://www.mediafire.com/download/jhf7n ... TALLER.zip

DDE12 · Post by **DDE12** » Thu May 12, 2016 10:53 pm

The driver in doctorwizz's post worked. I had to uninstall and delete drivers twice before version 3.2.0.0 showed up. Thank you very much for the help.

bbking67 · Post by **bbking67** » Thu Apr 26, 2018 6:48 pm

This works. Thanks for posting--I thought I had a bad cable!

Weird that downgrading to an 11 year old driver works...

doctorwizz · Post by **doctorwizz** » Thu Apr 26, 2018 7:06 pm

Yep, still the only driver that works

209 downloads

Post by **The Robman** » Thu Apr 26, 2018 9:30 pm

Just in case the file ever disappears from mediafire, I have saved a copy here:
https://www.hifi-remote.com/forums/dload ... e_id=25191