attila

Hi @sib You should have: CS to Select, SCLK to Clock, MOSI to DQ0, MISO to DQ1 Pin-5 or 11 to GND and Pin-6 or 12 to V+ 3.3V The other interrupt pins and DQ2-3 are not required. You can find info about the Pmods at: https://reference.digilentinc.com/reference/pmod/pmodacl/start https://reference.digilentinc.com/reference/pmod/pmodacl2/start

On Digital Discovery the index for DIO-24 is 0, 25 is 1,... dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(1<<0)) # DIO-0 / DIO-24 dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(1<<1)) # DIO-1 / DIO-25 dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(1<<2)) # DIO-2 / DIO-26 dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(1<<3)) # DIO-3 / DIO-27 dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int((1<<0) | (1<<1) | (1<<2))) # DIO-0:2 / DIO-24:26

Hi @RAJEEVA You can find the examples and manual in the SDK folder: DigitalIO.py # enable output/mask on 8 LSB IO pins, from DIO 0 to 7, DIO 24 to 31 for Digital Discovery dwf.FDwfDigitalIOOutputEnableSet(hdwf, c_int(0x00FF)) # set value on enabled IO pins dwf.FDwfDigitalIOOutputSet(hdwf, c_int(0x0012))

Hi @sib You can find script examples in Protocol tool/ SPI-I2C Custom and Sensor tabs. You can also find SPI/I2C examples in the SDK:

Hi @caesun For such purpose you could use the OpenScope or OpenLogger: https://store.digilentinc.com/usb-scopes-instruments-circuits/

Hi @m72 Thank you for the observation. I managed to reproduce the issue. Until this gets solved, please use lower cursor numbers as reference.

Hi @juliosilva The devices can be used with single board computers (BeagleBone, RaspberryPi4...) using the ARM build of WaveForms. https://blog.digilentinc.com/analog-discovery-2-is-now-compatible-with-raspberry-pi-4/ The phones and table are not supported due to USB device driver.

Hi @PBritten The custom waveforms in Wavegen are stored in a the .Custom container to be able to reuse them in multiple Channels and different modes. Wavegen1.Custom.set("MyWave", arr) Wavegen1.Channel1.Custom.Type.text = "MyWave" Related posts: https://forum.digilentinc.com/search/?q=wavegen custom script&type=forums_topic&nodes=8

Hi @m72 After adding the Order option in Logic Analyzer (splitting the Input selection in two) I have forgotten to update the Protocol/Logic Analyzer to set the Order option automatically. Thank you for the observation, it is fixed for the next release.

Hi @m72 This looks like a digital issue in the ADC. Have you used for this tests the WF v3.11.23 I sent you in private message?

Hi @m72 You have in private message a software version which changes a bit the digital timings. Please install this, reconnect the device to make sure it will get reconfigured and start the application. Let me know if this solves the issue. The scope inputs are rated for up to +/-50V, but it should survive higher voltages due the 820k series resistor before the 7.5-20mA protection. High voltages (with energy) usually damage the gain selector analog switch, which leads to DC reading. https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual#scope_input_divider_and_gain_selection The attenuation option is intended to scale the scope readings, it is not a device feature. For instance when you use a 10x scope probe (9M series), the scope input will actually get 1/10 of voltage. Specifying 10x attenuation the software will multiply the readings by 10, to compensate this. You can also use this to reflect external voltage dividers, amplifiers... Edit: The calibration adjust the amplitude and offset.

Hi @m72 This may look like a digital issue, from ADC to FPGA... but i don't it is since we should see similar glitch on the upper side too. Could you provide detail about the experiment? I see you have set 10x probe... Are you using (single ended) BNC probe at 10x ? In case you are using differential input with high common mode voltage, the signal might enter in limitation or clamping starts to act, which also depends on the offset: https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual?redirect=1#scope_driver https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual?redirect=1#scope_signal_scaling The highlighted "noise band" indicates high frequency signals (noise, glitch), above current sampling rate, which indicates some analog issue:

Hi @eos33 I have added HDMI CEC interpreter to the latest WF beta build: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

Hi @m72 The 24 refers to the digital input lines.

Hi @m72 The 1kHz is generated from the 100MHz system clock with 50% duty. The 1.1kHz is actually generated as 1.099989kHz with 49.9945% duty. Due to this the 180* phase, the middle falls in low level which gets used as initial value. For the next release I have modified the duty to round up, so the 1.1kHz will have 50.005499945% duty and the 180* phase will start high. I'm also adding negative delay for the next version. Thank you for the observation. Current version: Next version:

Hi @m72 The preview is further fixed. I hope there are no more issues with this: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ Here you have the project: EMU_2CH_EACH_V10 (2).dwf3work

Hi @m72 The B, C and the preview for pulse are fixed, modified to have shared workspace list: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ Thank you for the observations.

Hi @m72 The pulse preview is not correct. I will look into this. Thank you for the observations. You could use a custom bus or signals to easily create/modify such patterns.

Hi @KeithRussell Good to hear you managed to fix it.

Hi @m72 I have fixed the "pit top" for next version. I was unable to reproduce the crash. If you add multiple interpreters (Bus,I2C,SPI,UART...) it will use more memory and process the capture slower... The DD ram is 4Gbit (256MB). With 8 bit sampling (input: 800MHz x8) you can capture in ram 256M samples, with 16 bit (400MHz x16) 128M, with 32 bit (100-200MHz x32) 64M (67108864). At lower rate you can capture up to 100Mi samples. In this case the data is streamed over USB, which could lead to sample lost due to congestion.

Hi @KeithRussell The scope inputs of AD2 are rated to +/-50V. On your device probably the ADG612 analog switch got damaged: https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual#scope_input_divider_and_gain_selection

Hi @m72 Thank you for the observation and sorry for this. It is fixed in the latest version: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ I just notice that certain frequencies cause PLL not locked error. In this case select "Force Programming". I have to look exactly what synthesizer settings or PLL reset sequences lead to such problems.

Hi @JColvin @rprr It looks like all the USB 2/3 ports of RPi4B are working reliably with AD2. I have updated the post:

Hi @Grimmers The Raspberry Pi 4 Model B is working well with the Analog Discovery 2 when connected to the USB 3 (blue) ports. It was running continuously for more than 24 hours. The connection to the device over the USB 2 (black) ports dropped after 6-12 hours. It looks like the problem was caused by the external USB hub. After connecting the AD2 directly to RPi4B USB 2.0 port it is working since 2 days.

Hi @Andras A. Comparing two different tools might not be the best option, it could give different results. B. At the moment the Impedance Analyzer interface takes control over the Supplies and DIO lines to control the IA Adapter. On the Adapter the negative supply and some DIO lines are unused. In the next software version I will add option to be able to control these. Having these you could use a small signal relay with ~5V control, similar to the ones on IA adapter but non-latching, to switch between the measured and control DUTs. https://reference.digilentinc.com/_media/reference/instrumentation/analog_discovery_impedance_analyzer_sch.pdf Edit: You could use the current software for plan B. First, in the Impedance interface using the Adapter option select the needed resistor value, then select "W1-C1-DUT...". This will release the Supplies and DIO lines to be used from other interfaces, and the latching relays on the Adapter will remain unchanged. Then you can use the Static IO or Negative supply for other purposes, to control the external relay...