attila

Hi @Zebel Unfortunately no. The SDK is the same for ADP 3000.

Hi @Julien Have you connected AD2 gnd to the circuit gnd?

Hi @reddish It will require a reference clock around 20MHz. The supported scaling is 1-8, like 8x10MHz = 80MHz or 8x12.5MHz = 5x20MHz = 100MHz or 5x25MHz = 125MHz or any arbitrary combination. It is also working with up to 15x but this is out of the spec.

Hi @reddish The next software version will add reference clock IO for ADP. The trigger IO is not on a clock capable pin. It is planned to be on the next products. This mostly affects the delay which is ignorable when compared to the external the wiring.

Hi @shadowcentaur The 250mA spec is for the amplifier IC. Toward the audio jack it has 100uF 33Ohm see: https://reference.digilentinc.com/reference/test-and-measurement/analog-discovery-2/reference-manual#audio The Wavegen has zero output impedance. Depending on the voltage level it can drive 10-50mA. https://reference.digilentinc.com/reference/test-and-measurement/analog-discovery-2/reference-manual#awg_out

Hi @Bambam Yes. The AD2 oscilloscope inputs are differential but not floating. USB isolator can be used to protect the computer, to filter noise from this and to have different AD2 and computer ground. Alternatively battery powered laptop can also be used to have floating ground.

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

Hi @reddish 1. Yes it can be controlled with the WaveForms app or with DWF SDK over USB or Ethernet. The DWF SDK is also preinstalled in the embedded Linux, so custom app/script developed on the computer can be ported/run in the device. 2. No. I will try to add such option for ADP3000 but not sure it is feasible or what limitations it will have. We are planning to have such support for next products.

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.

Hi @cwatt Such error is show on device disconnect so it is likely to be a contact issue. Since you tried multiple cables, USB sockets, computers... the inner micro USB contact plate could be broken or it could be a cold solder...

Hi @Richard H Right, I forgot the layout is flipped. The picture is corrected.

Hi @JC Gauthier You can use Logging Script for logging or Measurements to performs statistics. A more accurate measurement way would be using oscilloscope and FFT/Spectrum analyzer with averaging or peak hold. FileAppendLine("~/Desktop/scope/measure.csv", [(new Date()).toISOString(), Logic.Channels.DIN0.measure("Frequency")])

Hi @Jan Didden There is no such option in the Logger but you have Add Reference and Add Tab (after the buffer) in the Scope.

Hi @Richard H An adapter board would be the easier and safer to do. The R26/27 are on the bottom of the board.

Hi @Riccardo98 WaveForms application 3.16.22 should be backward compatible to MacOS 10.12 and the dwf.framework (API/SDK) to 10.9 https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Hi @Richard H The viable solution is using an external circuit with differential amplifier next to the shunt. In the ADP3000 the low range is 2V instead of the AD2 5V pk2pk. Increasing input capacitance on AD2 may make it unusable with 10x probes. Using switched resistors would be a problem at high frequencies. Higher amplification on the signal (and noise) may bring minimal improvement on the effective resolution.

Hi @Riccardo98 It looks like the Adept Runtime version 2.20.2 supports macOS 10.15 or newer. This is included in WaveForms version 3.15 or newer. Please use WaveForms 3.14.3 until this is solved.

Hi @RichSCorp The C code looks good if the hdwf and outBNC1 are correct, but what is before and after this? By default on the device close it is stopped. - You can use wait in the application until it is needed. - Or call the following before opening to continue running after close, see the earlier script dwf.FDwfParamSet(DwfParamOnClose, c_int(0)) I just notice the following 3 mistakes but this is not a showstopper. # analog-in dwf.FDwfAnalogInFrequencySet(hdwf, c_double(1e6)) # 1MHz sampling rate dwf.FDwfAnalogOutNodeEnableSet(hdwf, c_int(0), c_int(0), c_int(1)) # channel 1 enable dwf.FDwfAnalogInChannelEnableSet(hdwf, c_int(0), c_int(1)) # channel 1 enable dwf.FDwfAnalogOutNodeOffsetSet(hdwf, c_int(0), c_int(0), c_double(0.0)) dwf.FDwfAnalogInChannelOffsetSet(hdwf, c_int(0), c_double(0.0)) dwf.FDwfAnalogOutNodeAmplitudeSet(hdwf, c_int(0), c_int(0), c_double(5.0)) # 5 Vpk2pk range dwf.FDwfAnalogInChannelRangeSet(hdwf, c_int(0), c_double(5.0)) # 5 Vpk2pk range

Hi @Will_SC The script is run on device 1 and it is monitored by device 2 with WF app. sonar.py D1 Sc1 <-> D2 Sc1 <-> D2 W1 trigger pulse D1 W1 <-> D2 Sc2

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.

Hi @RichSCorp See the following: # analog-in dwf.FDwfAnalogInFrequencySet(hdwf, c_double(1e6)) # 1MHz sampling rate dwf.FDwfAnalogInChannelEnableSet(hdwf, c_int(0), c_int(1)) # channel 1 enable dwf.FDwfAnalogInChannelOffsetSet(hdwf, c_int(0), c_double(0.0)) dwf.FDwfAnalogInChannelRangeSet(hdwf, c_int(0), c_double(5.0)) # 5 Vpk2pk range # trigger detector dwf.FDwfAnalogInTriggerChannelSet(hdwf, c_int(0)) # channel 1 dwf.FDwfAnalogInTriggerTypeSet(hdwf, trigtypeEdge) dwf.FDwfAnalogInTriggerLevelSet(hdwf, c_double(0.0)) dwf.FDwfAnalogInTriggerHysteresisSet(hdwf, c_double(0.1)) dwf.FDwfAnalogInTriggerConditionSet(hdwf, trigcondRisingPositive) dwf.FDwfAnalogInTriggerFilterSet(hdwf, filterAverage) # use average samples in trigger detector # analog-out 1: trigger->wait->run->repeat from trigger, rearm dwf.FDwfAnalogOutNodeEnableSet(hdwf, c_int(0), AnalogOutNodeCarrier, c_int(1)) dwf.FDwfAnalogOutIdleSet(hdwf, c_int(0), DwfAnalogOutIdleOffset) dwf.FDwfAnalogOutNodeFunctionSet(hdwf, c_int(0), AnalogOutNodeCarrier, funcSine) dwf.FDwfAnalogOutNodeFrequencySet(hdwf, c_int(0), AnalogOutNodeCarrier, c_double(20e3)) dwf.FDwfAnalogOutNodeAmplitudeSet(hdwf, c_int(0), AnalogOutNodeCarrier, c_double(1.0)) dwf.FDwfAnalogOutNodeOffsetSet(hdwf, c_int(0), AnalogOutNodeCarrier, c_double(0)) dwf.FDwfAnalogOutTriggerSourceSet(hdwf, c_int(0), c_int(trigsrcDetectorAnalogIn)) dwf.FDwfAnalogOutWaitSet(hdwf, c_int(0), c_double(20e-3)) # wait length dwf.FDwfAnalogOutRunSet(hdwf, c_int(0), c_double(50e-3)) # pulse length dwf.FDwfAnalogOutRepeatSet(hdwf, c_int(0), c_int(0)) # repeat forever dwf.FDwfAnalogOutRepeatTriggerSet(hdwf, c_int(0), c_int(1)) # repeat waiting trigger dwf.FDwfAnalogInConfigure(hdwf, c_int(1), c_int(0)) # just configure analog-in dwf.FDwfAnalogOutConfigure(hdwf, c_int(0), c_int(1)) # start analog-out

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

Hi @Chuankun See the following posts:

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.

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.