DAQman

Support for Raspbian Bookworm and the Pi 5 is still in testing, and no release date has been given.  

The MCC DAQ HAT boards do not come with a ready-to-use software program. Instead, examples are provided for C and Python coding. Therefore, I would recommend some programming experience and familiarity with the Linux operating system. If you're comfortable with C, our MCC-118 data logger example displays a couple of channels graphically and saves the data to a file. 

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. 

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

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

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. 

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.

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

The maximum current the Analog Output can provide is 5mA, so the funny behavior is most likely because you are overloading it. Review the sensor's datasheets to determine the required current. 

There's no protection other than an ESD suppressor. The analog outputs come directly from the AD5623 D/A chip. 

The file is attached below.
IOtechPDAQ5x.14.0.0.0.en.dlp

Hello,
Two installations are required to get the PersonalDaq/50 series to work in DASYLab. The first one is the Personal DaqView software, which installs the drivers. Here’s the installation for that: https://www.mccdaq.com/downloads/iotech_software/PersonalDaq50_Series/pdaqviewsetup_x86_x64.exe
After installing the above application, Plug the PersonalDaq/55 into the USB port and wait at least 30 seconds and check the green power LED next to the USB connector – it must be on. If it is not, then it is not compatible with your Windows 10 system. A few customers were able to fix their systems by updating the BIOS drivers. My new Dell laptop didn’t work at first until I updated it. I was surprised to find 14 critical updates.
Next, copy the attached file to C:\Program Files (x86)\DASYLab 2020\pool\packages\. Run DASYLab’s Configurator 2020 utility and select the Packages page. Locate & open Unsupported Drivers and enable IOtech PersonalDAQ/5x Series.
Restart the computer and you should be all set. You will find the PersonalDaq/55 inputs on the following menu: ModulesInputs/OutputsPersonal DAQ5x
Best regards,
Measurement Computing

Posted on behalf of a customer
Hardware: DAQ 56
Software: Dasylabs 2020
Operating System: Windows 10

Problem Description:
We are using the DAQ 55/56 data acquisition interface. I've installed all of the driver recommended for the device and Dasylabs but it will not recognize the IOtech DAQ 56. Please advise. Best Regards
 
 

The +V terminal found on the USB-2408 can source up to 10mA, which is not enough for your application.
The video used a 700-ohm load cell to keep the current under 10mA.  Utilizing a signal conditioner to power it and amplify the signal is the correct approach. 

Your wiring diagram looks correct for channels 0 & 8. If you wanted channels 0 & 1, connect the second to pin 7 instead of 2. 
Ideally, all nine load cells should be powered by a single supply to reduce the risk of a ground loop.

Please have a look at the multi_hat_synchronuous_scan.py example. It demonstrates using two boards. The comment section provides a good description of its operation. You don't have to use an external clock & trigger, but it helps align the measurements from each board.
The maximum sample rate is dictated by the aggregate rate from all the boards. The data from each board is transmitted via a single SPI bus rated at 320k Sample/s.  Fifty-two channels times 5000 S/s put you under the maximum but doesn't leave a lot of room to do other things like write to files and update displays. 

The PCI-DIO24 and USB-DIO24H/37 are configured the same. They use the same parameters and functions to set port directions and to read/write them. However, the PCI-DIO24 is a few hundred times maybe a thousand times quicker. It isn't easy to provide further assistance without knowing what the software is doing.
 

I'm afraid there's not much to go on. If you've upgraded from an old version of Windows to Windows 10 or 11, InstaCal should be updated, too. 
 

Digilent/MCC cannot provide technical assistance for the MatLab Data Acquisition Toolbox for the MCC products. This is because MCC was not responsible for its creation. To gain a better understanding of what their library is doing, please reach out to the technical support at Mathworks.
 
 

You guessed correctly. The PDaqView Excel add-in is a 32-bit VBA application, which requires an Excel version that is 32-bit. You may find the following helpful:
https://support.microsoft.com/en-us/office/choose-between-the-64-bit-or-32-bit-version-of-office-2dee7807-8f95-4d0c-b5fe-6c6f49b8d261#:~:text=The 64-bit version of,Install Office on a PC.

Close the Open Layer control panel utility and restart it as an administrator. For example, right-mouse click C:\Windows\SysWOW64\dtolcpl.cpl and choose the Run as Administrator option to run it as an administrator. This will enable the Edit Name button, allowing you to give each device a unique name. After doing this, review the Open Layer example for multi-device control. It can be found in:
C:\Program Files (x86)\Data Translation\DotNet\OLClassLib\Examples\HardwareSpecificExamples\MultiDeviceSynchronizationAI\.
There's a function GetDeviceNames in Form1_Load that retrieves the names, and GetDevice(name) in the initializeButton_Click function that creates the device object.

I attached the wrong version of your worksheet. Attached is the correct worksheet.
Vibration-Oct2023-V2.DSB

If I were to guess, there could be something wrong with the Windows Registry, specifically the DASYLab 2016 keys and values.
DASYLab 2020 and DASYLab 2022 are the two versions we currently support. My recommendation is to install DASYLab 2022 using the Evaluation option. If it has the control module enabled, then the solution is to purchase a new copy.
 

1. DASYLab uses the Double data type, so there are plenty of digits to choose from. If you're using a Digital Meter module, there is a decimals field; under Options, there's a Digits field. Set Digits to 12 and Decimals to 4. If you're writing to a CSV or Text file, there is a setting in file Options to set the number of digits per channel.
The resolution numbers you listed are theoretical. Please look at page 19 in the user manual for absolute accuracy and noise specification. 
2. The DASYLab DDF format is very efficient, and you can choose between 4-byte floats or 8-byte doubles as the data type. You could do a rough calculation of channels * data type * block size to determine how many blocks it will take to come close to the max file size. The Multi-File setup will allow switch files based on the number of blocks. 
3. DASYLab buffers files data and writes it to disk periodically. To force, there is a Save File Every setting on the Write Data module setup dialog.

If the software is DAQami, DASYLab, TracerDAQ, or LabVIEW, the time between channels is determined by the sample rate. If you run it at the maximum aggregate sample rate, the time between the channels is 1uS or 1 / 1 Mhz. For example, if there are eight channels being used and the sample rate is 1000. In this scenario, the A/D is sampling eight times faster, so the time between channels is 1/8000 or 125uS. If you've created your program, the same holds if the BURSTMODE scan option is not used. BURSTMODE forces the channels together so that channel-to-channel time is 1uS.