attila
-
Posts
6,662 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Posts posted by attila
-
-
-
Hi @k_b
It is probably trigger on signal ringing, glitch on the falling edge.
Zoom in, increase the sample rate to have a better view. -
Hi @scott.moore
The alternate trigger to work with 5-10ms seems to require the Scope interface to be invisible. tt1.dwf3work
Having this in from adds a few milliseconds of delay, so it may not catch the next trigger.
Such method can be implemented with better performance in custom app/script.
And this is a solution with data processing in Script: tt2.dwf3work
-
The Scope.DigitalChannels.I2S.events is an array with the interpreted values from the current capture, .eventStamps the associated relative time.
-
Hi @scott.moore
What is the distance between the triggers ? What measurement precision do you need ?
The software timer only has a few milliseconds of resolution/precision.
If the distance is less than a few milliseconds, trigger on event 1 use a script to look for event 2
If it is more, you can configure alternate trigger and use the device trigger date&time difference for distance, for device system frequency resolution (8-10ns)
You can also use the sample time (trigger crossing interpolation) difference for higher resolution measurement. -
You will probably need to make some settings to suit your needs, such as the I2S options:
i2s.dwf3work -
Hi @scott.moore
The only way to do this is to trigger the capture with event 1, then process the waveform and look for event 2.
-
Hi @korn
Thank you for the request.
-
Hi @pieb
It could be something damaged in the analog circuitry, draining too much power after the analog rails are enabled and the current limitation shuts down the device.
For warranty and replacement contact the support.digilent @ ni.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number.
Otherwise, here you have some repair tips:
-
Than would be a bit complicated to do.
Alternatively to visualize analog and digital at the same time, use the Scope with Digital and a slow input signal. With tall digital row the data is also represented as analog signal and the digital data can be used in Math channels.
-
-
Hi @gvo
See the in WF SDK/ manual.pdf and samples/ py/ AnalogOut_Sine.py AnalogOut_Custom.py ... examples
Edit: The WF SDK/ samples/ dwfcmd/ command line application may also be useful for you.
-
Hi @AstroKevin
You could use the 'Run All' button in the top-right of the app, or a Script and launch the app from a batch file with workspace and -runscript argument.
-
Hi @AstroKevin
It should be configured after each device open.
You can set DwfParamOnClose 0 to keep the device outputs active and generator running after close. FDwfDeviceAutoConfigureSet 0 to reduce device communication time when setting many options.
See: AnalogIO_DigitalDiscovery.py -
Hi @AstroKevin
This is fixed in the latest release and beta version.
-
Hi @reddish
I'm sorry to hear that.
To avoid registration, the direct release links can be found under the Previous Versions and the latest beta version can be downloaded from:
-
-
Hi @spillari
Configure the SPI interpreter options in the Logic Analyzer to be 12bits.
Use CmdRead command, you can also use the SPI functions from the Script tool... -
Hi @BobA
Unfortunately we don't have part number for the housing in the assembly:
On 9/5/2023 at 7:38 PM, attila said: -
Hi @torbos
Could this be related to the AD3's Scope channel low/high range relay toggle ?
Most of the WF SDK examples mention using a settle delay after adjusting the offset/range or opening the device, for example:
dwf.FDwfAnalogInConfigure(hdwf, c_int(1), c_int(0)) # configure
time.sleep(1.0) # wait
dwf.FDwfAnalogInConfigure(hdwf, c_int(0), c_int(1)) # start
For the relays about 50ms delay is needed.AD3 high to low range ~20ms :
AD3 low to high range ~50ms :
AD3 offset settle ~5ms :
AD2 offset settle ~600ms :
-
Hi @BobA
female: Sullins PPTC062LJBN-RC
male: Sullins PBC06DBAN -
Hi @spillari
See the examples including the default one, and the Help tab or Help/Browse /Protocol/SPI/Sensor about this feature.
Configure the Logic Analyze according your needs (Samples, Rate...)
-
Hi @KTP
See the following:
In newer software version the Oscilloscope signals can be ported to digital, see:
-
Technical Assistance Required---SO: 119593---Part number: 410-395 (DPS3340)
in Test and Measurement
Posted
Hi @UNM
This is likely a mechanical problem since the voltage readback is a feedback from the connector's PCB.
The banana connector may got loose on the small vertical PCB. In this case you could take it apart and fasten the connector.