JRys

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.

The USB-2637 was designed to work with low-impedance signals. The best accuracy is achieved when the impedance is kept below 100 ohms. The main reason for this is the internal capacitance of the analog multiplex front end. Each time the board selects a different channel, a tiny charge passes through this capacitance to the next channel. A low-impedance source dissipates the charge, whereas a high-impedance source does not.  The higher the impedance, the longer the time constant. One solution is to buffer it to convert the high impedance to low. Another is to enable a channel connected to the ground after a channel with a high-impedance signal. The grounded channel will dissipate the charge before it can be passed on to the next channel with a high-impedance signal. 

Disconnect all but one sensor. If the sensor is externally powered, disconnect the laptop power supply. Doing this should produce a suitable measurement. Next, reconnect the laptop power supply and check for drifting. If it does, you could be looking at a ground loop. If it doesn't, connect another sensor and test for drifting. For minor ground loops, differential inputs are preferred over single-ended.

The USB-2627 input impedance is 1 G ohm and changing it is not possible. Instead buffer the signal. Use a voltage-follower op amp configuration to change your high impedance signal to low impedance. 
The board also uses analog multiplexers to expand the number of channels. High impedance signals will cause cross talk between channels and this could explain what you're seeing. A trick some use is to turn on an empty channel (connected to ground) after each high impedance connection. 
 

We offer no Linux support for the USB-1604HS series devices. It's strictly a Windows OS device.

The USB-1608FS-Plus-OEM board has a slot on all four corners to mount the board. The USB-1808X-OEM has holes instead of slots. Refer to the user manual for the mechanical drawing. 
https://files.digilent.com/manuals/USB-1608FS-Plus-OEM.pdf
https://files.digilent.com/manuals/USB-1808X-OEM.pdf
There is no OEM version of the USB-1604HS-2AO.
 

For calibration, please get in touch with sales@digilent.com indicating the devices you want to calibrate. They will email you a quote that is used to order the service beforehand.

Use  pulse_out_start and pulse_out_stop. There's an example called pulse_out.py in the Console examples.

 

The Universal Library is incompatible with the dot net core, so you are relegated to using dot net framework 4x for the time being.
 

You can use two DT9834 and synchronize them using the external D/A clock input, which could be driven by a counter channel's output. I believe you would need to change out the timing vi for a DtOLTimingSetOutput.vi because it provides the external clock option. 

You are going to be successful if you know what your sensors output. The USB231 measures voltage. Your sensors may output voltage or current. You mentioned at the beginning that you have a distance sensor that outputs 4-20 milliamps (mA). Because we measure voltage, not current, we use a resistor to convert the current to a voltage. Many customers use a 250 ohm resistor because that results in a voltage between 1 & 5 volts. The USB-231 must be in differential mode to measure the voltage drop across the resistor.
Your sensor measures 0 - 200mm; at 200mm, the measurement is 5 volts (20mA * 250). At zero distance, the measurement is 1 volt. The scale factor is 200 / (5 - 1) or 25. The offset is 0 = 1 * (200 / (5-1)) + b, where b is the offset. Rearrange the equation, and you get b  = -25. So the scale equation to get distance is f(x) = 25x - 25, where x is the measured voltage.
Here's a quick read on 4-20mA sensors https://digilent.com/reference/daq-and-datalogging/documents/current-sensors

It is up to you to modify the program to convert the voltage readings to something more meaningful, like temperature or distance. For example, a sensor rated at 100 with a 4-20mA (1 to 5 volt) output can be scaled by multiplying the voltage by 25 and subtracting 25, assuming you're using a 250 ohm shunt resistor.