attila

Hi @LarsB In the Logic Analyzer lines are used to connect sample points. These will be oblique at high zoom levels or when time base /div is comparable to sampling period, this to indicate uncertainly between sample points.

Hi @Kurt Blum Yes, using Source: External option.

Hi @joeck The FDwfDigitalIn-TriggerSet, ResetSet, LengthSet, CountSet and MatchSet, configure the trigger detector on digital signals. Like edge, pulse length, counter or patterns on UART, SPI, I2C.... protocols. For record mode, the FDwfDigitalInTrigger-PrefillSet and PositionSet specify the pre-trigger (at least how many samples to collect before looking for trigger event) and post-trigger (how many samples to collect after the trigger). From samples/py/DigitalIn_Record.py : # number of samples after trigger dwf.FDwfDigitalInTriggerPositionSet(hdwf, c_int(int(nSamples/2))) # trigger in the middle # number of samples before trigger dwf.FDwfDigitalInTriggerPrefillSet(hdwf, c_int(nSamples-int(nSamples/2))) I don't have a full overview on what you want to measure but you could use the pulse condition in your data processing, filter the data after capture.

Hi @Kurt Henry Did the device and your circuit have a common ground ? Without proper grounding there could be high voltage differences that could damage the device/circuits. According the discussion with the team, it would be complicated to troubleshoot, so please go for replacement.

Hi @J.J. There is no function exposed to add channel/signal. The Script together with the instruments can be saved in the workspaces so the entire setup can be reloaded.

Hi @mnorth The AnalogOut_sin.py generates signal on W1 and the AnalogIn_Record.py streams data from scope input 1+/-

Hi @Zapp The force reprogramming only reprograms the device fpga, which is otherwise automatically done when needed: first connection, version change or configuration selection change. You could try the latest software version: You could try to reprogram the USB controller EEPROM. In WaveForms / Device Manager under gear after Remote, select "Prog AD1,2...", press Find and in case you have multiple FTDI devices connected make sure the proper Device is selected, if AD2 Product is automatically select than it is ok. On some devices the C/D port configuration may be different which could cause communication errors. Press Program to make sure all bits are correctly set.

Hi @Jim_G You should have gotten response to your support email in ADP3450 topic. We suppose you've tried to cycle the board power. You could try to load the factory calibration or reset to zero under WaveForms/Device manager/Calibrate/Reset. The values should be small like in the picture. You could also try the latest version from here: https://forum.digilent.com/topic/8908-waveforms-beta-download/ and starting it in WaveForms in Safe Mode, to prevent loading of application/device options, recent files... If these don't help the oscilloscope ADC driver, offset or reference circuit is probably damaged. Do you know what was the last experiment the device was used? Could you describe the setup, tested component/circuit ? I don't remember seeing such failure with ADP3X50 but high voltages could damage the device like I've heard AD2's damaged by piezo electric experiment with 100s-1000s V On ADP3X50 each scope input has a ADA4817-2ACPZ next to the upper relays IC3,9,15,31 This is the first IC in the input path so probably these are damaged. On AD2 probably the ADG612 is damaged, see: For other problems see:

Hi @Kou Yes, you could use nilcicapi.dll installed by VirtualBench or the rebranded dadp5capi.dll installed by WaveForms. C:\Users\Public\Documents\National Instruments\VirtualBench Documentation\ The C API is the same.

Hi @Zapp It could be a cable contact issue, try using the original USB cable of the device or other cables you have at hand. Check the "Disable the current limitation..." or set USB Limit option to Maximum. Select Always ON for USB Power option. Sometimes the unpowered auxiliary supply power monitor can mess up the i2c communication with the usb power monitor, causing too high or low current/voltage reading. With the earlier two options (Max/ON) such misreading won't cause disconnect.

Hi @J.J. For Digital Discovery the system frequency can be adjusted in the Supplies tool.

Hi @Chazzo These numbers are for the worst case but the typical should be much better. 1. +/-10mV offset error +/- 0.5% of actual value, like for 1V it can be from 0.985V to 1.015V 2. common-mode input voltage 4. common-mode rejection (ratio) https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide

Hi @Icarus The FDwfDigitalInAcquisitionModeInfo is not yet utilized, it only returns (1<<acqmodeSingle)|(1<<acqmodeScanShift)|(1<<acqmodeScanShift) The next sw version will return valid info based on device capabilities, FDwfAnalogIn/DigitalInAcquisitionModeInfo

Hi @milu In Logic Analyzer set higher sample rate, more than double of the I2C frequency. The Errors in Protocol/I2C/Spy are probably due noisy signals, ringing or crosstalk: - make sure to have proper ground connection connection between the devices - twist the SCL/SDA wires with ground to provide some signals isolation - check the FreqFilter option, to filter out ringing - inspect the signals in Logic Analyzer with high (100MHz) sample rate In newer software version you can find Slave option in Protocol/I2C.

Hi @DroneGuru See the reply on your earlier post in the same topic: Are you using the latest version 3.18.30 (as today) ? Are you using the Standard mode with DDR buffering allowing 128Mi samples @ 125MHz or the Linux mode with limited rate ?

Hi @Kou You are looking at the AnalogIO_AnalogDiscovery2_Power.py example which is for Analog Discovery 2 as the file name suggests. See the following for ADP5250: AnalogIO_ADP5250_Power.py

Hi @latot It is safe but not recommended. The device won't be damaged but it is never recommended to push anything to the limits. The AWG output should be used as a voltage source up to 10mA. The protection PTC will heat up in considerable time, milli... seconds..., the output current will gradually drop and slightly depend on the ambient temperature. If the predictable current is important for your use-case use at least a limiting resistor.

Hi @mkj I don't understand exactly what you want to measure but you can use custom math channels, custom measurement, custom logging view... Script tool in WaveForms application, all with javascript or custom application/script using the WF SDK. See the Help of the application and examples in the specific editors.

Hi @Greg McDaniel Yes, the oscilloscope, awg channels, digital pattern generator and logic analyzer can run in parallel, generate and capture signals at the same time. The Analog Discovery 2, ADP3X40, Digital Discovery... (except ADP5250) have streaming play and record option if you are interested in this.

Hi @Kou For ADP5250 supplies set current limit too.

Hi @shirogeek With probes for AD2+BNCAdapter make sure it can be compensated to at least 45pF. If you are building custom probe watch out for the component voltage ratings. Take care

Hi @AlexanderGDean This crosstalk could between the wires which act as antennas. This could be highly reduced by shielded cables but twisted wires also help a lot. Twist the positive and negative scope inputs together and for single ended usage connect the negative to the ground near the test point; twist each of the used digital, trigger, wavegen and supply wire with ground.

Hi @kdonoghue The AUX monitors the 5VDC supply of the AD2.

Hi @latot There should be one ground, the external circuit/device GND should be the same as the AD2 GND and this is connected to the computer via the USB cable. The Wavegen output is protected for shorting it the ground, to the other Wavegen or to the device's +/-5V supplies. I've just measured the short to ground current of +55mA and -45mA, with slightly higher peak (~65mA) until the PTC kicks in.