Fausto

Hello @ChristianW. UL error code 8 - An analog output function or method was called with a board number that referred to a board that does not have an analog output (D/A). I tested a MCC USB-3106 with a RPi 4 (Debian 12, 64 bit) and the AOut example from libuldaq-1.2.1, but I did not get error code 8 with initial tests. Here's what I did to reproduce the error code 8. First, I tested the uldaq example, a_out.py, which worked and did not generate an error code 8. Then, I retested the python example again with a value outside of the voltage output range to cause the example to fail. Next, I retested the libuldaq-1.2.1 example, AOut, and that's how I was able to generate the error code 8. Cycling the USB cable connection and retesting the AOut example seemed to have cleared the issue. Does cycling the USB cable connection resolve your issue? What other devices are you using? Do you have other USB-3104 modules with the same issue? If so, please test those USB-3104 modules with a Windows OS and MCC's InstaCal utility application or MCC's DAQami application. Regards, Fausto

Hello @Belette. Besides referencing the USB-1208LS User's Guide, take a look at the Universal Library Help for the device's supported functions and example programs. Also, the Universal Library C examples are saved to the C:\Users\Public\Documents\Measurement Computing\DAQ\C\Sample32 directory. Regards, Fausto

Hello @m3rd. If the drivers were successfully installed, then the LED should be on when you connect the DT9813-10V module to the USB port. Screw terminal 20 is the USB +5 V Out and screw terminal 19 is Ground. With the DT9813-10V module connected to the target system, please provide screen captures from your system, as I have provided below. From Windows File Explorer: From the Open Layers Control Panel applet in Windows Control Panel: From Windows Device Manager: Regards, Fausto

Hello @Engineer_Steve. You might have seen that the USB-1208LS is supported by Warren's Linux drivers, but not the UL for Linux Library. So you will need both libraries if you continue to use both devices. Supported MCC hardware for UL for Linux Regards, Fausto

Please send me a private message with the serial numbers that are failing in InstaCal, so we can discuss replacements.

You need to extract the files. Please reach out to your IT admin.

@Scott D, Thank you for the responses. Please update InstaCal and retest without any external signal connections. Do your USB-1024LS modules pass the Internal DIO tests in InstaCal? If all ports pass, then exit InstaCal. Connect all terminals of Port A to screw terminal 30 (PC+5V) on the USB-1024LS. Run your application for Port A. Any issues? Repeat the test for Ports B and C. Any issues? A port channel should always have a connection to either ground or a voltage level greater than 2 V (according to the device's specification for an input high voltage). All digital lines are pulled up HI via 47 KOhm resistors, so they will read HI without any signal connected to the terminal(s). If there's an issue with your relay, then that may be causing the issue with the digital inputs. Regards, Fausto

Hello @Saha. Please reference the following forum post. Regards, Fausto

Uninstall QuickDAQ from Windows Control Panel - Programs and Features. Restart your system and then reinstall the Data Translation OMNI software, which includes QuickDAQ. NOTE: You will need to unzip the downloaded file in order to install the software. Launch QuickDAQ after the installation has completed. If you still have an issue, then have your IT admin reinstall the software. Regards, Fausto

The USB-1608G does not support pulse width measurements, but the MCC USB-1808X does.

Hello @Scott D. What is the history of each USB-1024LS module (i.e. new, used, worked previously)? Which Windows OS and InstaCal versions are installed on the target system? Which software application are you using with the modules? Have you tested the modules on a different Windows system with InstaCal? Are you connecting the USB-1024LS module to a USB port on the target system or using a USB hub? What type of signal and voltage level are you connecting to the USB-1024LS module? What are the serial numbers on the backside of the USB-1024LS modules? Regards, Fausto

Hello @Engineer_Steve. Did you install libusb as mentioned in the Prerequisites instructions on the GitHub repo for MCC Universal Library for Linux (uldaq)? I was able to use an USB-1208HS-4AO with the uldaq examples a_in.py and a_in_scan.py; no errors. Please test that example. USB-1208HS-4AO User's Guide Supported MCC hardware for UL for Linux Universal Library Python API for Measurement Computing DAQ devices Regards, Fausto

@m3rd, The AppData folder is a hidden folder. If your user login has sufficient rights, you can enable the File Explorer to show hidden items (files and folders). If you do not have sufficient rights, then contact your IT administrator to enable the hidden files and folders. Afterwards, delete the QuickDAQConfiguration.xml file and launch QuickDAQ. Does the Device Selection window appear? Please provide screen captures of the Open Layers Control Panel applet and QuickDAQ's Device Selection window. Regards, Fausto

Hello @Zachkeeb104. The counter input channels on an USB-1608G are event counters. They do not measure duty cycle. Which daq device did you use successfully with LabVIEW? Please provide a screen capture of your working semi period option scenario. Regards, Fausto

Hello @STuson. The MCC 128 DAQ HAT has a 16-bit A/D and four analog input voltage ranges (+/-1 V, +/-2 V, +/-5 V, +/-10 V), while the MCC 118 has a 12-bit A/D and only one analog input voltage range (+/-10 V). If your voltage signal range is 0 - 0.6 V, then an input range of +/-1 V, using a MCC 128, will give you better resolution. Some lite reading. https://digilent.com/blog/accuracy-precision-resolution-and-sensitivity-what-do-they-mean/ Regards, Fausto

Hello @Sirius. That will work. The USB-1608GX has an analog input voltage range up to +/-10 V. How and what were you intending to connect to the digital channel? Regards, Fausto

Hello @m3rd. The other option to use in order to determine if your DT9813-10V device is detected by your Windows system (which OS version are you using?) is to use your Windows Taskbar's search field, enter Control Panel and click on the search result to open it. Select View by: Large Icons. Scroll and click on Open Layers Control Panel (32-bit). Click the OK button if you get the following message. Does your DT9813-10V device appear in the list? If the device does not appear, please test your DT9813-10V with a different USB cable connected directly to a USB port on the host system (no hub), as well as with another Windows system. If your device is in the list, then click the Close button. Back in the All Control Panel Items window, click on Programs and Features. Click on the Publisher heading to sort the column. Scroll through the list until you find Data Translation. Which version of QuickDAQ is installed? Next, open your Windows File Explorer. Browse to the C:\Users\{username}\AppData\Local\Data Translation\QuickDAQ\Config directory. Delete the QuickDAQConfiguration.xml file. Launch QuickDAQ. Does the Device Selection window appear? Close any other open applications that may be blocking this window's view. In the Device Selection window, select OpenLayersDevices for the Device Family. Your DT9813-10V should appear in the Available Devices field. Click the ADD >> button to add the device over to the right side. Click the OK button afterwards to continue with QuickDAQ. Lastly, what is the serial number from the backside of the DT9813-10V case? Regards, Fausto

Hello @Twyman Plumb. Currently, there is no MCC ULx for NI LabVIEW support for LabVIEW 2024. An update will be posted once it is available. Please continue to use a previous version of LabVIEW with ULx for NI LabVIEW and your MCC devices. Regards, Fausto

Hello @m3rd. Is the device detected by QuickDAQ and the Open Layers Control Panel applet? Please send me a private message with the serial number from the backside of the DT9813-10V case. Regards, Fausto

Hello @Twyman Plumb. Which device will you be using with LabVIEW 2024 and which drivers did you install? Regards, Fausto

Hello @Giorgio. Which versions of LabVIEW, Windows OS, and InstaCal do you have installed on the target system? What is the serial number of your USB-1208FS-Plus? Is the issue reproducible with an ULx for NI LabVIEW vi example or a custom example? If you are using a custom example vi, then please modify the vi example in any way necessary so that I can test it with my system and device. Regards, Fausto

Hello @jensr. Yes, start your testing with the pi5 branch. We have not completed our testing, so please let us know if you find any issues. Regards, Fausto

Hello @Saha. While it is possible to capture data on both boards, using the same application, the MCC 128 and the MCC 172 do not support synchronized capture of data between the two boards. The MCC 128 uses a successive approximation A/D converter type, while the MCC 172 uses a delta sigma A/D converter type. The MCC 172 samples can only be synchronized with other MCC 172 boards due to the type of ADCs used. The delta sigma converters have a sampling clock rate much higher than the data rate (512x). The MCC 172's sampling clock uses a 26.2144 MHz clock, which can be divided down by a microcontroller to get lower sampling rates. The MCC 172 sampling rate must be integer divisors of 26.2144 MHz / 512. The clock & trigger syncing with the MCC 172 through the RPi GPIO header allows multiple MCC 172 boards to use the same 512x ADC clock and trigger signal so that all the ADCs will start converting at the same time and run from the same clock, resulting with all subsequent samples in sync. This clock cannot easily be used for other ADC boards (i.e. MCC 118, MCC 128), because of that high rate. Refer to the MCC 172 example, fft_scan.py, for an example that uses the Numpy library and alter the example to suit your application's needs. Python examples for the MCC 128 are located here. Regards, Fausto

Hello @Sirius. The MCC USB-1608GX does not support simultaneous capture of the analog input channels, since the channels are multiplexed before reaching the A/D. Additionally, the MCC Universal Library function, DaqInScan(), is not supported by the USB-1608GX. Synchronously reading 3 AI (voltages) and 1 DI (pulse) is not supported on the USB-1608GX. If you set the sampling rate to the maximum supported rate of 500 kHz aggregate and connect your digital signal to the 4th analog input channel, would that scenario work for your application? An alternative MCC device is the USB-1808X. Regards, Fausto

Hello @m3rd. Download and install Data Translation's QuickDAQ software application on to a Windows 10/11 computer. Afterwards, with the DT9813-10V connected to the host computer, launch QuickDAQ. In the Device Selection window, select OpenLayersDevices for the Device Family. Your DT9813-10V should appear in the Available Devices field. Click the ADD >> button to add the device over to the right side. Click the OK button afterwards to continue with QuickDAQ. If your DT9813-10V device is not listed as an available device, then click the Cancel button to exit. Using your Windows Taskbar's search field, enter Control Panel and click on it to open. Select View by: Large Icons. Scroll and click on Open Layers Control Panel (32-bit). Click the OK button if you get the following message. Does your DT9813-10V device appear in the list? If the device does not appear, please test your DT9813-10V with a different USB cable connected directly to a USB port on the host system (no hub), as well as with another Windows system. Regards, Fausto