[Analog Discovery troubleshooting]

Hi @MiaPka

Try with a newer version of software:
https://reference.digilentinc.com/reference/software/waveforms/start
https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

 

[what can be expected for the (nearer) future]

Hi @chrisdoe

In about on month ADP3450 see: https://fb.watch/36SpWxtyIn/

[Frequency Limitation on Impedance tool]

Hi @mmachtey

See the following: default.dwf3work

plot1.X.data = Impedance.Traces.Trace.getData("Rs")

var rs = []
Impedance.Traces.Trace.getData("Xs").forEach(
    function(x){rs.push(-x)}
)
plot1.Y1.data = rs

[Frequency Limitation on Impedance tool]

Hi @mmachtey

In newer WaveForms version you can find in Impedance Analyzer Nyquist as well Custom plots.

https://reference.digilentinc.com/reference/software/waveforms/start

https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

 

[Analog Discovery 2, broken scope?]

Hi @EdWall

In case of the first screenshot if you have used BNC adapter this was probably set to AC coupling.
The scope inputs wires are differential. The scope channel reads the difference between 1+ and 1- or 2+ and 2-. This for instance to measure the voltage drop (current) on a shunt resistor.
Using it in single ended mode the negative inputs should be connected to ground. Connecting the positive to ground and negative to signal you will have voltage reading with "opposite sign".
And always make sure to have common ground connection between the devices and circuits!

[Analog Discovery troubleshooting]

Hi @Sairy

The AD1/2 have two scope input ranges 5 and 50Vpk2pk
https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual#scope_input_divider_and_gain_selection

[Analog Discovery Studio - No Device Detected - MacOS]

Hi @dbm

Thank you for the information.

[Are there any plans for Analog Discovery 3 with deeper memory?]

Hi @kaamil1984

128Mi sample recording at 1 channel at 125MHz will be suffice ?

 

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

Hi @m72

Thank you for the observation. It is fixed for the next version.

[Using the SDK with AD2 on Ubuntu]

Hi @ssm

Yes, you can use the SDK under Win, MacOS and Linux as well.
See the manual at /usr/share/digilent/waveforms/manual/dwfsdk.pdf

[Analog Discovery 2 Device Not Recognized]

Hi @maz

The "device descriptor request failed" indicates that the device attach is detected but the low level USB communication fails.
1. It could be an USB contact issue with cable, connector on host or device side.
Try other cable, other host connector, inspect the connector in the device. It is very hard to insert the microUSB reversely but such could break the inner contact plate.
2. The USB controller in the device could be damaged.

[Analog Discovery Studio - No Device Detected - MacOS]

Hi @rainerle

This is really weird.
Thank you for the update and let us know if you notice any further issue.

[Analog Discovery Studio - No Device Detected - MacOS]

Hi @rainerle

Did you try restarting your machine having the device unplugged?
Restart is better than Shutdown. The Restart cleans up UEFI-system-driver cache which could contain invalid device info.

Did you try with and without the driver-filter? This can be found in the WaveForms DMG
Old macOS version require the driver to be installed, new macOS versions don't require it, on some new Mac hardware it may not work with the driver.

[Scope Continuous Record and Save *.csv]

Hi @Slawek

You can also find for some controls the Script reference in the status-bar.

 

[Scope Continuous Record and Save *.csv]

Hi @Slawek

The Script tool provides access to most of the control behind the interface, a lot of objects and functions.
The commonly used ones are listed in the app Help and the Ctrl+Space can be used to reveal the child objects.
The Script access for scope-measurements-reset is currently not available but it will be in the next version.

Thank you for the clients since the feedbacks make the app evolve

[Scope Continuous Record and Save *.csv]

Hi @Slawek

The "acquisition" saving can't be automated but:
- In the Logging view you can select the export format under the 'gear' after the Source option.
- You can use the example script to save both picture and data.

[Scope Continuous Record and Save *.csv]

Hi @Slawek

The Record mode is intended to capture then analyzer. It may take long time for the data to be processed in various views, measurements...

You can use a Scrip to restart the capture:

do{Scope.start()}while(Scope.wait())

[Issue: device remains "in use" if not closed on exit, until all connected digilent devices are closed]

@malexander

Ok, Thank you

[Issue: device remains "in use" if not closed on exit, until all connected digilent devices are closed]

Hi @reddish

With 2 devices I can reproduce the issue you are describing.
Earlier I have tried with only one device and two application.

@malexander

Having 2 devices with separate apps connected to them. After killing one app or exit without disable/close, the following apps can't connect the device.
The JtscInitScanChain fails with scerrInitFailed. May be the DPTI enabled flag remains set in FTDIFW and JTAG enable fails?
Could we solve this problem?

[Issue: device remains "in use" if not closed on exit, until all connected digilent devices are closed]

Hi @reddish

It is working for me also with adept 2.19.2

[Issue: device remains "in use" if not closed on exit, until all connected digilent devices are closed]

Hi @reddish

I just tested it under Ubuntu 12.4 amd64.
I can connect to the device even after the other connected process was killed and busy flag is stuck.

Which Adept Runtime runtime version are you using?

I have tested it with 2.20.1 and .2

$ dpkg -l digilent.adept.runtime
||/ Name           Version        Description
+++-==============-==============-============================================
ii  digilent.adept 2.20.1         Digilent Adept Runtime
 

[Issue: device remains "in use" if not closed on exit, until all connected digilent devices are closed]

Hi @reddish

The device info is cached by Adept Runtime in shared memory. This is required because some info may be unavailable when a device is opened by another process.
In case an app which uses a device crashes or is killed, the busy/opened flag will not be cleared. The clear is also performed in normal detach.
When the last app using Adept Runtime closes, this gets unloaded from memory together with the info cache.
However a stuck flag does not prevent an app to connect to a device.

[WaveForms counter?]

Hi @Ondrej

Thank you for the counter idea. I will add it later.

[WaveForms counter?]

Hi @Ondrej

You could use the Sync mode in case the average signal rate is below 1MHz, up to 100M counts.
Set a high number of Samples, the Rate is only informative for representation.

[WaveForms counter?]

Hi @Ondrej

Like the Pulse/Counter trigger ?