attila

Hi @AKA The DIO drive on AD2 is 4mA. On AD3 is by default 4mA but can be adjusted with C API FDwfDigitalIODriveSet

Hi @AKA What header are you reconnecting ?

Hi @AndyMessier It can generate waveform or pattern from device buffer up to system frequency sample rate or higher, by skipping some, see AnalogOut_Custom.py example The system frequency, for all instruments can be adjusted with DwfParamFrequency. In play mode the data is streamed, transferred in chunks from computer, limiting the sample rate to 1-2MHz The newly added idle hold option keeps the last output value in done state, with finite run time.

Hi @malexander WF links to libs. My testing with Ubuntu 22 was also successful.

Hi @bobql 1. The Sensor tab on execution first calls the initialize function, where sensor register, global variables, file initialization... can be performed. 2. Calls the software loop function, without executing it in the device, to build a pattern with the transfers, like for CS, CLK and MOSI. 3. Starts to generate this pattern with hardware timer at the specified rate and iterations, and at the same time it captures the transfers. 4. Decodes the received MISO bits by software call of loop function, without executing it in the device. 5. At the end calls the finish function, where sensor register shutdown and file finalize can be performed. The software timing of the software function calls in not precise but the pattern generation is, which are basically loop function calls in hardware. Similar can be done in SDK. Pattern with digitalout functions, see DigitalOut_SPI.py example, repeat can be set to 'infinite'. Steps 3-4 can be merged, to receive and decode simultaneously, see DigitalIn_Spi_Spy.py. In Sensors tab these are separate since the sw loop execution takes some time and it would be a bottleneck at high rates.

@malexander Could you help with this ?

Hi @sng2024 The AD3 scope input have a high range of ~50V peak to peak and with offset adjustment can read +/-50V The probe attenuation can be specified with the Probe option under each channel option.

Hi @scorbetta I was suspecting to find multiple variants from this library, but it finds only one. I don't know why it is for you installed in /usr/local/lib64 Have you downloaded it from our site ? https://digilent.com/reference/software/adept/start The location shouldn't matter but it is strange since the adept.runtime...deb uses /usr/lib64

Hi @gcb See the reply on your earlier post:

Hi @SergeLafontaine The latest version is notarized, it should pass security:

Hi @Kyoko J If you are using the Analog Discovery Impedance Analyzer adapter, the connections are in this. J2 is the connector for Device Under Test, Load https://digilent.com/reference/add-ons/impedance-analyzer/start https://digilent.com/reference/add-ons/impedance-analyzer/reference-manual https://digilent.com/reference/add-ons/impedance-analyzer/getting-started-guide

What does the ldconfig -p | grep libdmgr list ?

Hi @bobql See the following post:

Hi @scorbetta

Hi @scorbetta The mentioned function should be in the latest adept.runtime Make sure the install succeeds, there are not errors listed sudo apt install ./digilent.adept.runtime_2.27.9-amd64.deb

Hi @Roche The frequency adjustment is intended for the Pattern Generator and Protocols. The device can generate natural division signals of the system frequency, like from 100MHz, 50, 25... and with 80MHz 40, 20... The Logic Analyzer can sample at up to 8x of system frequency.

Hi @gcb The instructions are the same or similar for newer VS versions. You can build app for x86, x64, arm64 or arm64ec, just use the corresponding dwf.lib dependency under project/Properties/Linker/Input

Hi @gcb 1. Wavegen/Play 2. Logic Analyzer/ Mode: Play

Hi @rjratnip See the following post:

Hi @fahiz The amount of data may be too much for the graph function used. You may need a different method for drawing.

Hi @malexander Only the new builds are signed, since 3.22.14, with the same key as adept.

Hi @AndayLe The FDwfAnalogImpedancePeriodSet is for different purpose.

Hi @CAM C The record mode uses data streaming. Since it doesn't know when the trigger will arrive it starts streaming immediately and stop after the given 'length'. This is why the samples collected in the software buffer need to be aligned at the end, see AnalogIn_Record_Trigger.py example. With position 0 the streaming starts with the trigger. The acqmode single returns a buffered aligned capture, up to maximum sample rate and device buffer size.

Hi @malb Currently the latest build for ARM Linux is 3.22.15

Hi @fahiz @Fausto Why are you limited to 0.2 sec ? with 1.5M samples and 1.5MHz capture rate the span in 1sec If you are interested in peaks you can use min/max sampling mode (FDwfAnalogInChannelFilterSet), less samples and lower frequency. The sampling rate should be at least 4 times than signal frequency, otherwise you see aliasing. https://www.ni.com/docs/en-US/bundle/labwindows-cvi/page/advancedanalysisconcepts/aliasing.html