attila

Hi @BCK

Hi @Arno It seems to be a USB contact issue. You can try gently cleaning the USB port, such as using air pressure or blowing.

Hi @Mathias G. I the sample code I sent there was: dwf.FDwfAnalogInFrequencySet(hdwf, hzClock) It needs this information to compensate ADC and processing delays for correct trigger position.

Hi @pen It is fixed in the latest version: Thank you for the observation.

Hi @Mathias G. Here you can find the installer: See the following example: AnalogIn_SamplingClock.py

Hi @chuqdd Like this:

Hi @RealPersonIPromise You could use the built in measurement and Script tool to automate things. These measurements are not available in the API/SDK only in the app. For custom application data processing needs to be implemented.

Hi @Walter76 It looks like some AC coupling going on 2+ Since 2- is fine we can rule out wiring problem. It may be a cold soldered resistor on the 2+ input: https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide#scope_input_divider_and_gain_selection How does 2+ behave at high range, having Scope Channel 2 Range above 500mV/div or in Network Analyzer Amplitude above 2.5V ?

Hi @jom I have seen it but it seems to me there are too many vertical lines, 'time grid' + overlay, which could make it hard to interpret. This is why I'm asking if it would be better to have options to select different grids: default time, 320/720, cylinders; Instead of adjusting the overlay on the signal, the signal (time position and base) should be adjusted on the grid.

Hi @Mathias G. 1. The temperature measurement is for the Zynq (CPU+FPGA), the hottest part of the device, which should be fine up to 85*C The AnalogInStatusRecord function is not doing to much, it should not block. This simply calculates and returns the sample statistics based on the last two FDwfAnalogInStatus calls which communicate with the device. 2. In your script Trigger2 is set to the be sampling clock, FDwfAnalogInSamplingSourceSet trigsrcExternal2(12) change it to trigsrcExternal1(11) to be Trig1 (closer to the edge of the device). Isn't the long "time of configuration" caused by this ? the sampling frequency is not what you expected to be, trigger pulses are being used for clocking The undocumented analog-io 15/2 returns the trigger1 frequency. I've added this to use for some automated adjustment from the app, but it is not yet used. dwf.FDwfAnalogIOStatus(hdwf) dwf.FDwfAnalogIOChannelNodeStatus(hdwf, 15, 2, byref(hzTrig1)) 3. The next software version will correct the (+/-10..20) sample trigger delay for external sampling clock.

Hi @PhilipJ Yes, the event represents the edge of the signal and the change in the value of the interpreter. Labels are pushpins on the 'screen', not associated with time. Use X cursor for fixed time. Set first/last sets the position to be the left/rightmost.

Hi @PhilipJ Enable the Navigation. Edit: It will be enabled by default in the next version.

Hi @Mathias G. How many samples do you collect ?

Hi @BCK The next software version will offer export time settings. It will be available in beta in the coming days.

Hi @nurber3

Hi @Xavier Jiang You probably used Record mode to capture multiple samples, which uses data streaming and has limited rate, ~3MHz for AD2 and ~10MSps for AD3.

Hi @ionica The functions are the same with some new options, like more buffer for instruments, system frequency adjustment 50-125MHz, phase modulation and summing, supply voltage readback, DIO pull... See the SDK manual in the installation.

Hi @ionica The Lock-in is only available in the WaveForms application Scope interface, it is a software feature.

Hi @DigilentFan You could use a script like this to port Scope data to Logic Analyzer. function toDigital(rg){ var rgd = []; var l = 0; rg.forEach(function(v){ if(v<1.0) l = 0; // logic with hysteresis, < 1V else if(v>2.0) l = 1; // > 2V rgd.push(l); }) return rgd; } var rg1 = toDigital(Scope.Channel1.data); var rg2 = toDigital(Scope.Channel2.data); var rg = []; var c = rg1.length; for(var i = 0; i < c; i++){ rg.push(rg1[i]|(rg2[i]<<1)); // Scope1 as DIO0 and Scope2 as DIO1 } Logic.RemoveTab("FromScope"); Logic.AddTab("FromScope", rg, Scope.Time.Rate.real);

Hi @Mathias G. Are you using a new WaveForms version like 3.20.1 or newer? I'm getting stable trigger using your code with this.

Hi @Ondrej No offense meant, just trying to direct people with the screenshots. The next version will add a new property that returns a high-precision trigger position, which is useful for newer devices ADP3X50, AD3...

Hi @Leo_W Good to hear that. Do you know how it got damaged ? Could have been a temporal short on the USB_D3_P/N lines which go to the canvas connector J13 ?

Hi @Xavier Jiang Could you provide more detail about the problem ? The devices can capture and generate waveforms which fit in the device buffer (4,8,16,32k .. 128M) up to maximum rate (100/125MHz). The Record and Play uses data streaming. It is intended for larger waveforms and the device buffer is used as fifo. The AD2 can Record up to about 3MHz on 1 or 2 channels. The AD3 is still USB FS (2.0 480Mbps). The Scope buffer is shared between the channels. It can record at about 10MSps, 10MHz for 1 channels and 5MHz for 2 channels. It is normal for the devices to heat up, the AD2 consumes at least 1.5W and the AD3 3W.

Hi @danaur Try using measurement names without underscore and "~!@#$%^&*()+{}|:\"<>?,/;'[]\\-=" The underscore is considered by the autocompletion as the end of word, and therefore does not display child nodes, functions, properties correctly. Fixed for the next version and adding note about this feature in the Help. Thank you for the observation.

Hi @JonD @Derek Eder I'm planning something for automotive measurements once I have a clear idea of what is needed. How about having custom grids with options for 720, cylinders... ? this instead of the default 10x10