[Verification of details of AD2 scope measurements pane: Value & Average]

Hi @vkristof

Yes.
The Voltmeter and Logger tools basically perform scan capture in background and at the specified rate (Update time) calculate the DC, AC/DCRMS
Just like performing separate captures on full device buffer size (at sample rate of buffer_size/update_time) for each set of value.
With single just one set of value is calculated on device buffer size. 

[Unable to connect to Analog Discovery 2]

Hi @criniod

I still suspect there is a contact issue rather than damaged USB controller.
Please try using the device with an older computer/laptop with ordinal USB Type A connector.

For warranty and replacement contact the support.digilent at ni.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number

[Record progress is obscured when there is no white waveform where the status updates]

Hi @Wayne Contello

For the next version the progress is moved up, after the status:

Thank you for the feedback.

[SPI Protocol Analyzer: Large Number of Bytes]

Hi @edwardjs

If you are using the Logic Analyzer:
- If you are using Digital Discovery you can capture up to 256M samples at up to 800MHz
- With Analog Discovery you could record 100M samples at up to about 1MHz or using compression for burst at higher rate.
With the Protocol tool SPI/Spy you can log data at similar rates.

[Triggering when rising edge]

Hi @kang

In Wavegen select Synchronized and check Run/Auto.

The Wavegen trigger output is high while running. A trigger event is the edge of signal so the Scope will trigger only when Wavegen is started or restarted.

With No Sync or Independent option the channels may drift from each other due to small difference in periods.
With Sync option and finite Run time the channels are resynchronized periodically.

 

[I want to know how to get data by using trigger signal i selected.]

See:

 

[WaveForms issues and suggestions]

Hi @sintech

In the current WF version double click on Data view brings the selected time/sample to middle.
For the next version I've added menu which lets you set first and last samples too.
Then, this can be cut in a new tab.

[Voltage Settings of Digital Discovery WaveForms]

Hi @A-M

You could synchronize them using the same trigger signal. At high frequency analysis you may notice the jitter between the independent oscillators of the devices.

[EIS for LiIon Cell starting configuration]

Hi @ees4all

I don't know much about EIS but you probably need AC coupling for the Wavegen, like a 100nF.
You could also try using 3.7V offset but it may take some time to charge (stabilize) the cell.

[Digital Discovery Write to UART Speed?]

Hi @Alejandro-Dev

You could use a custom pattern and run it in repeated mode.

 

[WaveForms issues and suggestions]

Hi @sintech

Could you elaborate this "Fit selection to window" ?
How would you like to enter the amount of samples ? Type in the first index and number of samples ?

[Voltage Settings of Digital Discovery WaveForms]

Hi @A-M

No. The adjustable DIO voltage 1.2-3.3V is the same for all IOs.
If you are using these only as inputs, you can set it to 1.8V The ~0.8V logic threshold should be good for 1.8-3.3V signals.
For outputs, depending on your requirements:
- you could set it to 3.3V and use OD output for 1.8V signals with external pullup
- or create resistive voltage divider for 1.8V
- or use external level shifter/translator 

[SPI Dual Example Question]

Hi @Alejandro-Dev

The "Digital_Spi_Dual.py" examples is the following: 
dwf.FDwfDigitalSpiClockSet(hdwf, c_int(1))  # Clock = DIO-1, Digital Discovery DIO-25
dwf.FDwfDigitalSpiDataSet(hdwf, c_int(0), c_int(2)) # 0 DQ0_MOSI_SISO = DIO-2, Digital Discovery DIO-26
dwf.FDwfDigitalSpiDataSet(hdwf, c_int(1), c_int(3)) # 1 DQ1_MISO = DIO-3, Digital Discovery DIO-27

WaveForms SDK Reference Manual.pdf :

 

 

[WaveForms issues and suggestions]

Hi @sintech

Use workspaces instead of projects. The projects are just instrument snapshots.
A workspace represent a session and the name of the current one is shown in the app title. This contains all the used instruments and device options as well.

The next version will improve cursor precision (for high position/range rations) and initial place glitch (in case the window is resized during workspace/project loading).

Changing of byte/word order is not supported, only bit endianness. 

You can use delayed capture in normal (Repeated mode, like capture 1us a week after the trigger at 10ns precision) and in Record mode expressed in percentage.

It is supported if you specify the WR signal as Clock for the Bus. The CS as Enable.
You can add another Bus using the same data lines and different clock, like for RD...

The next version will have "Add tab with visible data" button.
This lets you cut chunks from a large capture. This data then can be processed, exported, saved....

[Unable to connect to Analog Discovery 2]

Hi @criniod

It is most likely a contact issue.

Does the microUSB plug enter in the socket AD2 fully?
Some usb cables may have shorter metal tip. The plastic relief may hinder full insertion, this stumbling in the AD2 case.

[Unable to connect to Analog Discovery 2]

 

[Unable to connect to Analog Discovery 2]

Hi @criniod

Try using the original or other USB cables you have at hand, other USB socket, HUB...

[Operating ZMOD ADC 1410 at lower sampling rate.]

Hi @su_21

Leave the 100/400MHz ADC sampling frequency and skip the unneeded samples to reduce to the required rate, or perform averaging/filtering.

Changing the ADC freq would affect the vertical range (and offset), would require new calibration.
The 4x input clock is useful to reduce the jitter, to have better accuracy.

[FDwfDeviceOpen disables power supply on Analog Discovery 2]

Hi @DurandA

I don't notice any shutdown with latest WF version 3.16.3 or 3.16.31
https://reference.digilentinc.com/reference/software/waveforms/start
https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

 

from ctypes import *
import sys
import time
from dwfconstants import *

if sys.platform.startswith("darwin"):
    dwf = cdll.LoadLibrary("/Library/Frameworks/dwf.framework/dwf")
else:
    dwf = cdll.LoadLibrary("dwf")

hdwf = c_int()

dwf.FDwfParamSet(DwfParamOnClose, c_int(0))

for i in range(10):
    dwf.FDwfDeviceOpen(c_int(-1), byref(hdwf))
    if hdwf.value == 0:
        print("failed to open device")
        szerr = create_string_buffer(512)
        dwf.FDwfGetLastErrorMsg(szerr)
        print(str(szerr.value))
        quit()

    dwf.FDwfDeviceAutoConfigureSet(hdwf, c_int(0))
    dwf.FDwfAnalogIOChannelNodeSet(hdwf, c_int(0), c_int(0), c_double(1))
    dwf.FDwfAnalogIOChannelNodeSet(hdwf, c_int(0), c_int(1), c_double(1.0+i/2))
    dwf.FDwfAnalogIOEnableSet(hdwf, c_int(1))
    dwf.FDwfAnalogIOConfigure(hdwf)
    dwf.FDwfDeviceClose(hdwf)

 

from ctypes import *
import sys
import time
from dwfconstants import *

if sys.platform.startswith("darwin"):
    dwf = cdll.LoadLibrary("/Library/Frameworks/dwf.framework/dwf")
else:
    dwf = cdll.LoadLibrary("dwf")


cDev = c_int()
dwf.FDwfEnum(0, byref(cDev))
if cDev == 0:
    print("no device detected")
    quit()

dwf.FDwfParamSet(DwfParamOnClose, c_int(0))

hdwf = c_int()

for i in range(10):
    dwf.FDwfDeviceOpen(c_int(0), byref(hdwf))
    if hdwf.value == 0:
        print("failed to open device")
        szerr = create_string_buffer(512)
        dwf.FDwfGetLastErrorMsg(szerr)
        print(str(szerr.value))
        quit()

    dwf.FDwfDeviceAutoConfigureSet(hdwf, c_int(0))
    dwf.FDwfAnalogIOChannelNodeSet(hdwf, c_int(0), c_int(0), c_double(1))
    dwf.FDwfAnalogIOChannelNodeSet(hdwf, c_int(0), c_int(1), c_double(1.0+i/2))
    dwf.FDwfAnalogIOEnableSet(hdwf, c_int(1))
    dwf.FDwfAnalogIOConfigure(hdwf)
    dwf.FDwfDeviceClose(hdwf)

 

[How to measure Scope and Protocol]

Hi @kazu

See the Help tab or tutorials at https://reference.digilentinc.com/software/waveforms/waveforms-3/start

No. The Protocol uses the Pattern Generator and Logic Analyzer device resources, so it can't be used at the same time.

[FDwfDeviceOpen disables power supply on Analog Discovery 2]

Hi @DurandA

Use the following in all apps and scripts using the device:

...
dwf.FDwfParamSet(DwfParamOnClose, c_int(0)) # 0 = run, 1 = stop, 2 = shutdown
dwf.FDwfDeviceOpen(...
dwf.FDwfDeviceAutoConfigureSet(hdwf, c_int(0)) # 0 = the device will be configured only when calling FDwf###Configure
...
dwf.FDwfAnalogIOChannelNodeSet(hdwf, c_int(0), c_int(0), c_double(True))
dwf.FDwfAnalogIOChannelNodeSet(hdwf, c_int(0), c_int(1), c_double(1.20))
dwf.FDwfAnalogIOEnableSet(hdwf, c_int(True))
dwf.FDwfAnalogIOConfigure(hdwf)
...
dwf.FDwfDeviceClose...

 

[Waveforms + Analog Discovery : How to configure the buffer size of the individual instruments]

Hi @ABwalker

Such configuration is not available.
You could use the Scope Record mode to capture more samples at lower rate < 1-2MHz

 

[Python Script Not Reading Oscilloscope Channel 1 Voltage Correctly]

Hi @bhysjulien

Most probably the voltage is out of range on the selected 5Vpk2pk range.
Set it to 50V like this:
dwf.FDwfAnalogInChannelRangeSet(hdwf, c_int(0), c_double(50)) # channel 1
dwf.FDwfAnalogInChannelRangeSet(hdwf, c_int(1), c_double(50))  # channel 2

[Digital Discovery I2C Clock Stretching]

Hi @DavidLee1997

dwf.h

DWFAPI int FDwfDigitalI2cTimeoutSet(HDWF hdwf, double sec);
 

[Is (beta version)digilent.waveforms_beta_v3.16.30.dmg borken?]

Hi @HILO