All Activity

I should mention that I have USB keyboard, USB mouse, and even USB headphone. None of those are recognized by the Horizon Client, but all working when I use my virtual machine Debian.

Thanks attila. I'm using VMWare Horizon Client on which I have a Debian OS. On my VMWare, I have only "USB Unavailable".

Thanks attila. I'm using VMWare Horizon Client on which I have a Debian OS. On my VMWare, I have only "USB Unavailable".

Hello @Fausto Are there any records of validation of the DAQami software? The ISO accreditation was just an example.

Hello @Ross MacKenzie. Digilent does not make our products in line with/accredited by ISO. This includes MCC hardware and software. Regards, Fausto

Thanks JColvin. That was the problem. Everything seems to be working seamlessly now. Best, Dominic

Thanks JColvin. That was the problem. Everything seems to be working seamlessly now. Best, Dominic

I am hoping to acquirer a copy of your validation records for DAQami software . Sometimes this is as simple as a one pager signed saying the software validated this software per your ISO quality system. Thanks, Ross

Using 12-volt power, you do not have to do anything with the Scaler resistor. It will override our resistor because it has a much lower value.

Hi @JColvin when we last spole I was using a NI Virtual bench with the LabView Virtual Bench library. We have now recieved an ADP 5250 and I am trying to get this to work with the same library, the Virtual Bench library uses a VirtualBench Device I/O Control, this unfortunately isnt finding the 5250, I can see the 5250 in waveforms though Is there a way to get the labview control to see the 5250?

Then I do not understand this part in the features section:

Hi @Clyde On ADP3X50 the Digital IO voltage is adjustable between 1.2V and 3.3V The VIO output of this, first 2 pins of the DIO connector, is protected and can deliver up to 300mA. The 4 USB host ports are available in Linux mode. 2 of this can deliver 500mA and the other 2 900mA. The device has no other power supplies. Eventually the 2 AWG channel can output +/-5V 30mA 50R

Hey @Fausto, what should I do with the internal pull-up on the scaler?

I was speaking of the adjustablle power supply, not digital I/Os.

Hi @Dominic, Are you using the Digilent Toolbox rather than the old Data Acquistion toolbox which did not support non-blocking functions? There's a guide on how to set that up here if this is the case: https://digilent.com/reference/test-and-measurement/guides/matlab-getting-started. Please let me know if you are using the new toolbox but still running into this issue. Thanks, JColvin

Hi @BlazeIt, I suspect this may more likely be the source of a different issue (driver, baud rate, etc), but I have sent you a PM. Thanks, JColvin

@Kevin.C Will SHA512 work? I downloaded the rpm packages from our website and ran rpm -qip and looked at the signature field. All of them, with the exception of Waveforms, appears to be signed with RSA/SHA512. Please let me know if this works and I will work with Attila to get Waveforms signed with SHA512. malexander@vm-u22-lts:~/Downloads$ ls digilent.adept.runtime-2.27.9.aarch64.rpm digilent.adept.runtime-2.27.9.x86_64.rpm digilent.adept.utilities-2.7.1.i686.rpm digilent.adept.runtime-2.27.9.armhf.rpm digilent.adept.utilities-2.7.1.aarch64.rpm digilent.adept.utilities-2.7.1.x86_64.rpm digilent.adept.runtime-2.27.9.i686.rpm digilent.adept.utilities-2.7.1.armhf.rpm digilent.waveforms_beta_3.22.18.x86_64.rpm malexander@vm-u22-lts:~/Downloads$ rpm -qip *.rpm Name : digilent.adept.runtime Version : 2.27.9 Release : 1 Architecture: aarch64 Install Date: (not installed) Group : System Environment/Libraries Size : 25044427 License : see /usr/share/doc/digilent.adept.runtime-2.27.9/EULA and /usr/share/doc/digilent.adept.runtime-2.27.9/license-openssl-ssleay.txt Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:39 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.runtime-2.27.9-1.src.rpm Build Date : Mon 30 Jan 2023 02:03:57 PM PST Build Host : rpi4-ubuntu64 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Runtime Description : The Adept Runtime consists of the shared libraries, firmware images, drivers, and configuration files necessary to communicate with Digilent's devices. Name : digilent.adept.runtime Version : 2.27.9 Release : 1 Architecture: armhf Install Date: (not installed) Group : System Environment/Libraries Size : 21202338 License : see /usr/share/doc/digilent.adept.runtime-2.27.9/EULA and /usr/share/doc/digilent.adept.runtime-2.27.9/license-openssl-ssleay.txt Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:54 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.runtime-2.27.9-1.src.rpm Build Date : Mon 30 Jan 2023 01:27:45 PM PST Build Host : rpi4-ubuntu32 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Runtime Description : The Adept Runtime consists of the shared libraries, firmware images, drivers, and configuration files necessary to communicate with Digilent's devices. Name : digilent.adept.runtime Version : 2.27.9 Release : 1 Architecture: i686 Install Date: (not installed) Group : System Environment/Libraries Size : 23160188 License : see /usr/share/doc/digilent.adept.runtime-2.27.9/EULA and /usr/share/doc/digilent.adept.runtime-2.27.9/license-openssl-ssleay.txt Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:54 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.runtime-2.27.9-1.src.rpm Build Date : Mon 30 Jan 2023 11:31:24 AM PST Build Host : michael-u16-32 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Runtime Description : The Adept Runtime consists of the shared libraries, firmware images, drivers, and configuration files necessary to communicate with Digilent's devices. Name : digilent.adept.runtime Version : 2.27.9 Release : 1 Architecture: x86_64 Install Date: (not installed) Group : System Environment/Libraries Size : 25120940 License : see /usr/share/doc/digilent.adept.runtime-2.27.9/EULA and /usr/share/doc/digilent.adept.runtime-2.27.9/license-openssl-ssleay.txt Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:55 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.runtime-2.27.9-1.src.rpm Build Date : Mon 30 Jan 2023 11:47:30 AM PST Build Host : michael-u16-64 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Runtime Description : The Adept Runtime consists of the shared libraries, firmware images, drivers, and configuration files necessary to communicate with Digilent's devices. Name : digilent.adept.utilities Version : 2.7.1 Release : 1 Architecture: aarch64 Install Date: (not installed) Group : Applications/Communications Size : 6042364 License : see /usr/share/doc/adeptruntime/copyright Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:55 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.utilities-2.7.1-1.src.rpm Build Date : Tue 13 Jul 2021 05:14:31 PM PDT Build Host : rpi4-ubuntu64 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Utilities Description : Adept Utilities is a set of command line applications that can be used in conjunction with the Adept Runtime to manage and communicate with Digilent's devices. Currently Adept Utilities consists of three applications: Digilent Adept Utility (dadutil), Digilent JTAG Config Utility (djtgcfg), and Digilent NetFPGA-SUME Flash Configuration Utility (dsumecfg). The Adept Utility provides a command line interface for discovering Digilent devices, querying device information, manipulating the device table, and setting device information. The JTAG Config Utility allows users to initialize, program, and erase FPGAs and CPLDs on Digilent boards using a command line interface. The NetFPGA-SUME Flash Configuration Utility allows users to write bit or bin files to a specific section of the flash memory on Digilent's NetFPGA-SUME. For more information please consult the associated man documentation. Name : digilent.adept.utilities Version : 2.7.1 Release : 1 Architecture: armhf Install Date: (not installed) Group : Applications/Communications Size : 6013249 License : see /usr/share/doc/adeptruntime/copyright Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:56 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.utilities-2.7.1-1.src.rpm Build Date : Tue 13 Jul 2021 05:43:01 PM PDT Build Host : rpi4-ubuntu32 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Utilities Description : Adept Utilities is a set of command line applications that can be used in conjunction with the Adept Runtime to manage and communicate with Digilent's devices. Currently Adept Utilities consists of three applications: Digilent Adept Utility (dadutil), Digilent JTAG Config Utility (djtgcfg), and Digilent NetFPGA-SUME Flash Configuration Utility (dsumecfg). The Adept Utility provides a command line interface for discovering Digilent devices, querying device information, manipulating the device table, and setting device information. The JTAG Config Utility allows users to initialize, program, and erase FPGAs and CPLDs on Digilent boards using a command line interface. The NetFPGA-SUME Flash Configuration Utility allows users to write bit or bin files to a specific section of the flash memory on Digilent's NetFPGA-SUME. For more information please consult the associated man documentation. Name : digilent.adept.utilities Version : 2.7.1 Release : 1 Architecture: i686 Install Date: (not installed) Group : Applications/Communications Size : 6013794 License : see /usr/share/doc/adeptruntime/copyright Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:56 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.utilities-2.7.1-1.src.rpm Build Date : Tue 13 Jul 2021 04:15:52 PM PDT Build Host : michael-u16-32 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Utilities Description : Adept Utilities is a set of command line applications that can be used in conjunction with the Adept Runtime to manage and communicate with Digilent's devices. Currently Adept Utilities consists of three applications: Digilent Adept Utility (dadutil), Digilent JTAG Config Utility (djtgcfg), and Digilent NetFPGA-SUME Flash Configuration Utility (dsumecfg). The Adept Utility provides a command line interface for discovering Digilent devices, querying device information, manipulating the device table, and setting device information. The JTAG Config Utility allows users to initialize, program, and erase FPGAs and CPLDs on Digilent boards using a command line interface. The NetFPGA-SUME Flash Configuration Utility allows users to write bit or bin files to a specific section of the flash memory on Digilent's NetFPGA-SUME. For more information please consult the associated man documentation. Name : digilent.adept.utilities Version : 2.7.1 Release : 1 Architecture: x86_64 Install Date: (not installed) Group : Applications/Communications Size : 6039466 License : see /usr/share/doc/adeptruntime/copyright Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:56 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.utilities-2.7.1-1.src.rpm Build Date : Tue 13 Jul 2021 04:45:04 PM PDT Build Host : michael-u16-64 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Utilities Description : Adept Utilities is a set of command line applications that can be used in conjunction with the Adept Runtime to manage and communicate with Digilent's devices. Currently Adept Utilities consists of three applications: Digilent Adept Utility (dadutil), Digilent JTAG Config Utility (djtgcfg), and Digilent NetFPGA-SUME Flash Configuration Utility (dsumecfg). The Adept Utility provides a command line interface for discovering Digilent devices, querying device information, manipulating the device table, and setting device information. The JTAG Config Utility allows users to initialize, program, and erase FPGAs and CPLDs on Digilent boards using a command line interface. The NetFPGA-SUME Flash Configuration Utility allows users to write bit or bin files to a specific section of the flash memory on Digilent's NetFPGA-SUME. For more information please consult the associated man documentation. Name : digilent.waveforms Version : 3.22.18 Release : 1 Architecture: x86_64 Install Date: (not installed) Group : Engineering/misc Size : 68189182 License : see /usr/share/doc/digilent-waveforms/copyright Signature : RSA/SHA1, Fri 12 Apr 2024 01:23:28 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.waveforms-3.22.18-1.src.rpm Build Date : Fri 12 Apr 2024 01:23:10 AM PDT Build Host : attila-u16-64 Summary : Digilent WaveForms Description : Digilent WaveForms Application, Runtime and SDK. Support for Digilent Scopes & Instruments products.

Hi @Clyde, I have moved your question to a more appropriate section of the Forum where the engineer most familiar with the Analog Discovery Pro 3450 will be able to give accurate insight into this. I know that the trigger DIO signals themselves are protected by ESD diodes and PTC thermistors, but I am uncertain about digital supplies themselves regarding overcurrent protection. Thanks, JColvin

Hi @jmckinney I'm largely not familiar with FreeRTOS, but is there a chance that the data cache could be messing with the ability of the DMA to pull block descriptors from memory? https://www.freertos.org/FreeRTOS_Support_Forum_Archive/May_2016/freertos_Zync_UDP_TCP_with_DMA_IP_f531ef1cj.html seems potentially relevant. Caching issues are a pretty standard problem with non-scatter-gather DMA, where it just makes data unable to be seen by either side unless you flush or invalidate as appropriate. Pointers in block descriptors that aren't coming through as expected could cause all sorts of issues. If that's the cause, might be worth trying to disable the caches entirely, though I'm not sure how this affects the FreeRTOS setup. If you haven't, I'd also try putting an ILA on the DMA's AXI4-full master interfaces. Thanks, Arthur

Hi @BEBERL, If the transducer is analog based, i.e. sends out some sort of voltage based on the measured pressure, it might be possible to interface the Analog Discovery device (whether AD2 or the newer AD3) with it. I'm guessing it is analog based on the picture that shows 3 wires (presumably power, ground, and the signal) going into the extension cable. If it instead uses some sort of serialized digital interface, you would then have to figure out the communication scheme that it uses, which could be quite a bit of debugging to figure out as I'm not readily seeing any documentation for it. If this is the case, the Analog Discovery device could still potentially interface with the transducer, but the level of effort to get it working, if at all, is a big unknown. If it is an analog output signal, you would need some sort of physical adapter to readily connect to the wires (or be willing planning on splicing the cable open to connect to the individual wires via a breadboard or soldering pin headers to them). You could then use the analog input channels on the Analog Discovery device to measure the variable voltage coming out of the transducer as well as some sort of math channel to convert the measured voltage to the correct units. I'm presuming there is some sort of documentation out there that would tell you what first or second order linear equation the transducer follows. As for powering the transducer, the Analog Discovery device can probably do that for you as well with its external power supplies. The catch with this is that I don't know what voltage the transducer operates at. If you have some sort of datasheet regarding the electrical specifications of the transducer as well as the wiring setup, I might be able to provide a more conclusive answer for you. Thanks, JColvin

Hi, This model has a built in power supply. Does this power supply have the ability to set the current limit? Is the output current protected against an excessive current draw? Thanks.

Manually updating did the trick... thanks.

You should manually update the hardware specification: https://digilent.com/reference/programmable-logic/guides/vitis-update-hardware-specification. Vitis generally won't see changes to the filesystem. When just overwriting the copy of the file buried in the platform project, I'd be concerned that Vitis might need to extract other files from it, which it might not happen automatically during a build - I expect it won't see the copy without the manual update. One common issue that could come up after this (though I don't think you'll run into it here) is that if your XSA file has a different name, the extracted bitstream name changes. In this case, you'd need to go into the system projects Run/Debug Configurations, and change the path to the file to reflect the name of the new XSA.

Use mcc172_a_in_scan_start first to start the acquisition, then use mcc172_a_in_scan_status to determine the number of samples in the buffer. Study the attached C program. It requests 256 samples and displays the loop execution time, samples read, channel 0, channel 1, and the number of samples left in the buffer after the read. continuous_scan2.c

Hi @Fausto thank you for your reply. QuickDAQ now starts and I have tested it with a DT9816-S.