[Discovery 3 with Raspberry Pi Zero 2W over current error]

Hi @rjratnip

It could be a similar hub or driver problem as it is with RPi1,2,3 where FTDI USB packets are randomly lost or corrupt.

 

 

[i2c on logic Analog Discovery2]

Hi @woldes

The I2C should be read as logic high in idle. Do you have pull-ups on the SCL and SDA ?

[Logic Detector as trigger in Scope. Is it possible?]

Hi @m72

Set the UART Baud to Manual.
With Auto the Rate is recalculated for each capture which is handled as configuration change and the Buffer counter is restarted.
It will be corrected in the next version.

[EclypseZ7 Dual device mode]

Hi @StefKay

Looking at the project, unfortunately there are no clock capable DIOs, so reference clock for device synchronization is not really possible with EclypseZ7.

[Saving measurments in buffer to a single .csv file]

Hi @GCompton

You can use Logging/Script or the Script tool for custom export.

[Multichannel pulse height analyzer]

Hi @GCompton

With the current sw version you can select Trigger 1 to output 'Scope Detector' and select Sampling Clock T1
This will store one sample for each trigger event with 15 cycle delay, 150ns delay for 100MHz or 120ns with 125MHz system frequency.
The next version will let you select directly 'Scope Detector' as Sampling Clock.

 

[SPI MISO line shows no data]

Hi @Rohan16

If you referring to the SPI mode with '0th clock pulse' ? This can be adjusted with Polarity and Phase options.

[EclypseZ7 Dual device mode]

Hi @StefKay

It looks like dual mode with reference clock is not supported with EclypseZ7. I will try to add support for this next week.

[Discovery 3 with Raspberry Pi Zero 2W over current error]

Hi @rjratnip

1. It could be an adapter/cable contact problem.
2. The AUX supply can only be blocked by the the under/overvoltage 4.11V/5.76V protection circuit.
You could have a grounding issue. Are the RPi and 5V supplies floating or grounded ? If both are grounded make sure to use nearby sockets, same splitter.
With the default 'USB Power' 'Stop with AUX' the USB supply line is turned off if the AUX voltage is ok, 4.5V...5.5V
If this option is 'Always ON' the USB and AUX currents will balance according the voltage/cabling resistance. If the USB voltage is higher than AUX, the AUX current will be lower. 

Verify the voltage of your supply or use powered HUB.

[SPI MISO line shows no data]

Hi @Rohan16

The embedded JavaScript does not support binary number format but the interface does.

[Difference between data viewed in Waveforms GUI and recorded with SDK]

Hi @Marcus Watson

Are you using similar vertical range for C2 in WF and script ?
The AD3 scope inputs have two input ranges. If C2 with WF app is in low range (high resolution) and with script in high range, the lower resolution could hide details.
dwf.FDwfAnalogInChannelRangeSet(hdwf, 1, c_double(5.0)) # C2 low range

 

Approximate overlay looks like this:

[EclypseZ7 Dual device mode]

Hi @StefKay

T1 = DIO14 = B6

[Multichannel pulse height analyzer]

Hi @GCompton

The AD3 bandwidth of 9/30MHz may be too low for such pulse lengths.
The device has sampling clock option trigger IOs but this requires digital level signal. Now I tried to enable a sample on analog trigger event but this with the current 'firmware' has a minimum trigger to sampling delay of 12cycles, 96-120ns
The only eventual option I see is capturing more data, with min/max sampling and processing it.

[SPI MISO line shows no data]

Hi @Rohan16

See the following:

  

[Analog Discovery 2 Power Supplies Sink Current]

Hi @Ammar Kh

See the user supplies schematic:

https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide#user_supplies_control

 

[Generation of 5V Input Signal @ 60 Hz with Half-Cycle Fault Interruptions]

Hi @Jimmy Guerrero

See the following:

[Error: ...either not designed to run on Windows or it contains an error]

Hi @tyoung_google

I was referring to check your SSD/HDD

[Error: ...either not designed to run on Windows or it contains an error]

Hi @tyoung_google

Verify your disk and try to reinstall WaveForms, including Adept Runtime section.
It looks like the files are corrupt. The installer has integrity checking, so if this was corrupt during download or copy, it should prompt an error message and not let to continue.

[Question about phase between digital output and analog waveform]

Hi @liu

The latest version is built for 32 (armhf) and 64bit (arm64) ARM.

 

[Waveform improvements]

Hi @sintech

Yes, the interpreter has to be run after data change, new capture, buffer or tab change change. Only the raw data is saved in background, the processed data is not.

[Waveform improvements]

Hi @sintech

2. 

 

[How to split measurements in XX Mb files]

Hi @Albert Cirera

You can use View/Logging to save each measurement separately.

[SPI MISO line shows no data]

Hi @Rohan16

Currently you are only sending an 0x0A 8bit command.
Enter the words you want to write here, like it is by default prefilled:

[AD2: play wavegen, record scope, trigger]

Hi @bharathb

See the AnalogOutIn_PlayRecordStereo.py example

[Current Limiting IV Curves]

Hi @joshna

Probably the V_DS input voltage on the analog input channel is out the range. 
The analog inputs of AD3 have two input ranges, approximately 5V and 50V pk2pk, and adjustable offset.
Set offset or range dwf.FDwfAnalogInChannelOffsetSet(hdwf, #, c_double(2.5)) or dwf.FDwfAnalogInChannelRangeSet(hdwf, #, c_double(50.0))