attila

Hi @enelson Could it be a ground loop issue ? Try powering the AD2 from 5VDC supply to minimize such.

Hi @cmillionbrown Most probably it is a mUSB contact issue. The revF or newer should be protected from eeprom corruption but it could be reprogrammed.

Hi @shishir Make sure the compatibility mode is off.

Hi @ALackOfNumbers You can use a Script like this combine to two consecutive bytes in a word: Protocol.UART.Receiver() var rg = [] while(wait()){ var t = Protocol.UART.ReceiveArray() if(!t.length) continue rg = rg.concat(t) while(rg.length>1){ var v1 = rg.shift() var v2 = rg.shift() print(v1,v2) print((v1<<8)+v2) // MSB first } }

Hi @exsurgo_ankit Yes. These are the maximum tolerances for the components and in the important analog areas like around the amplifiers 0.1%R and 1%C are used. Beyond that, each device is calibrated during the manufacturing test process. You can find the specs at: https://reference.digilentinc.com/test-and-measurement/analog-discovery-2/specifications#arbitrary_waveform_generator

Hi @TheStumbler You could use the following custom interpreter:

Hi @TheStumbler There is no GPIB interpreter available. You could create a custom protocol decoder or use Bus and signals.

Hi @DShade It looks like the saved csv contains timestamp and data. The 2D should be processed in script to skip the timestamp. Or simply export the csv without timestamp.

Hi @joshva Have you installed the WaveForms application ? https://reference.digilentinc.com/reference/software/waveforms/start If it is not detected by the application, first try using the original USB cable or other cables you have at hand, try using other USB adaptor/HUB. Does the device show up in under System Information / Hardware / USB ? For more troubleshooting tips see the following post:

Hi @Federico Massimi Could you attach a screenshot?

Hi @MissingRedstone Please take a look at the following post.

Hi @Alejandro-Dev See: /usr/share/digilent/waveforms/samples/py

Hi @duckythescientist Install digilent.adept.runtime 2.22.1 and digilent.waveforms 3.16.28

Hi @Albert Terheide - delete DigilentFtdiDriver.kext from /Library/Extensions/ - disconnect device - Restart! the MacOS - reconnect the device The connection problems usually are caused by wrong cable contact, try another USB cable, try other socket, powered USB hub or auxiliary 5VDC power supply.

Hi @heretop It is added to the latest beta version: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Hi @Rolf_K It is fixed in the latest beta version: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Hi @enelson It is fixed in the latest beta version: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Hi @Orel56 It is not possible. It is recommended to use workspaces. You can also configure the unused DIOs to output a constant value 0,1,Z

Hi @Keith K This error indicates buffer overflow, samples are lost or corrupt. 1. There is a bug in WF 3.16.3 causing such false warning/error at low sample rate Try installing the latest beta version which fixes it: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ 2.a Try capturing lower number of samples (sampleRate X acquisitionTime), below 8192/channel to use simple acquisition instead of streaming/record 2.b In case you need long capture try reducing the sample rate, the recording should work at up to 1-2MHz

Hi @abadialali Please take a look at the AnalogOutIn_PlayRecord.py example found in the WaveForms SDK/ samples/ py

Hi @Alejandro-Dev The wiring may have been loose, contact issue...

Hi @enelson Thank you for the observation. It is fixed for the next software build. Edit: To overcome this problem with the current software set Oversampling to 1

Hi @abadialali 1. If the analog-in is triggered on analog-out, the analog-out should be started (FDwfAnalogOutConfigure) only after the analog-in is armed, otherwise this will miss the trigger. dwf.FDwfAnalogInTriggerSourceSet(hdwf, trigsrcAnalogOut1) dwf.FDwfAnalogInConfigure(hdwf, c_int(0), c_int(1)) wait(?) or verify analog-in state dwf.FDwfAnalogOutConfigure(hdwf, c_int(0), c_int(1)) 2. If you are generating a periodic signal the analog-in can be triggered by the detector on analog-in channel. The transition trigger will require setting the conditions, hysteresis, length. dwf.FDwfAnalogInTriggerSourceSet(hdwf, trigsrcDetectorAnalogIn) dwf.FDwfAnalogInTriggerTypeSet(hdwf, trigtypeEdge) dwf.FDwfAnalogInTriggerLevelSet(hdwf,c_double(0.0)) If you are capturing up to device buffer size of samples you can use the normal capture mode, acqmodeSingle. See the application Help, SDK examples and the manual pdf.

Hi @brandonsss The Analog Discovery Wavegen outputs have zero output impedance and current of 10-50mA. You have shorted the two outputs and the positive rail came out as winner. Use some series resistors like 1k to limit the current, W1->R->SC1+->R->W2

Hi @matt.casavecchia The record performs streaming so each FDwfDigitalInStatus/Record/Data returns a chunk of data. This lets you record unlimited number of samples. For low amount of samples, up to device buffer size 4/16k, you can use the normal acquisition.