Jump to content

attila

Technical Forum Moderator
 View Profile  See their activity

  • Posts

    6,454

  • Joined

  • Last visited

 Content Type 

Everything posted by attila

  1. attila
    Hi @MaxRdgz You can use the Script tool with Scope.run() function and the command: C:\Program Files (x86)\Digilent\WaveForms3>WaveForms.exe "C:/MyWorkSpace.dwf3work" - runscript
  2. attila
    Hi @m72 Thank you for the observation. It is fixed for the next version.
  3. attila
    Hi @Zebel The measurements are available only in the app and not from sdk.
  4. attila
    Hi @Zebel http://www.radioradar.net/en/measurements_technics/oscilloscope_measurement_fundamentals.html
  5. attila
    Hi @Zebel The WF SDK provides raw data and network/impedance analysis. The measurements and others are implemented in the WF app. In custom app the measurements needs to be implemented. You could eventually use instead custom app the Script tool in the WF app to access the measurements, like: var acrms = Scope.Channel1.measure("ACRMS")
  6. attila
    Hi @EzeStare The Constant Voltage and Current options will change the Wavegen Amplitude and with Adapter also the Resistor value. The Custom lets you write script to control the Amplitude, Offset, Resistor based on frequency step and reading. The editor provides some examples.
  7. attila
    Hi @ssm Yes, you can use the SDK under Win, MacOS and Linux as well. See the manual at /usr/share/digilent/waveforms/manual/dwfsdk.pdf
  8. attila
    Hi @maz The "device descriptor request failed" indicates that the device attach is detected but the low level USB communication fails. 1. It could be an USB contact issue with cable, connector on host or device side. Try other cable, other host connector, inspect the connector in the device. It is very hard to insert the microUSB reversely but such could break the inner contact plate. 2. The USB controller in the device could be damaged.
  9. attila
    Hi @rainerle This is really weird. Thank you for the update and let us know if you notice any further issue.
  10. attila
    Hi @EzeStare 1. The Wavegen output has zero impedance. https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual#awg_iv 2. By default the selected Resistor is used, but you can select Constant Voltage/Amplitude or Custom Mode which change the Resistor value. 3. The shorter cables are better and open/short compensations can be used to reduce the effects of the wiring.
  11. attila
    Hi @rainerle Did you try restarting your machine having the device unplugged? Restart is better than Shutdown. The Restart cleans up UEFI-system-driver cache which could contain invalid device info. Did you try with and without the driver-filter? This can be found in the WaveForms DMG Old macOS version require the driver to be installed, new macOS versions don't require it, on some new Mac hardware it may not work with the driver.
  12. attila
    Hi @qraa The record rate, streaming over USB is supported up to about 1-2MHz, depending on the host computer, USB... Notice the "samples lost/corrupt" warnings prints at the end of the script.
  13. attila
    Hi @Slawek You can also find for some controls the Script reference in the status-bar.
  14. attila
    Hi @Slawek The Script tool provides access to most of the control behind the interface, a lot of objects and functions. The commonly used ones are listed in the app Help and the Ctrl+Space can be used to reveal the child objects. The Script access for scope-measurements-reset is currently not available but it will be in the next version. Thank you for the clients since the feedbacks make the app evolve
  15. attila
    Hi @Slawek The "acquisition" saving can't be automated but: - In the Logging view you can select the export format under the 'gear' after the Source option. - You can use the example script to save both picture and data.
  16. attila
    Hi @Slawek The Record mode is intended to capture then analyzer. It may take long time for the data to be processed in various views, measurements... You can use a Scrip to restart the capture: do{Scope.start()}while(Scope.wait())
  17. attila
    @malexander Ok, Thank you
  18. attila
    Hi @reddish With 2 devices I can reproduce the issue you are describing. Earlier I have tried with only one device and two application. @malexander Having 2 devices with separate apps connected to them. After killing one app or exit without disable/close, the following apps can't connect the device. The JtscInitScanChain fails with scerrInitFailed. May be the DPTI enabled flag remains set in FTDIFW and JTAG enable fails? Could we solve this problem?
  19. attila
    Hi @reddish It is working for me also with adept 2.19.2
  20. attila
    Hi @MarceloNotThePLCguy You should try the latest version: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ The DD RPI4 issue was solved in the 3.13.20 I let such setup run again and there were no errors in the past 16 hours.
  21. attila
    Hi @alexplcguy Have you used WF 3.13.20 or newer? I tested it by running with the device for days on RPI4 with Raspbian and Ubuntu 18 64bit
  22. attila
    Hi @reddish I just tested it under Ubuntu 12.4 amd64. I can connect to the device even after the other connected process was killed and busy flag is stuck. Which Adept Runtime runtime version are you using? I have tested it with 2.20.1 and .2 $ dpkg -l digilent.adept.runtime ||/ Name Version Description +++-==============-==============-============================================ ii digilent.adept 2.20.1 Digilent Adept Runtime
  23. attila
    Hi @reddish The device info is cached by Adept Runtime in shared memory. This is required because some info may be unavailable when a device is opened by another process. In case an app which uses a device crashes or is killed, the busy/opened flag will not be cleared. The clear is also performed in normal detach. When the last app using Adept Runtime closes, this gets unloaded from memory together with the info cache. However a stuck flag does not prevent an app to connect to a device.
  24. attila
    Hi @Ondrej Thank you for the counter idea. I will add it later.
  25. attila
    Hi @Ondrej You could use the Sync mode in case the average signal rate is below 1MHz, up to 100M counts. Set a high number of Samples, the Rate is only informative for representation.
×
×
  • Create New...