attila

Well, I've seen enough to submit my order!  ?  Thanks again.

@attila I'll try out your suggestions and experiment more during this week. Thanks for the help so far! :) 

Hi @FrankS
Use one oscilloscope channel to capture the filter/DUT input (Wavegen output) and the other one for the filter output, as it is used in Network or Impedance Analyzer.
Emulating the Wavegen output or sampling DAC data is not supported since these may not be precise and could be misleading. The signal can be attenuated, distorted due to current limitation, at high frequency the DAC and output latency could be significant...

I just found out the cause of failure. Please see the picture. Yello : C217, Blue : D7, Anode. The anode waveform seems to be ok. It comes switching. However, AVCCC-5V is wrong. And I checked L5. L5 is completely opened. L5 might be damaged. It should be replacement. I would like to say "Thank you for your help."
 

Many thanks.

Hi @AML
You could use a Script like this to automate analysis and export:

for(var i = 0; i < 100 & wait(1.5); i++){ // wait 1.5 seconds Impedance.single() // start if(!Impedance.wait()) throw "Stopped" // wait to finish print(i) Impedance.Export("~/Desktop/imp/"+i+".csv") // see Help/Script and Impedance/File/Export for more info }  
If you are interested only for measurements at a specific frequency: set Constant frequency, specify required Steps and rate using the Settle under Options (or use Averaging).

Thank you Attila.
Sean

Hey attila, 

thanks, it worked now! 

Hi Attila,
Thank you for the link. I was concerned that the USB functionality might not be supported in WSL.
Sean

Hi @MikeWatson
The difference I notice is that in the WF app the sampling rate is 80kHz and in you app 50kHz.
The 5V glitch may be filtered out by the lower rate average sampling.
Also notice the noise band. This is a simultaneous lower rate capture of min/max samples.
It indicates that you have higher frequency components between 4.6-5.2V and glitches down to ~2.5V and up to ?7V.
Depending in the sampling rate, the 5V trigger may capture at these higher frequency components.
1. Use the same sampling rate.
2. Try using the decimate filter for the trigger detector. This will look at the raw 100MHz samples rather than the default averaged samples at specified sampling rate.
FDwfAnalogInTriggerFilterSet(hdwf, filterDecimate)
Set the trigger level to at least 5.5V

Yes! That solved my problem!
Thank you for fast response!
Best Regards,
Tood
 

Hi @Alejandro-Dev
Not implicitly supported.
It could be implemented using Pattern Generator ROM Logic but this would be a bit tricky work.
 

Hi @ajsb85
SPI master and spy/analyzer is supported.
See the following post:
 

Hi @edwardjs
If you are using the Logic Analyzer:
- If you are using Digital Discovery you can capture up to 256M samples at up to 800MHz
- With Analog Discovery you could record 100M samples at up to about 1MHz or using compression for burst at higher rate.
With the Protocol tool SPI/Spy you can log data at similar rates.

Hi @m72
Thank you for the feedback.
I will add more ticks and labels in the next version.

Hi @BDS
In Sync mode the Rate is only used for representation.
If the frequency of the Clock signal is specified correctly the time representation will be correct.

Hi @hugocoolens
I don't know from which instrument you want to export.
Like in Network Analyzer uncheck Magnitude and leave Phase, File/Export or Channel2 gear/Export, uncheck unneeded Options


 
You could also use a Script for custom file saves, like:

Hi @hugocoolens
The next software version will use phase wrapping according to the offset in Export and Script access too.

Hi @hugocoolens
Yes, see the latest beta version:
 

Hello again @attila
I just wanted to let you know that I have not seen this issue since I updated to the beta, you linked to. Thank you very much!
NT

@attila Thank you

Thank you Attila. I will explore the Waveforms API with a dedicated SBC as an option for my application.
Sean

Thank you Attila.
Sean

Hi Attila 
This fixed the case now the I2C part of the library works. 
Below are the updated and working drivers.
Best wishes & friendly greetings
SIB 
Digilent_AD2_Script_I2C_control_of_on-semi_CAT9532.dwf3work Digilent_AD2_Script_I2C_control_of_on-semi_CAT9532.js Digilent_AD2_Script_master.js

Hi @kang
Simply use one of the trigger IOs.
dwf.FDwfAnalogInTriggerSourceSet(hdwf, trigsrcExternal1)
and if you want to specify the edge: rising, falling or either:
dwf.FDwfAnalogInTriggerConditionSet(hdwf, DwfTriggerSlopeFall)