View previous topic :: View next topic |
Author |
Message |
E_Blue
Joined: 13 Apr 2011 Posts: 417
|
Windows 10 USB CDC driver support |
Posted: Tue Sep 22, 2015 8:02 am |
|
|
Hi have a device that works ok until windows 8, now with Windows 10 the driver is installed properly but theres no communication between the device and the PC.
So I think that the problem must be the driver or the .inf file.
Does anybody tried to connect a PIC device with CDC to a PC with Windows 10?
Edit:
I tried with a VB.NET 2010 application and works ok, the problems appears when somebody tries to connect with the device using a VB6 application. _________________ Electric Blue |
|
|
Ttelmah
Joined: 11 Mar 2010 Posts: 19515
|
|
Posted: Tue Sep 22, 2015 8:42 am |
|
|
MsComm is no longer supplied/supported. You can download it from some sites on line, and there are instructions on how to install it in W10. |
|
|
E_Blue
Joined: 13 Apr 2011 Posts: 417
|
|
Posted: Tue Sep 22, 2015 9:39 am |
|
|
I created a specific application for my device in VB.NET 2010 and works ok but since my device have a similar protocol to configure it as an older version of the same device designed by another person some people uses the older version of PC application that is designed under VB6.
Summarizing
My device
VB6 application until W8.1 works ok
VB.NET works in all platforms from XP to W10
Older device
Works OK with the VB6 even in W10
The older version uses an FT232 _________________ Electric Blue |
|
|
Ttelmah
Joined: 11 Mar 2010 Posts: 19515
|
|
Posted: Tue Sep 22, 2015 11:07 am |
|
|
The point is that VB6, uses MSComm. VB.Net doesn't (well, you can, but you don't by default).
Hence MSComm missing = serial not work in VB6.
The FT232, can be driven without using MSComm (depends how it is written, but FTDI did supply a DLL, and .bas code to allow direct drive from VB). |
|
|
E_Blue
Joined: 13 Apr 2011 Posts: 417
|
|
Posted: Tue Sep 22, 2015 2:19 pm |
|
|
Ok, understood, thanks. _________________ Electric Blue |
|
|
|