attila

Hi @mturner The averaging or oversampling requires stable trigger and periodic signal so consequent captures are averaged and phased correctly. In your screenshot it looks like it identified a periodicity of 297kHz and phases the signal according to this. Notice the "Channel range will be extended" indicating that with such offset value the high vertical range is used. You may consider using the AC coupling. The noise capture can be disabled under Time/Options or showing disable for each channel individually under the Channel's gear menu.

Hi @johannsi99 The record streams data over USB which limits the sample rate to about 1-2MHz. Use the default (single) acquisition mode to capture up to device buffer (8-16Ki) samples at up to maximum sample rate (100MHz).

Hi @Tamires The sustainable stream rate depends on the available USB, CPU, storage... bandwidth. To prevent or reduce chance of device buffer overflow: - use the 2nd device configuration to have mode scope buffer - connect the device directly to the computer, avoid hub with multiple devices connected that share the USB bw - close unnecessary applications, services that could block the system - store at lower resolution 64, 32 or 16 bit and avoid text format, to reduce storage size The 'corrupted' samples indicates that buffer over flow could have occurred, when two consecutive chunks exceed the device buffer size. This is uncertain but it could be a buffer overwrite. The record length can be set to unlimited (-1) and stopped from script, like it is implemented in the record py example loop. Here I've used the Rec option in the WF app with AD2 and passed 300M samples at 1 MHz for 2 channels storing samples as double without any issue. This is similar to the the py record examples just easier to use.

Hi @Camarillo In your last capture the 100us pulses sampled at 625us (1.6kHz), with the default average mode, will represent at most 16% (100/625) of the sample value.

Hi @RyanD The ADP5250 does not support recording. The Analog Discovery and ADP3X50 can use internal digital data compression but have 16 DIOs. The Digital Discovery can sample 32bits with 256MiB buffer but it does not use data compression.

Hi @suktan The Voltmeter and Logger use the continuous Scope capture and calculates DC and RMS from the samples. For 1 sec Update rate and with 8Ki sample buffer it will use 8192Hz sample rate. Notice the RMS: 4Hz to 2kHz info in Voltmeter showing the 4/update to rate/4 limits. The crest factor depends on the signal frequency and the sample rate.

Hi @Camarillo With Repeated mode when changing the time Base the sample Rate is also adjusted. The default Sample Mode for the Channels is Average. You could use Record mode for up to 1-2MHz or Min/Max sampling.

Hi @Toberius Not the IA Adapter but the Analog Discovery device is listed in the Device Manager. The Adapter can be selected in the Impedance Analyzer as Order option: https://digilent.com/reference/add-ons/impedance-analyzer/getting-started-guide#settings

The ADP5250 can be used from LabVIEW with the VirtualBench driver. See: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x15jCAA The driver can be installed manually to newer LabVIEW versions like it is described here: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kJXaSAM Like from C:\Program Files (x86)\National Instruments\LabVIEW 2019\... to C:\Program Files\National Instruments\LabVIEW 2021\...

Hi @joeck Use record mode to have information about lost/corrupt samples like in case of a "hiccup". The scan modes do not give such info, these are intended to simply get the last N samples. For AD1,AD2,ADP3 you can enable the data compression which will support higher rate for typical burst transfers protocols SPI,I2C... See WF SDK/ samples/ py/ DigitalIn_Record.py DigitalIn_Record_Compress.py

Hi @Andrzej Probably other ICs on the device are damaged as well, like NC7SZ126 and/or the FPGA. On software connection the FPGA done flag is verified through JTAG. This bit should be low but in your case it looks like it is read as high. The DptiIO communication fails since with ERC 2 the FPGA is not programmed but I don't see the cause of the following connection retry error of 3077. You could try "Force programming" under right-click or Options in this Device Manager. This will skip the done flag verification and program the FPGA but this will probably also fail.

Hi @Psoas The IC20 switch limits the initial USB power consumption. Bypassing it will exceed the initial/unconfigured USB spec of 100mA (~50mA with IC20 and ~220mA with bypass) but I'm unaware of any host using such limitation so the device should work normally with the bypass. https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide#analog_supplies_control http://www.analog.com/en/switchesmultiplexers/analog-switches/adp197/products/product.html

Hi @Robin Oswald 1. The "coherents" is the older method with periodic restart (at least 1ms) of Wavegen that creates 0-10ns shift and the steps you have noticed, it will be removed later. The "coherent" does not restart. 2. The "cohere" is the number of segments for 'coherence' measurement. It is available regardless of averaging.

Hi @MagicSmoke I've added it to the to-do-list. Thank you for the post.

Hi @Robin Oswald In the latest version the NA uses continuous signal also for coherent averaging. (After updating reconnect the AD2 or select with force reprogramming in order the new triggering to work.) I hope the coherence calculation is fine now. For coherent averaging the coherence is calculated on the averaged data and for mag/phase averaging the coherences are averaged.

Hi @bhayesoberst

Hi @bhayesoberst I've managed to reproduce a bug when using more than 100M samples, probably it is the same as you have noticed. It will be fixed in the next version.

Hi @bhayesoberst Which software version are you using? Have you tried the latest beta version? https://forum.digilent.com/topic/8908-waveforms-beta-download/ Please provide some information, steps and/or screenshots, to be able to reproduce the problem. Thank you

Hi @Robin Oswald 1. With coherent average there is just a phase shift on the signal, at worst (10ns) like this: 2. I think it is ok. In the earlier experiment C2 = W1 (sweep 1V) + W2 (1MHz 1V) When the stimulus signal freq equals to the other one, the spectrum is concentrated at the signal, there is only one peak (@1MHz), coherence is 1 ... C1 and C2 have 1 peak. When the two signals have the same magnitude but different frequency, we have two equal peaks (0.9995Mhz and 1MHz), coherence is 0.5 ... C1 has 1 peak and C2 2 peaks.

Hi @Robin Oswald When coherent averaging is selected the signal generator is periodically restarted in order the scope to trigger in each capture during averaging at the same phase. The restart period is the full number of signal cycles which cover a scope capture. Like for 8192 samples captured at 100MHz is 8.192us and this, for signals from 999.88kHz to 1MHz will be the same 82us due rounding to the 100MHz system frequency. The periodicity of this could interfere with the other signal. For the next version I've added a minimum condition of ~1ms restart period and this seems to solve the coherent step artifact. Here W1 is connected to 1+ and 2+, and W2 with 1MHz to 2- R1 is the earlier step issue and C1 with the ~1ms fix. The Coherence plot is working. The referenceerror is wrong, it is due to the TH# parameter and fixed for the next version. I want to fix and test a few new things before building the next installer. Hope to be ready with it next week. Thank you for the observation.

Hi @Dimitris Check the Auto after "Run: Continuous" or set a finite Run time. Edit: The "firmware" in the next software version 3.18.29 (next week) will generate Wavegen trigger on each signal start when the runtime is continuous.

Hi @Louism Long time ago (10+years) some of the first USB 3.0 laptops had problems (probably host controller/driver issue) with USB 2.0 devices and a USB hub was a solution. I haven't heard of such a problem since. Could it be a contact issue? It could also be a wrong driver installed. To solve this: Having the device connected without hub, go to Windows Device Manager, open "USB Serial Converter", Uninstall Device with Delete checked. Then, reconnect or press Scan for hardware changes, Search auto... or from C:\Program Files (x86)\Digilent\Runtime\UsbDriver\ or install D2XX driver from https://ftdichip.com/drivers/d2xx-drivers/ like https://www.ftdichip.com/Drivers/CDM/CDM v2.12.36.4 WHQL Certified.zip

Hi @Tamires

Hi @mdm102 The latest version lets you add 20. I just notice the default color for the 16+ is white, which needs to be corrected.

Hi @mkj With TS (three-state) output half of the buffer is available since each sample is stored on 2 bits to represent: 0, 1 or Z Use PP, OS or OD