attila

Hi @nanderson It is probably an issue with the FTDI driver. Disconnect the device and reinstall WaveForms (check Adept Runtime section which includes the driver) or install the driver manually from: https://ftdichip.com/wp-content/uploads/2023/09/CDM-v2.12.36.4-WHQL-Certified.zip https://ftdichip.com/drivers/d2xx-drivers/

Hi @Abhijan The latency is approximately the configuration time which is approximately 1ms, 0.125 to 4ms. It depends on the host controller, hub, buffer/waveform size, if AM/FM is used... AnalogOut_Test.py with AD2

Hi @Magda For W1-C1-DUT-C2-R-GND is: re = magnitudeRatio*cos(phase) im = magnitudeRatio*sin(phase) gp = 1.0/rReferece + 1.0/rProbe bp = cProbe*2*PI*hz y = gp^2 + bp^2 rs = (im*bp+gp*(re-1))/y xs = (im*gp-bp*(re-1))/y + open/short compensation

Hi @sjn See the following example:

Hi @dmangione The Play stopped working when the DDR RAM oscilloscope buffering was introduced and the AWG buffer size was increased. It will be fixed in the next version. Thank you for the observation.

Hi @Sid Price It was corrected long time ago. The beak trigger negative pulse longer than 10 bits (1+8+1+parity), for 19.2kHz >520.832us In capture it looks like there is an extra parity bit. Make sure to configure the interpreter correctly.

Hi @Andy-205 The audio/scope inputs have separate ground (GNDA) for better isolation from the rest of the adapter. The Wavegen output amplifier is powered by the V+/- power supplies channels and the ferrites are for filtering.

Hi @Alrie To reduce crosstalk between wires try twisting each signal wire with GND or at least the critical ones like CS and CLK Make sure the digital IO voltage is set correctly since this also adjust the input logic threshold (about half of the VIO)

Hi @Steve Pratt See the measurement names in Logic/View/Measurements.

Hi @BFisher You could print it like this: var dt = new Date(); print(dt.toISOString()); // -> 2024-01-05T10:41:16.768Z

Hi @fizzbang Thank you for the observation. @JColvin probably knows who the editor of this guide is. https://digilent.com/reference/test-and-measurement/guides/waveforms-network-analyzer

Hi @Andy-205 Make sure to enable the power supplies, see: https://digilent.com/reference/add-ons/audio-adapter-plus/getting-started https://digilent.com/reference/add-ons/audio-adapter-plus/start

Hi @bfpa40 Don't you have a USB contact problem ? Have you tried using a different port or cable ?

Hi @bfpa40 Could you try updating with another OS and/or computer ? I've just tested updating from WF 3.16.1 fw:33C and from failsafe fw:331, with Linux and Windows, and it is working for me.

Hi @Karneades No, since the Math channels are performed in the software (application). Eventually you could export longer Math channel data and import it in Wavegen to Play.

Hi @Oleg The samples are 16 bits, so 4 channels take 8 bytes, x 1M samples = 8MB, / 40MBps = 0.2 sec to transfer However the captures can be performed much faster, at up to 1GBps, 125MHz x 4 channels See the following example with device buffering: AnalogIn_Buffers.py

Hi @qwertylex The Record capture in the application is limited to 200M samples/channel, 200sec @ 1MHz Allowing Math channels in "Record to File" could slow down the process causing device buffer overflow. With AD3, ADP3X50... you also have in device filter channels. To visualize imported high values, change the Channel's Attenuation to adjusts the selectable Range, like with 100X it lets to set 500V/div.

Hi @BFisher For reception in Protocol the device only stores the protocol specific bits so there is no time information memorized. The View/ Stamp inserts informative software time stamps. For timing analysis use the Logic Analyzer. For newer devices (DigitalDiscovery, AD3, ADP3X50...) a precise trigger time stamp (based on device RTC) is stored for each capture.

Hi @fizzbang The default reference channel in the application is Channel 1 but this can be changed under Phase / Ref It is mentioned in 2.2 "set the phase reference to channel 2" https://digilent.com/reference/test-and-measurement/guides/waveforms-network-analyzer

Hi @bfpa40 Are you using USB connection to the device ? If not, try this. If you are not using the Ethernet connection disable it, since without link it could cause initial boot or communication delays. From which WaveForms version and Firmware version are you trying to update ?

Hi @Dan N Use Record Mode and Export. The in device filters are real-time, provides in-device routing from Scope to AWG signal or modulation, but are limited in taps/order compared to (software) Math channels. For ADP3X50 and EclypseZ7 normal capture mode can be used since these provide 128&256Mi sample device buffer.

Hi @Oleg The 10ms should be sufficient for the acqmodeSingle to transfer the capture to the computer and rearm for the next capture. ADP3X50 lets you capture up to 128Mi samples on up to 4 channels at up to 125MHz. For this acqmodeSingle or Record can be used. The acqmodeRecord is intended to be used for larger captures than the device buffer using data streaming. ADP3X50 also provides device buffering (memory segmentation) with <1us latency between captures which can be enabled with FDwfAnalogInBuffersSet.

Hi @KatharinaSt Create a custom waveform (Type/Cog/New) like this, Frequency 1.5ms, Run: 2s (pic1) The repeat Trigger option (the last checkbox) selects to rearm for each Wait-Run cycle, or unchecked will only arm initially, once triggered repeat Wait-Run the specified number of times without rearming. (pic2)

Hi @wolfie Sure, stop is part of the I2C protocol. You can use the "Debug with Logic Analyzer" (in top-right corner) to inspect the signal timings. You should use: // Read(address, [sub address byte1, byte2...], count of bytes) // Returns the read bytes array from the specified device address and subaddress using repeated start. Read(addr, [regaddr 4, 3, 2, 1], N) Edit: This will generate what you have described: start, addr write, sub-address bytes, repeated-start, addr read, N bytes, stop.

Hi @DaniS You can capture or record a longer waveform and use View/Audio to play it back on the computer audio at adjustable rate. Live playback is also supported but at the same rate as the scan capture, or lower with tempo. AD3, ADP3x50 provides in device routing from Scope to AWG output or as modulation.