attila

Hi @arnavguptagenerac Reduce the sample rate, like to 160kHz as it is in your WaveForms app screenshot, to get have 5.12ms 8192/160k dwf.FDwfAnalogInFrequencySet(hdwf, c_double(160000.0))

Hi @Anthocyanina Just increase the height of the Bus or the interpreter you are using, specify format, skip bits if needed... Alternatively in the Script tool you can add plots or transfer the Logic Analyzer data to Scope channel data or Wavegen...

Hi @Mandar Most of the TM devices Analog Discovery 2, Digital Discovery, ADP3450/3250... except ADP5250 offer I2C spying. This is a lateral feature and it does not support high transfer bandwidths but the Logic Analyzer instrument with triggering can be used to capture interested events.

Szia @Ákos I've forwarded your question to the logistics team to see if (at least) the replaced probes are tested. To make sure, you could also ask Mouser if the probes are tested with AD2+BNC. It is expected, the BNC adapter 2nd scope input has about 3pF higher capacitance than the 1st one.

Hi @JohnC124 The AD2 has two input ranges (gains), with 1X 50/5Vpk2pk, 0.1X 5/0.5V, with 0.01X 0.5/0.05V, with 10X 500/50V... With 1X and 5V range the scope input is in low range but with 0.1X and 5V in high range, so the resolution will be about the same. See the Trace info on bottom left of your plot area. To have the same input range/gain after changing the attenuation adjust the range option to the lower or higher value.

Hi @Leo_W Controlling the devices from separate threads should somewhat improve the performance but if these are connected to the same root hub the improvement may be little. https://docs.microsoft.com/en-us/dotnet/standard/threading/using-threads-and-threading

Hi @rim This seems to be a bug in the underlying libraries, Qt5.12, when 3D plots are above each other. It is solved in Qt5.15 and this will be used in the next installer if all other things work correctly. Thank you for the observation.

Hi @Virus That was a PRG18BB470MB1RB, similar to R145 but on AWG2 output: https://digilent.com/reference/test-and-measurement/analog-discovery/reference-manual#awg_out Is the digital part of the device working, USB controller... ?

Hi @Kirsan

Hi @Leo_W

Hi @AlanB Here you can find the new version in which there is no need for DataSet after Configure: Try with param stop. With run option, if the previously used application exited with shutdown the IO voltage level translators remain disabled. dwf.FDwfParamSet(DwfParamOnClose, c_int(1)) # 0 = run, 1 = stop, 2 = shutdown If the run option is needed, after open use the following to set the IO voltage and enable the translators: # set digital voltage between 1.2 and 3.3V dwf.FDwfAnalogIOChannelNodeSet(hdwf, c_int(0), c_int(0), c_double(3.3)) dwf.FDwfAnalogIOConfigure(hdwf, c_int(0)) The Digital Discovery play output captured with Analog Discovery:

Hi @Leo_W I just notice the Eclypse support is not enabled the WF software but it will be in the tomorrow version 3.18.50

Hi @Stephen Creswell Your use case is acceptable and will not violate the license agreement. Here is the newer eula license.txt that is/will be included in newer sw releases. PS: In the new license agreement 'The Software' specifically means Digilent's software component (Adept, WaveForms, etc) not the customer program.

Hi @AlanB The following is working for me, with internal loopback on DIO lines: DigitalDiscovery_PlayRecord.py

Hi @Stephen Creswell I've forwarded your question to the legal team. Hope to have a reply soon. Regarding the technical side, see the following post:

Hi @LJH Yes, the analog-in offset shifts the input range. The raw (16bit) ADC values are offset but the processed voltage samples are compensated for this to return the real input voltage.

Hi @Paul Rankin Triggering on multiple channels is only supported for digital IOs, in Logic Analyzer and in Oscilloscope interface using cross-trigger or after adding digital channels.

Hi @Stephen Creswell The restrictions in the agreement are only to prohibit the use of free Digilent software with cloned hardware. There is no restriction for your application to be used without Digilent product or other products, only the Digilent provided software (application, libraries...) should be used together with Digilent hardware.

Hi @Leo_W The DCFG_07_01_01.bin ! file should be programmed to the QSPI or copied to the SD card. The PL will be programmed only on software connection, so the PLGOOD will not light up on PS boot.

Hi @Bnm Which WaveForms version are you using? I've just tested the AD2 calibration with WF v4.18.1 and v4.18.49 bot are working fine. Use the links to calibrate it step by step ...

Hi @abia Use Ctrl+Space in Script tool or see the toolbar:

Hi @LJH See the following: adp3450.py I've added trigger for analog-in, changed analog-out to custom mode since the number of samples fits in the buffer, changed the rate and run length

Hi @towen This seems to be an unique (hub or driver) bug in earlier versions of RPIs since it is working fine with other SBC and computers. Reducing the transfer lengths and packing reduces the IN transfer oddness on RPI.

Hi @towen See the WF SDK: This API mostly handles raw data and processing (like measurements) need to be done in custom app/script. The API provides some functions for Network-Impedance Analysis and Spectrum/FFT processing.

Hi @AlanB Until this bug is solved use the following workaround, call DataSet twice, before and after Configure. FDwfDigitalOutPlayDataSet FDwfDigitalOutConfigure FDwfDigitalOutPlayDataSet