attila

Hi @Carl Troili See the included example, I get above 3000 captures / second.

Hi @Yisong Make sure to have GND connection between devices and circuits. Is the digital voltage level 0/3.3V ?

Hi @JAlaj In newer sw version the CS can be controlled by hardware. With the SPI/Custom or Script or API if the .Start/Stop() is not called the .Read/Write() will automatically assert CS.

Hi @skuznicki Don't you have deb or rpm package manager in you Linux ? This would automatically install the dependencies like libusb-1.0

Hi @PAPPP It will be fixed in the next version. Thank you for the observation.

Hi @skuznicki Install the digilent.adept.runtime and digilent.waveforms, armhf for 32bit ARM and arm64 for 64bit ARM Linux. The waveforms installers contain the WF app which requires Qt5. The digilent.waveforms.adp3X50_#.#.#_armhf.deb is intended for the ADP3X50 embedded more. This does not contain WF app, only WF runtime (dwf.so and other required files), WF SDK (manual) and it should work on other 32bit ARM OSs.

Hi @abedbaltaji Could you show what are you calling ? a piece of code or script

Hi @abedbaltaji With the default device buffered acquisition mode acqmodeSingle the trigger position is set relative to the middle of the capture. The T0 to be at the first sample set this to capture time span/2, like: dwf.FDwfAnalogInTriggerPositionSet(hdwf, c_double(0.5*cSamples/hzRate)) Use other values for different position. With acqmodeRecord, data streaming for long capture at lower rates, with trigger position 0 the streaming is started at the trigger event. With AD2 the record should work up to about 2.5MHz, depending on USB, system...

Hi @JAlaj Enable the "Multi MISO" and select the MISO channels you need. Like here MOSI is DIO-2 and MISOs are DIO-3,4,5 If you have multiple CSs you can use "Multi Select"

Hi @abedbaltaji

Hi @dynamatt The script is working for me with 3.20.1, 3.20.24 (I only added to print the sw version and device name) Again, script uses AD2 and DD is used for slave. What are you powering from the AD2's V+ 3.3V ? Is ~500ms sufficient for this to power up? Running code in WF Script, to have similar timing as in the earlier Python script, would look like this: Supplies.MasterEnable.checked = 1 wait(0.5) for(var i = 0; i < 5; i++){ print(Protocol.I2C.Read(0x62, 6)) wait(1) } Supplies.MasterEnable.checked = 0

Hi @lokobob99 See the following post:

Hi @JimR2 The Math (and other tabs) should work with 65536 samples, only the Alter is not working with such number of samples. Anyway, higher number of samples only matters when generating low frequency signals, kHz or lower. After implementing DDR RAM buffering for Scope and Logic Analyzer the earlier used FPGA BRAM for these was reallocated to the AWGs, so the buffer size has increased. The Alter uses some integer operation to handle eventual interpolation (if the destination and alter sizes differ) and this with 64k indices caused overflow on 32bit integer. I have to re-re-test some new features and other fixes. Hope to have a beta release on Monday. The 64k refers to the (maximum) AWG carrier device buffer size, or AM/FM/PM buffer size depending from where was the editor opened. On Analog Discovery 1, 2 the signal is stretched to fill the buffer, but on newer devices AD3, ADP3X50, EclypseZ7... it can handle different number of samples. This is also used to synthetize more precise frequencies.

Hi @dynamatt Could you attach some code or script with problem ? Here a Python example is run on Analog Discovery 2 and Digital Discovery is used as slave with WaveForms application.

Hi @JAlaj I recently added multi-CS support for Protocol/SPI/Spy. I will also add multi-MISO support. Probably sometime next week as I'm in the middle of implementing a different feature.

Hi @JimR2 The Alter is not working with 65536 samples. Until this problem is solved please set Samples to a lower value then go to Alter, or use Math tab or any other function even with 65536 samples. Thank you for the observation. Edit: If is fixed for the next software version.

Hi @reddish Yes, it is fixed. Thanks for noticing.

Hi @outback Then use the 'h' prefix just like it is in the receive.

Hi @alpanth Yes.

Hi @reddish Like most features and functions, these were added at the request of the users. C-API can be used with other languages where FFT functions/libraries are not available.

Hi @norandomtechie Update digilent.adept.runtime: https://digilent.com/reference/software/adept/start

Hi @alpanth Yes, the range and offset get returns the actually available full scale ADC range and the configured offset DAC voltage. This is useful to know the reading resolution, where does the signal clip, to convert the samples to voltage units in case the 16bit data function is used...

Hi @reddish The API will be public in the next version. I don't wanted to publish it before finalizing the functions.