attila

Hi @tomas61 Like:

Hi @tomas61 Use .visibledata Use X.data and Y1.data

Hi @Toladar The programming probably fails because the device is busy, opened as COM port. On Windows open Device Manager: - make sure the "Load VCP" is unchecked. If it is, uncheck and reconnect device. - make sure the driver version 2.12.28.0 update from Windows update or https://www.ftdichip.com/Drivers/CDM/CDM v2.12.28 WHQL Certified.zip

Hi @VijayViswanath The AD2 max sampling rate is 100MHz. The Logic Analyzer device buffer size is 4/16k In Logic Analyzer you can have measurements for all DIOs.

Hi @VijayViswanath Modulating of external signal is not supported, but I will add such option in the a few months.

Hi @VijayViswanath Are you look for such signals? You can try the software/hardware features in demo mode: https://reference.digilentinc.com/waveforms3 https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

@malexander Could you help in this issue? @Toladar When I run the Enumerate.py the first time the FTDI lib returns no data. The following runs however are correct. Could you try running the script twice? What Linux distribution/version are you using? Could you try the device with Windows or MacOS? $ python Enumerate.py FTDI Version: 0x10408 Devices: 1 1. SN: flags: 0x1 type: 0x3 id: 0x0 locid: 0x0 DMGR Version: 2.8.8 Devices: 1 1. SN:210321A419AA Analog Discovery 2 PDID: 0x40300360 DWF Version: 3.13.15 Devices: 1 1. SN:210321A419AA Analog Discovery 2 $ python Enumerate.py FTDI Version: 0x10408 Devices: 1 1. SN:210321A419AA Digilent USB Device flags: 0x2 type: 0x8 id: 0x4036014 locid: 0x103 DMGR Version: 2.8.8 Devices: 1 1. SN:210321A419AA Analog Discovery 2 PDID: 0x40300360 DWF Version: 3.13.15 Devices: 1 1. SN:210321A419AA Analog Discovery 2

Hi @Toladar Try reinstalling Adept Runtime: https://reference.digilentinc.com/reference/software/adept/start Try running the Enumerate.py You only have to reprogram the EEPROM in case it was accidentally erased with some USB development application, like FT_PROG

Hi @ThaRev The recording on Digital Discovery is performed as normal capture in one chunk in DDR. Only the data from here to computer is transferred in smaller chunks. Transferring 256MB over USB 2.0 takes about 8 seconds. Doing it in smaller chunks (with record) gives to feedback on the progress and possibility to cancel it. The Record mode is for traditional Logic Analyzer usage: specify rate, samples and position. Changing the view (zoom, pan) does not affect the next capture setup. Transferring and processing large amount of data takes time, so you capture wait and inspect the data for longer time. The Repeated mode is for Oscilloscope like usage for timing or bit level analysis. Changing the view will affect the next capture. It is done with less samples so processing takes less time. Lets you quickly zoom in and increase sample rate automatically to have better resolution for the next capture. For smooth scan Screen or Shift mode we also need low amount of samples. The next software version will let you capture max samples in Repeated mode with Digital Discovery. Thank you for sharing you opinion.

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.

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 @Camarillo See the following picture:

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.