Hi JP there was a another forum posts about the same chipset, it looks like it seems to have an issue with our products. I know that none of our scopes use this chipset.
System.ArgumentOutOfRangeException: Length cannot be less than zero.
[2236] Parameter name: length
[2236] at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
[2236] at a.b()
[2236] at co..cctor()
[2236] --- End of inner exception stack trace ---
[2236] at dU.a()
[2236] at kx.a()
[2236] at kx.b()
[2236] at kx.d()
[2236] at z.b()
[2236] InitalDeviceLoadSequence: Info: Complete
I would be happy to test something if you are interested.
Regards
JP
-->
Hi
If I unplug the serial port and the starts PicoScope6 it finds the 3206. I can then reconnect the serial port and both of them are working.
So it seems that the PicoScope6 software are having trouble enumerating the USB devices when the FTDI device is connected. The 3206 device is always shown in the device manager as a "PicoScope 3000 series PC Oscilloscope" and the USB VID and PID of both devices are different.
The debug print out captured with DebugView shows an exception, here is the interesting part:
[2236] Environment: Info: Current Directory - C:\Program Files\Pico Technology\PicoScope6
[2236] Environment: Info: Total Physical Memory 3755888640
[2236] Scanning for USB devices: Info: Begin
[2236] Device: Error: Exception while enumerating devices
[2236] Device: Error: System.TypeInitializationException: The type initializer for 'co' threw an exception. ---> System.ArgumentOutOfRangeException: Length cannot be less than zero.
[2236] Parameter name: length
[2236] at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
[2236] at a.b()
[2236] at co..cctor()
[2236] --- End of inner exception stack trace ---
[2236] at dU.a()
[2236] at kx.a()
[2236] at kx.b()
[2236] at kx.d()
[2236] at z.b()
[2236] InitalDeviceLoadSequence: Info: Complete
I would be happy to test something if you are interested.
I too have seen this problem.
I don't think the problem is with the FTDI Driver as they are generally rock solid and are in use in thousands of products around the world. It is probably THE most popular usb-serial chipset in the world. Having said all of that - it could be that their latest driver, or one particular version of it, behaves slightly differently than before.
As the contributor above states, there is an exception thrown by PicoScope while enumerating the USB devices and this seems to be an area worth investigating. It would be good if PicoScope could catch this exception and handle it, rather than terminating. Especially considering that it is enumerating non-pico devices at the time, so it should be able to happily ignore the mis-behaviour.
I'd love to know when this issue is addressed, since by nature of my products I have to have both pico and several USB-SERIAL convertors in use at the same time, and it's a pain having to unplug all the serial devices before starting PicsoScope.