Post Go back to editing

ADALM2000 does not start under Windows 10 after installation

Hi,

I followed the installation steps and Scopy does not start after installation under Windows.

In another Windows it starts but completely blocks the internet. I am super frustrated.

Please I need help! 

Parents Reply
  • Meanwhile I tried your suggestion(ipaddr ipaddr_host  changes on the other PC(internet blocking issue), it didnt work. But lets look at it after we can solve the first one(Scopy exiting immediately after start). Because it is more critical. Im using the latest firmware and SW and drivers ect. And the internet blocking issue always exsited. I could live with that. But now in one of my PC Scopy does not even start.

    Both machines are 64 bit Windows. I cant believe such critical issues exists in both PCs. 

Children
  • Someone will look into these dumps. Since you have problems on more installations, and we're not aware of such issues. 

    Are your Windows PC managed?

    -Michael

  • Hi I dont know what you mean by managed. But Scopy used to work on this PC before(with again blocking internet) and I uninstalled it maybe 6 months ago. Recently I reinstalled it and the issue(closing right after start) began. Im very frustrated about this ongoing major issues. Do you have only Linux support? I really need help and dont want to buy another device since they are expensive.

  • It seems I solved the first issue myself. 

    Here what I did:

    Eventlog of Windows was showing an issue with libusb-1.0.dll.

    Scopy was installed in: C:\Program Files\Analog Devices\Scopy

    I downladed the latest verison of libusb-1.0.dll here https://libusb.info/

    Then I copied libusb-1.0.dll into Scopy folder and overwrote the existing one. So far it works. 

     

    So the next issue is with the other PC where Scopy blocks internet when USB is plugged in.

  • The internet blocking may be related to phonehome feature of Scopy (it checks if scopy needs to be updated). It could be your firewall that's acting up. Either allow Scopy to access the internet, or go to Scopy preferences, and uncheck "Enable automatic update checking". 

    Besides this feature, Scopy does not access the internet in any way.

    -Adrian

  • Another issue may be related to the fact that the ADALM2000 creates a virtual ethernet device when plugged in, check out mhennerich response up in the thread.

  • Hi,

    Both didn't work for me. Its happening before I open Scopy.

    Here I am going the write details without private info. I hope you or some support people here can help me.

    So the issue happens when I plug ADALM2000 right after it pops up the ADALM2000 drive. 

    Here is my config file:

    [NETWORK]
    hostname = m2k
    ipaddr = 192.168.4.1
    ipaddr_host = 192.168.4.10
    netmask = 255.255.255.0

    [WLAN]
    ssid_wlan =
    pwd_wlan =
    ipaddr_wlan =

    [USB_ETHERNET]
    ipaddr_eth =
    netmask_eth = 255.255.255.0

    [SYSTEM]
    xo_correction =
    udc_handle_suspend = 0
    # USB Communication Device Class Compatibility Mode [rndis|ncm|ecm]
    usb_ethernet_mode = 0

    [ACTIONS]
    diagnostic_report = 0
    dfu = 0
    reset = 0
    calibrate = 0

    Here is the network situation before ADALM2000 is connected:


    Wireless LAN adapter Local Area Connection* 3:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Wireless LAN adapter Local Area Connection* 4:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Wireless LAN adapter Wi-Fi:

    Connection-specific DNS Suffix . :
    Link-local IPv6 Address . . . . . : fe80::1997:7a44:fded:cb05%7
    IPv4 Address. . . . . . . . . . . : 10.209.196.138
    Subnet Mask . . . . . . . . . . . : 255.255.128.0
    Default Gateway . . . . . . . . . : 10.209.128.1

    Here is the network situation after ADALM2000 is connected:

    Ethernet adapter Ethernet 2:

    Connection-specific DNS Suffix . :
    Link-local IPv6 Address . . . . . : fe80::15e3:e73b:7426:a862%17
    IPv4 Address. . . . . . . . . . . : 192.168.4.10
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :

    Wireless LAN adapter Local Area Connection* 3:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Wireless LAN adapter Local Area Connection* 4:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    Wireless LAN adapter Wi-Fi:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :

    As you see above IPv4 address of Wireless LAN is 10.209.196.138 and ADALM2000 has 192.168.4.10. And when I plug the USB of the ADALM2000 it creates virtual Ethernet but disconnects the Wifi. Disabling and enabling them also didn't work.

    I have been struggling with this years.

  • It didnt work. I followed the exact steps:

    1. Open Registry Editor.

    2. Go to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WcmSvc\Local.

    3. Create/change the fMinimizeConnections registry DWORD to 0.

    4. Close Registry Editor and reboot.

    Still ADALM2000 blocks the Wifi adapter in two PCs. 

  • Tried rest advices still no luck. I dont know what ADALM2000 does and Windows locks the entire WLAN

  • This issue must be specific to your setup. On all PCs I've seen so far the RNDIS adaptor doesn't disable WLAN. 

    What you can do is to DISABLE the RNDIS interface. And instead use the default IIO over USB instead. That's what you might be using anyways.

    Do a right click on the RDNIS adaptor in:

    Control Panel\All Control Panel Items\Network Connections

    And select 'Disable'

    -Michael