Windows 10: cannot install drivers ...

[Pidea]

I did yes.  Anmer and I spent quite a while today looking at it.  It appears that the problem is possibly with the SBS1 itself but I won't be able to confirm that until Monday now.

Phil

[Anmer]

Hi Rob

From what I can see, the drivers are installed OK.  The firmware update failed too and we know a different SBS worked OK with the same PC.

Chris at TMRF thinks it may be a hardware failure and we're trying to confirm this.

[G4UMW]

Ok Mike, thanks for the update.

[Pidea]

OK, it looks like I've got a dead SBS-1 box :-(

On a brand new Windows 10 PC I've installed the latest BaseStation into C:\Kinetic\BaseStation.  I've posted a screen shot of Device Manager before plugging the SBS-1 in showing the USB devices installed (Before.png).

I then plugged the SBS-1 into a USB port that I know works.  Device manager updated and showed a new USB device USB Serial Convertor B but the other one was still listed as a Dual RS232 in Other Devices (After.png)

I then navigated to the C:\Kinetc folder and ran CDM20814_Setup.exe with the SBS-1 plugged in.

This caused the Dual RS232 under Other Devices to appear as USB Serial Convertor A (After driver.png)

Running the SBS1LinkTester produces the following output:

Starting test, attempting to open USB link...
Opening USB link: BaudRate = 921600; USBTypeAutoDetectOverrideDesc = ""; USBTypeAutoDetectOverrideComPort = 0
Getting port to use...
Determining if Dual RS232 B is correct SBS-1 device
Determining if Dual RS232 A is correct SBS-1 device
Error: No matching port names found!
Opening device Dual RS232 B
VID: 0403; PID: 6010
Link successfully opened
Closing link
Test completed successfully!

Although it says that the test completed successfully the line "Error: No matching port names found!" still appears and BaseStation still fails to receive any data from the unit despite having between 2 and 3 blue lights on.

Phil

[Attachment deleted by Admin to save file space]

[Anmer]

Have you tried the firmware upgrade again?

[Pidea]

Sorry, meant to mention that too.

I get the same error message using Chris's method of associating the KFF file with the prog-sbs1-5v.exe program.

But if I run prog-sbs1-5v.exe without any arguments I get the same result as well so it looks as if the firmware file isn't even being passed to prog-sbs1-5v.exe program.

Dragging the KFF file onto it doesn't work either nor does running it as Administrator.

The error message is "Error : [Dual RS232 A] is not compatible with this utility".

Phil

[Anmer]

Thanks.

If you want to post me the SBS-1, I can test it here and return it to you, postage paid by me.

PM if this is an option.  Or post to TMRF for Chris to take a look?

[Pidea]

Thanks for the offer Mike.  I'll talk to my friend who's got one and see if he's around this week and I'll let you know.

Phil

[Pidea]

Further update to this saga !

I swapped my SBS-1 with a friend (massive thanks to RustyTwig) who has one running on his machine and mine worked perfectly !  But ......

When he tried to install it on a Windows 7 laptop that had never run BaseStation before this is what he got:

Windows 7
BaseStation disk version 1.1.1.130
Run setup.exe
Allow changes - yes

Wizard:
Next - install
Next - read me
Next - destination folder
Change C:\Kinetic\BaseStation\
OK

Next - ready to install
Finish

Insert USB
Installing device driver software
Device ready to use

Error: Program can't start because ftd2xx.dll is missing
Copy ftd2xx.dll (172kb) in System 32 folder

Restart BaseStation
Configure
Testing Setup
Test failed

Firewall blocked access
Allow access

Restart Basestation
Application error:
exception EAccess Violation in module
BaseStation.exe at 00000220

Restart windows
Remove USB

Run BaseStation
ftd2xx1.dll missing
Copy ftd2xx1.dll to BaseStation folder

Change BasaeStation.exe properties
Run program in Compatibility mode for Win XP (Service Pack 3)

Run BaseStation startup
Configure
Test progress
Failed Test
Application error:
exception EAccess Violation in module ....
Runtime error 217 at 0034056A

Tried with a later version of ftd2xx.dll but still no joy.

So it appears that it will run but that that there's some kind of problem with it which stops it from being properly detected.

I could get around this by borrowing his SBS-1 and installing it on my machine and then swapping it back with mine but given that there's a problem it may just fail further in the future.

Is this something that Chris Taylor can repair at all ?

Phil

[Anmer]

Hi Phil

So your SBS-1 worked OK on your friend's PC?  What version of Windows and BaseStation was he running?

Did his SBS-1 run OK on your laptop?

[Pidea]

After a round trip to Llandrindod Wells I can confirm that my friends SBS-1 works perfectly on my Windows 10 PC and that my SBS-1 definately doesn't work on his so it looks like my SBS-1 is at fault.

Specifically it looks like the part that identifies itself to the computer when plugged in has failed as it doesn't load the drivers.

We tried various combinations of firmware and versions of BaseStation to no avail so it's off to Chris Taylor tomorrow to see if he can breathe life into it !