attila

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...

Hi @m72 In this high resolution capture it looks like SDA is rising while SCL is still high. To overcome such situations lower the sample Rate, to 100MHz or lower. This way it will likely capture SDA and SCL change at the same time, which should be interpreted correctly. Note that the setup time for Stop condition is no respected:

Szia @Andras The WaveForms Sound Card option is solution for free... in case the audio IO limitations are suitable for the requirements. Here some IA measurements are compared between AD2 and Sound Card:

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.