View previous topic :: View next topic |
Author |
Message |
DDE12
Joined: 13 Oct 2014 Posts: 82 Location: United States |
Posted: Sat Apr 30, 2016 7:09 pm Post subject: JP1.x USB cable (Prolific) on Windows 10 |
|
|
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. |
|
Back to top |
|
|
3FG Expert
Joined: 19 May 2009 Posts: 3367
|
Posted: Sat Apr 30, 2016 8:30 pm Post subject: |
|
|
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/ShowProduct.aspx?p_id=225&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. |
|
Back to top |
|
|
doctorwizz
Joined: 25 May 2005 Posts: 23
|
|
Back to top |
|
|
DDE12
Joined: 13 Oct 2014 Posts: 82 Location: United States |
Posted: Thu May 12, 2016 11:53 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
bbking67
Joined: 06 Mar 2005 Posts: 9
|
Posted: Thu Apr 26, 2018 7:48 pm Post subject: |
|
|
This works. Thanks for posting--I thought I had a bad cable!
Weird that downgrading to an 11 year old driver works... |
|
Back to top |
|
|
doctorwizz
Joined: 25 May 2005 Posts: 23
|
Posted: Thu Apr 26, 2018 8:06 pm Post subject: |
|
|
Yep, still the only driver that works
209 downloads |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21239 Location: Chicago, IL |
|
Back to top |
|
|
|