[Mac + Analog Discovery 2 + Waveforms 2015: No device detected]

@malexander @attila

So, the saga continues.  Recent news :

• RMA'ed the device and got another.  I bought another powered USB hub.  Still not working.
• Dug up an old laptop, put linux on it.  Device verified as working - at least in linux.
• Spent more time clicking in the google machine.  Someone posted this as a diagnostic maneuver :

  • 
    export ADEPT_RT_LOGDETAIL=1
    export ADEPT_RT_LOGFILE=~/adept_erc.log
    python digi_enum.py
    
    dyld: warning, LC_RPATH @executable_path/../Frameworks in /Library/Frameworks/dwf.framework/dwf being ignored in restricted program because of @executable_path
    
    Digilent FTDI Enumeration library loaded
    Devices: 1
     1. SN:210321A96879 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x140e0
    
    FTDI Version: 0x10202
    Devices: 1
     1. SN:210321A96879 'Digilent USB Device' flags: 0x2 type: 0x8 id: 0x4036014 locid: 0x140e
    
    DMGR Version: 2.8.4
    Devices: 1
     1. SN:210321A96879 'Analog Discovery 2' PDID: 0x40300360
    
    DWF Version: 3.10.9
    Devices: 1
     1. SN:210321A96879 'Analog Discovery 2'
    
    cat adept_erc.log
    
    System Time     Process     Thread        ERC     ERC String                  Message
    2330798318      4468        4517828032    1       ercNotSupported             FTDIC::FGetInfo unsupported device attribute

Does that error message mean anything to anyone??

[Mac + Analog Discovery 2 + Waveforms 2015: No device detected]

Sorry for the confusion.  The comment about parallels was posted by a different user.  I do not have that installed.

Thanks.

1 hour ago, malexander said:

@zaxxon

I'm not sure what's preventing libftd2xx from accessing the device, but if we can't resolve that issue then Waveforms will never be able to see the AD2. I read back through your posts and noticed that you were running Parallels desktop. Can you confirm that the AD2 USB device is not being taken over by parallels and passed to a VM?

Thanks,
Michael

 

[Mac + Analog Discovery 2 + Waveforms 2015: No device detected]

I do not have  /Library/Extensions/ DigilentFtdiDriver.kext.

I do have /Library/Extensions/FTDIUSBSerialDriver.kext/

So, I deleted that - and restarted.  Still not working.

Thanks.

 

 

[Mac + Analog Discovery 2 + Waveforms 2015: No device detected]

I do not have any devices attached.   I have in the past, and have installed drivers from FTDI on a few occasions.

[Mac + Analog Discovery 2 + Waveforms 2015: No device detected]

Thanks for the input.  FWIW, I have used various development boards with FTDI chips over the years.  I am sure I have installed drivers. 

I did install Waveforms 3.9.1 and the dwf.framework.  Not the DigilentFtdiDriver.pkg.  I have not tried to access the device through any other application - with the exception of the MacOS System Report to review USB devices. 

Here is the output from the digi_enum.py script :

dyld: warning, LC_RPATH @executable_path/../Frameworks in /Library/Frameworks/dwf.framework/dwf being ignored in restricted program because of @executable_path

Digilent FTDI Enumeration library loaded
Devices: 1
 1. SN:210321AA28F7 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x141b0

FTDI Version: 0x10202
Devices: 1
 1. SN: '' flags: 0x1 type: 0x3 id: 0x0 locid: 0x0

DMGR Version: 2.8.4
Devices: 0

DWF Version: 3.9.1
Devices: 0

Run as user or sudo - same result.  I am not sure why, but with the powered USB hub the device is not seen by the OS (or the script).  Those USB ports are otherwise functional.

Thanks,

Doug

[Mac + Analog Discovery 2 + Waveforms 2015: No device detected]

On 12/31/2018 at 11:59 AM, hartfort said:

This Issue still seems to persist.

I have the just downloaded the digilent.waveforms_v3.9.1.dmg and always get the message saying no device detected.

Im running MacOS 10.14.2 Mojave.

I noticed that the device is listed in my networking devices(see picture attatched).

Also i am also running a VM on my system, is it possible that parallels somehow messes with the drivers for the AD2?

I would love to get this fixed. Thanks!

 

Same issue here.  Same OS.  Same problem. I tried a powered USB hub - no go. The device is recognized by the os FWIW.

Thanks for any help.