attila

Hi @dave slagle I'm unable to reproduce beachball... For me the WF app seems to be paused after one minute the Mac goes to sleep (I've connected a LED to an AD2 output controlled from software). The software resumes immediately on wakeup and reacts to the inputs/adjustments fine. On you machine it could be a low level USB driver / hardware issue, like something related to USB suspend... @malexander Do you have MacOS 10.14 to test sleep/wakeup ? You could try to disable the auto Reconnect option to reveal eventual communication error.

For multiplication purpose the Amplitude Modulation can be used with index of 100% and offset of -100%

Hi @Joao Paulo The sub/register address is not read but written by the master. See the following post:

Hi @yogeshL Yes, these are on the to-do-list but I don't know when it will be implemented. Thank you for bringing this up.

Hi @Abhishek Prakash If you want to process the samples continuously see the WF SDK/ samples/ py/ DigitalIn_Record.py example. For scan mode see the following example: DigitalIn_ScanScreen.py

Hi @RobbN The easier would be using Script tool in the WF app to automate the measurement and logging data to text/csv file or calling external app/script. Another solution would be using the WF SDK for custom app/script. See the manual and examples/ py/ AnalogImpedance_Measure.py AnalogImpedance_Meter.py AnalogImpedance_Analyzer.py ...

Hi @eivind_k Here you can find it:

Hi @ChristianMaru The easies is to generate such using frequency modulation in the device. +-5Hz/83.68Hz = FM of 5.975143 %

Hi @bitstre@m State trigger is not supported. See the following post:

Hi @blipton Yes.

Hi @Fortune Given this erratic behavior and the earlier "verification failed" message I don't think JTAG reprogramming will succeed or help. Please go for replacement.

Szia @Andras Yes, it is expected. The FFT is performed on the whole captured samples. Which in case for scan shift/screen and record equals to the visible samples. For repeated capture the visible may be less since it is rounded off (like 8000 for 8192) trying to get nicer sample rate for the given time base and at low time base only a portion is shown (like for 8192 buffer and 100MHz max the minimum capture is 81.92us) With scan screen the hump is significant during middle crossing because before FFT the samples are windowed (default FlatTop) having a peak in the middle. The FlatTop looks like M1 and the scan is stopped close to the middle:

Szia @Andras This is due to discontinuity in the scan screen data. Use shift or repeated mode.

Hi @Rohit_Verma To measure time between captures you can use something like this. For quick captures also set the sample rate high, divider to low, like to 1. ... dwf.FDwfDigitalInDividerSet(hdwf, c_int(int(1))) ... print("Waiting for acquisition...") dwf.FDwfDigitalInConfigure(hdwf, c_bool(0), c_bool(1)) try: while True: start = time.time() while True: dwf.FDwfDigitalInStatus(hdwf, c_int(1), byref(sts)) if sts.value == 2 : # done break print("elapsed: "+str((time.time()-start)*1000)+"ms") except KeyboardInterrupt: # Ctrl+C pass ...

Before version 3.15.5 the maximum number of captured samples (acquisition time X sample rate) was equal to the default Scope buffer size, which is 8192 for AD2. Setting it higher it was silently limited to this number. Since version 3.15.5 recording will be used when specifying to acquire more than the buffer size. This requires the Read to be called immediately after Run. The Force trigger can be called from separate a thread. Adjust the analog and digital array size in the MSO Read Block Diagram as needed.

Hi @Rohit_Verma 1. The following lines are to wait for the capture to finish. while True: dwf.FDwfDigitalInStatus(hdwf, c_int(1), byref(sts)) if sts.value == DwfStateDone : # 2 break 2. If you want to trigger on DIO-7 negative pulse length use: dwf.FDwfDigitalInTriggerResetSet(hdwf, c_int(0), c_int(0), c_int(0), c_int(1<<7)) # low, high, rise, fall dwf.FDwfDigitalInTriggerSet(hdwf, c_int(1<<7), c_int(0), c_int(0), c_int(0)) # low, high, rise, fall dwf.FDwfDigitalInTriggerLengthSet(hdwf, c_double(5e-4), c_double(7e-4), c_int(0)) # 500-700us dwf.FDwfDigitalInTriggerCountSet(hdwf, c_int(1), c_int(0)) 3. If you want to precisely count the pulse rate use the record to collect a fixed number of samples and count the pulses in you script. You could use the sync capture mode and rely on the available samples, see DigitalIn_Sync.py and the following post. This will be software controlled start/stop so it will have a uncertainty of milliseconds.

Hi @Rohit_Verma You could perform recording either on analog or digital-in and count the edges/pulses in software.

Hi @blipton There is no dedicated counter feature.

Hi @Fortune The Linux USB update reprograms the eMMC and it should not write in the QSPI flash where the boot, standard firmware and IDs are. The firmware update from the WF app should only update the needed sections in the flash. Does the front LED blink once or continuously when you power it on ? Is device detected by the WF app ? Make sure the terminal app is connected since on power cycle this also gets reset. As a last resort the device could be reprogrammed with JTAG cable. Do you have such ? For warranty and replacement see the following: https://digilent.com/shop/shipping-returns/#return-policy

Hi @Someone It can be done like this: // 10us right shift var i0 = round(hzRate*10e-6) var cs = rgData.length for(var i = i0; i < cs; i++){ rgFlag[i] = 1; rgValue[i] = rgData[i-i0]&1; // DIO-0 }

Hi @eivind_k Unfortunately there is no workaround, the samples need to be aligned at the end in the application/script. With the next software version 3.18.11, for zero pre-trigger case the data will be aligned in the library.

Hi @dave slagle I was running today for several hours the Impedance Analyze with AD2 on MBP late 2013 v10.15.7 without any issue. You may try with a newer software version (>3.16.31 but preferably the latest) to reprogram the USB controller. Disconnect the AD2, open WF Device Manager, press "My device is not listed", connect the AD2, press Find Device, make sure the AD2 is detected, press Program Device. Reconnect the AD2.

Hello, The latest WF beta version adds support Phase Modulation and mixing of two waveforms. https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Hi @mete The high speed adapter/probes are important above 100MHz sampling, for signals above 50MHz or for phases below 10ns. The twisted wires are useful to reduce crosstalk. https://digilent.com/reference/test-and-measurement/digital-discovery/reference-manual

Hi @mete The embedded resistors in the HS probes are to reduce the signal reflections that could cause oscillation/ringing.