Update: May 15, 2013

[joecar]

From post #1:

Important:

This latest software update requires updated USB drivers (V2.08.28). You cannot use this version of the software with older versions of the USB drivers.
If you are having difficulty connecting to FlashScan/AutoCal after installing this update, DO NOT DOWNGRADE THE USB DRIVERS. The problem is possibly a USB 2.0/3.0 incompatibility.
Try using FlashScan/AutoCal in a USB 2.0 port instead of a USB 3.0 port.

[GMPX]

I strongly recommend not upgrading if you're in a production environment and have USB 3.0.

Nick, what I have found with the USB3.0 ports on my PC (and this was before the update so I don't think it is the latest FTDI drivers) is the V2 wouldn't be recognised for at least 20 to 30 seconds when plugged in, it was the oddest thing, after it finally woke up everything was fine. This also happened on a number of USB memory sticks too, it wasn't just the V2.

[ScarabEpic22]

From post #1:

Going to edit my previous post, I was going to try downgrading my drivers today but guess I wont do that just yet.

[vortecfcar]

From post #1:

Joe, if you read my post you'll see that we did update the drivers and still are unable to connect on any of the USB ports.

Nick, what I have found with the USB3.0 ports on my PC (and this was before the update so I don't think it is the latest FTDI drivers) is the V2 wouldn't be recognised for at least 20 to 30 seconds when plugged in, it was the oddest thing, after it finally woke up everything was fine. This also happened on a number of USB memory sticks too, it wasn't just the V2.

Maybe it's just our computers, or we're idiots, but we sat there and waited until it said drivers loaded successfully and still received error messages indicating inability to connect.

Nick

[joecar]

Joe, if you read my post you'll see that we did update the drivers and still are unable to connect on any of the USB ports.
...

Oh, I was just alerting that the old driver cannot be used.

[joecar]

Paul,

Here are some minor things I saw:


in the BBx Search bar, the Channels box is truncated:




in HAPI the firmware/bootblock fields are blank (not sure if they're supposed to be):

[GMPX]

Maybe it's just our computers, or we're idiots, but we sat there and waited until it said drivers loaded successfully and still received error messages indicating inability to connect.

Don't be so hard on yourself Nick
The point I was trying to make was I don't think that USB3.0 ports behave exactly like USB2.0 ports. I avoid using USB2.0 devices on my USB3.0 ports, it's almost like a USB3.0 port tries to behave like a 3.0 port by default (which makes sense) and when it finally figures out it's got a 2.0 device connected it drops down to 2.0 spec, but that doesn't happen instantly.

Unfortunately for us we are a little bit at the mercy of FTDI's USB drivers, we assume they have thoroughly tested them on USB3.0 ports.

I know earlier this week I had some major issues with USB communications when I was testing some of Paul's updates until I was able to install the latest release with matching drivers, I wonder if there is some installer issues with some computers.

[Blacky]

in the BBx Search bar, the Channels box is truncated:

What settings do you have for font DPI?

in HAPI the firmware/bootblock fields are blank (not sure if they're supposed to be):

Its a bug, fixed in the next update.

Regards
Paul

[Blacky]

Unfortunately for us we are a little bit at the mercy of FTDI's USB drivers, we assume they have thoroughly tested them on USB3.0 ports.

I have logged a support call with FTDI, but still no response yet...

Regards
Paul

[joecar]

What settings do you have for font DPI?

1440 x 900 @ 96 DPI



My screen is odd sized due to my laptop being a MacBook.