JRys

All the MCC devices that have analog output work the same way. None of them have onboard memory for the waveform. It was one of the ways we kept our costs low.

Hey Davide, I ran through the Zynq server guide using my ArtyZ7, to get the echo server working. Could you create a new Vitis application based on the attached xemacpsif_physpeed.c file? Copy it to the same place as directed. Start Vitis and create a new echo server application based on your design.xsa file. Go into the Board Support Package under zynq_fsbl and enable lwip213. Once this is done, rebuild the design wrapper and, when done, build the project. Please let me know if you have better results. Thanks, John xemacpsif_physpeed.c

An underrun condition means the driver is being prevented from updating the 231. A similar condition on the input side is overrun. The waveform is stored in the USB driver's memory, not on the device. An interrupt occurs continuously once the cbAOutScan is called, telling the driver it needs more data until cbStopBackground. An underrun condition happens when the USB driver does not handle the interrupt, which can occur if a Windows Process hogs the system. Perhaps a security scan. What is interesting is it should happen with the DAQami software, too. If it doesn't, then I'm not sure what it is. I ruled out a hardware issue because you have two devices doing it. See if you can rule out the PC by trying another.

The Data Translation software is located here: https://files.digilent.com/#downloads/DTSoftware/

You could use our DAQami program to test the device. Enable an analog output channel and place it on an Output display window. Right-mouse click the slider control, and for Signal Type, select Waveform. How long have you owned these devices, and which version of Windows are you using?

PostView is used to display data captured by Personal DaqView. Captured data will consist of a binary .bin file and a header file .dsc, which has the number of channels, input ranges, sample rate, and so on. Both files must be present for PostView. It can be started from the Personal DaqView GUI or by itself. However, when it is started from Personal DaqView GUI, it works only if data was recently captured. Both programs were not upgraded to Windows 10 or 11, so you must run them with the Run as an administrator Windows start option. Information about using the programs can be found in the following user manual: https://files.digilent.com/manuals/personal_daq50_series.pdf

Personal DaqView is for the PersonalDaq/54, 55, & 56 only. DaqView, a different program, is for DaqBook/2000, DaqLab/2000, DaqBoard/2000, DaqBoard/3000, and PersonalDaq/3000 series products.

Please see our ULAO04 example in \Public\Documents\Measurement Computing\DAQ\VBWIN\. It outputs a continuous square wave. I can't run the VB6 version because VB6 is too old and not supported on Windows 10 or 11. I ran the same example in VB.NET form and did not experience a program starting the waveform on a USB-231.

The software was never officially supported for Windows 10, but some customers have made it work. It typically works best if you have a computer purchased with Windows 10. If the computer is old and upgraded to Windows 10, you may have to go to the manufacturer's website and update your BIOS and drivers. If the computer is quite old, Windows 10 support may not be available. After you install the Personal DaqView software, plug the device in and watch the power LED. If it stays on for about 20 seconds and goes out, that means the computer lacks the appropriate support.

You can use two or more USB-3101FS, but there isn't a way to synchronize them. You could use two USB-1208HS-4AO to get up to 8 analog outputs. The two can be synchronized with an external trigger and a clock, however, they are 12-bit outputs, not 16-bit.

We don't provide schematics, hardware details, or technical support for such an application. But all the information needed to write the AD5623 DAC is in mcc152_dac.c in the daqhats library.

The USB-3104 cannot output a 1000 Hz sine wave. It has a low update rate of 100 Hz / Number of channels. The USB-3101FS is a high-speed unit.

It could be board zero is experiencing a hardware failure. Could you run the MCC DAQ HAT Manager app, typically found under Accessories, and test each board?

Thank you for the test results. It looks like there is an issue with the output circuitry. Please private message me with your contact information, device serial number, and sales or purchase order number.

Measurement Computing did not offer protective cases for their OEM-style boards.

The maximum input frequency is 10 MHz. Multiple this number by 60 to determine the maximum RPM - 60 million revs per minute. Some of our software support places artificial limits on the speed at which the measurement can be read. For instance, our DASYLab software allows for only one read per second. Our LabVIEW support limits the sample rate, too. Because of these limitations, I recommend using Python or C to create your own app and take full advantage of the features found on the USB-QUAD08.

The note about grounding is because the Raspberry Pi power is essentially a floating measurement device. Many IEPE sensors are isolated from their case, making them floating sensors, too. Because of this, they can be more susceptible to noise. Connecting to a common earth ground will help.

When using charge mode sensors, your system noise will be a function of the cable length. It is for this reason that IEPE sensors are more desirable. On the other hand, charge mode sensors can withstand higher temperatures because they lack internally sensitive electronics. There are charge mode amplifiers that convert the signal to IEPE. A charge mode amplifier can shorten the cable length if your application is at a high temperature.

The Counter inputs found on the USB-2416-4AO are totalizing counters. In other words, they increment their count each time they get a pulse. Our software support for DASYLab and LabVIEW can measure some frequencies by determining the count difference every second. Frequencies below 5Hz can be challenging to read because the measurement will have few counts. Let me know the make and model of your pressure sensor as well as other signals you plan to hook up.

You could upgrade your computer to something really really fast, or take a different approach. The attached Python script records data to a binary file and after the data collection is finished, reopens the file for reading. Writing a binary file is much faster. So, I'm suggesting that you record to binary and after it is done, make the CSV when time is less critical. If you capture more than one million scans, you could make series of CSV files instead of one big one. a_in_scan_file.py

DASYLab primarily works with National Instruments PC based daq products, like the USB-6212. It does not have support for the cFP-2200 real-time controller module.

Unfortunately, we don't have the resources to debug your program and it sounds like you have done exhaustive testing. If I had your hardware setup, I would make a worksheet with just the COM modules connected to a Digital Meter or List module. Set the Master COM module to Output every measurement value immediately. This is a setting in Options->Data Output. I might also be tempted to connect a Counter Module to each COM channel output. Set the counter to count samples. You may find that most of the devices are returning consistent data, but one or two are not. Because of the way you have the worksheet set, it must receive ten samples from every device to output a block of samples.

We do not have a Python module with routines to convert a .wdd file. The following is information about the file format and below is a link to a utility to convert the files. https://files.digilent.com/downloads/WebDAQ/WebDAQFileConverterUtility/1.0.0/WDFileConverterSetup.exe

The attached zip file contains the available drawing files. MCC128_CAD.zip

Please get in touch with the support team at Physitemp to resolve the issue. Our quickest thermocouple reader is the E-TC, which can return four samples/sec/channel and can be controlled with the DASYLab software.