All Activity
- Past hour
-
def.framework will not install on Sonoma 14.4.1 Apple M3 Max
SergeLafontaine replied to SergeLafontaine's question in Test and Measurement
Thanks for your quick response. The latest beta digilent.waveforms_beta_v3.22.18.dmg behaves the same way. When explicitly copy and paste the def.framework to the Framework folder (password required), and try to run my application I still get the message "dwf.framework" can't be opened because Apple cannot check it for malicious software. - Today
-
USB-2416-4AO DI/O Support
metalhouse replied to metalhouse's question in Measurement Computing (MCC)
Hi @Fausto, Thanks for this. Just to confirm, what ports on the DAQ will I need to use to send an actuating signal to the relay you have shared? Regards, MT -
JColvin started following Streaming mode in ADP3450
-
Hi @jenga, The record mode (I'm presuming that is what you are meaning by streaming) bottleneck for the ADP3450 is limited by the connection to the host computer; either the USB 2.0 connection or the Ethernet connection, depending on which configuration you chose. As both communication options are packet based, data is transferred in chunks. Because of the on-board DDR memory, the streaming of data in chunks is largely mitigated since the device can continue to capture data and store it in the DDR memory while some subset is transferred over to the computer (presuming you aren't attempting to capture data faster than you can transfer it over anyways). The WaveForms Help tab has typical values for transfer rates and latency: In terms of other numbers, each analog input is stored in a 16-bit (2 byte) format, as well as the 16 digital channels being represented in a 2-byte format, so you'll correspondingly be limited in what maximum sample rate you can achieve based on how many channels you have enabled. There are several built-in Record mode examples in Python that should be of help: USB 2.0 with its overhead tends to top out at around 40 MByte/s, so with 3 two-byte channels acquiring data over USB, this ends up capping you at a sampling rate a bit over 6.5 MHz (best that I can tell, the screenshot from record to file is showing 13.1 MS/s // 26.2 MB/s for the measured rates because it is not taking into account the remaining third of the 6 bytes per sample bandwidth portion that the digital data is taking up): With a gigabit Ethernet connection, you'll of course then be able to achieve the faster rates: If you are wanting to have faster streaming, I would instead point you towards the ADP2230 with its USB 3.2 Gen 1 connection: Let me know if you have any questions. Thanks, JColvin
-
artvvb started following Meassuring energy of a pulse
-
Hi Ellile, If the other end of your resistor is grounded, that should be correct - the "Energy through C1 100R C2" example, which seems to be what you're basing this on, calculates power from the current through the resistor multiplied by the voltage at the top of the resistor. Current is calculated as the voltage difference across the resistor divided by the resistance in ohms - so, if C2 would measure 0 by the other end of the resistor being grounded, the modified example is fine. Energy is calculated by integrating the power - summing it all up, with each sample multiplied by the amount of time between samples. There might be a little bit of error from the digitization process, but that's what having a sufficient sample rate is for. Thanks, Arthur Edit: Moved the thread to the T&M subforum, which is more appropriate for this topic.
-
Apologies for the delay. I haven't been successful in reproducing your setup. Some additional settings that might help are 1. the constant values applied to the CONFIG interface of the XFFT IP - I assume the tlast port is tied to a constant one. 2. XFFT settings - both the Configuration and Implementation tabs include settings that affect what values are provided to the CONFIG interface. I'd also be curious about why the XFFT S_AXIS_DATA interface's tlast port seems not to be connected - in simulation, not asserting tlast at the expected time causes the XFFT core to assert either an event_tlast_missing or event_tlast_unexpected error. If you haven't, please review the product guides for both of these IP cores: https://www.xilinx.com/support/documents/ip_documentation/xfft/v9_1/pg109-xfft.pdf https://docs.amd.com/v/u/en-US/pg141-dds-compiler
-
malexander started following Waveforms not opening
-
@scorbetta What Digilent hardware, if any, do you have attached to your system when attempting to launch Waveforms? Does this error show up immediately when you launch the application or are additional steps required to reproduce it? Can you try executing "nm -D --defined-only /usr/local/lib64/digilent/adept/libdmgr.so | grep DmgrSetNetworkConnTimeout" and providing the output? It should be something similar to "000000000000237d T DmgrSetNetworkConnTimeout". When I install the debian package in Ubuntu 22.04 LTS using "sudo apt install ./digilent.adept.runtime_2.27.9-amd64.deb" the library files always end up in "/usr/lib64/digilent/adept" on my system. It's possible that "/usr/lib64" is a symbolic link to "/usr/local/lib64" on your system. Can you execute "ls -al /usr/lib64" and see if that's the case? @attila I can't replicate this behavior in Ubuntu 22.04 but the package always installs the files in /usr/lib64/digilent for me. If "ldconfig -p | grep libdmgr" is able to find libdmgr.so the location of the library should only matters if the application (Waveforms in this case) loads the library (instead of links to it) and specifies a relative or absolute path that doesn't match up with "/usr/local/lib64/digilent/adept/ibdmgr.so". Do you expect to see the reported error if the library can't be loaded or is this error more in line with a missing symbol? Thanks, Michael
-
Fausto started following USB-2416-4AO DI/O Support
-
Hello @metalhouse. The USB-2416-4AO can sink up to 150 mA max (per eight channel DIO bank) and supports a voltage level of +15 V. Take a look at the following solid-state relay (SSR). https://www.phoenixcontact.com/en-us/products/solid-state-relay-module-emg-17-ov-ttl-24dc2-2943259?type=pdf https://www.phoenixcontact.com/en-us/products/solid-state-relay-module-emg-17-ov-ttl-24dc2-2943259 The +5 output terminal 35 can source 10 mA max. for the SSR. Regards, Fausto
-
JColvin started following AD3 and Waveforms and higher voltages
-
Request for Signed Packages (SHA256)
Kevin.C replied to Kevin.C's topic in Technical Based Off-Topic Discussions
cc @attila Currently unable to run this on CentOS 9 as a result of this, could i get your help with getting the latest beta package signed with SHA256? Thank you so much for the help & support here! -
Hi Attila, Is there anyway to mimic in labview the "Sensor" feature implemented in the Waveforms GUI? We have a 5 axis sensor that I would like to read at very consistent read rates. Below is a test case I have done using the a script in Sensor tab. I found that the longer the iterations, the outcome is worse....i.e. timing is not correct.
-
@malexander Could you help with this ?
-
Yes, that's the page where I took it... I'll try force it under /usr/lib64...
-
Yes, that's the page where I took it... I'll try force it under /usr/lib64...
-
attila started following AD3 and Waveforms and higher voltages
-
Hi @sng2024 The AD3 scope input have a high range of ~50V peak to peak and with offset adjustment can read +/-50V The probe attenuation can be specified with the Probe option under each channel option.
-
Hi @scorbetta I was suspecting to find multiple variants from this library, but it finds only one. I don't know why it is for you installed in /usr/local/lib64 Have you downloaded it from our site ? https://digilent.com/reference/software/adept/start The location shouldn't matter but it is strange since the adept.runtime...deb uses /usr/lib64
-
Hi @Kevin.C The betas are signed with the same key as a recent Adept Runtime release, here: https://digilent.s3.us-west-2.amazonaws.com/Software/Adept2+Runtime/2.27.9/digilent_public_key.asc. We've only recently started signing these installers. Your questions are very appreciated and should help us make sure these downloads are as clear as possible. Thanks, Arthur
-
attila reacted to an answer to a question: Impedance analyzer to Analog Discovery 2
-
Visual Studio SDK 32 vs 64 bit C project, and "readme.txt" errors
attila replied to gcb's question in Test and Measurement
Hi @gcb See the reply on your earlier post: -
def.framework will not install on Sonoma 14.4.1 Apple M3 Max
attila replied to SergeLafontaine's question in Test and Measurement
Hi @SergeLafontaine The latest version is notarized, it should pass security: -
PostView - Active Device not recognized
Jay Bland replied to Jay Bland's question in Measurement Computing (MCC)
Thank you for letting me know, I'll check the machine to make sure it's completely updated. If that doe not resolve the issue do you have any other ideas? -
Impedance analyzer to Analog Discovery 2
Kyoko J replied to Kyoko J's question in Test and Measurement
Hej @attila Thank you and we will look into them.- 2 replies
-
- impedance analyzer
- connector
-
(and 2 more)
Tagged with:
-
Visual Studio SDK 32 vs 64 bit C project, and "readme.txt" errors
gcb posted a question in Test and Measurement
I just downloaded and installed the WaveForms program, including the SDK. The 'WaveFormsSDK/samples/c/readme.txt' file has instructions for creating a Visual Studio project using the SDK. But these instructions are confusing. I need some clarification. * It only references Visual Studio 2013. I assume that newer versions of VS are OK to use? I am using VS 2022. * It says to create a new project via "File/New Project/Win32 Console Application...". Do I have to use 32 bit, or can I use 64 bit? * The statement in the file " - Copy C:\Program Files (x86)\Digilent\WaveFormsSDK\lib\x86\dwf.lib (or from x64 for 64bit application) to your project folder." certainly seems to imply that a 32 or 64 application is acceptable, as long as you copy the appropriate "dwf.lib" to the project. * I created it as a new 64 bit console project, but it crapped out compiling it because the 'sample.h' file did not have an 'ifdef' case for _WIN64. So I added a case for this and then one of the sample programs would compile and run. * The statement "- Add Existing Items/ device_enumeration.cpp, samples.h, dwf.h" should read "- Add Existing Items/ device_enumeration.cpp, sample.h, dwf.h". * The statement " - Add Existing Items/ device_enumeration.cpp, samples.h, dwf.h" refers to a file "dwf.h" that you never mentioned needed to be copied to the project directory. You should have mentioned this needed to be copied, and where to get it from. I figured it out. * There is also an 'if defined(WIN32)' statement in "dwf.h" file. It seemed to work even without changing this. So bottom line - is a 64 application supported, or should I just stick with 32 bit? I prefer the speed of the 64 bit version, but I guess either is OK. -
cp3 joined the community
-
Hello @Przemek. Please investigate what changes were made recently to your application, i.e. OS update/upgrade, new host PC, updated DT software, IT changes to PC. What type of environment is the DT9805 module in during operation, to suspect a broken connection? Please test the DT9805 with Data Translation's QuickDAQ application on that system. Any issues? Please test the DT9805 with a different PC and Data Translation's QuickDAQ application. Any issues? If you have a backup DT9805 module, please swap the modules and retest. Please swap out the USB cable and retest. If you use a USB hub, retest with an externally powered USB hub or connect the DT9805 directly to the target system. Regards, Fausto
-
Automation support for MCC USB-2416-4AO
Fausto replied to metalhouse's question in Measurement Computing (MCC)
Hello @metalhouse. The DAQami software does not support an automation process. Take a look at the DASYLab software for your application. If you are a LabVIEW user, then you can use Universal Library for NI LabVIEW™ with the USB-2416-4AO and LabVIEW. Regards, Fausto -
Hello @msmith. The MCC USB-3101FS has a low output impedance of 0.1 Ohms and an output update rate up to 100 kS/s per channel. The MCC PCIe-DAS1602/16 has an input impedance of 10 MOhms and an aggregate sampling input rate of 100 kS/s, since the analog inputs are multiplexed to the ADC. What is the output rate and output range of the signals from the MCC USB-3101FS channels? Configure the analog input channels on the MCC PCIe-DAS1602/16 board for differential mode. What is the input range of the analog input channels on the MCC PCIe-DAS1602/16 board? Choose a narrow range. Regards, Fausto
-
mitchellc30 reacted to an answer to a question: Dasylab 13 to 2022 upgrade DAQ communication Issue
-
Dasylab 13 to 2022 upgrade DAQ communication Issue
mitchellc30 replied to mitchellc30's question in Measurement Computing (MCC)