attila
-
Posts
6,655 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Posts posted by attila
-
-
Hi @ThaRev
The Repeated more is intended for timing analysis or short communication message.
The number of samples is limited since in this mode the whole capture is transferred at once. With millions of samples this would block the application, making it laggy.
Use the Record mode fore larger captures. In this Mode the data is transferred in chunks which does not block the app and it can be cancelled.
-
Hi @Anton
The PS/2 interpreter is not supported since it was considered obsolete.
Is this protocol still used in education?
-
Hi @tomas61
Use ".data =" not ".data[]"
if(!('plot1' in this)) setPlots(1)
...
var lData = Scope1.Channel1.data
plot1.Y2.data = lData
... -
Hi @tomas61
See the Help tab of the application, like in the earlier screenshot, or select Browse in the Help menu.
-
Hi @Camarillo
You have fixed the oscilloscope, but it looks like the AWG output is damaged too
You can verify the following rails, when the device is connected and opened with WaveForms, between the no load component pads and device ground.
Bottom left edge of the board:
In the following post you have further troubleshooting:
-
-
Hi @tomas61
The data should be the data from the last capture.
You are performing 10x10 captures and the thresholdLow is decremented for each capture by 8x0.01 The threshold value for last capture will be 7.92 lower than for the first capture. You may want to initialize it for each capture.
-
Hi @martin1701
After cutting trace between JP1200 the hardware IDs should be USB\VID_04B4&PID_8613
To verify if the trace is cut properly, with unpowered board you can measure the continuity using a DMM on the jumper vias.
Still having device descriptor failure indicates hardware issue.Is the USB connector looking good? Please inspect the soldering and if the internal contact plate is not broken.
You may try contacting for warranty and replacement, support dot digilent at ni dot com.
They will need your name, when you purchased the device, whom you purchased it from (i.e. Digilent or a distributor), and the serial number on the underside of the device. If you purchased the board from a distributor, you will need to contact them about their warranty. -
Hi @tomas61
You can use the wait() function or instrument.wait() or dialog like Tool.question() .getNumber() ...
See the examples or the Help tab in the application.while(var i = 0; i < 10 && wait(1.5); i++) { ....
if(Scope.wait()) throw "Stopped"
if(!Tool.question("Continue?")) throw "Abort"
-
Hi @martin1701
In case the USB device is not detected (hardware id/unknown) and this is due to the erased firmware, you need steps 1-4.
Other possibility could be data signal contact issue (cable, plug problem), issue with the supply or damaged IC.
-
Hi @Hans_ESC
The cursors are not accessible from script.
-
Hi @martin1701
I have not heard such problem with newer revisions but you could try the following procedure:
-
Hi @martin1701
It could be problem with USB cable or connector, the differential data lines not making contact. Try using other cable and computer plug.
On EE revF or earlier boards, the problem could also be due to erased USB firmware.Do you have a revF or board?
You can find this info on the bottom of the board under the Xilinx TI logo.You have the reprogramming application in private message and instruction in the following post:
-
Hi @Stretch
You can find phase measurement under oscilloscope measurements add global measurement.
The XY view does not have cursors.
-
Hi @Camarillo
It is most probably the C2 ADG612 damaged, the first IC in the input path.
The 2.7v is the maximum input reading with high gain, <= 500mV/div
Sorry for the late reply, I'm off work this week.
-
Hi @slalps
Good to hear it is working.
Than you for the feedback. -
Hi @slalps
Probably the FTDI drivers/libraries are messed up on your system, causing application crash. This is the first time I see such...
You can use the CDM uninstaller to remove the installed drivers:
Readme: https://www.ftdichip.com/Support/Utilities/CDM_Uninst_GUI_Readme.html
Application: https://ftdichip.com/utilities/#cdm-uninstallerAdd the following products: 6001, 6010, 6011, 6014 (most common devices) and press Remove Devices. See picture below.
Connect your device and install the driver from Windows Update or FTDI setup (it should be the same):
Page: https://ftdichip.com/drivers/vcp-drivers/
Installer: https://www.ftdichip.com/Drivers/CDM/CDM212362_Setup.zip
-
Hi @Camarillo
According your measurements the offset DAC is working.
I almost forgot that odd reading or output offset could be due to wrong calibration.
Since the offset voltage is applied this it likely good, but please perform a "Load factory" and see the oscilloscope readings again to make sure the calibration is not culprit.
Otherwise the 21V reading is likely due to damaged ADG612.
The one for channel 2 is on the right side, the 16pin IC above the trimmers. -
Hi @nikko
I'm glad to hear it is working.
-
Hi @slalps
1. In the "USB Serial Converter" properties, make sure the "Load VCP" is unchecked:
In case it is checked other application may try to use it as COM device, blocking access to it.
2. Make sure you have the latest driver installed:
Reinstall WaveFroms and check the Adept Runtime section or install the driver manually: https://www.ftdichip.com/Drivers/CDM/CDM21228_Setup.zip
Reconnect the device in order the new driver to be loaded.
3. The USB EEPROM might be erased by other USB development applications.
In this case use the "My device is not listed", reprogramming option in WaveForms Device Manager.
-
Hi @slalps
This looks like a PC/OS issue...
The AD2 should be detected as "USB Serial Converter" in Windows's Device Manager.
Do you see such or "unknown device" showing up when you conned the device?
It may take a minute to be detected as "unknown device"...
-
Hi @nikko
In case it is an F or earlier revision the USB firmware could be corrupt.
See the following instructions and try to reprogram with the Windows application you have in private message.
-
Hi @Camarillo
I meant measuring the VOFF_SC2 relative to the device GND with external DMM.
Having the scope channel 2 range 500mV/div or lower, changing the offset between -2.5V and 2.5V should change the VOFF_SC2 between ~1V and ~3V
Above 500mV/div for offset between -25V and +25V change VOFF between ~1V and ~3V. -
Hi @laurent
In case your script quits the device gets closed and the outputs stopped.
Set the following parameter before opening the device to keep it running on quit/close:
dwf.FDwfParamSet(DwfParamOnClose, c_int(0)) # 0 = run, 1 = stop, 2 = shutdownThe VIO could be stopped due to over-current.
See the SDK/ samples/ py/ AnalogIO_DigitalDiscovery.py
Logic Analyser PS/2
in Test and Measurement
Posted
Hi @Anton
No, you don't need to be in education.
I only asked it to have an estimation on how many people would need such feature, where to put it on the priority list.
12-18 years ago, during my faculty years, the PS/2 it was already obsolete but still used in lab works.
I just asked some professors and students, it is not used since many years.
I will try to make an interpreter for you.