Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited

  • Days Won


attila last won the day on September 18

attila had the most liked content!

About attila

  • Rank
    Prolific Poster

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

6408 profile views
  1. Hi @Wayne.B In case you are using Analog Discovery, the "Samples Lost" indicates device buffer overflow, loosing data while streaming to computer. Try using the 4th device configuration which allocates 16k samples for digital input (Logic Analyzer).
  2. Hi @menach_g For DIO 24 (Digital Discovery) use: # trigger detector mask: low & hight & ( rising | falling ) dwf.FDwfDigitalInTriggerSet(hdwf, c_int(0), c_int(0), c_int(1<<24), c_int(0)) # DIO 24
  3. Hi @Lesiastas Sorry, but I'm not familiar with VB6, VBA. This was my biggest VB application so far Please search on the net for solutions, like: probably a += b should be written as a = a + b
  4. Hi @Wayne.B I wanted to say not, but I just notice that such option is already added Use the UART Spy in the beta version:
  5. Hi @thoriam In case you are supplying the amplifier with +/- voltages you can connect one of the inputs to GND. In case you are supplying it with + and GND, you can drive one input with a DC voltage using Wavegen Channel 2. The Network Analyzer controls Wavegen Channel 1 to generate stimulus signal and you can specify offset.
  6. Hi @Serdar I don't know when will such feature be added for Digital Discovery. You could use a micro-controller or FPGA development board for such purpose:
  7. Hi @Serdar Unfortunately it is not supported. The custom pattern is limited to 32k/channel.
  8. Hi @Serdar You could use a custom Bus and import data from file (up to 32k/channel) or use Script to generate custom pattern or parse the imported data.
  9. Hi @m72 After adding the Order option in Logic Analyzer (splitting the Input selection in two) I have forgotten to update the Protocol/Logic Analyzer to set the Order option automatically. Thank you for the observation, it is fixed for the next release.
  10. Hi @m72 This looks like a digital issue in the ADC. Have you used for this tests the WF v3.11.23 I sent you in private message?
  11. Hi @Grant Edwards It is not possible to analyzer scope data as protocol, but the Logic Analyzer and Protocol tool supports inverted option for UART.
  12. Hi @PaulW Good to hear it is working and thank you for posting the solution. The problem could have been with the Adept Runtime version. The Xilinx SDK installing/downgrading to an older version of this. The WaveForms also installs/uses this Runtime and due to frequent releases contains the latest version. The Xilinx processes may remain in background, blocking access to devices. In this case you could kill the hanging process from TaskManager or reboot.
  13. Hi @rwodnick Pulses might be hidden by sampling with any capture device. Like a 10ns pulse will be rarely visible with 1MHz (1us) sampling, 1% chance to catch. Select the Noise option to use half of the buffer to store pulses/glitches that might be hidden by the current sampling rate. See DIO 24 below. This option is supported by each device: Analog Discovery 1, 2, AD Studio, Digital Discovery, Electronics Explorer. With Repeated and Scan capture modes the sample rate is adjusted automatically based on time base. These modes are intended for scope-like operation, like timing analysis. Use the Record mode for traditional logic analyzer usage, to capture more samples and analyze data/protocols.
  14. Hi @m72 You have in private message a software version which changes a bit the digital timings. Please install this, reconnect the device to make sure it will get reconfigured and start the application. Let me know if this solves the issue. The scope inputs are rated for up to +/-50V, but it should survive higher voltages due the 820k series resistor before the 7.5-20mA protection. High voltages (with energy) usually damage the gain selector analog switch, which leads to DC reading. The attenuation option is intended to scale the scope readings, it is not a device feature. For instance when you use a 10x scope probe (9M series), the scope input will actually get 1/10 of voltage. Specifying 10x attenuation the software will multiply the readings by 10, to compensate this. You can also use this to reflect external voltage dividers, amplifiers... Edit: The calibration adjust the amplitude and offset.