Hi all, I recently bought a PCSGU250 and yesterday I was testing it when I ran into something really weird and I would like to know what’s going on.
SYMPTOMS:
While in RUN mode (continuous readings) my scope stops acquiring at random times.
Same happens sometimes on SINGLE mode (one-shot acquisition).
DETAILS:
The PCSGU250 looks functional and relay state chenges are all audible (AC/DC/GND coupling, ON/OFF power, etc.) [OK]
First the scope was calibrated without attached circuits [OK]
Velleman default 60MHz probe set to x10 attenuation [OK]
The problem tends to happen on shorter time division settings (from 0.5ms lower), it doesn’t happen on higher settings (1ms, 5ms …); on 0.1ms it samples for some seconds then stops, on 50us it samples for a frames then stops, on higher settings it just takes a single shot and stops.
When it stops sampling it actually looks like it is not receiving input signals at all. In this condition:
the circuit is still attached
the RUN button is still depressed
the status indication below the button is “Running”
A direct consequence is that the scope doesn’t trigger anymnore (even if trigger level and CH V-axis are moved up and down)
TESTS PERFORMED:
Tested without circuits attached at all (only viewing etherial noise)
Tested on other CH
Tested on other v/div settings
Tested also on Probe&Osc x1 attenuation
Tested on other USB ports
Tested on other Computer
Tried rebooting PC
Tried disconnecting PCSGU250 and re-connecting (application close first then disconnect)
Tried installing both (one at the time) drivers PCSGU250Driver and PCSGU250Driver_WinUSB (this one simply doesn’t install: error)
Tried using triggering both ON and OFF
Tried also using the SpectrumAnalyzer and it leads to the same problem: OK below 60KHz and stops sampling at random over 120KHz, becomes worse for higher settings (300K, 0.6M) where it takes single shots although remaining in “Running”
NOTES AND REMARKS:
In the same way when using SINGLE acquisition mode, it sometimes acquires correctly and others it stops without ever acquiring. In this particular case the programme cannot be closed/stopped/exited (File>Exit) and as soon as I press SINGLE or RUN again and the acquisition starts again (for a while) the programme closes (as if it was waiting for data to be acquired before closing).
All the test mentioned above have failed at some point leading to the problem (acquisition stop/failure).
Please help, I would like to find out if I have to RMA (I’m from Milan - Italy) and I bought this product from an Italian shop.
I am available to perform any tests or receive suggestions.
Thanks in advance,
Andy
SYSTEM SPECS:
Desktop -
AMD 940BE (3GHz quad core)
8GB RAM
1TB SATA-RAID 0
8 USB 2.0 ports
Vista Ultimate 64bit
Notebook -
INTEL T2300 (1.6GHz dual core)
2GB RAM
80GB SATA
4 USB 2.0 ports
XP Pro SP3
If you have the v1.06 running:
This may be a driver compatibility problem.
Please remove the PCSGU250 driver (dated 12/19/2007, version1.0.0.6) and
install the driver from the CD folder: PCSGU250Driver_WinUSB
This driver is dated 05/21/2008, version 1.0.0.0
[quote]Tried installing both (one at the time) drivers PCSGU250Driver and PCSGU250Driver_WinUSB (this one simply doesn’t install: error)[/quote]What is the error message. Is it same message both in the Desktop and Notebook PCs?
Yes, I have downloaded v1.06 and also v1.07 (test version which I like a great deal more due to all the additional features). The scope works but has the same acquisition problems (mentioned before) on both versions.
NOTE: The version provided on the original delivered mini-CD is v1.01 and renders the same issues
Driver PCSGU250 (despite PCSGU250Driver_WinUSB doesn’t) warns that the driver is not digitally signed but that’s OK, it installs correctly and allows me to turn the scope ON (blue READY led: on).
The error message I get is the same for both PCs:
[code]Windows encountered a problem installing the driver software for your device
PCSGU250
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
CLOSE
[/code]
The only odd thing I noticed is that when the HW device is found, it is named “PCSGU250 Oscilloscope/Function Generator” (with a yellow exclamation mark) and as soon as I install the PCSGU250 software driver it changes name into “PCSGU250” and the exclamation mark goes away.
I tried installing PCSGU250Driver_WinUSB the from the original mini-CD and also from the internet (http://www.velleman.eu/distributor/support/downloads/?code=PCSGU250) but the results are the same for both the installation phase (only one driver of the two installs) and the scope utilization phase.
I wish I could get that second driver to work, maybe that is the key to my problems … I don’t know how to force it.
[…]
I have just been testing some more on other things that the function generator can do and just found another problem
CH1 active and “Running” in SpectrumAnalyzer with Velleman 60MHz probe (x10) linked to the FuctionGenerator on sweep mode
I stop the sweep somewhere in between the values and the peak stops at frequency (A) [OK]
On the generator I de-select the sweep mode to move on to manual (sine wave) and select a different frequency (B)
The generator digital frequency is shown to be (in digits) as (B) but in reality the generator is still rendering frequency (A) as visible on the actually running CH1 SpectrumAnalyzer: kind of stuck at same frequency showing the same peak @(A) and the only variation is given by normal noise which constantly changes around it.
Is this a bug of version 1.06 and everybody out there has it too or is it my scope that is having serious HW or driver or firmware problems?
Maybe there is some sort of conflict with other USB device using the WinUSB driver in your PCs?
[quote]The only odd thing I noticed is that when the HW device is found, it is named “PCSGU250 Oscilloscope/Function Generator” (with a yellow exclamation mark) and as soon as I install the PCSGU250 software driver it changes name into “PCSGU250” and the exclamation mark goes away.[/quote]This is OK.
[quote]Driver PCSGU250 (despite PCSGU250Driver_WinUSB doesn’t) warns that the driver is not digitally signed but that’s OK, it installs correctly and allows me to turn the scope ON (blue READY led: on).[/quote]Both of the drivers are not digitally signed. It is strange why WinUSB doesn’t warn. It should warn.
Maybe you have other USB device having a digitally signed WinUSB driver installed in your PCs. On some strange way this causes the problem…
Here is a link to download newer version 1.0.0.2 of the WinUSB driver: velleman.eu/downloads/files/ … sbdrv2.zip
Please remove the previous driver before installing this one.
[quote]- CH1 active and “Running” in SpectrumAnalyzer with Velleman 60MHz probe (x10) linked to the FuctionGenerator on sweep mode
I stop the sweep somewhere in between the values and the peak stops at frequency (A) [OK]
On the generator I de-select the sweep mode to move on to manual (sine wave) and select a different frequency (B)
The generator digital frequency is shown to be (in digits) as (B) but in reality the generator is still rendering frequency (A) as visible on the actually running CH1 SpectrumAnalyzer: kind of stuck at same frequency showing the same peak @(A) and the only variation is given by normal noise which constantly changes around it.[/quote]This seems to be a bug. This will be fixed in the next release.
If you close the sweep function when the “Stop Sweep” button is down the frequency is locked.
Workaround: Release the “Stop Sweep” button before switching to the other waveform functions.
Yes, I think that you really have a point there, that must be the problem; I will further debug that as soon as I have some time to spare.
I finally managed, by beggin a friend to lend me his PC (XP SP2), to test the PCSGU250Driver_WinUSB driver again and it worked; scope samples at any given frequency continuosly both in Oscilloscope and SpectrumAnalyzer modes!
I downloaded and tried to install these also (after deleting previous drivers) but the result is the same on my computers; on my friend’s PC (XP SP2) it works correctly. I truely think I have some conflits/problems on both my PC.
The workaround does the trick and I will wait for the next release to see the latest improvements. I’m glad to be useful to the debugging/development of the software.
[quote]I downloaded and tried to install these also (after deleting previous drivers) but the result is the same on my computers; on my friend’s PC (XP SP2) it works correctly. I truely think I have some conflits/problems on both my PC.[/quote]This is a very strange problem. - You get the error message and can’t get the WinUSB driver installed on both of your PCs!
What USB devices do you have connected to these PCs?
I have just now finished installing a Virtual Machine with a default WinXP and I have successfully loaded PCSGU250Driver_WinUSB_v1.0.0.2 together with PCLab2000LT v1.07 on it.
It now works fine on my PC. This further demonstrates that I must have something going on my PC drivers/services …
Do you know of any services which MUST be on in order to make the software/drivers work? I know that I have been customizing the PC a lot during time, I hope I haven’t turned some processes off which are essential to the SW.
It is good that you got the PCSGU250 driver installed and the scope running in the virtual PC!
[quote]Do you know of any services which MUST be on in order to make the software/drivers work?[/quote]Sorry - I have no idea what services are needed.
[quote]I know that I have been customizing the PC a lot during time, I hope I haven’t turned some processes off which are essential to the SW.[/quote] It seems that this may be the reason to the problem.
I have also tried patching Vista to SP2 (I was on SP1 before), but all that to no avail. I was hoping that windows winusb driver would be refreshed (in case of corruption); either SP2 does not contain updates for that file or that file/driver is not the problem.
Fortunately I have my workaround now but I’m still very puzzled.
[quote]either SP2 does not contain updates for that file or that file/driver is not the problem[/quote]I have Windows Vista SP2 (x32) and the WinUSB driver is running without any problems.
The driver seems to work well under Windows 7 (x64) too.
[quote=“VEL255”]This seems to be a bug. This will be fixed in the next release.
If you close the sweep function when the “Stop Sweep” button is down the frequency is locked.
Workaround: Release the “Stop Sweep” button before switching to the other waveform functions.[/quote]
Well, I just downloaded the official v1.07 and guess what? The problem is GONE!!
The sweep bug I reported has vanished! I think I’m going to give Velleman’s support one big THUMBS UP
Do you know of any services which MUST be on in order to make the software/drivers work? I know that I have been customizing the PC a lot during time, I hope I haven’t turned some processes off which are essential to the SW.