PCSGU250 with Windows 7

Bought my PCSGU250 in spring 2010, my PC had the OS Windows XP: all perfect.
Now I have a new laptop with Windows 7, problems: I cann’t install my PCSGU250.
Help!! What to do? can anybody send me a complete install program so it is working with Win 7? Please?
Thanks in advance, Anke

Cannot install the program or cannot install the driver?

Here a link to the page where you can download the latest version 1.08:
velleman.eu/distributor/supp … U250&type=

I can install the program, but cann’t install the hardware!!! I downloaded your version …1.08 but the answer after install hardware is: ‘no hardware response’ etc.
what now? Anke

Have you installed the driver?

When I used de OS Windows XP it was not necessary to install apart anything, now (whithin Windows 7) I don’t know where and what to install.
Isn’t there anywhere a manual for installing the PCSGU250 with Windows 7 or can you tell me where I what has to do or copy to? Please?
In mean time I “installed” the thing on an other PC with Windows 7, the same story: no hardware response, make sure the USB is connected etc, choose options/ hardware setup etc.
Please?

The PCSGU250 needs a driver to be installed in Windows XP too. The instructions to install the driver are on p.6 of the manual: velleman.eu/downloads/0/user … 2000lt.pdf

To install the driver in Windows 7:
First you have to download the driver file package from this downloads page:
velleman.eu/distributor/supp … U250&type=

Extract the package to any folder:
When installing, you have to browse to the this folder.

Next steps:

  • Connect the USB connector of the PCSGU250 to the PC.
  • Go to the Device Manager.
  • Install the driver.

Here you can download the detailed step-by-step instructions to install the driver: box.com/s/vh9olqyx3idhhxn8ujwm

All done, it is working, thank you.

Hi, I had the same problem as described in the first post in this thread, and I used the method described in https://www.box.com/s/vh9olqyx3idhhxn8ujwm. I was able to install the driver without any problems, but now I get a message “I/O error 103”.

I use Windows7 64 bit.

What can I do further?

p.s. installation under XP has never posed any problems.

[quote]Hi, I had the same problem as described in the first post in this thread, and I used the method described in box.com/s/vh9olqyx3idhhxn8ujwm. I was able to install the driver without any problems, but now I get a message “I/O error 103”.

I use Windows7 64 bit.

What can I do further?

p.s. installation under XP has never posed any problems.[/quote]

Apparently I had to start the PCLab2000LT as administrator. If I do so the I/O error 103 is gone. :oops: :oops:

Thanks anyway!

The I/O error 103 indicates that the program can’t load the file pcgu250.bit.
When the PcLab2000LT is installed, this file is put to the installation folder.
In Windows 7 the default installation folder is: C:\Program Files (x86)\Velleman\PcLab2000LT

When the PcLab2000LT is run for the first time, Windows 7 makes a copy of the pcgu250.bit file to the folder:
C:\Users<username>\AppData\Local\VirtualStore\Program Files (x86)\Velleman\PcLab2000LT
Next time Windows uses this copy.
The bad thing is that the software update doesn’t update this copy of the file. It has to be manually deleted when a new version of the PcLab2000LT is installed.

Strange thing is why your Windows 7 doesn’t allow the program to load the pcgu250.bit file.
I made a test in Windows 7 x64:

  • First I created new user account for a standard user.
  • Then I run the PcLab2000LT under this account.
  • There was no need to use “run as administrator” option.

[quote=“VEL255”]The I/O error 103 indicates that the program can’t load the file pcgu250.bit.
When the PcLab2000LT is installed, this file is put to the installation folder.
In Windows 7 the default installation folder is: C:\Program Files (x86)\Velleman\PcLab2000LT

When the PcLab2000LT is run for the first time, Windows 7 makes a copy of the pcgu250.bit file to the folder:
C:\Users<username>\AppData\Local\VirtualStore\Program Files (x86)\Velleman\PcLab2000LT
Next time Windows uses this copy.
The bad thing is that the software update doesn’t update this copy of the file. It has to be manually deleted when a new version of the PcLab2000LT is installed.

Strange thing is why your Windows 7 doesn’t allow the program to load the pcgu250.bit file.
I made a test in Windows 7 x64:

  • First I created new user account for a standard user.
  • Then I run the PcLab2000LT under this account.
  • There was no need to use “run as administrator” option.[/quote]

Thanks! :smiley: :smiley:

Hi,

I have my PCSGU250 on an Acer Netbook running Windows 7 Home Premium. The PCSGU250 has Firmware 1.01 & Software 1.08. Everything runs fine except when I’m running low frequency.

For example:

I’m trouble shooting a complex clock pulse timing issue and using LEDs to view the characteristics. So I’m running the clock pulse generator at 1Hz to 5Hz. The screen takes 15 to 20 seconds to refresh. This is impractically slow.

I suspect you are aware of this. Is there a batch or other file that can be used to ‘tweek’ the system in order to improve this? Are you planning to address this in the next software version? Is there a Firmware upgrade/update required to fix this?

Thanks in advance. Other than this issue … I enjoy using my PCSGU250.

Sincerely,

Greg East

In the oscilloscope mode all the data have to acquired to the oscilloscope’s memory before displaying the waveform. On the 500ms/div range this takes indeed rather long time.
The USB communication used is too slow to transfer the data in “real time” at the 250 samples/second used on the 500ms/div range.

In the transient recorder mode the data is immediately transferred to the PC software and displayed on the screen. The minimum sampling interval is 10ms (100 samples/second) in this mode.

Can you use the transient recorder mode?
Using the File menu option “AutoSave Data” you can save a continuous record of data to file.

I am very disappointed in that. Why can’t you extrapolate the data and decompress (expand) the data? At lower frequencies people aren’t looking for high resolution. The digital Tektronix I owned (before I had to sell it for $ because of the fine American Economy) did not have this problem.

This just isn’t right. You should develop a multi-mode scope that can display in either real time or ‘memory retain’ modes. Interactive game graphics handle this kind of data just fine.

I tried your suggestion with the transient recorder and it’s even slower … it’s terrible. For $300, it should not have this limitation. So I guess your present architecture will continue to suffer from this shortcoming and you’ll make no effort to fix it. I know I’m not the only one with this complaint.

On another issue: My CH1 probe seems to impart excessive probe load to my circuits … an they are not at all sensitive circuits.