[ADP3450 Communication Faults on USB after time]

Hi @David Wells

I'm glad it's working now.

I still think it was a USB cable contact problem on the computer side. The ADP3X50 does not require USB power, it uses less than 1mA for host detection.

[DD Manchester Hex display]

Hi @yattr

Configure the capture to cover the required time by adjusting Samples and Rate in the top-right.

[Logic Analyzer: 1-Wire Custom Script]

Hi @Empower

Could you provide more detail on this 'custom' 1-wire ? like a spec sheet 

[Recording at 400 MHz for more than 1 second]

Hi @bodevalley

With Digital Discovery you can use the Repeated mode (acqmodeSingle) to capture up to 256Mi samples at up to 800MHz on 8 inputs.

[Digital Discovery to collect 16 bit SPI data - multiple slaves with same CS, CLK, MOSI and individual MISO]

Hi @Shalin

You can generate custom pattern with the Pattern Generator and add custom interpreter in Logic Analyzer, but the existing I2C interpreter may also be suitable.
I'll try to implement I3C support later, but unfortunately cannot give you a deadline for this.

[Waveforms Spectrum Multiple Issues with Noise Density]

Hi @DTM_RD3

The next version will add Math to Spectrum.

[Acquire multiple triggers with ADP3450]

Hi @JerryM

Deep capture buffer and device buffering are available in Standard mode.
For custom application/script it can be enabled with FDwfAnalogInBuffersSet.

[streaming from the ADP3450 scope to my PC]

Hi @csullender

ADP3450 lets you capture up to 128Mi samples on up to 4 channels at up to 125MHz.
Longer captures require data streaming which are limited by USB or Ethernet bandwidth to about 20-30Ms/s, 5-8MHz on 4 channels.

You can use WaveForms application or custom apps/scripts see WF SDK / samples/ py/

[AD3 Exhibiting strange behavior]

I missed the second part of the question...

The AD3 requires slightly more power than AD2. The connection problem could be caused by USB contact or power insufficiency. Try using other port, cable, powered hub, 5VDC aux supply.

The newer software version improves the detection of some problems caused by low supply voltage:

 

On Windows make sure "Load VCP" is not checked.

[Waveforms Spectrum Multiple Issues with Noise Density]

Hi @DTM_RD3

The marker and some measurement magnitudes are rounded to 3 decimals, so smaller values are displayed as 0s.

Thank you for the observation. It will be fixed in the next version.

[AD3 performance problem's]

Hi @Ola

The device internal noise (+nearby equipment radiation influence) can be measured by shorting the inputs.

[Waveforms skipped(???) support for NI Virtual Bench]

Hi @DigilentFan

It is supported in the latest public release and newer beta versions, since 3.19.29 (2023-03-24)

 

[DD Manchester Hex display]

Hi @yattr

In newer WF version the Buffer is only used in Repeated mode. This, to reduce the workspace/project size and save/loading time since the record is intended for large captures. If you want to keep the captures, these can be saved in tabs with the + (Add Tab) or scissors button.
Are you referring to operation this change ?

[Suitability of AD3 as digitizer for the vhs-decode project]

Hi @joebobjoe

The AD3 has multiple parallel running instruments which share the same communication channel, so the data streaming (record/play) is performed in chunks. Due to the latency the streaming can use about half of the communication bandwidth, 10MSps = 20MBps = ~40MBps/2
The ADP3X50 has DDR-RAM, which lets you capture up to 128Mi samples on up to 4 channels at up to 125MHz. Even longer records on this device can almost fully utilize the USB/Eth bandwidth tanks to the larger chunks allowed by deep device buffer.
The EclypseZ7 with Zmod-Scope, AWG... is a development board which can be also used similar to ADP3X50 with WaveForms.

[Oscilicope Channel 1 of ADK2 not working]

Hi @grkees

Probably the ADG612 on C1 was damaged by high voltage.

If the device is in warranty, for replacement contact support.digilent@ni.com, specifying the Date of Purchase, Seller and Purchase Order/ Web order Number.

See the following for repair instructions:

 

[AD3 Exhibiting strange behavior]

Hi @coleblax

This is normal. In AD3 the oscilloscope input ranges are switch by relays, which toggle when setting rage to 500mV/div or lower and above this, or during initial software connection.

[AD3 performance problem's]

The IC spec sheets only refers to the IC itself, not including the frontend and nearby radiation sources.

Again, note that with 1V/div the ADC is high range ~50V pk2pk, with my AD3 62.82V, LSB 3.83mV
and here DAC + ADC is measured

 

Here the ADC is in low range, ~5V pk2pk, LSB 335uV
DAC LSB ~670uV

 

With 1V amplitude the DAC is also at low range LSB ~170uV

[AD3 performance problem's]

You want to perform the math on the digital loopback of W1 ?

54 minutes ago, Ola said:

5*asin(sin(2*PI*10*Time))*2/PI - W1-1.5e-3

W1 channel capture in Scope represents the digital samples sent out to the AWG1 DAC. However on your screen W1 is unchecked and if you have performed the capture this way, you may not have data to process.

[AD3 performance problem's]

Could you tell me the math used for INL DNL ?

[Digital Discovery to collect 16 bit SPI data - multiple slaves with same CS, CLK, MOSI and individual MISO]

Hi @Shalin

I3C is not supported natively but it can be implemented in Logic Analyzer with Custom decoder.

[Analog Discovery 3 WaveForms - Automotive Measurements - Custom Probes Needed Please]

Hi @JonD

I'm working on it.

[Entering a custom pattern in the patter generator on the fly instead of writing in a csv file and then importing it]

Hi @Archan

See the Help/Script or WF SDK / samples/ py/ DigitalOut_Custom.py DigitalOut_CustomBus.py examples

[AD3 performance problem's]

Hi @Ola

See the following:

 

[Effect of activating option Ib/Vbe when using transistor tester with WaveForms Tracer]

Hi @linear_guy

Sorry but I don't see the problem.

The top row starting with Vrc controls the W1 and the bottom row starting with Vrb controls the W2.

With 'No Adapter' the drawing on the left shows the circuit setup:

With Adapter the drawing it does not show the connections since these are controlled by relays on the adapter.

With Adapter the Emitter (setup GND) is referenced to +/-5V (V+ or V-) to have 10V range.
Without Adapter is by default referenced to AD GND but this can be changed under Options.
The signals are generated the same way and measurements performed the same way.
For devices with 2 oscilloscope channels and Adapter additional measurements are performed automatically in a second run, like above the Ib/Vbe checkbox.

For devices with 4 oscilloscope channel it expects a different setup:

As you can see the 'Ic/Vce(Ib)' uses Rb and 'Ic/Vce(Vbe)' expect no (short on) Rb:

[DD Manchester Hex display]

Hi @yattr

Could you explain what is not working ?