attila

Hi @modmix I'm not sure if it is true but Windows Defender identifies it as threat! The AD1 and AD2 hardware are very similar. The API is identical. The only differences are in the power supplies configuration where AD2 voltages can be adjusted and user supplies vs auxiliary supply monitoring. The "Impedance Analyzer"/"Audio Analyzer Suite" software should work with AD2 if the creator would allow connecting to it. For this he only needs to accept the ID of AD2 like it does for AD1.

It is not possible. On the BNC adapter the Scope and AWG channels are available only through the BNC connectors. On the other side of the adapter the GND, Supplies, Trigger and Digital lines are available. You could create impedance analyzer circuit with fixed reference resistor, like it is shown in the Help.

Szia @Andras The quick measure and cursor position used only frequency value which was useless in constant frequency mode, zero range. The updated software uses percentage unit for x axis in this corner case: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Szia @Andras For this you don't necessarily need a script. In the interface you can set constant frequency (Start = Stop), specify a long Settle time and press Single. Like the following will run for 50 minutes, 100 samples at about 2/min rate, 30s + a few milliseconds due software processing.

Hi @makk The ferrites are probably good. Most likely the USB pins are not making contact or the PCB trace is broken. Here you can find the layout and more info:

Hi @m72 Thank you for the observation. I have fixed this display glitch with large amount of samples and constant SPI data, for the next software release. PS: You can use the Events view to pinpoint words/bytes/events and double-click in this list will navigate the waveform (change time position) to be visible.

Hi @Grimmers Thank you for the detailed information. The failure on USB 2 port is similar to the ones received on previous RPi B models, "Communication error... ERC 0x02" which indicates reading/IN timeout, loss of data in device to host transfers. On previous version the data was more often corruptly received, resulting wrong device status reading, voltage, current... Lets hope the USB 3 port will be reliable.

Szia @Andras I don't know. With RPI 1B+, 2B, 3B, 3B+ the problem could be related to the 4xUSB hub or its driver. According the reports it is working with model A which has a different USB circuit, as well with other ARM boards. I hope we will be able to order a 4 B soon to test it.

Hi @m72 The preview will represent such corner cases correctly in the next software release. Thank you for the observation.

Hi @m72 It will be added to the next software. Thank you for the observation. In case you need it, you can also use the Scope in mixed mode, having Digital/Logic Analyzer channels in the same interface:

Szia @Andras This is a completely different library than the one provided by the FTDI. In order to use this the Adept Runtime would need to be modified. On the other hand I don't see in this lib support for the FIFO data transfer mode nor the MPSSE used by AD, so it is unusable for this purpose.

Hi @zaxxon @malexander That error log is not an error. It is generated when dinfoFWVERRom is called during the device enumeration process in the DWF library. For Analog Discovery this is not used, it is ignored even if it fails. In the above output the device is detected by the DWF library so it should be also detected by the WF application.

Hi @jagjordi The I2C Spy is supported by the software bot not the slave operation mode.

Hi @fonak 1. A opens a dialog with several options and B is for quick compensation and enable. 2. The compensation is performed at constant amplitude and the collected data is used also in CC/CV mode. 3. Input gain, angle, voltage and current are not compensated. The other are compensated: phase, impedance, inductance, capacitance, factors.... 4. You can specify average in number of measurements and averaging time for each step. The step is complete when both the number and time are satisfied. Each measurement contains by default at least 16 stimulus periods. 5. time domain data -> Goertzel -> circuit model (C1/C2 or (C1-C2)/C2 or C2/(C1-C2)) -> compensation -> sqrt(Rs^2+Xs^2) and atan(Xs,Rs) Let me know if you need more info

Hi @Jaye Here you can find the supported systems: https://reference.digilentinc.com/waveforms3

I thank you for the ideas and observations.

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.

Hi @fonak I thank you for the ideas. I plan to add CV/CC mode which will require auto resistor switching on wider frequency range, mentioned by @kojak

Hi @zaxxon Could you confirm that you don't have the /Library/Extensions/ DigilentFtdiDriver.kext? If you have it, please delete this kext.

I'm using Macbook with powered USB hub and never had such problem. @malexander have you seen such problem?

Hi @Cleber Borges The principle of measuring the gain/phase in NA and input gain/phase in IA is the same, except that the NA shows C2/C1 and IA C1/C2. In the Network Analyzer FFT is used since it has option of using external signal generator and spectrum analysis (THD, THD+N, HD2, HD3... plots) In the Impedance Analyzer Goertzel filter is used since the frequency is known, always generated by the AWG of the same device. The input gain and input phase are raw values (C1/C2) the further measurements (impedance, admittance, phase...) take in account the scope probe impedance and open/short compensation.

Hi @Cleber Borges 1-2. The Network Analyzer is intended to characterize transfer function of amplifiers/filters (C2/C1) mainly in form of magnitude and phase, Bode magnitude/phase, Nichols, Nyquist plots. It has custom scriptable plots that can be used for impedance analysis too. This was added before implementing the IA interface. The Impedance Analyzer goes further in calculations, it is intended to characterize elements (circuits, components, materials) in complex form like real and imaginary part, resistance and reactance, capacitance and dissipation, inductance and quality. The IA takes in account the scope probe impedance, the value of this can be comparable to the measured element at high impedance and high frequency; open and short compensation; DUT = like R*|C1/C2|- |RC2|- |Open|- |Short| 3. The NA performs FFT on C1, C2 and gives the magnitude for C1 as C1/Set_Amplitude, for the other channels as C#/C1 and phase C#-C1. 4. I'm not sure if understand correctly, but if you close the circuit without resistor basically you short the C2 to ground... The IA needs a resistor for current limitation and reference.

Hi @jostikas Yes. The calibration parameters are stored in the device eeprom. Which WaveForms version are you using? The output voltage might be low, close to zero because of current limitation. In case this is wrongly calibrated, you might set in the interface 212mA but the actual limitation might be 0mA. 1. Reconnect the 12V power supply for the board to make sure it is reset. 2. Under WaveForms/Settings/Device Manager/Calibrate/Reset/ you can Load the factory calibration. 3. The parameter table should contain values like in the picture. 3. Here you can also recalibrate the needed parts by clicking on the links in the "Calibrate" list, like Positive Power Supply Current & Ammeter, and follow the instructions.

Hi @jostikas I don't see any problem with the project. On workspace save or load all the instruments are stopped, including the power supplies for which the stop means turn off.

Hi @fonak 1. The measurement list is growing, I will have to add option to add/remove items in measurements mode. 2. Rdc: I'm not sure how to fit this in the existing interface which doing AC measurements. Will this DC measurement require a new operation mode? Thank you for the suggestions.