attila

Hi @alexplcguy @MarceloNotThePLCguy The issue is solved in the latest version:

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.

Hi @Giovanni First of all, connect to the device with WF application in order the analog circuitry to be enabled. The VREF1V2_AWG and VREF1V_AWG is generated by the IC42. You should also verify the 3V3 input of this. These are buffered by IC13 as VREF_AWG1/2. https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual#awg_reference_and_offset You can find the respective layout sections in the following post: https://forum.digilentinc.com/topic/4714-analog-discovery-waveform-generator-failure/?do=findComment&comment=19153

Hi @sintech First of all I would like to thank you for this post. 1. I have added Select option for Events view. 2. First value drawing alignment is fixed for the next release. 3. In Protocol under View menu you can find option for "Max. Lines" to prevent slowdowns. The load also depends on the line (message) length, so you can try to use a line limit of 100... 4. The next macOS version will fix one possible software issue. You can post it here, or send steps to reproduce or report log to me in private message. 5. You are right. I wanted to make this Play mode a bit more user friendly before documenting it. 6. At the moment you can use ROM Logic in Patterns to output on an unused DIO line and capture it together with the input data. 7. I will add export "all events" later. 8. Added name to 'Add signal" for the next release. 9. I use to add Labels or Note to describe the channels, cursors... Would it be convenient to have Name column in the Cursor View and tooltip on the cursors buttons ('1 v', '2d1 v'...) ?

Hi @MarceloNotThePLCguy I will try to reproduce the issue, but if it is similar to RaspberryPI problem we won't be able to fix it. Are you using amd64/x86-64 ? @malexander Have you heard of such issues? Do you have any idea to help this problem?

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

Hi @alexplcguy Yes, it is likely to be a driver/kernel issue.

Hi @alexplcguy Are you using the DD with a computer? Such errors use to appear with RaspberryPi4 with AD1,2 DD. Due to some FTDI driver/kernel issues. Sudden disconnects or power loss should give other errors. The Pattern Generator features of AD and DD are identical, except the DD has more buffer for custom pattern and ROM logic. On the hardware side the DIOs drivers are a bit different. On the DD the IO voltage/threshold, drive strength and slew rates are adjustable, it has level shifter to interface with 5V signals. This should however not influence the PWM timings.

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.

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...

Hi @Cappernicus Here you have for AD1. The PWRSAV is used the same way as on AD2.

Hi @Cappernicus The VCCA is an internal rail of the controller. It should be measured on the marked capacitor, above the 'IS' of the 'discovery' label. According the AD2 EEPROM setting the PWRSAV# option should not be used. This signal is used with a 10k pull-down for other purpose. If you suspect this to be the problem you can try to solder a temporal ~2k pull-up to OE_JTAG and DVCC3V3. See the bottom layout: Connect USB, use the WaveForms application/ Device Manager / "My device is not listed" to reprogram the EEPROM. Disconnect and remove the pull-up. To test this, I have configured the AD2 to 'Suspend on ACBus7 Low' and 'Self Powered' The VCCA was indeed low and device not detected. With the above method I was able to recover it.

Hi @tomas61 See the Help tab, press F1 or Browse under Help menu. 1. To round a number to 2 decimals you can use: round(value*100)/100 2. To format the number for text conversion use: value.toFixed(2)

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?