[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 ?

[WaveForms counter?]

Hi @Ondrej

You can use Measurements or "Quick Measure":

[Mac "No device detected" analog discovery2 waveforms]

Hi @bill v

The newer WF software should warn you to install or remove the driver, depending on MacOS version.

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

Hi @m72

You could use "Not Ends with" or "Not Contains", Filter: "K"

[Electronics Explorer Troubleshooting]

Hi @AndrewG

I've added app link to the end of main post:

 

[LabView]

First, install WaveForms release or the latest WF beta version.

T&M devices can be controlled from LabView using:

- Digilent WaveForms VIs or digilent_waveforms_vis-1.0.3.26.vip
Contains VIs similar to VirtualBench VIs, some examples, help and it is compatible LabView 2010 or newer.
Provides limited access to device features.

- Analog Discovery Toolkit for LabView
Not recommended. It is a re-branded version of previous package.
In order this to work, delete the wrongly included dwf.dll from LabVIEW 20XX/vi.lib/Digilent/_AD2 Toolkit_internal_deps/

- WaveForms SDK
The API can be used with LabView/Tools/Import/Shared Library. See the LabForms project as example.
You can find manual and several Python sample scripts under WF SDK/samples/py

All above can be used with Windows. For Linux and MacOS the .vip archive needs to be extracted.

 

[AD2 scope oversampling with ext trigger: communication error]

Hi @wna

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

[Scripts]

Hi @tomas61

You could use start or exec functions to call an external application to perform the task.

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

Hi @m72

The source of the problem is that the actual generator rate is not 176kHz but 176,056Hz  (100MHz/568)
For this the run time should be 22.72us (4/(100e6/568))
The WF app in the auto run calculation takes in account the desired rate... I will fix it now

Thank you for the observation.

[Scripts]

Hi @tomas61

See: https://www.google.com/search?q=js+2d+array
https://stackoverflow.com/questions/966225/how-can-i-create-a-two-dimensional-array-in-javascript

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

Hi @m72

I've added the "speed test" for internal development purposes, but good to know people are trying to use the new features

Thank you for the observations, I will look at them.

[Analog Discovery troubleshooting]

Hi @Cappernicus

If the USB data lines are good and the 3.3V rail is good but the device is not detected most probably the USB controller is damaged.
On AD1 the USB is supplied with DVCC3V3 and on AD2 from USB 5V.

The pull-up should have helped if the EEPROM was accidentally reprogrammed to use the Suspend option.
In Suspend the device is not detected and VCCA is down. In this case the other internal rail VCCCORE is still on.

At this point I don't have any other idea than replacing the USB controller...