attila

Hi @Ondrej Like the Pulse/Counter trigger ?

Hi @Ondrej You can use Measurements or "Quick Measure":

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

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

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

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.

Hi @MarceloNotThePLCguy Is it working?

You may have to press the Auto or Manual buttons in the Device Manager. The reprogramming is only needed if the USB eeprom is accidentally erased by USB dev tools. The eeprom data looks good on your device.

Hi @MarceloNotThePLCguy Try reconnecting the device or restart the system.

Hi @alexplcguy @MarceloNotThePLCguy The latest version overcomes the RPi4B driver issue with Digital Discovery: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/

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

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

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)