jack1

I was using version 3.21.3 I just downloaded and installed version 3.22.2 This latest version does say the startup error is do to low power from my powered USB 2.0 hub. This version also started on one try from my MB USB 3.0 port. I'll get a newer powered type 3 USB hub. Maybe this will fix the problem. Jack

I'm using a powered USB 2.0 hub. The problem seems to be somewhat erratic. Sometimes I can clear the error by plugging the AD3 into a motherboard 3.0 USB port, sometimes not. I haven't tried a different a USB cable. I can't use your supplied cable as all my ports are looking for type A connections. I'm using the AD3 as a Logic Analyzer. At one point I noticed that I was getting clearly bad data (erradic logic pulses) displayed on Waveforms by the AD3, so I cycled power on the AD3 and it then threw a PLL error. After several attempts to cycle power, plugging into the MB port or hub port, the error was cleared and data display became reasonable again. I know the data was bad because it was generated by an Arduino and I was independently monitoring the data via the Arduino's serial link. I'll get a USB A to C adapter so I can try your supplied cable, or a whole new cable. The real thing that worries me is the fact that the AD3 started behaving erratically, without throwing any errors. I suspect these problems are related. Jack

I recently purchased an Analog Discovery 3 from the Digilent webstore. When I first powered it up I got a PLL not locked error. After cycling power, this initial error went away. However, now that I've been using this device for about a week this PLL error has returned and won't reset. What do you suggest?