Some USB cables are incapable of power delivery necessary to the ADALM2000 (or are just plain flakey). Please use the provided USB cable. Also in order to troubleshoot this, you try using two cables, plug in a separate cable to the USB connector for power delivery (to the USB power connector), while using the center USB connector for data transfer. If using two cables works, it normally means it's a cable, or voltage droop issue on the host.
Preferences.ini contain the user-settings that are saved in-between sessions. Sometimes these can get messed up and can cause problems. In order to reset them, go to:
These file are located in:
C:\Users\<your_username>\AppData\Roaming\ADI Sometimes this is a hidden directory, and you unhide it.
and delete (or rename)
Preferences.ini.bak. The preference is to rename things with a different suffix, so if you need to report a bug, the file still exists.
Scopy configuration can sometimes get messed up when updating as opposed to uninstall/reinstall. If you are facing this issue, you can try uninstalling Scopy and then reinstall.
Make sure you install Scopy in a location that doesn't require any write privileges since Scopy needs to write to it's installation folder.
If you are having trouble connecting through USB, you can always connect to the ADALM2000 through the network interface. The USB connection can cause all kinds of problems on various systems. In order to connect through the emulated network interface follow these steps.
Visit the ADALM2000 firmware page https://github.com/analogdevicesinc/m2k-fw/releases.
Compare the latest firmware version on this page with the one you have installed. Follow these steps to update the firmware.
Some laptops limit the amount of current that can be delivered via an USB port (either native or from a docking station/usb hub). In order to workaround this issue you can try the following:
Download latest version of https://github.com/analogdevicesinc/libiio/releases .
Open a command prompt and run
iio_info -u "ip:192.168.2.1"
Download the debug files associated with your release. From the same place you downloaded the release, download the “debug-64.zip” file. If you can't remember where you downloaded the release from, a safe bet would be to redownload and reinstall Scopy and the appropriate debug archive.
You can now reproduce bug/crash/hang