attila

Hi @Ricky Yes, see the WaveForms SDK manual and examples here:

Hi @ad2user You could use the frequency modulation for this purpose. Like here 4.096ms period with 2048 FM buffer (bits) will give 500kHz bitrate. If you need more bits you can use play mode for FM.

Hi @AbbyM You can use the Standard boot mode which with DDRam buffering can capture up to 128MiS @ 125MHz or 32MiS @ 31.25MHz on 3-4 channels @reddish The record without DDRam buffering is not the most efficiently implemented. In this case, in each iteration the entire device buffer 256/512KiB is dumped.

Hi @Himayala1 The 16bit format samples are raw samples. To convert these to voltage see the note in the record dialog, like: V = 59.1970011866 * 1372 / 65536 - 0.002321186682 These range and offset values depend on the device/channel calibration. The 16bit format may be useful for long records with binary, wav, tdms saving to reduce the file size. The 32-64bit float values represent voltage, like 1.1 is 1.1V, these do not need conversion like the 16bit format.

Hi @SilverSurfer The scope inputs are differential but not floating! see: https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide#scope_input_divider_and_gain_selection Voltages above +-50V relative to device GND can damage the device/scope inputs. The device GND is connected over USB to the computer. To make the device floating you could use USB isolator, battery powered laptop, eventually floating laptop supply but this can be a bit risky...

Hi @toddkrein I think you can analyze the above circuit without powering it. With supply on Line it will likely damage the device/AWG !

Hi @AbbyM

Hi @sergiodorazio Could it be some crosstalk, glitch, ground loop issue? Try using short wires and each (specially SCLK and CS) twisted with a ground wire.

Hi @AbbyM For 64bit ARM the arm64 and for 32bit ARM the armhf should be used. You have in message the links to a newer release candidate version.

Hi @Chinmay Chobe You can find the manual and examples here:

Hi @MNSKev I'm glad to hear that.

Hi @Sangkyu Choi 5V, 2.5A 5.5/2.1mm connector, positive inner pin https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide#other_features https://digilent.com/shop/5v-2-5a-switching-power-supply/

Hi @Himayala1 It could be... Could you attach some screenshots or WaveForms workspaces with data ?

Hi @AbbyM The DDRam buffering improves recording for ADP3X50 in standard mode, otherwise it is transparent to the user. In your screenshot an AD2 is used. You may want to try using some newer sw version: https://digilent.com/reference/software/waveforms/waveforms-3/start

Hi @AbbyM Try reinstalling digilent.adept.runtime and digilent.waveforms

Hi @Himayala1 Are you comparing captures with the same rate ? At different rates higher frequency components may be sample/averaged differently. Here I compared the following which overlap, except the sub-sample trigger positioning which is not applied for the imported data. C1 - Rec. 200@50Hz 64bit + Import Bin R1 - Record 200@50Hz R2 - Single 4sec@8kHz

Hi @Himayala1 The maximum record rate with Analog Discovery (1&2) is about 1MHz.

Hi @Sid shak You could use View/Measurements (for added top level signals), View/Counter (for trigger), Cursors or Quick Measure.

Hi @toddkrein I don't know exactly your setup but I've used the AD2+IA to measure impedance of powered device. Either by using floating power supply for the device or USB isolator for AD2. The scope inputs are have two gain/range steps 5/50V. At low range the resolution is better 5Vpk2pk, +/-8V input with +/-5.5V offset. The AWG outputs should not be driven/shorted to external rail. When the AD2 is on these are protected up to +/-5V

Hi @Fortune Apparently it is set for Linux Recovery Mode, to boot from USB drive but this is not found. Enter the following uboot command, or reset the device and press S or any key then change the boot mode from WaveForms app.

Hi @AbbyM

Hi @alex_alk It will be improved/fixed in the next version. Thank you for the observation.

Hi @MNSKev For the ADP5250 to be supported by LabVIEW/VirtualBench VIs the following DLL(s) needs to be replaced in Windows/System32 nilciuserapi.zip If you are using 64bit Windows and a 64bit app (like the File Explorer): - the nilciuserapi.dll from directory x64 should be copied to the Windows/System32 in order the 64bit apps to use it - the nilciuserapi.dll from directory x86 should be copied to the Windows/SysWOW64 in order the 32bit apps to use it For 32bit Windows the nilciuserapi.dll from directory x86 should be copied to the Windows/System32. These DLLs should be included in a newer version of VirtualBench installer (like v20) but I'm not sure if this will happen. I could include it in the WaveForms installer but it wouldn't be nice to overwrite files belonging to other kits.