attila

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.

Hi @qwertylex Add Digital signals or interpreters in Scope and Add custom Math channel with digital channels name (or other operations if needed), then export. (Natively it is not supported since analog and digital can have different number of samples and rate.

Hi @qwertylex It only supports TDMS export, but not import yet. Importing can be done with the Script tool with a bit of JavaScript knowledge.

See the following: https://digilent.com/reference/test-and-measurement/bnc-adapter-board/reference-manual https://digilent.com/reference/test-and-measurement/bnc-adapter-board/getting-started-guide

Hi @analog123 The BNC adapter is in AC coupling. Set it to DC behind the BNC connector.

With WaveForms application only two devices (for now) and more only with custom app/script.

Hi @BenjaminEley See the following posts:

Hi @josan The WaveForms application only provides JTAG protocol interpreter. JTAG programming can be implement with any device which has 4 DIO lines, but writing such application would be complicated. You can use Adept application or Adept utilities / djtgcfg application and any USB-JTAG cable/module to program most of the Xilinx FPGAs. Note this is only tested for FPGA variants which are used on Digilent products. https://digilent.com/reference/software/adept/start https://digilent.com/reference/programmers/start

Hi @Hamza Oncuer See the AnalogOut_Sweep.py example and the manual.

Hi @zorgoban See the Help tab, press F1, Help/Browse

Hi @BigBob In the import file dialog use type filter and press Ctrl+A to select all files. The next software version will add Scope.Tabs.Remove(name), Scope.Tabs.ClearTabs() and Scope.ClearBuffers() Merry Christmas

Hi @BFisher The Digital Discovery DIO/DINs support 1.2-3.3V single-ended signals. Newer WaveForms version provides digitization, so devices with analog inputs (oscilloscope) could be used with custom thresholding or differential signals. Analog Discovery inputs are differential or math channel could be used.

Hi @STMAN The next software version will add 'delta t' property to the TDMS exports.