ewb_topic

It seems that Digilent dismissed the Eclypse Z7 Waveform SDK and LabVIEW not working well

using the maximum value of 8192 as a reference for the AD series buffer.And divide the maximum buffer value by 1024, which results in an integer value of 8000, making it easier for calculation. buffer=2500@125kS/s,2500@500kS/s，50@100MS/s，buffer Maximum value should not exceed 8000.

I discovered an interesting phenomenon that when using VIPM's Digilent Waveform VIs programming, the waveform update speed is very slow and the same for 1k 、1M、and 10M sampling rates. In this video, natural noise signals are used to demonstrate the update speed of the signal. The faster update display speed of the high sampling rate collected signal is inconsistent with this. 5月31日.mp4

The following video uses Waveform 3.19.34 and oneAD devices, AD1 and one device eclypse z7. In order to meet the requirements for the size of the uploaded video, the video has been compressed and resized. 5月17日2.mp4

I recorded a new video to provide more information and better describe the problem. The following video uses Waveform 3.19.34 and two AD devices, AD1 and AD2. In order to meet the requirements for the size of the uploaded video, the video has been compressed and resized. PS:The program here is programmed using Waveform SDK to import DLL, not implemented using VIPM Digilent Waveform VIs programming. 5月17日1.mp4

Yes, the work in the video was tested based on Waveform 3.19.34, and the software used for testing is exactly the same as the one used with the Waveform 3.8.8 version. In the Waveform SDK 3.8.8 environment, there are no problems with AD1, AD2, and ADS. Especially in the ScanShift mode and ScanScreen mode, LabVIEW crashes only occur on the Eclypse Z7. Therefore, I think there may be unknown bugs in the 3.19.34 SDK and its earlier versions. The update speed of the waveform signal on the Eclypse Z7 screen is also a known issue. Currently, the update speed seen is completely different from using AD1, AD2, and ADS. The display speed is very uniform but very slow, rather than the real-time update speed of AD1, AD2, and ADS, which is very fast. I hope that the upcoming Waveform SDK can solve the aforementioned issues encountered when using LabVIEW to call the Waveform SDK with the Eclypse Z7.

DAQWare for Digilent ADS 1.0.7(SDK3.10.9 x64) https://tla.lanzoul.com/i6IuQ0bdmjqh password:tlase DAQWare for Digilent ADS 1.0.7(SDK3.8.8 x64) https://tla.lanzoul.com/iuByz0blw6ta password:tlase The above version requires support from LabVIEW 2015 development environment and also requires support from Waveform 3.8.8 environment Waveform 3.8.8 supports AD1, AD2, and ADS, but does not support Eclypse Z7. The above software is only used to demonstrate that the support for AD1, AD2, and ADS is working properly.

I have done some work using LabVIEW on the waveform SDK of Digilent, such as developing AD1, AD2, and ADS , and the effect is good. Recently, when working on Digilent Eclypse Z7 in a similar way, I encountered some problems, such as: 1. When changing the sampling rate, there is almost no difference in the update speed of the displayed waveform. For example, for sine waves with frequencies of 1k, 10k, and 100k, the waveform captured by the oscilloscope during testing has no visual difference in frequency, and the phenomenon of not being able to see signals with higher frequencies and faster changes can be referred to the video. 2. When the oscilloscope is in single acquisition mode, the acquired results are basically normal. However, when using the scanshift and scanscreen modes, LabVIEW will crash and exit. The above abnormal phenomena are only found in Eclypse Z7 and have not been found in the use of AD1, AD2, and ADS. Are there any friends who have encountered similar situations? 1.mp4

sdk version 3.18.59

ECLYPSE Z7 Add zmod adc 1410，this module adc is 14 bit，why sdk recognizes adc is 16bit？