attila

Hi @Anthocyanina The entry field let you type in values or select from the presets list which can be scrolled by the mouse wheel. The plot axis let you adjust the respective range with the wheel or right mouse drag, and the offset with left button drag. Holding the Shift or Ctrl key slows down or speeds up these operations, and the Alt key swaps the offset/range adjustment. These operations also working on the plots when enabled.

Hi @mmmm Use dwf.FDwfDigitalInInputOrderSet(hdwf, c_int(1))

Hi @Someone In the Event view use Select: Highlight and double click to position an event or use the right click options. With the other Select modes this sliding happens, which will be fixed in the next version, 3.18.42 Thank you for the observation.

Hi @lokobob99 The DIOs can drive LEDs. The DIO short current is about 12mA, but it will drive a LED at about 5mA. If you need more power you could drive a LED with multiple DIOs, configuring the same PWM for each.

Hi @mmmm See the WF SDK/ samples/ py/ DigitalOut_Pins.py or other examples.

Hi @lokobob99 Which digipot do you want to control?

Hi @lokobob99 Is the servo supplied properly? Do you have common ground between the device and the servo? The pulse length should be between 1-2ms which is 5-10% duty at 50Hz

Hi @R Hari Chandana Use arguments for the application. I would recommended to use workspace (with script): Windows> "C:\Program Files (x86)\Digilent\WaveForms3\WaveForms.exe" workspace.dwf3work -runscript Linux$ waveforms workspace.dwf3work -runscript For the next iteration it is suffice to call: Windows> "C:\Program Files (x86)\Digilent\WaveForms3\WaveForms.exe" -runscript Linux$ waveforms -runscript To load and run or run a script tab use: Windows> "C:\Program Files (x86)\Digilent\WaveForms3\WaveForms.exe" -script myscript.txt/js Linux$ waveforms workspace.dwf3work -script myscript.txt/js Windows> "C:\Program Files (x86)\Digilent\WaveForms3\WaveForms.exe" -script "file 1" Linux$ waveforms workspace.dwf3work -script "file 1"

Hi @chromedome81 For up to 32Ki samples the Pattern Generator can be used and for more samples the Logic Analyzer Play mode, see:

Hi @ManonH With 100MHz system frequency 20MHz can be generated but not with 50% duty, like with 3-2 timing 40% or 2-3 60% duty. dwf.FDwfDigitalOutDividerSet(hdwf, S_Clk, c_uint(1)) # 100MHz default dwf.FDwfDigitalOutCounterSet(hdwf, S_Clk, c_uint(3), c_uint(2)) # 100M/(3+2) = 20MHz low/high 3/2 40% With ADP3X50 or Digital Discovery (and future products) the system frequency can be adjusted. dwf.FDwfDeviceParamSet(hdwf, DwfParamFrequency, c_int(80000000)) # 80MHz and with this or 120MHz, 20MHz with 50% can be generated. dwf.FDwfDigitalOutDividerSet(hdwf, S_Clk, c_uint(1)) dwf.FDwfDigitalOutCounterSet(hdwf, S_Clk, c_uint(2), c_uint(2)) # 80M/(2+2) = 20MHz low/high 2/2 50%

Hi @Someone I'm unable to reproduce it. Could you send me the workspace and/or screenshots? Thank you

Hi @R Hari Chandana The WaveForms SDK/API exposes functions to control the TM devices. It is up to your custom application/script how is this executed in foreground or background. If you are referring to the Script tool in the WaveForms GUI application, this can not run in background but it can be started with arguments to load workspace or load, start script. There is also a small command line application with source code that can simplify the control, generate and capture with devices, see: C:\Program Files (x86)\Digilent\WaveFormsSDK\samples\dwfcmd\

Hi @Matt Ownby The system frequency is adjustable on some devices. For Digital Discovery the digital-in rate is 8x. The default system freq is 100MHz (digital-out) and the digital-in 800MHz. The sample format can be selected to be 8, 16 or 32; BYTE, WORD (uint16) or DWORD (uint32) Many examples mention the bit order and sample format, like DigitalIn_Record.py: rgwSamples = (c_uint16*nSamples)() # 16bit per sample format dwf.FDwfDigitalInSampleFormatSet(hdwf, c_int(16)) # for Digital Discovery bit order: DIO24:39; with 32 bit sampling [DIO24:39 + DIN0:15] dwf.FDwfDigitalInInputOrderSet(hdwf, c_int(1)) The trigger bits also follow the order option. With DIN first order bit mask 4 (1<<2) represents DIN-2 and with DIO first order bit mask 4 represents DIO-26 (24+2). See the manual pdf if the SDK folder: Thank you for your post. I will try to add more explanation to the manual, like:

Hi @Guy R The CS is software controlled in the WaveForms app/ Protocol/ SPI Master, Custom and the WF SDK/API FDwfDigitalSpiSelect, with 100us - ms latency. If you need precise control for CS you could use WF app/ Patterns or WF SDK FDwfDigitalOutDataSet or Protocol/SPI/Sensor, see WF SDK/ samples/ py/ DigitalOut_SPI.py DigitalOut_Custom.py DigitalOut_CustomBus.py

Hi @Arin George 1. If the device buffer of 256MiB for Digital Discovery is overflown, when capturing above this size and the USB transfer can't keep up. 2. Chunks are the new samples in each status/read iteration. 3. Automatic. 4. USB 2.0 HS 480Mbps This is a 32b 256Mi 1GB capture, 4X the device buffer size is working up to ~10MHz (~45MBps) (pic1) but at 20MHz buffer gets overflown (pic2). Note that for RPi the USB and processing rate specially with 2 devices will be lower than with a computer.

Hi @Choon Shin See the following:

Hi @Britishkid You can use the Pattern Generator like this to trigger on Scope Detector with the needed delay/wait and run/length time. Set the Scope to sample at 100MHz or use trigger filter decimate. With lower rate and averaging the uncertainty will increase from 10ns (100MHz). Note there will be a 360ns pipelining delay due to ADC and data processing.

Hi @Guy R You can find some C and many Python examples in WF SDK/ samples/ py

Hi @Bartt Some dependencies may be broken. Try reinstalling digilent.adept.runtime and digilent.waveforms https://digilent.com/reference/software/adept/start https://digilent.com/reference/software/waveforms/waveforms-3/start try: apt fix-broken install

Hi @bryan78 This jump is related to the newly added cross-tracking between the plot and Event view. It will be fixed in the next version.

Hi @Albertu95 For falling edge set Hysteresis to zero or set level + hyst. This falling edge level +/- hyst will corrected in the next version.

Hi @bryan78 This bug may be related to the recently added cross-tracking between the plot and Event view, and Data view in Logic Analyzer and Scope. I will try to reproduce and fix it next week. Thank you for the observation.

Hi @CFalardeau97 It the application is in the PATH or next to the app then it can be called just by name (like: ping, cmd, ...) otherwise the full path should be used, like: Tool.start("C:/test/myapp.exe"). The argument array is optional, depends on your app. The work directory is also optional, it depends if you need this for your app or not. In some cases the app may need to be open like this: Tool.start("cmd", ["/c myapp.exe"], "C:/test/")

Hi @CFalardeau97 You can use Tool.start or Tool.exec like: print(Tool.exec("C:/Windows/System32/cmd.exe", ["/c", "pwd && dir"], "C:/temp"));

Hi @bryan78 Could you provide more detail about the problems? I don't seem to be able to reproduce.