Hi there - I recently purchased a PCSGU250 and am trying to get it to work properly on my new Windows 10 tablet (Surface 3 Pro).
I’ve used other guidance to disable the driver authentication checks so that the USB driver(s) would install, so now I get a blue light, the function generator works, and when I do my FIRST run of the transient analysis tool (only one I’ve tried so far), it works great. When I re-run, however (hitting either the Run or Single buttons), nothing displays on the o-scope screen, and it typically ends up locking up the app entirely. Nothing I can do short of killing it in task manager gets me out of it.
Is this a known issue? Note that I also have to run the app in compact mode, with Windows 7 selected as well as run as admin, to get anything to happen at all …
Thanks much! I really hope I can get this working, I don’t want to have to return the device!
Jeff
There may be some sort of compatibility problem.
This is not a known issue.
Are you using the latest software and the latest driver?
If not, they are available here: velleman.eu/support/download … u250&type=
I bought a PCSU200 and tried to install the software.
After installing the PCLab software (successful) Windows 10 reports a problem installing the (windows 8) driver (“problem while adding to the archive”)
Am I doing something wrong?
Thanks for any help.
Since Velleman doesn’t seem to supply any real support, the forum is my last resort
If you have problems with the Win 8 driver you can use the Win 7 driver instead.
Download and extract the driver: “Drivers for Windows Vista and Windows 7. (Can also be used for Windows XP)” from: velleman.eu/support/downloa … e=PCSGU250
Well, for whatever reason, the Windows 7 USB drivers seem to work much better than the Windows 8 drivers on Windows 10. I now can do multiple runs and the app doesn’t lock up. The only oddity that I’ve noticed is that when I am using the Transient Recorder and I select a time div other than 1s, once I hit Run it switches to a 1s time div for the real-time display, then reverts back to the time div I’ve selected once the run is stopped. This isn’t a deal-breaker but it is somewhat annoying, certainly. Is this by design?
Update: also, something isn’t getting totally cleaned up in the driver or some supporting software, because when I close the app entirely and then restart, the app appears to hang. Closing the app and unplugging/replugging in the USB cable seems to fix the problem mostly, however.
[quote]The only oddity that I’ve noticed is that when I am using the Transient Recorder and I select a time div other than 1s, once I hit Run it switches to a 1s time div for the real-time display, then reverts back to the time div I’ve selected once the run is stopped. This isn’t a deal-breaker but it is somewhat annoying, certainly. Is this by design?[/quote]The sample rate and the record length are identical on all ranges from 1s/div down to 20ms/div.
During the recording the whole record is displayed on all the ranges 1s/div down to 50ms/div.