EASYC and RobotC USB Connection problems with 64Bit Windows 7

[davefrederick]

I am a Vex Robotics mentor to 10 students in Manassas, Va.
In the past month (April 2012), two of the students have experienced USB connections problems between their laptops and the Vex Cortex Controllers. The Device Manager indicates the driver could not be started (Error 10).

After some checks, I noticed that both of the hosts are 64 bit Windows 7.

The hosts were able to program the Vex Cortex for many months and then stopped. Tried the usual Microsoft driver resolution process of removing the driver and re-installing. No luck.

Any Ideas on how to resolve this?

I have reviewed the Windows Driver Installation Log (setupapi.dev.log) and attached the last action below?

Any ideas?

Thank you in Advance,
Dave Frederick
Mentor, Manassas VA



>>> [Device Install (Hardware initiated) - USB\VID_067B&PID_2303\6&202fce4a&0&1]
>>> Section start 2012/05/08 10:49:03.614
ump: Creating Install Process: DrvInst.exe 10:49:03.623
ndv: Retrieving device info...
ndv: Setting device parameters...
ndv: Searching just Driver Store...
dvi: {Build Driver List} 10:49:03.712
cpy: Policy is set to make all digital signatures equal.
dvi: Enumerating INFs from path list 'C:\Windows\INF'
inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository

\ser2pl.inf_amd64_neutral_2d105b2c9e5e9abe\ser2pl. inf' ([strings])
dvi: Created Driver Node:
dvi: HardwareID - USB\VID_067B&PID_2303
dvi: InfName - C:\Windows\System32\DriverStore\FileRepository

\ser2pl.inf_amd64_neutral_2d105b2c9e5e9abe\ser2pl. inf
dvi: DevDesc - Prolific USB-to-Serial Comm Port
dvi: DrvDesc - Prolific USB-to-Serial Comm Port
dvi: Provider - Prolific
dvi: Mfg - Prolific
dvi: ModelsSec - PRO.NTAMD64
dvi: InstallSec - ComPort
dvi: ActualSec - ComPort.NTAMD64
dvi: Rank - 0x00ff0001
dvi: Signer - Microsoft Windows Hardware Compatibility Publisher
dvi: Signer Score - WHQL
dvi: DrvDate - 07/17/2009
dvi: Version - 3.3.5.122
inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository

\ser2pl.inf_amd64_neutral_e0e24ed5af01cfc3\ser2pl. inf' ([strings])
dvi: Created Driver Node:
dvi: HardwareID - USB\VID_067B&PID_2303
dvi: InfName - C:\Windows\System32\DriverStore\FileRepository

\ser2pl.inf_amd64_neutral_e0e24ed5af01cfc3\ser2pl. inf
dvi: DevDesc - Prolific USB-to-Serial Comm Port
dvi: DrvDesc - Prolific USB-to-Serial Comm Port
dvi: Provider - Prolific
dvi: Mfg - Prolific
dvi: ModelsSec - PRO.NTAMD64
dvi: InstallSec - ComPort
dvi: ActualSec - ComPort.NTAMD64
dvi: Rank - 0x00ff0001
dvi: Signer - Microsoft Windows Hardware Compatibility Publisher
dvi: Signer Score - WHQL
dvi: DrvDate - 10/27/2008
dvi: Version - 3.3.2.105
dvi: {Build Driver List - exit(0x00000000)} 10:49:03.929
ndv: Selecting best match from just Driver Store...
dvi: {DIF_SELECTBESTCOMPATDRV} 10:49:03.930
dvi: Using exported function 'PortsClassInstaller' in module 'C:\Windows\system32\MsPorts.Dll'.
dvi: Class installer == MsPorts.Dll,PortsClassInstaller
dvi: No CoInstallers found
dvi: Class installer: Enter 10:49:03.935
dvi: Class installer: Exit
dvi: Default installer: Enter 10:49:03.936
dvi: {Select Best Driver}
dvi: Selected driver installs from section [ComPort] in 'c:\windows\system32\driverstore

\filerepository\ser2pl.inf_amd64_neutral_2d105b2c9 e5e9abe\ser2pl.inf'.
dvi: {DIF_DESTROYPRIVATEDATA} 10:49:03.938
dvi: Class installer: Enter 10:49:03.939
dvi: Class installer: Exit
dvi: Default installer: Enter 10:49:03.940
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 10:49:03.941
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [Prolific USB-to-Serial Comm Port]
dvi: InfFile - [c:\windows\system32\driverstore\filerepository

\ser2pl.inf_amd64_neutral_2d105b2c9e5e9abe\ser2pl. inf]
dvi: Section - [ComPort]
dvi: Signer - [Microsoft Windows Hardware Compatibility Publisher]
dvi: Rank - [0x00ff0001]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 10:49:03.948
inf: Opened PNF: 'C:\Windows\INF\oem51.inf' ([strings])
ndv: Searching Windows Update for drivers... 10:49:03.973
ndv: Acquired WU search serialization mutex. 10:49:03.974
ndv: About to release WU search serialization mutex. 10:49:06.657
ndv: Found driver on Windows Update, downloading - 0.1 MB... 10:49:06.660
dvi: {Build Driver List} 10:49:12.264
cpy: Policy is set to make all digital signatures equal.
dvi: Enumerating INFs from path list 'c:\windows\temp\dmiwu\{9e9b71a3-3b9e-4278-9db3-34dc729401fa}'
sig: {_VERIFY_FILE_SIGNATURE} 10:49:12.277
sig: Key = ser2pl.inf
sig: FilePath = c:\windows\temp\dmiwu\{9e9b71a3-3b9e-4278-9db3-34dc729401fa}\ser2pl.inf
sig: Catalog = c:\windows\temp\dmiwu\{9e9b71a3-3b9e-4278-9db3-34dc729401fa}\ser2pl.cat
sig: Success: File is signed in catalog.
sig: {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 10:49:12.336
dvi: Created Driver Node:
dvi: HardwareID - USB\VID_067B&PID_2303
dvi: InfName - c:\windows\temp\dmiwu\{9e9b71a3-3b9e-4278-9db3-34dc729401fa}\ser2pl.inf
dvi: DevDesc - Prolific USB-to-Serial Comm Port
dvi: DrvDesc - Prolific USB-to-Serial Comm Port
dvi: Provider - Prolific
dvi: Mfg - Prolific
dvi: ModelsSec - PRO.NTAMD64
dvi: InstallSec - ComPort
dvi: ActualSec - ComPort.NTAMD64
dvi: Rank - 0x00ff0001
dvi: Signer - Microsoft Windows Hardware Compatibility Publisher
dvi: Signer Score - WHQL
dvi: DrvDate - 04/02/2012
dvi: Version - 3.4.31.231
dvi: {Build Driver List - exit(0x00000000)} 10:49:12.346
ndv: Selecting best match from Windows Update... 10:49:12.346
dvi: {DIF_SELECTBESTCOMPATDRV} 10:49:12.347
dvi: Using exported function 'PortsClassInstaller' in module 'C:\Windows\system32\MsPorts.Dll'.
dvi: Class installer == MsPorts.Dll,PortsClassInstaller
dvi: No CoInstallers found
dvi: Class installer: Enter 10:49:12.350
dvi: Class installer: Exit
dvi: Default installer: Enter 10:49:12.351
dvi: {Select Best Driver}
dvi: Selected driver installs from section [ComPort] in 'c:\windows\temp\dmiwu\{9e9b71a3-3b9e-

4278-9db3-34dc729401fa}\ser2pl.inf'.
dvi: {DIF_DESTROYPRIVATEDATA} 10:49:12.353
dvi: Class installer: Enter 10:49:12.354
dvi: Class installer: Exit
dvi: Default installer: Enter 10:49:12.355
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 10:49:12.356
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [Prolific USB-to-Serial Comm Port]
dvi: InfFile - [c:\windows\temp\dmiwu\{9e9b71a3-3b9e-4278-9db3-

34dc729401fa}\ser2pl.inf]
dvi: Section - [ComPort]
dvi: Signer - [Microsoft Windows Hardware Compatibility Publisher]
dvi: Rank - [0x00ff0001]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 10:49:12.362
inf: {SetupCopyOEMInf: c:\windows\temp\dmiwu\{9e9b71a3-3b9e-4278-9db3-34dc729401fa}\ser2pl.inf} 10:49:12.368
inf: {SetupCopyOEMInf exit (0x00000050)} 10:49:12.376
!!! ndv: Driver Store import failed, failing install.
ump: Server install process exited with code 0x00000002 10:49:12.466
<<< Section end 2012/05/08 10:49:12.475
<<< [Exit status: FAILURE(0x00000002)]

[jpearman]

Originally Posted by davefrederick

I am a Vex Robotics mentor to 10 students in Manassas, Va.
In the past month (April 2012), two of the students have experienced USB connections problems between their laptops and the Vex Cortex Controllers. The Device Manager indicates the driver could not be started (Error 10).

After some checks, I noticed that both of the hosts are 64 bit Windows 7.

The hosts were able to program the Vex Cortex for many months and then stopped. Tried the usual Microsoft driver resolution process of removing the driver and re-installing. No luck.

Any Ideas on how to resolve this?

I have reviewed the Windows Driver Installation Log (setupapi.dev.log) and attached the last action below?

Any ideas?

Thank you in Advance,
Dave Frederick
Mentor, Manassas VA

It looks like you have multiple versions of the prolific driver loaded. Have you recently updated the development software? Are you on EasyC or ROBOTC? (edit: OK, I see both)

These problems can be hard to debug, all I can tell you is the following.

I have a ROBOTC V3.04 installation running under Windows 7 pro 64 bit, the driver I have installed is version 3.3.17.203 which I downloaded from the prolific web site, however, this was back in October last year. Under programs and features it shows as PL-2303 USB to serial version 1.4.17, see if there are any other PL-2303 installations.

I have seen error 10 before but in my case it was a defective programming cable, have you tested the cables on other hardware or do you have a known working cable you can try.

I would try and uninstall all versions of the driver and then start again.

[MarkO]

Originally Posted by davefrederick

I am a Vex Robotics mentor to 10 students in Manassas, Va.
In the past month (April 2012), two of the students have experienced USB connections problems between their laptops and the Vex Cortex Controllers. The Device Manager indicates the driver could not be started (Error 10).

After some checks, I noticed that both of the hosts are 64 bit Windows 7.

The hosts were able to program the Vex Cortex for many months and then stopped. Tried the usual Microsoft driver resolution process of removing the driver and re-installing. No luck.

Any Ideas on how to resolve this?

I have reviewed the Windows Driver Installation Log (setupapi.dev.log) and attached the last action below?

Any ideas?

Thank you in Advance,
Dave Frederick
Mentor, Manassas VA

<< BIG SNIP >>

What Driver is Loading when the Vex USB-to-Ser cable is plugged into the Laptop?? ( Device Manager-->Ports ( COM & LPT )--> Prolific USB to Serial, Double Click and then Click the "Driver" Tab, if it is there.

Your Newest Driver appears to be, DrvDate - 04/02/2012, Version - 3.4.31.231.

I have seen a Code 10, I beleve it was for a Counterfeit Prolific Chip..


In Most Cases, you want the Latest Device Driver installed, in some cases, they don't work right, and an Older version of the Device Driver is better..



================================================== ==============================


Windows 7, Home Premium 64 Bit, SP1 , 6 GB RAM.


My Prolific Drivers are in this Folder, in the DriverStore:

C:\Windows\System32\DriverStore\FileRepository\ser 2pl.inf_amd64_neutral_5a6c8d63ecc6dc7f

The Date/Version is:
DriverVer=03/12/2010,3.3.11.152


I am not currently using the Vex USB-to-Ser cable, because it is too hard to plug and unplug. and the Vex Down-loader Software will "default" to ANY Prolific USB-to-Ser device, even if it is not connected to a Vex Controller.... I am using a Belkin for the Time being..


================================================== ==============================

Check current Driver Version, If possible...

I would try a different Vex USB-to-Ser cable, or find another Prolific based Cable..

Uninstall all related Drivers, and check in the Driverstore to make sure they were removed as well..

Try an Older Driver version to see if it works..

It has been my experience of working with the Prolific USB-to-Ser devices, for over 10 years now, that they will be Broken by MicroSoft, and need to be changed..

( I was working with the Bafo USB-to-Ser even before I got my first Vex Robot, and they were having problems on a regular basses... )

[davefrederick]

D.Frederick
We have resolved the Lapatop (EasyC or RobotC) to VEX Cortex Controller Issue. It appears that the current (2012) driver is not working. I rolled the driver back to the 2008 version and the communications works correctly.

Here are the 64 bit Driver (c:\windows\system32\drivers\ser2pl64.sys) versions and dates.

3.3.2.105 - 2008
3.3.4.122 - 2009
3.4.31.231 – 2012

[MarkO]

Originally Posted by davefrederick

D.Frederick
We have resolved the Lapatop (EasyC or RobotC) to VEX Cortex Controller Issue. It appears that the current (2012) driver is not working. I rolled the driver back to the 2008 version and the communications works correctly.

Here are the 64 bit Driver (c:\windows\system32\drivers\ser2pl64.sys) versions and dates.

3.3.2.105 - 2008
3.3.4.122 - 2009
3.4.31.231 – 2012

I can not get it to work either, on Windows 7 Home Premium 64 Bit.. The Installer seems to load the Drivers, but Windows is never able to install them for the Hardware, giving a "Code 28" error..

Edit:

I installed version 3.3.11.152, dated 3/12/2010 and that seems to be working.

[vamfun]

I have been trying to find the link for 3.3.11.152 prolific driver on the new prolific site. Anyone have it or a link where it can be downloaded without downloading driver id .exe

[MarkO]

Originally Posted by vamfun

I have been trying to find the link for 3.3.11.152 prolific driver on the new prolific site. Anyone have it or a link where it can be downloaded without downloading driver id .exe

Yea!!! The new Prolific Site....

Try this file, PL2303_Prolific_DriverInstaller_v1210.exe.

I downloaded this file on 13-JUL-2010 and placed it on the SilverLeaf web site for end customers, because Silverleaf sold a lot of Prolific adapters over 8 years and the Prolific site is only getting Harder and Harder to navigate...

[vamfun]

This is the current driver isn't it? Doesn't this have the same problems. I think I have tried that already. I want to get 3.3.11.152 version.

[jpearman]

Originally Posted by vamfun

This is the current driver isn't it? Doesn't this have the same problems. I think I have tried that already. I want to get 3.3.11.152 version.

Chris

Try this version, release notes say it is the one you want.

https://www.box.com/s/od9dl1puhx3ea958saut

PL-2303 Driver Setup Installer, Prolific Edition
Setup Installer Revision Note History
===========================================

System Requirement:
. Supports the following Windows OSes:
- Windows 98SE
- Windows ME
- Windows 2000 SP4
- Windows XP SP2 and above (32 & 64 bit)
- Windows Server 2003 (32 & 64 bit)
- Windows Server 2008 / 2008 R2 (32 & 64 bit)
- Windows Vista (32 & 64 bit)
- Windows 7 (32 & 64 bit)
NOTE: For Windows 7, please use RC build 7100 or above build version.
. USB host controller
. Device using PL-2303H/HX/X version chip


Supported device ID and product strings:
. VID_067B&PID_2303 for "Prolific USB-to-Serial Comm Port"


Driver Versions:
-------------------
- Windows 98/ME Driver: v2.0.0.19
- Windows 2000/XP/Server2003 (32 & 64-bit) WDM WHQL Driver: v2.0.13.130
- Windows Vista/7/Server2008 (32 & 64-bit) WDF WHQL Driver: v3.3.11.152

[vamfun]

This looks the same as MarkO's download , so thanks to you both for the links.