All Activity

@malexander 1. Nothing is attached 2. The error shows up immediately 3. The output is empty. Here's the output of `nm -D --defined-only /usr/local/lib64/digilent/adept/libdmgr.so | grep -i dmgr` instead: 0000000000001ae8 T DmgrCancelTrans 0000000000001960 T DmgrClose 0000000000001bf8 T DmgrClrFsadm 0000000000001b5e T DmgrDvcTblAdd 0000000000001b76 T DmgrDvcTblRem 0000000000001b8e T DmgrDvcTblSave 0000000000001976 T DmgrEnumDevices 000000000000198e T DmgrEnumDevicesEx 0000000000001a3a T DmgrFreeDvcEnum 0000000000001b9a T DmgrGetDtpCount 0000000000001ba6 T DmgrGetDtpFromIndex 0000000000001bc4 T DmgrGetDtpString 0000000000001a1c T DmgrGetDvc 0000000000001c70 T DmgrGetDvcFromHif 0000000000001a04 T DmgrGetEnumCount 0000000000001a96 T DmgrGetInfo 0000000000001908 T DmgrGetLastError 0000000000001c4a T DmgrGetSysInfo 0000000000001abc T DmgrGetTransResult 0000000000001b1a T DmgrGetTransTimeout 00000000000018bc T DmgrGetVersion 00000000000019ec T DmgrIsEnumFinished 0000000000001914 T DmgrOpen 0000000000001934 T DmgrOpenEx 0000000000001be2 T DmgrSetFsadm 0000000000001a46 T DmgrSetInfo 0000000000001c8e T DmgrSetLastErrorLog 0000000000001cac T DmgrSetLastErrorNoLog 0000000000001c24 T DmgrSetSysInfo 0000000000001afe T DmgrSetTransTimeout 00000000000019c2 T DmgrStartEnum 00000000000019f8 T DmgrStopEnum 0000000000001cc2 T DmgrSzFromErc 0000000000001c0e T DmgrTstFsadm 4. Here's the output total 12 drwxr-xr-x 3 root root 4096 apr 17 17:49 . drwxr-xr-x 14 root root 4096 ott 19 11:03 .. drwxr-xr-x 3 root root 4096 apr 17 17:49 digilent lrwxrwxrwx 1 root root 42 gen 2 14:22 ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2

Hi @AndyMessier It can generate waveform or pattern from device buffer up to system frequency sample rate or higher, by skipping some, see AnalogOut_Custom.py example The system frequency, for all instruments can be adjusted with DwfParamFrequency. In play mode the data is streamed, transferred in chunks from computer, limiting the sample rate to 1-2MHz The newly added idle hold option keeps the last output value in done state, with finite run time.

Hi @malexander WF links to libs. My testing with Ubuntu 22 was also successful.

Hi @bobql 1. The Sensor tab on execution first calls the initialize function, where sensor register, global variables, file initialization... can be performed. 2. Calls the software loop function, without executing it in the device, to build a pattern with the transfers, like for CS, CLK and MOSI. 3. Starts to generate this pattern with hardware timer at the specified rate and iterations, and at the same time it captures the transfers. 4. Decodes the received MISO bits by software call of loop function, without executing it in the device. 5. At the end calls the finish function, where sensor register shutdown and file finalize can be performed. The software timing of the software function calls in not precise but the pattern generation is, which are basically loop function calls in hardware. Similar can be done in SDK. Pattern with digitalout functions, see DigitalOut_SPI.py example, repeat can be set to 'infinite'. Steps 3-4 can be merged, to receive and decode simultaneously, see DigitalIn_Spi_Spy.py. In Sensors tab these are separate since the sw loop execution takes some time and it would be a bottleneck at high rates.

It is not working now also. Serial NO:00683966. can you provide the solution to make it work again?

can i program the cortex a9 processor in zybo using code composer studio?

Hello @fmendoza711. The WebDAQ 504 supports saving data from all four input channels to a SD media, up to the maximum sampling rate of 51.2 kS/s per channel. Consider a SDXC card (U3, A2, V30 or newer) with minimum write speeds of 90MB/second and a supported capacity up to 2TB. Format the SDXC card for an ext2/ext3 or ext4 file system. Regards, Fausto

@metalhouse, On the USB-2416-4AO, the DIO# channel(s) can be configured as digital output(s) via the software application. Regards, Fausto

Hello @sathvikum. Please review the following forum post. (Note: the master branch for the MCC DAQ HAT Library for Raspberry Pi will be updated to v1.5.0.0 in the near future.) Regards, Fausto

Hello I'm encountering a error while installing the files in the raspberry pi 4 B's terminal where I'm not able to detect the MCC DAQ HAT 128 board even though i follow the steps in which is listed in the installation guide ( https://mccdaq.github.io/daqhats/install.html ) . So please help me out with the issue thank you

I have been writing scripts in Python for the AD3 but I'm looking for some general advice on how to use the Arbitrary Waveform Generator Function. I see that it can run at 125Msps .. but what is the max memory data-points? Is there an example of how the memory can be filled from a file? (I see some .wav example but I think the sample rate is encoded in those? I want to define that at the full rate). In my application I'd like to play a waveform and hold the last sample indefinitely until I decide to play another waveform. Any high level advice on how I could do this or what sample files are the closest to this? Many thanks!

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.

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

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

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

@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

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

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

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