PC software: I installed the drivers, windows recognized the device as "USB Test and Measurement Device (IVI)".
But neither DigitalScope or WaveEditor were able to connect, complaining with message "The device is not connected".
Edit: After reinstalling the driver with the scope already connected, it worked.
The custom waveforms can be set up to 25MHz too.
I have dso2d10, installed all the software and drivers, but now my laptop sees it as "USB Test and Measurement Device (IVI)" but the waveform generator and keysight app cant detect it i don't know why, I tried everything (my firmware is 3205 from manufacture)
after contacting hantek official store on aliexpress he advised running the app as administrator but no luck.
what could be the problem? everything else is good with my oscilliscoop
Did you installed the IOLibSuite_18_2_28229?
Yes I did , before that it was generic USB i think, when i unistall the driver it appear as DSO2D10 but with a warning sign that the driver has some problem
Are you using Windows 11 22H2? I currently have exactly the same as you using this windows version. Works fine in Windows 10 22H2 and windows 11 prior to 22H2, so roll back, if this is your situation, and it will work.
I am using vmware player with windows 10 22H2 guest and pass through the USB device from the host (Windows 11 22H2) , whie the host refuses to work, it works fine in the VM, but also tested roll back and various hardwares and VMs (virtual box also works but video capture....) , just windows 11 22H2 on any hardware or in a VM refuses to work with the symptoms exactly as you describe.
Well, that explains a lot of things, I suspected it was from the windows version.
i will try to use a VM, but i used the software in compatibility mode where it can work in windows 8 or 7 environments with no luck.
Compatibility mode really dont do anything, just lies to programs about the version of windows they are running on.
Depending on how you got to 22H2 version you should be able to go to windows updates settings and uninstall the 22H2 update. Keysight software starts working immediately (tested in several installation scenarios) but if you feel up to running a Virtualbox or Vmware (if your using PRO Win then you also have the built in virtual machines but I don't recommend it for your daily basher.) then download and install windows 10 (from Msoft site ) in a VM and your gold.
I can't tell if it is Windows or Keysight/ivifoundation problem, so dunno who needs to update or fix what, but it looks like windows is rejecting the Keysight VISA libs,as the IVI instrumentation device always shows waiting/failed to load extension driver when you view it's properties and check event logs. 22H2 implemeted/fixed/broke? some security 'features' around drivers and signing, though signing does not seem to be the problem soooo......
That it does not affect windows 10 22H2 leads me to think this is something about Secureboot/TPM/UEFI as this is the ony real difference at this level, but this is probably completely bogus and a total red herring? Disabling / enabling related features has no effect so until windows become less opaque I am stumped, hence the workarounds.