In what conditions (settings) it freezes? Or does it do this just after the startup?
This may be a driver problem.
There are two alternative drivers on the disk.
If problems with the driver version 12/19/2007, 1.0.0.6 then you can remove this driver.
Unplug and plug the PCSGU250 and install the WinUSB driver from the folder: PCSGU250Driver_WinUSB.
Finally use Device Manager to check the right version is installed:
The version should be: 05/21/2008, 1.0.0.0
HI,
Driver is 5/21/2008 1.0.0.0
The scope has been running fine. Kept getting better with each update as issues were resolved. As I said I had one channel on the function generator and the other probe and its ground across a 121 x 12 VAC step-down transformer (isolation type). The output of the transformer is 12.58VAC read from a precision meter reading True RMS +DC. I ran all day. I swapped channels/probes then boink, the thing locked up. I powered down, waited, unplugged/plugged, etc. Booted and it worked for a while then froze up. even if I don’t have an external input and only go channel-probe to generator, it runs for a few seconds then freezes.
Something happened when I swapped the probes. It hasn’t run since. It’s been good straight through since Friday evening until tonight (Monday, Pacific Daylight time).
No, it is broken. Boo Hoo,
Greg
When swapping the probes may it be possible you connected momentary the transformer output between the grounds of the two probes? This causes a high short circuit current to flow on the PCB between the two input connectors. This may have damaged something on the board.
The input voltage 12.58VAC to the input in normal way (between the input and GND) do not damage anything.
If the input circuit amplifier is damaged it shouldn’t cause the scope to freeze.
Have you tried other USB socket of the PC?
[quote=“VEL255”]When swapping the probes may it be possible you connected momentary the transformer output between the grounds of the two probes? This causes a high short circuit current to flow on the PCB between the two input connectors. This may have damaged something on the board.
The input voltage 12.58VAC to the input in normal way (between the input and GND) do not damage anything.
If the input circuit amplifier is damaged it shouldn’t cause the scope to freeze.
Have you tried other USB socket of the PC?[/quote]
Hello VEL255,
Thanks for putting up with my frustration (unlike some others). I plugged the unit in this morning and the computer did not see it. It would not launch.
I switched USB connections between the Scope and my Belkin wireless. The wireless re-acquired fine and hooked up to the router. The computer saw the scope and was insistent upon loading drivers. I gave it the disk and it reinstalled but very balky … I had to try a couple of times. It finally took and I was a little surprised that all of the correct versions are now resident.
I hooked everything up like before and even swapped probes like before. Thing are now working (maybe it needed a good night’s sleep).
Thinking on the possible incident that might have caused (something), I’m recalling the failure occurred when I changed the (supplied) probe switch from 10X to 1X just before unhooking it.
I would appreciate your feeling if this could have caused a clitch that could have ‘shocked’ some firmware in the scope. I don’t know the protocols your product uses (PC / Scope).
Thanks,
Greg
Thanks,
Greg[/quote][/quote]
Hello VEL255,
Well things ran very smoothly for about 8 hours then it froze up again. I have uninstalled and re-installed the software twice more. Now when I boot the Scope it freezes whenever I toggle the “Run” button. Also there is NOTHING hooked up … no probe is even plugged into the front of the unit, once again - it freezed when I toggle the “Run” button with nothing plugged into it.
Things just seem to be deteriorating. Any help thanks,
Greg
Hi,
Have you tried the PCSGU250 on a different machine?
Maybe a friends machine if you don’t have another one?
Just a thought.
I don’t have another machine but thanks for the suggestion. I, like many, don’t think you should have to buy a computer to comply with the peripheral. I am running a purchased, out of the box, XP-Pro with SP2.
I even uninstalled the software and downgraded to the disc … V1.0.1, etc.
Again, it launches runs for a second, but if I toggle ‘Run’ “on-off” it freezes even if no probe is connected. I haven’t received any further suggestions from the Velleman folks of late.
Now I guess I contact the distributor, thanks,
Greg
Gmeast,
One of the main reasons I made this suggestion was to help figure out is a scope (PCSGU250) or is this a problem in the USB ports of the computer.
Could be a loose connector on the USB port or maybe the 5 volts is dipping a little.
Like I said it was just a thought.
I’m sorry about all the problems you’ve been having with this PCSGU250.
The cause to the problem may be some occasional component failure.
It is very difficult to say why this has happened.
It is very strange that the scope may run 8 hours and then froze up again.
Just as a final try: What happens if you remove the driver. - Unplug /plug the scope and install the other driver from the disk (non WinUSB version from the folder PCSGU250Driver).
Hi VEL255,
Ok well it seems the driver issue was the culprit. Why am I not surprised that REMOVAL of the WINdriver made it work. Anyway, I also did a ‘soft’ test and chose one of the probe ranges that was ‘too’ low and the Scope “actively” disconnected. This is how I would have designed it … good job.
I upgraded back to beta V1.07 and got good math and and rest of the functions.
I guess there’s a lesson to be learned in all of this … not exactly which one though.
Thanks at this stage.
other topic: now that I’m gun shy, what is the best way to protect this scope from voltage transient you might encounter with measurements of inductive circuits (motor, switches, etc) where you might encounter BEMF spikes …use TVS across the Scope connections or can you steer me to good circuits/components for this type of protection?
**Please anyone with experience here please comment or start another topic on “Scope Protection”
Thanks,
Greg
OK. I hope your PCSGU250 now finally stays operating…
There is a good over voltage and transient protection circuit at the input of this oscilloscope.
Anyhow, if very high transients may occur, it is good to use the x10 setting of the probe.
[quote=“VEL255”]OK. I hope your PCSGU250 now finally stays operating…
There is good over voltage and transient protection circuit at the input of this oscilloscope.
If very high transients may occur it is good to use the x10 setting of the probe.[/quote]
Hi VEL255,
Just as a confirmation, I un-installed the device (in device manager) and re-installed it several times switching back and forth between the two drivers. There is NO DOUBT that the WINdriver was the issue in my configuration
Other topic: When will there be the ‘official’ version of V1.07?
Thanks again,
Greg
[quote]Just as a confirmation, I un-installed the device (in device manager) and re-installed it several times switching back and forth between the two drivers. There is NO DOUBT that the WINdriver was the issue in my configuration[/quote]This is very strange. So far no one has reported this kind of problem with the WinUSB driver.
Anyhow, it seems it is good to have these two totally different driver alternatives for the PCSGU250.
We will collect all the improvements and all the user response to the test version first.
The last “official” release is from May 2009. I think it is soon time to update to v1.07.
Waiting for your comments on the beta…
[quote=“Wrong Way”]Gmeast,
One of the main reasons I made this suggestion was to help figure out is a scope (PCSGU250) or is this a problem in the USB ports of the computer.
Could be a loose connector on the USB port or maybe the 5 volts is dipping a little.
Like I said it was just a thought.[/quote]
Hi Wrong Way,
Thank you very much for input and I appreciate you suggestion.
Thanks,
Greg
[quote=“VEL255”][quote]-------------------------
We will collect all the improvements and all the user response to the test version first.
The last “official” release is from May 2009. I think it is soon time to update to v1.07.
Waiting for your comments on the beta…[/quote][/quote]
Well, the only thing I seem to be questioning is the “Probe Test”. I have noticed I cannot adjust one of my Velleman probes (I purchased a second probe). I can’t adjust the probe to get the ‘over sharp’ waveform IOW it doesn’t seem to have the range of adjustment to get a really ‘sharp’ square wave in the test.
I don’t know if this has to do with the probe or the input amp to the scope.
Just an observation. Thanks,
Greg
Strange if the first probe is OK with the adjustment but the new one you purchased doesn’t.
Does it seem these both probes are the same type?
This is the proper probe for the PCSGU250: velleman.eu/distributor/prod … /?id=19217
compensation range: 10 to 50pF
[quote=“VEL255”]Strange if the first probe is OK with the adjustment but the new one you purchased doesn’t.
Does it seem these both probes are the same type?
This is the proper probe for the PCSGU250: velleman.eu/distributor/prod … /?id=19217
compensation range: 10 to 50pF[/quote]
Hi VEL255,
Both probes are the same. The one that came with the scope and the second one I purchased from distributor same P/N.
Here are the scope captures of both probes. Note neither can be squared up properly. These are as good as I can get. Probe Test was performed on each probe, both channels = same.
Now the captures:
probe1 ch1
probe 1 ch2
probe2 ch1
probe2 ch2
I do recall when I first received the scope I DID have the full range of adjustment … Calibration was the first thing I did.
Anyway, there ya go,
Greg
[quote]I do recall when I first received the scope I DID have the full range of adjustment … Calibration was the first thing I did.[/quote]It is very strange why the calibration fails now.
What kind of square waveform do you see on the screen if you change to x1 setting of the probe?
[quote=“VEL255”][quote]I do recall when I first received the scope I DID have the full range of adjustment … Calibration was the first thing I did.[/quote]It is very strange why the calibration fails now.
What kind of square waveform do you see on the screen if you change to x1 setting of the probe?[/quote]
Hello VEL255,
I’m glad you asked. That’s what I last did before I shut down. In x1 setting the wave is ‘over sharp’, that is, it’s the other extreme and no adjustment or change in wave shape as you turn the screw on the probe a sin x10.
Greg