Jump to content

attila

Technical Forum Moderator
  • Posts

    6,655
  • Joined

  • Last visited

Posts posted by attila

  1. 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.

    image.png

  2. 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.

    image.png

    image.png

    image.png

  3. 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.

    image.png

  4. 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

  5. Hi @Ronnie

    For better performance turn off AutoConfigure, as it is in the earlier sample_bb2.py
    image.png

    Is the "wait" causing you 'much latency' ?
    This is only needed for the first capture, after device connection, offset, range adjustment.

    For the following captures you only have to restart the generator. 
    dwf.FDwfAnalogOutConfigure(hdwf, channel, c_int(1))
    The analog-in rearms itself so you only have to wait for the capture to finish. There is no need for FDwfAnalogOutConfigure.
    while True:
        if dwf.FDwfAnalogInStatus(hdwf, c_int(1), byref(sts)) != 1:

    (For other use cases the analog-out can also be configured to restart itself.)

     

×
×
  • Create New...