[Vertically zoomed xy plot not quite right.]

Hi @enelson

Could it be a ground loop issue ?
Try powering the AD2 from 5VDC supply to minimize such.

[Electronics Explorer Troubleshooting]

Hi @cmillionbrown

Most probably it is a mUSB contact issue.
The revF or newer should be protected from eeprom corruption but it could be reprogrammed. 

 

[Waveforms not installing on 64bit Windows 10]

Hi @shishir

Make sure the compatibility mode is off.

[How to read 16bit integers using WaveForms UART Protocol]

Hi @ALackOfNumbers

You can use a Script like this combine to two consecutive bytes in a word:

Protocol.UART.Receiver()
var rg = []
while(wait()){
    var t = Protocol.UART.ReceiveArray()
    if(!t.length) continue
    rg = rg.concat(t)
    while(rg.length>1){
        var v1 = rg.shift() 
        var v2 = rg.shift() 
        print(v1,v2)
        print((v1<<8)+v2) // MSB first
    }
}

[Analog Discovery 2 compliance query]

Hi @exsurgo_ankit

Yes. These are the maximum tolerances for the components and in the important analog areas like around the amplifiers 0.1%R and 1%C are used.

Beyond that, each device is calibrated during the manufacturing test process.

You can find the specs at: https://reference.digilentinc.com/test-and-measurement/analog-discovery-2/specifications#arbitrary_waveform_generator

[AD2 Logic Analyzer Active Low Inputs?]

Hi @TheStumbler

You could use the following custom interpreter:

[Any Protocol Definition for GPIB?]

Hi @TheStumbler

There is no GPIB interpreter available.
You could create a custom protocol decoder or use Bus and signals.

[AD2 Factory Calibration]

Hi @MissingRedstone

Please take a look at the following post.

 

 

[multi-user issue: failed to enumberate device]

Hi @BryanS

I've just tested enumeration and connecting sequentially to one device with different users, it is working under Ubuntu 16 but not with 20.

@malexander
Could you help in this?
Edit: With second user getting ERC 3090 on DmgrEnumDevicesEx

[Why are Python sample code and GUI scope values different in analog discovery2?]

Hi @Sangkyu Choi

Have you adjusted the channel vertical range? like:
dwf.FDwfAnalogInChannelRangeSet(hdwf, c_int(0), c_double(5))
By default the 50V pk2pk range is used which has lower resolution.

[Why are Python sample code and GUI scope values different in analog discovery2?]

Hi @Sangkyu Choi

The sample rate is probably different and regarding the noise band see the following post:

 

[Logic Detector as trigger in Scope. Is it possible?]

Hi @m72

Thank you for the observation. It is fixed for the next release.

[Tracer and JFETs, depletion MOSFETs, optocouplers, SSRs]

Hi @dimitri

The Transistor Tester Adapter was intended to use +5V or -5V rail as emitter/source to have unipolar 10V range.

The next software version will let you use bipolar voltages and adjust rails with Adapter.

[Tracer and JFETs, depletion MOSFETs, optocouplers, SSRs]

Hi @dimitri

Unfortunately there is no bipolar option in the Tracer tool.

[Analog Discovery 2 possibly damaged, any ideas for how to debug?]

Hi @Chuankun

The FPGA IDs are not read correctly over JTAG.
The USB controller soldering may not be good or other ICs are damaged as well, like the buffers or the FPGA.

 

[Analog Discovery 2, broken scope?]

Hi @EdWall

Due to high voltages usually the ADG612 gets damaged, resulting in positive or negative top of scale readings (like +/-25V, +/-2.5V)

First you could verify the resistors and the signal propagation on in the input path.

[Analog Discovery 2 possibly damaged, any ideas for how to debug?]

Hi @Chuankun

The USB controller could be damaged by high USB voltage. Make sure to look for a faulty/unregulated USB hub supply to prevent further problems.
You could try replacing the FT232H but likely other ICs on the board are damaged as well.

The ADM1177 is probably fine, this is rated up to 30V

 

[Analog Discovery 2 possibly damaged, any ideas for how to debug?]

Hi @Chuankun

See the following posts:

 

[Analog Discovery troubleshooting]

Hi @sourdoughconquistador

It could be an issue with the ftdi library or usb driver.

You could try updating the libftdo.so 
In the adept.runtime2.20.1 1.4.8 is included and the latest is 1.4.22 https://ftdichip.com/drivers/d2xx-drivers/
For me both are working.

[Logic Detector as trigger in Scope. Is it possible?]

Hi @m72

It is fixed in the latest version:
https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

You could reset/load the factory calibration or perform a new calibration.

 

[Logic Detector as trigger in Scope. Is it possible?]

Hi @m72

I will post an update fixing "AD2 blue" tomorrow.

Thank you for the observation.

[New Analog Discovery 2, PLL not Locked]

Hi @Light

For warranty and replacement the support dot digilent at ni dot com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number.

They will need your name, when you purchased the device, whom you purchased it from (i.e. Digilent or a distributor), and the serial number on the underside of the device. If you purchased the board from a distributor, you will need to contact them about their warranty.

[How to restore FT2232 EEPROM back to factory settings?]

Hi @Egenco

You could modify the FTDI driver INF to have the same VID/PID you have accidentally programmed, see in device manager/ details/ hardware IDs.
The INF file lists the VID/PID/interfaces the driver is associated to. https://ftdichip.com/drivers/vcp-drivers/
This modification will break the certification of the Windows driver so you have to boot with disable driver signature enforcement in order to install the driver.
Then you should be able to connect with FT_Prog to your device to change the VID/PID back.
Uninstall the driver with delete checked and reboot.

https://hassanulmakers.wordpress.com/2015/03/13/unbrick-bricked-ftdi-chip/comment-page-1/

[New Analog Discovery 2, PLL not Locked]

Hi @Light

Try using the original USB cable the device came with, other USB ports of the computer or powered USB hub.
Let us know if this help.

[Analog Discovery troubleshooting]

Hi @MiaPka

It looks like the PLL is not working but the analog circuitry is supplied since the ADC IC does not give error.

For warranty and replacement please contact support dot digilent at ni dot com 
They will need your name, when you purchased the device, whom you purchased it from (i.e. Digilent or a distributor), and the serial number on the underside of the device. If you purchased the board from a distributor, you will need to contact them about their warranty.