attila

Hi @Hamza Oncuer
The WaveForms application uses the same API, so the device should be detected with custom application as well.
Try using the FDwfEnum function or the FDwfDeviceOpenEx with fixed IP.
Eventually using the DmgrSetNetworkEnumTimeout from Adept Runtime to adjust the network timeout. The WF application sets this to 100ms for auto enumeration and 1s when the 'manual' button is used.

 

Hi @Anthocyanina
Unfortunately such option won't be available with AD2 since the device FPGA is already fully utilized, eventually for other/newer devices.
Thank you for your post.

Hi @Anthocyanina
Unfortunately such option won't be available with AD2 since the device FPGA is already fully utilized, eventually for other/newer devices.
Thank you for your post.

Hi @ysrevol
The DIOs are multiplexed in the device StaticIO having priority over the Patterns.
A DIO output will be 0 or 1 if this is configured in StaticIO. If here it is set to Z then the Pattern Generator will control this DIO.

Hi @ysrevol
The DIO levels can be verified by polling but you could use the ROM logic for in-device loopback/control.
 

Hi @Ricky
Sure, pic 1
With the 6th device configuration the supplies can also be used as slow AWGs, pic 2

Hi @ysrevol
1. For AD2 in WF app/ Settings/ Device Manager select 6th device configuration.
2. The 3.19. was release candidate but it is pushed to the next year. The latest beta version can be found at:
 

Hi @engi
Multiple register pipeline stages to align compensate the IO delays, the capture buffer split, multiplexed...
I'm working-researching something like these for a future device. Here generating square on W1 (also captured on C5), wired to C1, filtered in the device (captured on C3) and output on W2 (also captured on C6), but it will take some time to reach the market.

Hi @engi
The WaveForms application has a demo like sound card support.

Hi @Rolf_K
I don't know exactly how do you want to measure it but with Spectrum you can use the Logging view or Script like this:


Spectrum.run(); while(wait()){ var hz = Spectrum.Trace1.frequency; var mag = Spectrum.Trace1.magnitude; var c = hz.length; for(var i = 3; i < c; i++){ // 3 to skip DC if(hz[i]<500 && mag[i]<0.5) continue; if(hz[i]<150e3 && mag[i]<0.2) continue; if(hz[i]<500e3 && mag[i]<0.15) continue; if(mag[i]<0.1) continue; Spectrum.stop(); } }  

Hi @miv2k
Triggers are not working in Demo mode.

Thanks a lot, Attila!

Hi @attila
thanks for your help.
Now it works.

Hi @fonak
The CC/CV mode was added to WF beta 3.10.3
https://forum.digilentinc.com/topic/8908-waveforms-beta-download/
 
You can find the schematic of IA Adapter here:
https://reference.digilentinc.com/reference/add-ons/impedance-analyzer/start
Currently you can make lock-in amplifier like this:
 
Impedance
1. Thanks for reminding. I wanted to add offset compensation for DC, just got distracted with other projects.
2. At the moment you can use a script for history like this:

Impedance.run() // use averaging to control the sample rate Impedance.Frequency.Averaging.value = 0.2 plot1.X.AutoScale.checked = false var rg = [] while(true){ if(!Impedance.wait()) break rg.push(Impedance.Traces.Trace.getData("Impedance")[0]) if(rg.length>50) rg = rg.slice(1) // max length plot1.Y1.data = rg plot1.X.Range.value = rg.length plot1.X.Offset.value = -rg.length/2 }  
Power
1. With AD2 6th device configuration you can use the power supplies as AWG
With EExplorer board you can use voltage or current AWG.



2, 3 Ok
4. You can use F5/F6 to start/stop an instrument.
5. The AD/AD2 has no voltage or current readback.
On the EExplorer board you can adjust the voltage/current limit and also have voltage/current readback.
Protocol Logic
1. You can use script, similar to the previous IA
In the Logic analyzer increasing the row height you get analog representation for the bus, interpreted values

2. You have I2C scanner in Protocol/I2C/Custom/examples

Other
1. You can export and import data into Scope, Spectrum, Logic Analyzer...
2. Ok. 
Thank you for your suggestions.

thank you @attila for the great help,

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 @Himayala1
It could be...
Could you attach some screenshots or WaveForms workspaces with data ?

thank you!

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 @Sangkyu Choi
You could use 5VDC auxiliary supply for the device.

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 @rim
 

Hi @rim
Thank you for the observation. It will be fixed soon.

Hi @rim
This seems to be a bug in the underlying libraries, Qt5.12, when 3D plots are above each other.
It is solved in Qt5.15 and this will be used in the next installer if all other things work correctly.
Thank you for the observation.