attila

Technical Forum Moderator
  • Content Count

    2919
  • Joined

  • Last visited

  • Days Won

    188

Everything posted by attila

  1. Hello @Shane Yes. The PowerBricks use microUSB similar to AD2.
  2. Hi @Pierre The sweep time depends on multiple factors: - Samples: sweep steps/points - Average and Options/Averaging: time and number of measurements - Options/Settle: time - Options/Min Periods: the minimum number of signal periods to capture - one step takes at least about 10ms Sweep time = Samples x max ( ~10ms , Settle + max ( Average , Averaging x MinPeriods / Frequency ) )
  3. Hi @dumbguy 1. You can add Bus in Logic Analyzer. Here you can also specify Clock and Enable signals if you need such. 2. The twisted GND wires should reduce the probability of cross-talk. You can adjust the IO voltage/ logic threshold under the Supplies interface.
  4. Hi @pascalSarto Unfortunately it is not possible. It would require implementing CAN interface logic in the device. Currently the device performs data deserialization for various protocols and the sequence of bits gets interpreted in software.
  5. Hi @abcpt On the IA Adapter the Wavegen 1 and Scope 1+ join under the DUT socket:
  6. Hi @abcpt The two and four point measurements are hardware and not software facts. The WF Impedance Analyzer can work with four point setup. The current flow is between Wavegen and GND. You can connect the Scope 1+/2+ to DUT and 1-/2- to Resistor GND side. Such setup is also used on the IA Adapter.
  7. Hi @Barry I have just tested the installer with a standard user. This requires elevation and after entering an admin user credentials it installed correctly.
  8. Hi @Andy_Can Did you install the dwf.framework ?
  9. Hi @JoonYang Press the "Config" button for the popup window. You can also adjust the samples and rate on the right, after pressing the green arrow.
  10. Hi @bmac_2780 The software takes in account the probe-IA-PCB impedance and subtracts this from the measurement results. Additional to this, the open/short compensations should help to improve the results further.
  11. Hi @[email protected] In WF 3.12.2 the default option is already 'reboot later'. I just tried running: digilent.waveforms...exe /S, it does not reboot for me. Try the latest beta version, which updates the deprecated MSVCRuntime included in the 3.12.2 https://forum.digilentinc.com/topic/8908-waveforms-beta-download/
  12. Hi @matt.zimm Adjusting the frequency (or any other settings) will restart the Pattern Generator which results a few milliseconds of stopped state. You could use a ROM logic to switch between frequencies. Like here DIO 24-25 are input clocks and DIO 31 is select for output on DIO 39 You can have more input clocks and 2-3-4 select signals. The select can also be driven by Patterns with slow clock or counter.
  13. Hi @Leo_W The PGVCC5V0 is fine, it should be about 1.6V ( >1.3V ) Probably the IC10 is damaged.
  14. It is always fan to play with these. To Play on Wavegen, modulate it in the device, listen with speak on the 3.5mm jack, or capture with Scope, see the Spectrogram.. see it in 3D...
  15. Hi @RF68UF The Rate is the sample rate at which the channel data is played back on the computers audio output. The Speed is the ration between playback and capture rates = audio Rate / capture Rate (with Tempo 1x) The Tempo lets you skip capture samples. This is useful in case you capture (record) at high frequency, since the computer audio usually tops at 192kHz. For instance, if you capture at 1MHz with Tempo 10x will playback only every 10th samples, so with 100kHz you can play back at normal (1X) Speed. Speed = audio Rate / ( capture rate / Tempo ) If you want to continuously play back the capture data use Speed 1X and scan Screen.
  16. Hi @Leo_W I don't have too much experience with the ADS, I only have a prototype of this. The driver and protection circuit is the following and it is next to the 15V socket. @malexander Are you aware of any issues with the +12V rail ?
  17. Hi @wchao_iris The noise on such audio interfaces is usually due to ground loops, rather analog than digital problem. With AD2 you can analyzer the timing of such digital signals. For 6MHz signal you need at least double, 12.5-20MHz capture rate. The record-streaming function is limited to about 1MHz. With the 16k AD2 buffer (w 4th device configuration) at +12Mhz you can capture only about 1ms data.
  18. Hi @parkinsonp Make sure to have ground connection between the devices. The DIN lines have lower impedance that may interfere with the driver circuit. Try using the DIO lines. https://reference.digilentinc.com/reference/instrumentation/digital-discovery/reference-manual#input_dividers https://reference.digilentinc.com/reference/instrumentation/digital-discovery/reference-manual#io_level_translators
  19. Hi @Chris Pouzou The installer contains update for WF app as well for dwf.dll It has separate sections for WF app (app+libs+help...) and WF runtime (dwf.dll+device files) and WF SDK (help+examples) (In the earlier test I have used a loopback wire on mosi-miso)
  20. Hi @NightTrain You can use multiple devices with one machine with separate instances of WF applications, or by one custom script/application using WF SDK. The DD does not have dedicated trigger IO but any DIO/DIN can be used as trigger condition. It can capture up to 32bit samples at up to 200MHz, from 24 DIN and 16 DIO lines. Each device has its own oscillator so you may notice jitter/skew between devices with high frequency analysis.
  21. Hi @Chris Pouzou I have repeated your test using Python and it is working. I have modified the SDK/ samples/ py/ Digital_Spi.py : Digital_Spi2.py I don't know which WF version are you using, try the latest one: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ # continue running, driving output signals after device close dwf.FDwfParamSet(c_int(4), c_int(0)) # DwfParamOnClose; 0 = run, 1 = stop, 2 = shutdown .... dwf.FDwfDigitalSpiReset(hdwf) dwf.FDwfDigitalSpiClockSet(hdwf, c_int(1)) dwf.FDwfDigitalSpiDataSet(hdwf, c_int(0), c_int(4)) dwf.FDwfDigitalSpiDataSet(hdwf, c_int(1), c_int(7)) dwf.FDwfDigitalSpiSelect(hdwf, c_int(0), c_int(1)) dwf.FDwfDigitalSpiFrequencySet(hdwf, c_double(1e6)) rgbTX = (c_ubyte*2)(0xAA, 0x55) rgbRX = (c_ubyte*2)() dwf.FDwfDigitalSpiSelect(hdwf, c_int(0), c_int(0)) dwf.FDwfDigitalSpiWriteRead(hdwf, c_int(1), c_int(8), rgbTX, c_int(len(rgbTX)), rgbRX, c_int(len(rgbRX))) # write to MOSI and read from MISO print("TX: "+str(numpy.fromiter(rgbTX, dtype = numpy.uint8))) print("RX: "+str(numpy.fromiter(rgbRX, dtype = numpy.uint8))) dwf.FDwfDigitalSpiSelect(hdwf, c_int(0), c_int(1))
  22. Hi @Joseph Decuir Under System Preferences / "Security & Privacy" - select "App store and identified developers" - select "Run Anyway" On first launch: "Launch Anyway" or secondary tap and open... Sorry for the Apple policies...
  23. Hi @TheStumbler You could use the Pulse Counter in Logic Analyzer or in Scope mixed mode after Add Channel/ Digital/ Signals. For Reset use VSync and Source HSync, Count you can set it up to 32k lines.
  24. You can use Script plot for such purpose: ScriptPlot.dwf3work