Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by attila

  1. Hi @Stephanie There is no need to export the View/Logging. This can save data/picture or execute custom logging script automatically on each acquisition. The Logger tool also contains RMS measurements which can be exported to file.
  2. Hi @Stephanie You can use the Logging/Script in Scope like this: You can also log and File/Export the history from the Logger tool:
  3. Hi @juliosilva The latest beta version adds UART TX/RX sniffer option.
  4. Szia @Andras The UART is not suitable for RGB LED control. You can use a custom Patterns signal and script like this to build the data sequence for WS2812 RGB LEDs. Here you have the project: WS2812.dwf3work The default Analog Discovery configuration allocates 1k samples for each Patterns channel with this you can control 14 LED array (1024/24/3). With the 4th AD device configuration you will have 16k samples and can control 227 LEDs. With Digital Discovery 32k 455 LEDs... The supported frequencies are positive integer divisions of 100MHz base frequency: 100MHz, 50M, 33.3M, ... ~3.226M, 3.125M ...
  5. Hi @Thore The calibration is implicitly used in the SDK. The set or got voltage values with API functions are always corrected based on the device calibration parameters.
  6. Hi @sanfans The 8x800MHz, 16x400MHz, 32x200MHz is a limitation from the device DDRAM data rate. It is possible to synchronize devices with trigger, but the data merging might suffer from the jitter between independent device oscillators. The bandwidth of DIN lines is 100MHz+ This highly depends on the used adapter, wiring, termination, source drive/slew... The delay between captures varies from milliseconds to seconds, depending on the amount of captured data that needs to be transferred over USB to the PC, 20-30MBps.
  7. For the Protocol / SPI-I2C /Spy mode you should specify the approximate (or highest) protocol frequency which will be used to filter transient glitches, like ringing on clock signal transition. The Errors you get indicate the signals are not correctly captured. - make sure to have proper grounding between the devices/circuits - use twisted wires (signal/ground) to reduce EMI - use logic analyzer and/or scope to verify the captured data / voltage levels at higher sample rate at least 10x the protocol frequency Like here in the Logic Analyzer you can see a case when the samples are noisy:
  8. Szia @Andras You need higher sample rate, more than twice of the signal toggle rate in order the interpreter to decode correctly the I2C. You can use Record to capture more data like 400kHz for 100kHz I2C: You can also use the Protocol/I2C/Spy in case you are not interested in timing, you only need the decoded data.
  9. Hi @Pseudonym1 On Digital Discovery: - the DIO lines have high impedance, with optional 10k pull-up/down for each line - the DIN lines have 500k pull to adjustable common pull-down/mid/high level - the logic high level is adjustable between 1.2-3.3V, this also adjusts the input logic threshold
  10. Hi @john g If you have connected as it is in the drawing it is wrong. According the wire colors in the waveGen_DPO you have connected AD2 Scope to Tek Scope and in AFG_Scope looks like you have connected AD2 WaveGen to Tek AFG When connecting AD2 Scope to AFG you should have 3 connections: - AD2 GND (black) to AFG GND, this is a must, the scope inputs are differential but not floating - AD2 1- (orange/white) to GND, this is important specially for high frequency signals - AD2 1+ (orange) to AFG output When connecting AD2 WaveGen to Scope: - AD2 GND (black) to DPO GND - AD2 W1 (yellow) to DPO input
  11. Hi @zaxxon @malexander That error log is not an error. It is generated when dinfoFWVERRom is called during the device enumeration process in the DWF library. For Analog Discovery this is not used, it is ignored even if it fails. In the above output the device is detected by the DWF library so it should be also detected by the WF application.
  12. @malexander Could you help in this issue?
  13. Hi @john g Could you post photo with the wiring between the devices? It would be also good to see the Tektronix scope and awg configuration? scope time base, range, input coupling, generated frequency, amplitude... Can you see the signal generated between the Tektronix devices?
  14. Hi @cramcram Have you tried passing the following? CXXFLAGS='-D_GLIBCXX_USE_CXX11_ABI=0'
  15. Hi @Anjali Agarwal The Xilinx Platform Cable is not supported by Digilent software, like djtgcfg This USB device should be used directly with Xilinx tools like: iMpact, Vivado, EDK, SDK
  16. Hi @peerlesspalmer The relays on the IA Adapter are latching which are controlled with pulses, like this:
  17. Hi @john g Make sure you have ground connection between the devices and circuits! Without such the readings/measurements likely to be wrong or the devices/circuits can be damaged
  18. Hi @HYH Yes, you are right, the deleteFile should be after the readArray... Thank you for the tooltip idea.
  19. Hi @peerlesspalmer On the IA adapter the DIO lines are used to switch between the reference resistors using the relays. This is done automatically by the WaveForms application when in the IA interface Adapter is selected. From custom application you can use the FDwfAnalogImpedance* functions of the WF SDK, like: FDwfAnalogImpedanceModeSet(hdwf, 8 ) // select Adapter FDwfAnalogImpedanceReferenceSet(hdwf, 100.0 ) // select 100 ohms See the SDK manual and Python example codes:
  20. Hi @HYH The Script tool provides access to the model behind the app interface. With "text" properties set the text like you type in the combo box fields in interface (1ms), with "value" you can set numeric value (0.001). Patterns.Channels.DIO0.Divider.text = "1" Patterns.Channels.DIO0.Divider.value = 1 Not all the parameters are listed in the help, only the ones considered useful. To see the properties and children of the current node press Ctrl+Space (or enable code completion under View menu).
  21. Hi @HYH You can do this with script, like reading parameters from an external file: The script argument should work like this. >"C:\Program Files (x86)\Digilent\WaveForms3\WaveForms.exe" -script default.js This opens the WF app, loads and runs the script or the opened WF app runs the give script.
  22. Hi @agaelema Could you describe your wiring? Here W1 is connected to 1+, W2 to 2+, 1- and 2+ to GND. In the second screenshot the W2 amplitude is changed from 2 to 3V
  23. Hi @Damian Wolfe The board has common ground, the scope inputs are not differential. To measure the voltage drop you can connect two scope channels to the resistor and add a math channel, like C1 to VCC, C2 to drain and have M1=C1-C2
  24. Hi @HYH The easiest way to automate things is using the WF app and the Script tool. In the interface you can easily configure and test the setup, use a bit of JS code to modify/automate what needed. You can also use the File IO and exec/start commands to communicate with external apps. The project/workspace is compressed similar to this: