attila

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.

Hi @heretop I've added for the next software build 24bit format option but I don't think this will solve the problem you have. In the 32bit format the 24 effective bits should fit well. You could use the Time and FFT Views to investigate the signals like this:

Hi @heretop The fluctuations may be caused by the audio amplifier auto gain. Try disabling it if you have such option in the sound card configuration. Use the 32bit sampling since this fits the 24bits. The other options are just in case there is some compatibility issue. You could try using higher Settle time in Network Options, to see if this makes any improvement. The audio stream latency may vary from systems to system. See the related post:

Hi @Alejandro-Dev Yes, indices 0/1 on Digital Discovery are DIO-24/25

Hi @enelson I think you are referring to the noise band. Beside normal samples a smaller amount of noise (min/max) values are stored. This, to indicate glitches or higher frequency components that would be otherwise hidden by normal sampling. This can be disabled individually under each channel option (gear) or under Option dropdown.

Hi @abadialali It is working with the latest beta version: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Hi @matt.casavecchia You can use the Tool.exec or .start functions to launch an external application, see the Help in the app You can also use the WF SDK/API and for linking use -ldwf, see the manual and examples

Hi @Rolf_K It is fixed for the next build. Thank you for the observation. Edit: In the current software version when custom measurement is added the internal storage key is not updated, so this won't be saved properly. To overcome this perform a reordering (drag in row header) or add a defined measurement after adding custom(s).

Hi @Alejandro-Dev See the earlier mentioned SDK manual pdf

Hi @JuanCar You could use the Window trigger in Scope to detect enter or exit in range. For qualifier you could use some scripting in the Script tool or in the Scope/ View/ Logging/ Script.

Hi @mmachtey 1. The low/high warning are shown where the reference resistor and DUT impedance are different by magnitudes, so the result resolution/accuracy may be low. Try reducing the rms voltage value. 2,4. The Constant Voltage/Current implementations are similar to examples, see pic below. 3. The function is for the open/short compensation. https://forum.digilentinc.com/topic/21746-discovery-2-impedance-measurement-and-compensation-issues/?do=findComment&comment=62830

For the record, here is the same post with answers:

Hi @Albert Terheide The emulated driver is working on Mac mini M1 so it should also work on Air M1.

Hi @Albert Terheide I don't know how much power can this laptop provide. On earlier Air the USB A on one side was limited in power. The USB types/versions are (or should be) compatible. It should work with USB hub or direct connection, if you can find C to micro cable or adapter. If you get error on connection or during usage try powered hub or docking station.

Hi @Albert Terheide Yes, it should work. You can try the WaveForms application in demo mode if you don't have AD2. At the moment WF app is working in emulated mode on M1. Apple provides Rosetta 2 to be compatible with applications compiled for Intel architecture. We've tested this on Mac mini M1 and had no complain about the performance. The low level driver and software for M1 architecture is ready but the high level libraries are not yet available for M1. Due to this external dependency I don't know when we have native M1 build but hope it will be soon.

Hi @BryanS I've just tested enumeration and connecting sequentially to one device with different users, it is working under Ubuntu 16 but not with 20. @malexander Could you help in this? Edit: With second user getting ERC 3090 on DmgrEnumDevicesEx

Hi @Morgan MONROE On the IA adapter the contacts are Scope1&2 like in the following setup. You can find the reference manual and schematic at: https://reference.digilentinc.com/add-ons/impedance-analyzer/start The compensation is Zdut = Zopen*(Zshort-Zmeas)/(Zmeas-Zopen) The open/short compensation may not remove the addition capacitance added by the chamber/wiring. You may try to adjust the ProbeCap under Option dropdown to have a flat response. This, with Auto option for AD2 w Adapter is 43pF.

Hi @nburkitt It is not yet supported.

Hi @duckythescientist Thank you for the observation, it is fixed for the next build.

Hi @dpalma Copy the dwfconstants.py next to your script. This file is in the WF SDK python examples folder.

Hi @rbt You can use the following: fs = c_uint64() dwf.FDwfDigitalIOStatus(hdwf) dwf.FDwfDigitalIOInputStatus(hdwf, byref(fs)) print("Digital IO Pins: ", bin(fs.value&0xFFFF)[2:].zfill(16)) print("Digital IN Pins: ", bin(fs.value>>16)[2:].zfill(24)) Digital IO Pins: 0000000000010010 Digital IN Pins: 000000000000000000000001

Hi @Sangkyu Choi Have you adjusted the channel vertical range? like: dwf.FDwfAnalogInChannelRangeSet(hdwf, c_int(0), c_double(5)) By default the 50V pk2pk range is used which has lower resolution.

Hi @M Eckerson The sample rate can be positive integer divisions of the base frequency, which is 100MHz on Analog Discovery.

Hi @Sangkyu Choi The sample rate is probably different and regarding the noise band see the following post:

Hi @kashyap At 13MHz the reference signal (W1) drops 6dB, half of the amplitude which should be fine for such relative measurements.