attila

Hi @BigJ96 @leonvs The ADP3450 Scope can capture up to 128MiS at 125MHz, Logic Analyzer 64MiS at 125MHz but with data compression for typical burst signals much more. The length is unlimited at lower rates.

Hi @exsurgo_ankit For instance with Wavegen Custom/Math like below (/3 to fit in +-100% and 3V amp to amplify it back), or Func and Alter/Add twice.

Hi @leonvs Could it be a wrongly specified external/reference frequency ?

Hi @kmoto You could use Reference channel for this purpose or sample level shift with Math/Filter/Custom (1,0,0,0,0....)

Hi @Piotr Rzeszut Such could be implemented with custom application: FDwfDigitalInAcquisitionModeSet(hdwf, acqmodeRecord) FDwfDigitalInSampleFormatSet(device.hdwf, 16) FDwfDigitalInInternalClockInfo(hdwf, &hzBase) FDwfDigitalInDividerSet(hdwf, hzBase/UartRate/X) X = ~5 forever: FDwfDigitalInStatus(hdwf, 1, &sts) FDwfDigitalInStatusRecord(hdwf, &ca, &ce, &cw) for i in ca: uint16 sample FDwfDigitalInStatusData2(hdwf, &sample, i, 2) // 16bits = 2bytes process it: look for start, bits, stop... X=5 sample/uart-bit I've added UartSpy to the SDK motodo list but I don't know when I'll have time to implement it.

Hi @josu.jugo Beside the trigger level the selected filter, hysteresis and channel range (resolution) could influence the sensitivity. FDwfAnalogInTriggerFilterSet(hdwf, filterAverage) default is decimate which looks for trigger at 100MHz sample rate, average only at specified frequency FDwfAnalogInTriggerHysteresisSet(hdwf, 0.1) level +/-hyst FDwfAnalogInChannelRangeSet(hdwf, idx, 5.0) select 5Vpk2pk range (<=5.0) or 50V (>5.0) You could also use pulse, slope trigger and holdoff options.

Hi @maling Could it be a powering issue? Depending on usage each AD2 could take 2-5W. With 9 units this could be 18-45W, 3.6-9A/5V Is this in the limits of the USB hub/supply. Each FDwf functions returns true (1) on success or false (0) on failure. It could be used like this: bool myfunc(){ if FDwf...(.) ==0 return false if FDwf...(..) ==0 return false ... return true } if !myfunc() { FDwfGetLastErrorMsg(sz) print(sz) }

Hi @spbhanus See the links in the earlier post:

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

Hi @mkj Please use the included pdf manual in the WF SDK. This is the most up to date and correlated with the WF API/runtime version. Thank you for notifying the mistake in the online manual.

Hi @ca_michelle The bit order is corrected in the latest version:

Hi @Robin Oswald

Hi @longboard Try Independent or Synchronized (option after Channels), set Run to Auto and Repeat Trigger checked.

Hi @longboard The length is "unlimited" (limited by the host) since it is streamed, sent in chunks to the device.

Hi @ca_michelle Thank you for the observation. Next week you will have the version fixing this issue.

Hi @Robin Oswald I'm pretty confident the implementation is good, according the theory. This week I'm on vacation but next week I'll share beta version with these options.

Hi @reddish Regarding your question in private message, I reply here since it may be useful for other people too. The FDwfEnumInfo info is not really needed for custom apps. It is for delay loaded "Remote Devices"... With custom apps the IP or Alias can be used for connection. The other AMFM functions are only for the obsolete EExplorer... The enum filtering is backward compatible. You can still use device id for filtering, like FDwfEnum(devidDiscovery2) The filter meaning only changes when MSbit (Type) is used, like FDwfEnum(enumfilterType | enumfilterUSB)

Hi @Robin Oswald In coherent mode, C2 blue, when time captures are averaged the coherence is 1 because the "fixed noise" is mostly eliminated, C1 and C2 spectrums are almost identical. With the normal mag/phase average, the C1 captures only the W1 stimulus signal and R1(C2) = W1+W2 When the W1 and W2 are distant frequencies C1 has 1 peak and C2 has 2 peaks. When W1 and W2 are overlapped C2 has only 1 peak attenuated or amplified depending on phase. At close frequencies the two peaks merge or it is one wider. See at 200kHz and 290kHz with no averaging:

Hi @reddish Thank you for the notification. I didn't notice it is already released for public and also the download page is changed since I last visited it :)

Hi @LarsB Please attach the project and csv if possible.

Hi @reddish Adept 2.26.1 will be officially released together (or before) the wf 3.17.1 We have thought about repo but not yet committed to, it would be another thing to maintain...

Hi @reddish You can find the links to adept 2.26.1 at:

Hi @spbhanus 1. The MATLAB DAQ toolbox plugin only supports Analog Discovery 1/2 and provides limited features. However the WaveForms SDK which lets you to use all the features (including simultaneous analog/digital sampling) can also be used from MATLAB, see the following post: 2. Yes. With plugin like below and with SDK FDwfAnalogInChannelRangeSet https://www.mathworks.com/help/daq/getting-started-acquiring-data-with-digilent-analog-discovery.html 3. See the specifications in the WF app Help or on the reference page 4. For such low mV signals pre-amplification would be recommended. The ADP3450/3250 low range is 2Vpk2pk ~130uV resolution and ~30mV with 16bit sampling at 31.25MHz or lower. The AD2 low range has about 300uV resolution.

Hi @rakunann444 Here you can find the layout and more info: