I've been given a SBS-1 which, as far as I am aware, has never been updated. It has the serial number 00140.
I'm running on Windows 10 and cannot get the drivers to install. I've run the ftclean utility, rebooted and have run the executable to install the drivers from the CD numerous times without success. I seem to have a real mess of partially installed drivers.
If I run SBS1LinkTester I get 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 A is correct SBS-1 device
Determining if Dual RS232 B is correct SBS-1 device
Error: No matching port names found!
Opening device Dual RS232 A
VID: 0403; PID: 6010
Link successfully opened
Closing link
Test completed successfully!
Windows 10 seems to scatter files all over place - Basestation.ini wasn't located in the usual place (Program Files\Kinetic\BaseStation) but somewhere entirely different so I suspect that the FTDI drivers aren't in the place that the uninstaller thinks they are and therefore isn't uninstalling them properly.
I've spent hours on this so far without success .... has anyone got any idea ? Is there a way to manually remove the drivers other than using ftclean ?
Thanks in advance
Phil
I suspect that few of us have moved to Windows 10 so not a lot of experience.
But I don't understand the problem.
If SBS1LinkTester is saying it completed successfully, what is the problem? Seems like the drivers are in place.
Now you need to run BaseStation to display the SBS-1 output. If there errors when BS runs, tell us what those are.
Of course I may be missing the point completely :-[
As you can see from another recent thread, I had problems when upgrading to Windows 10 also, although not with the install. As one of the measures that I took I uninstalled Basestation and reistalled it completely using the Basestation 1-2-4-184 CDROM file downloadable from the Kinetic website. The install worked fine. I installed the file in the Program Files (86x) folder and everything was installed there under Kinetic -> Basestation
What I then found was that the program has to be run in admin status (and that applies for Basestation Reporter also).
@IanH, there is a problem in that the SBS1LinkTester reports "Error: No matching port names found!"
By contrast, here's what I should see:
Starting test, attempting to open USB link...
Opening USB link: BaudRate = 921600; USBTypeAutoDetectOverrideDesc = ""; USBTypeAutoDetectOverrideComPort = 0
Getting port to use...
Determining if Kinetic SBS-1 Beavis 8A is correct SBS-1 device
Opening device Kinetic SBS-1 Beavis 8A
VID: 0000; PID: 0000
Link successfully opened
Closing link
Test completed successfully!
@Snoopy: that's what I've tried to do but somewhere along the way the drivers seem to have got garbled so that they are only partially installed. Because Windows 10 seems to scatter them around I'm struggling to completely remove all traces using FTClean before re-installing from scratch.
If you install on windows 8 or 10 as per this video https://www.youtube.com/watch?v=lr0VHdNGD-Q
If you have the FTDI driver issue shut down basestation and with your SBS device connected by USB on Win Vista 7,8 or 10 right click on the Basestation shortcut select open file location.
In the folder is a red circle logo called CDMxxxxxx double click it and the drivers will be installed.
If you are still on XP go to C:\kinetic\basestation and find the red circle logo called CDMxxxxxx double click it and the drivers will be installed
Regards
Thanks for the reply Chris. My XP computer has finally died (it's been failing slowly for the last month or so) so I've switched my attentions to my Windows 10 laptop.
To remove any previous versions of BaseStation I've run ftclean and have uninstalled BaseStation, then rebooted.
I installed the latest version of BaseStation into C:\Kinetc\BaseStation as per the video and have double clicked on the CDM20814_Setup file in the folder where BaseStation is installed.
A command box told me that it's installed correctly but then Windows has just popped up a dialogue box stating that "This program may not have installed properly." It then gives me two choices so that I select that it runs in compatability mode or that it's running ok.
If I ignore that and run BaseStation the initial set up runs but fails when trying to connect to the SBS-1 which has a red and orange light and either one or two blue lights on it.
If I click on 'Install in compability mode' then it fails the BaseStation start up as well.
Looking in the device list I have a Dual RS232 installed but that's all.
SBS1LinkTester gives me the following:
Starting test, attempting to open USB link...
Opening USB link: BaudRate = 921600; USBTypeAutoDetectOverrideDesc = ""; USBTypeAutoDetectOverrideComPort = 0
Getting port to use...
Determining if Dual RS232 A is correct SBS-1 device
Determining if Dual RS232 B is correct SBS-1 device
Error: No matching port names found!
Opening device Dual RS232 A
VID: 0403; PID: 6010
Link successfully opened
Closing link
Test completed successfully!
Clearly the test has failed as there's an error (bolded).
Any ideas ?
Phil
Can I check that you've selected USB in BaseStation for connecting to the SBS?
Settings->Data Source
Yes, when the start up wizard runs I select USB rather than network ....
I then select Kinetic Vitrual Radar Receiver etc (their spelling mistake not mine !)
Phil
What Wizard are you referring to? The BaseStation setup?
Yes - the one which runs until BaseStation has confirmed that the data source (SBS-1 or whatever) is properly installed.
As the SBS-1 fails everyone it's like groundhog day!
Phil
Thanks Phil
Maybe I can do a remote connect with you at a convenient time and take a look together?
Today is not good for me.
I only recently found out what CDM20814.exe did (Feb 2015) :-[
Previously I had installed FTD2XX.LIB manually.
You might want to try downloading the latest Windows drivers from here: http://www.ftdichip.com/Drivers/D2XX.htm
Extract the ftd2xx.dll file from the i386 folder in that zip and copy into the Basestation folder (someone else might say they need to go elsewhere ?win32 folder?). The notes for these drivers indicate they work for Win10.
See if that works.
@anmer - thanks for the offer. Tomorrow will be better for me too as I'll be waiting in all day for a new Windows 10 desktop to arrive to replace my now dead XP box
@IanH - I tried that and still got the same result ....
I did a search across my PC for ftd2xx.dll and got this:
c:\Kinetic\BaseStation\ftd2xx.dll
c:\Kinetic\ft_drivers\i386\ftd2xx.dll
c:\Kinetic\ft_drivers\amd64\ftd2xx64.dll
c:\Windows.old\Windows\System32\DriverStore\FileRepository
C:\Windows.old\WINDOWS\System32\DriverStore\FileRepository\ftdibus.inf_amd64_fe4babd0c66b4519\i386\ftd2xx.dll
C:\Windows.old\WINDOWS\System32\DriverStore\FileRepository\ftdibus.inf_amd64_fe4babd0c66b4519\i386\ftd2xx64.dll
Running ftclean didn't remove any of these so I've manually removed them and have rebooted. I'll re-install the drivers and will update this later.
OK, after a break for food ....
I've reconnected the SBS unit and it hasn't installed any drivers so I ran the driver setup tool CDM20814.exe from the C:\Kinetic\BaseStation folder
Running SBS1LinkTester gave me the following results:
Starting test, attempting to open USB link...
Opening USB link: BaudRate = 921600; USBTypeAutoDetectOverrideDesc = ""; USBTypeAutoDetectOverrideComPort = 0
D2XX device failed to open
TEST FAILED!
which is different but is an error message that I have read about so I restored the ftd2xx.dll file that was in the recycle bin back to c:\kinetic\basestation.
Running SBS1LinkTester gave the same error as I've had before:
Starting test, attempting to open USB link...
Opening USB link: BaudRate = 921600; USBTypeAutoDetectOverrideDesc = ""; USBTypeAutoDetectOverrideComPort = 0
Getting port to use...
Determining if Dual RS232 A is correct SBS-1 device
Determining if Dual RS232 B is correct SBS-1 device
Error: No matching port names found!
Opening device Dual RS232 A
VID: 0403; PID: 6010
Link successfully opened
Closing link
Test completed successfully!
So I'm no further forwards but I wonder if the version of ftd2xx.dll that I have is wrong ? It's version 2.12.06.1
Any ideas ?
According to the FTDI website, v2.12.0 is the latest version. Did you try the setup-executable file, available here (http://www.ftdichip.com/Drivers/CDM/CDM%20v2.12.06%20WHQL%20Certified.exe)?
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
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.
Ok Mike, thanks for the update.
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]
Have you tried the firmware upgrade again?
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
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?
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
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:
QuoteWindows 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
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?
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 !