Jump to content

attila

Technical Forum Moderator
 View Profile  See their activity

  • Posts

    6,667

  • Joined

  • Last visited

 Content Type 

Everything posted by attila

  1. attila
    Hi @Kuz The next version will add width/height options, horizontal/vertical header for csv/txt exports, 1bit mono, 8/16 grayscale or 24bit color image options. Am I missing something ?
  2. attila
    Hi @Lihua For warranty and replacement contact the support.digilent @ ni.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number.
  3. attila
    Hi @Mavitaka Only the FPGA or Zynq development boards: https://digilent.com/reference/programmable-logic/start
  4. attila
    Hi @ctighe Calling Receive/Receiver function from Script the RX logging in the Protocol/UART will stop. The Receive function returns the characters received since the previous call or after initialization, calling Receiver. Try adding wait() before Receive.
  5. attila
    Hi @Dat Nguyen Do you have anything connected to the V+ output ? Can you tell me what you used it for last time? The device USB power/current is very low, it should be at least about 3W/600mA, and the USB voltage is too low. The lack of USB power, essentially dropping supply voltage could cause device malfunction. Try using other USB port, computer, powered hub, 5V DC auxiliary power supply. The latest software version overcomes a problem caused by low voltage, but the real solution is to provide sufficient power for the device.
  6. attila
    Hi @Steve_3 Here two periods are generated for each capture: test_undersampling_v4.py Analog-in: trigger-wait-run-wait-run-done I set the wait to 2ms to fit in the 8ms capture, but you can adjust the analog-in trigger position (secDelay) as you need it.
  7. attila
    Hi @Mavitaka Reference clock is not supported by Digital Discovery only Sync capture mode:
  8. attila
    Hi @Mavitaka The highest output frequency with Digital Discovery is 50 MHz, half of the default 100 MHz system clock which is adjustable.
  9. attila
    Hi @Steve_3 In v3 one analog-out run is performed for each analog-in capture. Having FDwfAnalogOutRepeatTriggerSet-1 each analog-out run will wait for trigger (analog-out capture). After each analog-in reading by the software (FDwfAnalogInStatus) a new capture is started which also initiates a new analog-out run. This is why the analog-out repeat is set to infinite (FDwfAnalogOutRepeatSet-0). Adding wait to analog-out would delay the signal relative to the analog-in start, shift the signal to the right in the capture. To shift it left (or right), to start the analog-out before (or after) the capture left-most sample use a positive (or negative) secDelay parameter.
  10. attila
    Hi @Hellsmoke See the WF SDK/ samples/ py/ AnalogIn_Trigger.py DigitalIn_Trigger.py example
  11. attila
    Hi @Kuz
  12. attila
    Hi @k_b The latest version adds glitch filter for edge trigger with Digital Discovery:
  13. attila
    Hi @jaejoo14 Contact the support for replacement. The relay on oscilloscope channel 1 is stuck on high range, so the reading is probably correct only with 1V/div and higher. Toggling the relay a few times, like changing between 500mV/div and 1V/div, should have removed temporary stuck, contact issue, oxidation. You could try the following to make sure all application settings are reset, but don't expect to help. /Applications/WaveForms.app/Contents/MacOS/WaveForms -safe-mode (For nicer app interface you could use Settings/ Options/ Style : Fusion)
  14. attila
    Hi @jaejoo14 For warranty and replacement contact the support.digilent @ ni.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number.
  15. attila
    Hi @jaejoo14 1. Make sure the attenuation is set to 1 X 2. The input range relay may be stuck or remain in bad position due to certain software settings. Try toggling Channel 1 Range between 500 mV/div and 1V/div Does it solve the problem ? Can you hear it clicking like it is for Channel 2 ? 3. If you have calibrated the device (WaveForms/Settings/Device Manager/Calibrate), make sure the Scope 1 Gains are low values, or select Reset/Load Factory.
  16. attila
    Hello, In AD3 the system frequency (ADC, DAC, DIO) is adjustable between 50-125MHz, so the sample rate can be set up to 8ns. The oscilloscope device buffer can up to 64k samples. The capture rate is limited by USB latency and can be up to about 2000 captures / second, when capturing up to 256 samples.
  17. attila
    Hi @Loic VINET Could you attach or send me the script ?
  18. attila
    Hi @Kuz I am working on it
  19. attila
    Hi @dmangione A device can be controlled by one application/script at a time. If you want to control it from script/custom app, make sure to close the WaveForms app or connect with it to a Demo device.
  20. attila
    Hi @Steve_3 See the following: test_undersampling_v3.py
  21. attila
    Hi @ryangill No, currently we have no T&M device with LVDS. You can find devices with LVDS IOs among the development boards, like Zmod connectors on Eclypse Z7, USB104 A7: https://digilent.com/reference/programmable-logic/eclypse-z7/start https://digilent.com/reference/programmable-logic/usb104a7/start
  22. attila
    You can use the analog-in trigger position: dwf.FDwfAnalogInTriggerPositionSet(hdwf, c_double(acqTime / 2 + sec_delay))
  23. attila
    Hi @Kuz Internally in the application for each channel a persistence 2d array is computed, from this rgb images generated and drawn/overlaid in the Persistence view. Exporting the image is not suitable for you ?
  24. attila
    Hi @Steve_3 The SamplingDelay is only for external sampling clock, when using a trigger input edge to validate sampling. You can use the AWG/AnalogOut Wait to delay the signal output relative to the trigger.
  25. attila
    Hi @Alessandro Are you using the latest sw version ? Do you see the same behavior with WaveForms application ? It is easier to use the app for troubleshooting, modify settings and see the result.
×
×
  • Create New...