attila

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.

Hi @DroneGuru It refers to the FPGA buffer. With DDR buffering make sure not to exceed the following limits for 1, 2 or 3/4 enabled channels. Above 128Mi samples the rate will be limited by the USB or Ethernet, around 4MS/s depending on the system, network... In the newer software version some recording issues are fixed: The installed pdf manual in the SDK folder in newer than the online variant and corresponds to the used software version:

Hi @latot The output impedance is zero because the PTC (fig19 R145) is in the feedback of the output amplifier: https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide#awg_out

Hi @DroneGuru The schematics are not public but here you can find a detailed description of AD2: https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide

Hi @Paul45011 Such trigger sequencing is not supported but it could be done with software validation. With a setup and Script like this: Logic.run(); while(Logic.wait()){// exit on Stop var data = Logic.Channels.Bus.data; if(data[data.length-1] != 0){ // last sample not zero print("last Bus sample not zero"); break; } } or with conditional export: if(Index > Maximum) return; var data = Logic.Channels.Bus.data; if(data[data.length-1] == 0) return; // do not save Logic.Export("~/Desktop/logic/acq"+Index+".png"); Logic.Export("~/Desktop/logic/acq"+Index+".csv", "Raw Data"); Index++;

Hi @Tamires The analog-in-record should work at up to 1-2MHz and digital-in-record around 2MHz but it depends on the system. The sync rate is specified by the external clock rate. See the earlier post:

Hi @latot It is safe to connect Wavegen outputs to Scope inputs. The Wavegen outputs have zero output impedance, drive of 10-50mA, at least 10mA at +/-5V and ~50mA around 0V. Have short protection between +/-5V but it is not recommended for long period of time since heat will be generated. The Scope inputs are rated to +/-50V. https://digilent.com/reference/test-and-measurement/analog-discovery-2/start

Hi @DroneGuru That is the noise band, see the following post: You may want to set the sampling rate to maximum or to the frequency you want to use it. At lower rates by default the samples are averaged. It can be changed under channels gear-dropdown. To see internal noise short the scope P/N inputs. Yes, there are various internal rails and buck-boost for user supplies, see: https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide

To verify the supply earth-ground connection, disconnect this from the socket and computer, use a multimeter to measure continuity or resistance between the earth contact and ground output.

Hi @Getz Instead of Demo device you could connect to Sound Card. The next software version will not display warnings/tips for tabs where data is imported.

Hi @Chazzo Such measurement can be performed with SDK starting from DigitalIn_Acquisition/Record/Scan....py examples. To connect 'slow' signals to the 0/3.3V DIOs you could use voltage divider with resistors. For such voltage and since you only need two signals you could use the Scope/AnalogIn.

Hi @latot You are seeing this behavior because your laptop supply does not have ground connection.

Hi @bremenpl The state option is available in newer software version:

Hi @dmeichle I'm not familiar with pydwf but you can find the WF SDK with many examples here: and the latest sw version is here:

Hi @bremenpl Set the Frequency to maximum, 100MHz. You have set it to 100mHz and with this the delay be up to 10sec.

Hi @longboard The AD2 has a common ground and the separation is only on the BNC Adapter.

Hi @bremenpl You could use a Script which at each run toggles the value: StaticIO.Channel0.DIO0.value = !StaticIO.Channel0.DIO0.value; StaticIO.Channel0.DIO1.value = !StaticIO.Channel0.DIO0.value; StaticIO.config() You could also use ROM logic. Like here DIO 0 is controlled by StaticIO (or externally) and DIO 1 by the Patterns ROM logic based on DIO 0 value, with 70ns delay.

Hi @Olivier Gombert 1. Launch the installer from admin command prompt otherwise the installer will ask for admin rights. 2. To overcome the driver installation ("Windows Security/device software") confirmation, add the certificate to the system before launching the installer with the following command: CertUtil -addstore TrustedPublisher nic.cer This nic.cer is the exported certificate from the certmr.msc

Hi @Paul45011 The input logic threshold can be adjusted in the Supplies tool. You could test it by connecting DIO to DIN line, generate signal with Pattern Generator on DIO and capture it with Logic Analyzer on DIN line.

Hi @mturner The averaging or oversampling requires stable trigger and periodic signal so consequent captures are averaged and phased correctly. In your screenshot it looks like it identified a periodicity of 297kHz and phases the signal according to this. Notice the "Channel range will be extended" indicating that with such offset value the high vertical range is used. You may consider using the AC coupling. The noise capture can be disabled under Time/Options or showing disable for each channel individually under the Channel's gear menu.

Hi @johannsi99 The record streams data over USB which limits the sample rate to about 1-2MHz. Use the default (single) acquisition mode to capture up to device buffer (8-16Ki) samples at up to maximum sample rate (100MHz).

Hi @Tamires The sustainable stream rate depends on the available USB, CPU, storage... bandwidth. To prevent or reduce chance of device buffer overflow: - use the 2nd device configuration to have mode scope buffer - connect the device directly to the computer, avoid hub with multiple devices connected that share the USB bw - close unnecessary applications, services that could block the system - store at lower resolution 64, 32 or 16 bit and avoid text format, to reduce storage size The 'corrupted' samples indicates that buffer over flow could have occurred, when two consecutive chunks exceed the device buffer size. This is uncertain but it could be a buffer overwrite. The record length can be set to unlimited (-1) and stopped from script, like it is implemented in the record py example loop. Here I've used the Rec option in the WF app with AD2 and passed 300M samples at 1 MHz for 2 channels storing samples as double without any issue. This is similar to the the py record examples just easier to use.