JRys

We have an example that demonstrates using the device without having to run InstaCal. It is DaqDevDiscovery01, in the following folder: \Public\Documents\Measurement Computing\DAQ\C\Sample32\. If you lack examples, reinstall InstaCal from our CD download. You will still need to install InstaCal because that is how our drivers and DLLs are installed.

The QuickDAQ software has two upgrade paths, the FFT and the Advanced FFT option. To try out these features, we enable them for two weeks after the initial installation. Purchasing the FFT Analysis option will enable the digital filter. The datasheet shows a breakdown of the features.

I'm glad to hear that it's working.

Here is a LabVIEW vi (attached below) that maintains a one minute buffer (6,000 scan at 100 Hz) that is constantly being updated with new data. It always has the most recent data. A loop counter counts to 6000 x 6 to enable the file write operation. Therefore, every six minutes, one minute of data is written to the text file. After one hour, the file holds 60,000 rows of data. CircularBuffer.vi

DAQami has not included support for the encoder channels (ctr 2 & 3). Please consider upgrading to the DASYLab software for support. If you know the C or Python languages, you could create a custom program, too.

Yes, they can be configured individually. When configured for thermocouples, use the 50 or 60 Hz Data Rate filter for best results. Use InstaCal to configure the channels unless you use the DAQami software.

Calibration reports, as well as data, were kept from being made available. Some customers do require data to meet specific requirements. For those, we recommend sending it to a calibration facility for verification with data.

AGND and GND are connected internally on the USB-1608GX. To minimize ground current noise, AGND is routed to keep digital switching ground noise away from sensitive analog measurements. For example, you could control a relay using a transistor to sink current. The transistor should be connected such that current flows into the GND ground trace. What little current flows from analog input signals will use AGND, and then both GND and AGND combine and are connected to the USB ground.

There is much more to making it work than just including the mccdaq.dll. There's also the cbw32 and cbw64 dll, and you need to be able to install a device driver. Instead, leave the mccdaq.dll out and compile the program to an exe. On the target PC, install InstaCal first, and then your program should work. If the program does not use device discovery, then also run InstaCal with the USB-201 attached so that it gets added to the board list. Lastly, delete any mccdaq.dll files that you may have installed previously. Our files should be in one place only, and that is C:\Program Files (x86)\Measurement Computing\DAQ\.

The requirement to use the MCC 134 is a Raspberry PI 3 or 4, and the Raspbian OS. We have not released support for the Bookworm version, so Bullseye is recommended. For Ubuntu, you could use our Linux driver, uldaq, and one of the supported USB devices, like the USB-TC. https://github.com/mccdaq/uldaq

MccMinilab.dll is not an MCC library file. It's likely from another company that built a software product around miniLab-1008.

The manual Labeling drop-down setting displays the current date-time on the axis. The Manual Label check button sets the label spacing. The only options are block number, seconds since measurement start, time, and date-time.

To find out what Raspberry PI resources are used by the mcc172, review the Interface Specifications section in the following datasheet: https://mccdaq.github.io/daqhats/_static/esmcc172.pdf

This is the closest one I could find: https://www.phoenixcontact.com/en-us/products/solid-state-relay-module-emg-17-ov-ttl-24dc2-2943259?type=pdf As shown below, you could also use a MOSFET transistor to control a solid-state relay.

MccMinilab.dll is not an MCC library file. It's likely from another company that built a software product around miniLab-1008.

The WBK16 was discontinued, and technical support is no longer provided. Below are the legacy downloads for the software and user manuals: https://files.digilent.com/downloads/iotech_software/WaveBook_&_StrainBook/waveviewsetup.exe https://files.digilent.com/manuals/wbk16.pdf https://files.digilent.com/manuals/wavebook_series.pdf https://files.digilent.com/manuals/waveview.pdf https://files.digilent.com/manuals/waveview_wavecal.pdf

Size is one different thing. The PCI-DIO96H is a longer board. The two boards have identical 50-pin connector assignments, the same port numbering scheme, and the same programming functions. For the majority of our PCI-DIO96 and PCI-DIO96H customers, the two boards operate the same. However, if your application bypasses our driver and writes directly to the hardware registers on the board, the two are incompatible. The following are the board register maps. https://files.digilent.com/registermaps/RegMapPCI-DIO96.pdf https://files.digilent.com/registermaps/RegMapPCI-DIOxxH.pdf

If the same setup worked with DASYLab, it should work with LabVIEW because they both use InstaCal to configure the channel input mode. Which input mode are you using and what is connected to channels 6 & 7?

The tech support hotline was taken down more than a year ago. I looked into the DASYLab 2022 Python script module, and it appears to have a problem loading modules such as CoolProp and others such as Numpy and Scipy, which are widely used. The modules have no problem installing into DASYLab's Python environment; it is just that the Script module crashes when trying to load them via the Python code file (script). As soon as there is more information, I will update this thread. In the meantime, if you have the CoolProp .whl package for Python 2.7, you could use DASYLab 2020 instead. Use your DASYLab 2022 serial number to activate it.

I connected signals to channels 6 & 7 and connected one of the digital outputs to the counter input, and your vi is responding appropriately. This leads me to believe you have a grounding issue or channels 6 & 7 are wired incorrectly.

InstaCal does not need to be run every time you run LabVIEW. I was only trying to clarify that you run it once to configure the inputs. Once that's done and InstaCal is closed, then run LabVIEW. Attach a simple LabVIEW VI demonstrating the problem, and I'll look at it.

DASYLab 2016 & 2020 use Python 2.7. However, DASYLab 2022 switched to using Python 3.9.6 because Python 2.7 is no longer maintained. Can you try the following: 1. Download CoolProp-6.6.0-cp39-cp39-win32.whl from https://pypi.org/project/CoolProp/#files to C:\Scripting\. 2. Update PIP in the DASYLab folder by doing the following: Open a CMD window as Administrator (type CMD in the search box, then right-mouse Command Prompt, and select "Run as Administrator"). Change the directory to the DASYLab Python folder: cd C:\Program Files (x86)\DASYLab 2022.1_en\python Run the following command: python -mpip install --upgrade pip 3. Install CoolProp using the following command: python -m pip install c:\scripting\coolprop-6.6.0-cp39-cp39-win32.whl Follow the steps the previous employee had left for installing the script package.

To be clear, InstaCal only needs to be run once to set the input mode to eight or sixteen channels. After that, you simply run LabVIEW.

Instead of probing the input terminals, they could use a resistor to simulate a temperature. Take, for instance, this thermistor profile. For this 10k thermistor, a 270 ohm resistance should return a temperature close to 134 degrees C. Use a 1% or 0.1% resistor for best results.

It should work if the inputs are set to single-ended mode, and your actuator requires less than 5mA to move.