• 1
attila

Analog Discovery troubleshooting

Question

During device opening internal chips are enabled and configured. This results in consumption increases, specially when the 100 MHz clock (PLL) is started. The needed current increases from 100mA to 500mA. In case the USB can't provide enough current the voltage drops below the minimal required for the device to operate and communication fails.

 

In case you get “Device configuration failed (PLL 1)" or "Communication with the device failed.” error message:

The device needs at least 2W/400mA from USB cable. To satisfy this:

- Try to use different USB cable and computer plug.

- Use the USB plug on the back of the PC, not the one on the front panel.

- Use short cable, do not use long cable or cable extender.

- Use powered USB-hub, avoid un-powered hub.

- Use USB-Y cable to load power from two plugs.

 

Device not detected by WaveForms:

Open Windows Device Manager then connect the device and wait up to one minute for a device to appear:

 - USB Serial Converter, with warning

- Connect the device directly to the computer's USB plug without using external hub.

- Restart the computer.

- Reinstall WaveForms, including the Adept Runtime section.

 - USB Serial Converter, without warning

- Restart the computer.

- Reinstall WaveForms, including the Adept Runtime section.

- Other application might have erased the USB controller EEPROM (FT_Prog, programming cable drivers...)

 Use the "My device is not listed" button in WaveForms application Device Manager to reprogram the EEPROM.

 - Unknown Device

    Check the Hardware IDs under device Properties, Details tab

- USBVID_0403&PID_6014

  The USB driver is not installed.

- Restart the computer.

- Reinstall WaveForms, including the Adept Runtime section.

- USBVID_0000&PID_0000

  Device not identified or malfunction. See "Nothing shows up".

 - Nothing shows up:

- Connect the device directly to the computer's USB plug without using external hub.

- Try to use different USB cable and computer plug.

   The device or its plug might be damaged.

Edited by attila

Share this post


Link to post
Share on other sites

Recommended Posts

  • 1

Hello,

In virtual machine options try to disable USB 2.0 support, at least this helps me when using VirtualBox.

I'm using 15' MacBookPro too with dual boot to OS-X and Windows using Boot Camp, and Analog Discovery is working well.
The left side USB port on 13' MacBookPro seem to provide insufficient power.

You might try the new cross-platform WaveForms3 beta version with Windows/OS-X/Linux support. https://forum.digilentinc.com/topic/98-waveforms3-beta/

Share this post


Link to post
Share on other sites
  • 0

I was getting  “Device configuration failed (PLL 1)" error.

I tried different things. finally, I disconnected the cables and rebooted the laptop - that fixed the problem.

Share this post


Link to post
Share on other sites
  • 0

Hi,

Created this account to ask this:

I just got the device and after plugging in the USB  cable windows told me it was updating the firmware on it. I tried to stop it but couldn't. 

Very well.

I open waveforms and see the device and chose "Select"

And the reply I get is this:

"Device configuration failed
please check usb cable connections.
for further information consult the help

DPhil failed ERC:2
Programmed image id is wrong
Communication  after programming failed or image device id is wrong"

 

I was so much looking forward to use the analog discovery and this start up problems really kills it. 

How can i fix this? 

 

/ Blitz

Share this post


Link to post
Share on other sites
  • 0

Hello,

When connecting the device probably it was looking for driver update. The device should work with the provided driver as well with the one found by update.
Having the device plugged, in Windows Device Manager under USB controller, select USB Serial Controller and try Update Driver software.

As the device configuration is programmed the consumption increases a bit and having insufficient power could cause error.
Please try the following:
- Try to use different USB cable and computer plug.
- Use the USB plug on the back of the PC, not the one on the front panel.
- Use short cable, do not use long cable or cable extender.
- Use powered USB-hub, avoid un-powered hub.
- Try USB 2.0 plug of your computer or try using USB 2.0 hub.

What is the model of your computer/laptop and which Windows version are you using?

Share this post


Link to post
Share on other sites
  • 0

Hi Attila,

Thanks for your fast reply. 
I did get it to work on my friends computer. 

But i did try all USB connections and a different shorter cable then the one supplied with analog discovery. 

Maybe the problem is due to me using a macbook. With a windows virtual machine?

 

All the best/ Blitz

Share this post


Link to post
Share on other sites
  • 0

Waveforms is unable to detect the analog discovery 2. I'm prompted with "No device detected." dialog.

Current system: Mac OS X 10.10, Waveforms 3.1.5, driver is installed, USB cable is connected directly to laptop (not running in a VM).

I tried unloading the driver ($ sudo kextunload -b com.apple.driver.AppleUSBFTDI) per discussion mid way down this thread: https://forum.digilentinc.com/topic/98-waveforms3-beta/

Any suggestion as to why this is happening?

 

Share this post


Link to post
Share on other sites
  • 0

Please try restarting the Mac without the AD2 connected, try using another USB port or USB hub.

Let me know if it is working or you need further assistance.

Share this post


Link to post
Share on other sites
  • 0

I have the AD2 and it was working great until now. I plugged it in as normal and it didn't light up nor was it detected. I have tried different cables, ports, and other computers. Nothing seems to work. I need help as soon as possible with this, as it is for class.

 

Thanks

Jon

Share this post


Link to post
Share on other sites
  • 0

Hi Jon,

Could you provide more information ?
Which OS are you using ?

In case it is Windows:
Do you see "USB Serial Converter" appearing in Windows Device Manager ?

Make sure the driver version is not 2.12.4 For the solution see the following post:

 

If the driver version is good, probably some other application did overwrite the EEPROM content.
Try reprogramming it using the application I sent you in private message.

Edited by attila

Share this post


Link to post
Share on other sites
  • 0

Could I get the program too? Our AD kit doesn't show up on the computer at all. 

It did once, after it started giving us trouble, but Waveforms 2015 would end abruptly after about 2 seconds of starting the waveform generators.

Share this post


Link to post
Share on other sites
  • 0

A customer on our website asked the following question:

Hi,
I did all the troubleshooting techniques  in the thread and I am still getting the error "Device configuration failed". I am attaching the error message with this email.

Is there anything further the customer could try? The error message they refer to is available on our Gallery here.

Thanks,
JColvin

Share this post


Link to post
Share on other sites
  • 0

Hello,

Since the connection to the device gets to the PLL configuration it is unlikely to be a hardware problem.
It rather seems to be a powering issue, supply limitation from computer, bad cable or broken USB plug (in case it is an Analog Discovery 1).

Make sure there is nothing connected to the device, try using powered USB hub and a short phone charger like cable, try with the latest WaveForms 2015.
 

Share this post


Link to post
Share on other sites
  • 0

A customer on our website asked the following question:

Hello Digilent! Since i could not send my feedback through your feedback option in Waveforms, i will attach the entire message here:

Version: 2.7.5 32bit (2014-02-05)
Device: Analog Discovery rev: C configuration: 1
Open Forms: 4; Handle Count: 917; GDI Objects: 155; User Objects: 107; Threads: 32; Memory Working Set: 114,42 MB; Processor Time: 00:00:05.6316361
-------------------------------------------------------------------------------------------
OS : Microsoft Windows 7 Ultimate Service Pack 1
version: 6.1.7601 language: 1033
architecture: 64-bit Operating System
.NET : v2.0.50727.5485 v3.0.30729.5420 v3.5.30729.5420
CPU 1: Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz L2: 256 kB L3: 6 MB
RAM : 8 GB @ 1,6 GHz in 2 banks
GPU 1: NVIDIA GeForce GT 540M 2 GB
USB 1: Standard Enhanced PCI to USB Host Controller
USB 2: NEC Electronics USB 3.0 Host Controller
Screen1: Generic PnP Monitor (1920x1080 dpi: 96)
-------------------------------------------------------------------------------------------
Please describe your issue here:


Hello Digilent!

I have been adviced to make contact to you about my problem with analog discovery by one of my teachers. 

When i was working with my Analog Discovery yesterday, it suddenly stopped working. The problems are as follows;

1. I cannot connect my analog to waveforms - it tells me that "Device configuration failed" and gives me the error message:

DptilO failed ERC:7
Device configuration failed (PLL 3).

2. When i somehow sometimes manage to get through the configuration phase, Waveforms simply tells me that "The Analog Discovery has stopped working due to an overcurrent condition" - even though i haven't connected it to anything at all. 

3. All the time i am let through to the Digilent Waveforms menu, there is a flashing message in the bottom right corner saying "Discovery OFF".

I do of course have screenshots of all three issues, but it seems like i cannot attach them here. 

For troubleshooting i have tried using different USB ports on my PC - and even tried connecting the Analog Discovery to different Computers, where other Analog Discoveries were working, but nothing seemed to be able to solve the problem - my Analog Discovery gave the same error messages everywhere. 

I also tried the provided troubleshooting steps and restart the analog etc. 


I hope that you can help me!
 

I'm not familiar with this error, so I don't personally have any recommendations, but I'll make sure the appropriate engineer see's your question. You can post any screenshots that you have though on our Forum Gallery (you'll need to create an album).

Thanks,
JColvin

Share this post


Link to post
Share on other sites
  • 0

It seems the device does not get enough power or something is damaged in it which consumes too much after the device clocking is started.

You could try using a powered USB hub.

In case it is still not working please contact the support for warranty and replacement.

Share this post


Link to post
Share on other sites
  • 0

I'm also having problems with the AD

Two different Macs, Mini and Macbook Pro. Both see the USB device in the System Report under USB but when Waveforms 2015 (latest version downloaded today) opens the device is not detected. I've tried various lengths of USB cable and directly into the USB ports as well as through a powered USB hub.

Peter

Screenshot 2017-02-21 09.42.50.png

Share this post


Link to post
Share on other sites
  • 0

Following up my problem above. I installed Waveforms on a Windows laptop plugged in the AD and found it worked, moved it back to the two Macs and it worked. I'm not sure if the firmware upload on the Mac's broke it but I'm up and running now.

 

Peter

Share this post


Link to post
Share on other sites
  • 0

Hello,

For some reason my AD2 device stopped working today after a few months of good service. The board is powered via and external DC 5V/1.2A power supply and it is plugged into a USB socket at the back of my PC. I tried to connect it to two different PCs and tried to restart them both with the board disconnected.

Basically, when I open WaveForms 2015 ver. 3.5.4 (Windows 10 x64) it throws the following error:

WF_error_not_calibrated.png.2592846cf96d07732738168b19699044.png

And if I try to calibrate it:

WF_error_connection.png.79f9ca0e0229154a1a9d3d4f6f5e977b.png

And sometimes:

WF_error_connection_1.png.c5668085aee7f5fe4ea92827f3db8143.png

Also, factory calibration parameters are all zeroes:

WF_calibration.png.d5173bc590179b5fd14319f11fb42b40.png

When I disconnect the external power supply I'm getting a different error:

WF_no_power.png.197e76f6e2e603c4cb93ffe4954017d4.png

 

Thanks,

Maks.

Share this post


Link to post
Share on other sites
  • 0

Hi @Maksym Galemin

In the last picture, since the USB voltage and current is read from the device, the fpga gets programmed and communication with this and power monitors is working. Following this, as the other ICs are started most probably runs out of power, internal voltages drop and components are reset, communication is lost or incorrect.
In the first pictures it seems that in the first stage of connection, during the fpga programming runs out of power.
The USB controlled is directly powered from USB line, so this remains connected to the PC.
I was thinking loud... :)

The loss of power could be because of USB cabling, to high resistance on cable or oxidized plugs.
The unprogrammed device gets power parallely from USB and auxiliary supply. When connecting to the device with software, after the device fpga is programmed and this sees auxiliary supply it turns off the USB supply switch. In case the aux supply can't provide enough power the device is reset.

Please try to not to use auxiliary supply, try to use a different USB cable and/or powered hub. 
We recommend using 5V/2A supply, mostly because the increased capability of the power supplies.

Edited by attila

Share this post


Link to post
Share on other sites
  • 0

Hi @attila,

Thanks for your response, as you suggested I've tried to connect the board using different USB cable and through a powered USB hub (StarTech ST7300U3M) but without any success. Now I can see the following error:

WaveForms_no_device.png.4141cf143800694ac62e9678050f47a7.png

We've purchased 6 boards in total so far and it's just this one board which gives us a bit of grief, all other boards are working fine. Is there a chance that we can replace that board somehow as this issue is blocking our testing at the moment? Thanks!

 

Regards,

Maks.

Share this post


Link to post
Share on other sites
  • 0

Hi @Maksym Galemin

Since you have other devices that are working we can exclude cabling other external problems. It is most likely the device is damaged.

The 5V auxiliary supply should be protected for reverse polarity and up to 20V, scope inputs up to 50V, digital IOs 20V... Could it happen that device was connected to voltages or external sources exceeding any of these?
The AD ground is connected to computer ground through the USB cable. The earth/ground of different socket plugs could be wrongly wired and have high voltage difference. Connecting together circuits/equipment supplied from such plugs could blow up fuses, in case of AD the ferrites or protection diode toward the USB VCC/GND. Could it happen that the device ground was connected to another voltage level that the computer ground? 

For warranty and replacement please contact support_at_digilentinc.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number.

Share this post


Link to post
Share on other sites
  • 0

Hi @attila,

11 hours ago, attila said:

The 5V auxiliary supply should be protected for reverse polarity and up to 20V, scope inputs up to 50V, digital IOs 20V... Could it happen that device was connected to voltages or external sources exceeding any of these?

No, this device wasn't connected to voltages exceeding these values.

11 hours ago, attila said:

The AD ground is connected to computer ground through the USB cable. The earth/ground of different socket plugs could be wrongly wired and have high voltage difference. Connecting together circuits/equipment supplied from such plugs could blow up fuses, in case of AD the ferrites or protection diode toward the USB VCC/GND. Could it happen that the device ground was connected to another voltage level that the computer ground?

Not sure I understand the question, but this board was always connected to USB port either on my personal PC or on our test server PC.

 

Thanks,

Maks.

Share this post


Link to post
Share on other sites
  • 0

Hi @Maksym Galemin

I was referring that connecting the ground wire of the AD device to a different voltage level (like to an external circuit which is supplied from a different source and grounding) could cause high current to pass the ground line toward the computer. This could burn the ferrite or protection diode in the AD.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now