attila

Hi @lokobob99 The hzAcq is the sampling rate in Hertz, 1000 = 1kHz

Hi @spencer_oe According the last error message, the USB voltage is very low 4.4V even with initial, minimum power consumption. Try using the original or other USB cables you have at hand... see the instructions in the error message.

Hi @edtriccorp The BNC adapter can slightly increase the input capacitance and crosstalk on the DIO lines due to the longer traces. It is important to have good GND connection between the devices and circuits, use more GND wires to reduce resistance. To reduce the crosstalk on the flying wires use twisted signal wires with GND, specially for the critical like clock and chips select signals.

Hi @TrentSteel Such option is on the whishlist but I don't know when I'll have time to implement it. Yes, it could be implemented on EclypseZ7 development board. To obtain such capture rates, beside embedded sw development, probably it also needs some HDL knowledge, to modify one of the existing example projects.

Hi @TrentSteel Such device buffered multi-capture mode is unfortunately not supported. The device can store only one capture at a time, up to 125MHz and 128Mi samples, with about 500-2000Hz capture rate (fetch to host and rearm), or continuously stream/record at 10-35MHz (for one channel).

Hi @edtriccorp 1. You can use add Digital channels in Scope to capture analog and digital inputs at the same time. 2. For traditional logic analyzer operation mode use the Record Mode in Scope and Logic Analyzer. 3. If you are only interested in the digitally transmitted data use the Protocol 'spy' tools.

Hi @LHji See the Help tab/ Impedance

Hi @smcdaid You can set it to higher number, above the device buffer size. Like at 100MHz with buffer size 4000 and position of 4004000, you will get 4k samples starting from 40ms after the trigger, T+40ms+40us

Hi @smcdaid The ADC, Trigger, DIO have different processing (analog to digital converstion, pipelining...), triggering and path to buffer time lengths. These are compensated from software, by actually capturing with a few less or more samples after the detected trigger event, depending on the selected trigger source and sample rate(s). To compensate for the mixed mode (Scope/Logic) delay between analog/digital-in, trigger the digital-in on analog-in, as it is in the earlier example. dwf.FDwfDigitalInTriggerSourceSet(hdwf, c_ubyte(trigsrcAnalogIn)) For other triggering (or even for this) schemes you can make the analog-in or digital-in to take a few samples less or more, or process/represent the captures shifted. With other triggering schemes make sure the independently running instruments trigger on the same trigger event and not on consequent ones (if this is important for the measurement) dwf.FDwfDigitalInTriggerPositionSet(hdwf, c_int(int(cSamples/2-1)))

Hi @Jan Mrázek If it has the problem with (the original and) different cables and computers, then it is likely a device problem. For warranty and replacement contact the support.digilent @ ni.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number.

Hi @Maxime I'm not too familiar with the MatLab support but it should support up to 100/125MHz, to generate and capture up to the device buffer size. AD3 has about twice the buffer size and data stream limitation of AD2.

Hi @Yakudza The FB18/19 can be replaced with 0R, a short wire or solder. These connect the USB's VCC/GND to the rest of the device.

Hi @federico.massimi It should be compatible, 2x15 100mil (2.54mm pitch) https://digilent.com/shop/breadboard-breakout-for-analog-discovery/ https://digilent.com/shop/breadboard-adapter-for-analog-discovery/ https://digilent.com/shop/analog-discovery-2x15-ribbon-cable/ https://digilent.com/shop/2x16-flywires-signal-cable-assembly-for-the-digital-discovery/

Hi @ysrevol Normally, the FTDI USB driver should be available from Windows Update, so it should be automatically installed on attach. Despite this install error, is device detected and working with WaveForms ? If not, try installing this driver: https://ftdichip.com/wp-content/uploads/2021/08/CDM212364_Setup.zip https://ftdichip.com/drivers/d2xx-drivers/

Hi @Mathias G. This may be caused by the range-relay switching. By default on device open and close from software the inputs and outputs are stopped, reset to high range, zero offset... and all settings applied for each *Set call. - use the following before device open to keep the setting (relays, offsets..) after device close dwf.FDwfParamSet(DwfParamOnClose, c_int(0)) # 0 = run, 1 = stop, 2 = shutdown - use the following after device open dwf.FDwfDeviceAutoConfigureSet(hdwf, c_int(0))# 0 = the device will be configured only when calling FDwf###Configure - or use about 0.01-0.1 second delay after analog-out configuration

Hi @XCR Use the Synchronized mode:

Szia @Andras For 64bit ARM Linux use the arm64.deb, for Debian based package like Raspbian, or aarch64.rpm for RedHats

Hi @nurber3 The compensation range of that probe seems to be insufficient. The following 1/10x probe should be compatible with AD1,2,3 https://digilent.com/shop/bnc-oscilloscope-x1-x10-probes-pair/

Hi @edtriccorp The analog representation of the digital values is auto scaled between minimum and maximum value, for 8 bit UART from 0 to 255. This is useful for data transmission over parallel bus, SPI, I2C, I2S... Currently it does not have manual scaling option, but if you think it is needed I can add such.

Hi @Mathias G. Have you try without Record ? as the example I gave you earlier: The Record is more complicate (to use and internally), it is intended to capture large amount (or unlimited) number of samples using data streaming.

Hi @AudriusM

Hi @Alekyakoi @JColvin The next sw version will ask for the update directly (on Select) if it is available.

Hi @matsuya You have it in a private message.

Hi @Mathias G. Please let me know what problem you encountered. In the newer software/firmware version with Standard Boot mode the Oscilloscope and Logic Analyzer captures directly in the DDR RAM and this let you capture 128Mi samples or 32Mi / channel at up to 125MHz. It also adds in device FIR/IIR channels, option for in device Scope to Wavegen signal or modulation routing, ability to capture Wavegen digital output and modulation... For these features I had to drop the backward compatibility of the new firmware with the record used in the older software. The firmware version is show in the tool-tip: To program the firmware from a specific software version, in the Device Manager hold down the Ctrl key (and wait or press Manual). The "My device..." and Update under Options should appear, select Update All.

Hi @santa It is fixed in the latest version: