Will there be support for vista 64-bit or do I need to look for a other scope? It´s use FTDI driver and they have support for 64-bit so I guess it will not be mutch work to have it working?
Best regards /Jörgen
Sorry, if I know there are no plans to get a digitally signed driver for Windows Vista 64-Bit at the moment.
I have Vista 64 Ultimate edition.
What I can’t understood is where is not any Vista 64 driver.
Also there are kits for Windows 95 having difficulties to turn under Windows XP.
Some product doen’t work under Virtual machine (VMWare).
I think Velleman need to update drivers.
It will going to be very difficult for us to use products new systems and the late of Velleman.
Vista 64 exist more than one year and beta since two year.
If needed, I have Visual Studio 2008 and I can give my contribution to compile for x64.
Finaly I could install and run PC-Lab2000SE within Vista 64.
This is what to do
First download FTDI CDM 2.04.06 WHQL Certified driver for Vista 64
Link is ftdichip.com/Drivers/CDM/CDM … tified.zip
In this package, replace the original FTDIBUS.INF file with the lines undershown.
Copy past in notepad and save it as FTDIBUS.INF.
; FTDIBUS.INF
; Copyright © 2000-2008 FTDI Ltd.
;
; USB serial converter driver installation for Windows 2000, XP, Server 2003, Vista, Server 2008 (x86 and x64).
;
[Version]
Signature="$Windows NT$"
DriverPackageType=PlugAndPlay
DriverPackageDisplayName=%DESC%
Class=USB
ClassGUID={36fc9e60-c465-11cf-8056-444553540000}
Provider=%FTDI%
CatalogFile=ftdibus.cat
DriverVer=03/13/2008,2.04.06
[SourceDisksNames]
1=%DriversDisk%,
[SourceDisksFiles]
ftdibus.sys = 1,i386
ftbusui.dll = 1,i386
ftd2xx.dll = 1,i386
FTLang.Dll = 1,i386
[SourceDisksFiles.amd64]
ftdibus.sys = 1,amd64
ftbusui.dll = 1,amd64
ftd2xx64.dll = 1,amd64
ftd2xx.dll = 1,i386
FTLang.Dll = 1,amd64
[DestinationDirs]
FtdiBus.NT.Copy = 10,system32\drivers
FtdiBus.NT.Copy2 = 10,system32
FtdiBus.NTamd64.Copy = 10,system32\drivers
FtdiBus.NTamd64.Copy2 = 10,system32
FtdiBus.NTamd64.Copy3 = 10,syswow64
[Manufacturer]
%Ftdi%=FtdiHw,NTamd64
[FtdiHw]
%USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6001
%USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_00
%USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_01
%USB\VID_10cf&PID_1000.DeviceDesc%=FtdiBus.NT,USB\VID_10cf&PID_1000
[FtdiHw.NTamd64]
%USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6001
%USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_00
%USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_01
%USB\VID_10cf&PID_1000.DeviceDesc%=FtdiBus.NTamd64,USB\VID_10cf&PID_1000
[FtdiBus.NT.HW]
AddReg=FtdiBus.NT.HW.AddReg
[FtdiBus.NTamd64.HW]
AddReg=FtdiBus.NT.HW.AddReg
[FtdiBus.NT.HW.AddReg]
HKR,“ConfigData”,0x00010001,0
[ControlFlags]
ExcludeFromSelect=*
[FtdiBus.NT]
CopyFiles=FtdiBus.NT.Copy,FtdiBus.NT.Copy2
AddReg=FtdiBus.NT.AddReg
[FtdiBus.NTamd64]
CopyFiles=FtdiBus.NTamd64.Copy,FtdiBus.NTamd64.Copy2,FtdiBus.NTamd64.Copy3
AddReg=FtdiBus.NT.AddReg
[FtdiBus.NT.Services]
AddService = FTDIBUS, 0x00000002, FtdiBus.NT.AddService
[FtdiBus.NTamd64.Services]
AddService = FTDIBUS, 0x00000002, FtdiBus.NT.AddService
[FtdiBus.NT.AddService]
DisplayName = %SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\system32\drivers\ftdibus.sys
LoadOrderGroup = Base
AddReg = FtdiBus.NT.AddService.AddReg
[FtdiBus.NT.AddReg]
HKR,DevLoader,*ntkern
HKR,NTMPDriver,ftdibus.sys
HKR,EnumPropPages32,“ftbusui.dll,FTBUSUIPropPageProvider”
[FtdiBus.NT.AddService.AddReg]
;HKR,Parameters,“LocIds”,1,31,00,00,00,32,00,00,00,00
;HKR,Parameters,“RetryResetCount”,0x10001,1000
[FtdiBus.NT.Copy]
ftdibus.sys
[FtdiBus.NT.Copy2]
ftbusui.dll
ftd2xx.dll
FTLang.dll
[FtdiBus.NTamd64.Copy]
ftdibus.sys
[FtdiBus.NTamd64.Copy2]
ftbusui.dll
ftd2xx.dll,ftd2xx64.dll
FTLang.dll
[FtdiBus.NTamd64.Copy3]
ftd2xx.dll
[Strings]
Ftdi=“FTDI”
DESC=“CDM Driver Package”
DriversDisk=“FTDI USB Drivers Disk”
USB\VID_0403&PID_6001.DeviceDesc=“USB Serial Converter”
USB\VID_0403&PID_6010&MI_00.DeviceDesc=“USB Serial Converter A”
USB\VID_0403&PID_6010&MI_01.DeviceDesc=“USB Serial Converter B”
USB\VID_10cf&PID_1000.DeviceDesc=“PCSU1000_Oscilloscope”
SvcDesc=“USB Serial Converter Driver”
ClassName=“USB”
Connect PCSU1000 to the USB of the PC.
When driver is asked, choise to select the place of this package.
Windows is going to say driver isn’t signed. Accept installation.
Don’t mater about it. The INF file will make it digitaly signed.
Disconnect PCSU1000 from the Vista X64 Computer
In a diferent computer, install PC-LAB2000SE under Windows XP.
Copy PCSU1000 Files and folder from XP to a Vista 64 computer.
Copy those folders to c:\Programs in Vista x64.
c:\Program Files\Velleman
Copy those folders to ProgramData\Microsoft\Windows\Start Menu\Programs
c:\Documents and Settings\All Users\Start Menu\Pc-Lab2000SE
Copy files to c:\Windows\System32 in Vista x64:
c:\Windows\System32\CP210x.dll
c:\Windows\System32\DLPORTIO.DLL
c:\Windows\System32\DLPORTIO.SYS
c:\Windows\System32\DSOLink.dll
c:\Windows\System32\FASTTime32.dll
c:\Windows\System32\PCGU1000Link.dll
c:\Windows\System32\PCSU1000D.dll
Create a text file and rename it as PCSU1000.reg
Edit past and save the under lines:
REGEDIT4
[HKEY_LOCAL_MACHINE]
[HKEY_LOCAL_MACHINE\SOFTWARE]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls]
“C:\WINDOWS\system32\CP210x.dll”=hex(7531):01,00,00,00
“C:\WINDOWS\system32\DLPORTIO.DLL”=hex(7531):01,00,00,00
“C:\WINDOWS\system32\DLPORTIO.SYS”=hex(7531):01,00,00,00
“C:\WINDOWS\system32\DSOLink.dll”=hex(7531):01,00,00,00
“C:\WINDOWS\system32\FASTTime32.dll”=hex(7531):01,00,00,00
“C:\WINDOWS\system32\FTD2XX.dll”=hex(7531):02,00,00,00
“C:\WINDOWS\system32\PCGU1000Link.dll”=hex(7531):01,00,00,00
“C:\WINDOWS\system32\PCSU1000D.dll”=hex(7531):01,00,00,00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PC-Lab2000SE]
“DisplayName”=“PC-Lab2000SE”
“UninstallString”="%WINDIR%\uninst.exe -f"C:\Program Files\Velleman\PC-Lab2000SE\DeIsL1.isu" -c"C:\Program Files\Velleman\PC-Lab2000SE\_ISREG32.DLL""
[HKEY_LOCAL_MACHINE\SOFTWARE\Velleman]
[HKEY_LOCAL_MACHINE\SOFTWARE\Velleman\PC-Lab2000SE]
[HKEY_LOCAL_MACHINE\SOFTWARE\Velleman\PC-Lab2000SE\3.08]
Apply this registry file to the Vista x64 computer.
Now connect PCSU1000 to the Vista x64 Computer
Clic on Start menu
Open PC-Lab2000se menu folder
Clic on Pc-lab2000se menu
When PC-Lab2000Se start, select PCSU1000 button and make calibration of your scope.
What’s all.
CSU1000 run perfectly under Vista 64.
Thank you very much. This worked great with my PCSU1000. Is there a similar solution for the PCGU100 function generator?
Thanks again.
David
Sorry, but the SiLabs CP210x driver (used for the PCGU1000) is behaving different way compared to the behavior of the FTDI driver for the PCSU1000.
The SiLabs CP210x driver doesn’t install on 64-bit OS (except on 64-bit XP) after the VID and PID modification.
I tried to install version 3.03 of the software, but it failed.
I would like to try to test this procedure with Windows7 64bits.
Can you please publish a link to a newer version of the PCSU1000 software? I found a download link of the rev4 software that does not work anymore.
Also, the link on the ftdi site has been changed, I have downloaded: CDM20814_WHQL_Certified.zip
If it will be updated frequently, better get it from this page: ftdichip.com/Drivers/VCP.htm
Find “Currently Supported VCP Drivers:” and choose the stable version from “x64 (64-bit)”, or if you like russian roulette, take the beta 
Here is the link to download the latest PcLab2000SE software and the latest driver for the PCSU1000:
velleman.eu/support/download … 1000&type=
Here is the link to download the latest pre-release PCLab2000SE v4.04: box.com/s/c9nis5ro05if3oop9ptk
On windows7 the installation of v.4.03 works perfect. I did not need to do any of the tweaking you mentioned above.
Version 3.03 had 64bit compatibility issues.
I did not install the cp210 driver because the link you gave is of a Vista driver. I downloaded a W7 package instead:
silabs.com/Support%20Documen … ista_7.exe
Thank you very much!
i have just bought a usb oscilloscope pcgsu250, once i have installed the program, i see that when i connect the probe to my circuit the oscilloscope is really very slow ( even several seconds) and the volt amplitude of the wawe is not correct. There is no problem with the function generator.
I have seen my windows vista version from 2007 and is a 64 bit.
I am schocked, is possible that pcgsu250 scope dont work with vista 64 bit???
Please download and install the latest software v1.09 and the driver v1.0.0.2 “Drivers for Windows Vista and Windows 7. (Can also be used for Windows XP)” from the downloads page: velleman.eu/support/download … U250&type=
Here you can download the instructions how to update the existing driver: box.com/shared/66aei7j31s
Instead of the CD use the downloaded and extracted driver folder and files.
i have done this yesterday afternoon, but i have the same problem, the oscilloscope doesn´t work well.
The wave is extremely slow, there is a delay of several seconds between i change the input voltage conditions and i see the output wave, and the wave is not running in my secreen its appear like flash in the screen.
Have you checked in the Device Manager that you really have the driver v1.0.0.2 installed?
If yes, then this is very strange problem.
Can you test the oscilloscope in other PC?
yes, I had installed driver 1.0.0.2 and the problem was the same in other pc with operative system windows 7.
I have claimed the electronic shop in which I bougth it, this morning, I expect news