Cleverscope CS320 & USB to Serial Adapter Clash

Cleverscope CS320 & USB to Serial Adapter Clash, a forum discussion on Cleverscope. Join us for more discussions on Cleverscope CS320 & USB to Serial Adapter Clash on our Interface issues forum.

Back to Forum Index : Back to Interface issues   RSS

10 Aug 2009
Posts:

We are having issues with using our Cleverscope CS320 on a PC that also has a specific USB to Serial Adapter connected. These USB to Serial Adapters are standard item Dick Smith (Product Code: XH8290, web link http://www.dse.co.nz/dse.shop/4a7f4217019289f82741c0a87f3b06f5/Product/View/XH8290). We use these a lot in our factory as most PC only come with one physical serial port and we need three to four on each PC.

With one of these USB to Serial Adapters connected when the Cleverscope software tries to communicate with the scope it reports that there is a problem with the USB port (error ‘5102’). If you then remove the USB to Serial Adapter (without restarting the Cleverscope software) it is then able to communicate with the scope. I also found that if I open the serial port of the USB to Serial Adapter (with HyperTerminal) this also resolves the problem, I can then close the serial port and while the Cleverscope software is running it has no problems, but if you restart it your back to the communications problem.

I have found that the USB to Serial Adapter appears to be using the same (or similar) FDTI drivers to that of the Cleverscope, which may explain the problem, ie the Cleverscope is thinking the USB to Serial Adapter is the scope and using that port to communicate.

Here are some details on the FTDI drivers for both the USB to Serial Adapter and the Cleverscope;

USB to Serial Adapter:
Driver Files:
ftser2k.sys - 2.04.16 built by WinDDK
serenum.sys - 5.1.2600.2180 - Microsoft
ftserui2.dll - 2.04.16 built by WinDDK

Extract from usbview.exe
Device Descriptor:
bcdUSB: 0x0110
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x0403 (Future Technology Devices International, Ltd)
idProduct: 0x6001
bcdDevice: 0x0400
iManufacturer: 0x01
iProduct: 0x02
iSerialNumber: 0x03
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: Full
Device Address: 0x02
Open Pipes: 2

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Cleverscope CS328 MSO:
Driver Files:
ftdibus - 2.04.16 built by WinDDK
ftbusui.dll - 1.2.01
ftd2xx.dll - 3.01.18
FTLang.dll - 1,3,0,1

Extract from usbview.exe
Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x0403 (Future Technology Devices International, Ltd)
idProduct: 0xEEA8
bcdDevice: 0x0400
iManufacturer: 0x01
iProduct: 0x02
iSerialNumber: 0x03
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: Full
Device Address: 0x02
Open Pipes: 2

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

It would be good to know if there is some fix or automatic work around for this problem.

Thanks
John

31 Aug 2009
Posts: 396

Hello John,
Sorry about the wait. The issue here is that the serial port adaptors are using the FTDI default VID and PID (which they are not supposed to). The defaults are kind of magic, and over-ride our Inf file, for reasons we can not work out. The only solution we have come up with is to change the PID/VID combination to use our own Cleverscope Vendor ID. (When we started we just used FTDI's, and we used a Product ID we obtained from them. Since then we have obtained our on VID). Please email us, and we will send you Mprog and the appropriate file to change the Pid/vid combination, and a new Inf File. There is one downside - if you have used our driver you will have to manually change the PID/VID detection string in Cscope Transmit Commands/ Open Cleverscope, or use the newer version of our driver, which we will update. I'll let you know when that is done.
Back to Forum Index : Back to Interface issues   RSS
You must be logged in to post a reply



You need to Register or Log In before posting on these forums.

×

Your shopping cart is empty.