Fausto

Hello @nbv. Thank you for the chronological clarifications and additional troubleshooting. That is strange indeed. I'd ask you to swap the original MCC 152 in address 1 with the scavenged MCC 152 in address 0 just to see if the issue returned, but why disrupt what's working now. You tested multiple RPi modules and multiple MCC 152 boards in the various address locations. It seems to be an intermittent issue, but not sure of the root cause. Regrettably, I don't have any other suggestions at this time. Keep us posted if you find anything else. Regards, Fausto

Hello @CHA_CHO. That issue cannot be addressed in the field. I will send you a private message for a repair RMA. Regards, Fausto

Hello @epicbutter. The Keithley KPCI-488LPA is not a MCC device. The obsolete MCC device along the same type of interface would have been the MCC PCI-488. A quick Google search shows that the KPCI-488LPA is still sold by other vendors. Try reaching out to those vendors. Regards, Fausto

Hello @Fukuda. DASYLab V12.0.1 was released in April 2012 and supported by the following Windows OS releases. • Windows 7 32 bit • Windows 7 64 bit • Windows Vista 32 bit, SP2 • Windows Vista 64 bit • Windows XP Pro SP3 For your Windows 7 system, please update the OS with all available Service Pack releases. At the time of the DASYLab v12.0.1 release, InstaCal was at version 6.23. However, the MCC drivers were updated with new signature certification for the Microsoft extended verification at that time, especially for Windows 7 64-bit users. Recommend installing InstaCal version 6.60. (InstaCal Archive) Install InstaCal first and then verify the software can detect the connected MCC USB-2408 device. Afterward, close InstaCal and install DASYLab v12.0.1. At the end of installing DASYLab, a user must enable the Measurement Computing package in DASYLab's Configurator utility. Since DASYLab v12.0.1 is not supported, I used DASYLab's 2022 Configurator as a visual. Next, close the Configurator and launch DASYLab v12.0.1. The MCC-DRV modules are stored in the Modules - Inputs/Outputs - MCC-DRV folder in the DASYLab browser. Regards, Fausto

The following is a list of the DASYLab software release dates as well as the Windows operating systems supported for each release. (DASYLab Archive) 2022.1 (v16) Feb-2023 • Windows 10 32 bit • Windows 10 64-bit 2022 (v16) May-2022 • Windows 10 32 bit • Windows 10 64-bit 2020 (v15) March-2020 • Windows 10 32 bit • Windows 10 64-bit • Windows 8 32 bit • Windows 8 64-bit • Windows 7 32 bit • Windows 7 64 bit 2016 (v14) Nov-2016 • Windows 10 32 bit • Windows 10 64-bit • Windows 8 32 bit • Windows 8 64-bit • Windows 7 32 bit • Windows 7 64 bit V13 Aug-2013 • Windows 8 32 bit • Windows 8 64-bit • Windows 7 32 bit • Windows 7 64 bit • Windows Vista 32 bit, SP2 • Windows Vista 64 bit • Windows XP Pro SP3 V12.0.1 Apr-2012 • Windows 7 32 bit • Windows 7 64 bit • Windows Vista 32 bit, SP2 • Windows Vista 64 bit • Windows XP Pro SP3 V12 Oct-2011 • Windows 7 32 bit • Windows 7 64 bit • Windows Vista 32 bit, SP2 • Windows Vista 64 bit • Windows XP Pro SP3 V11 SP1 Sep-2010 • Windows 2000 SP4 • Windows XP Pro SP3 • Windows Vista 32 Bit, SP2 • Windows Vista 64 bit • Windows 7 32 bit • Windows 7 64 bit V11 Sept-2009 • Windows 2000 SP4 • Windows XP Pro SP3 • Windows Vista 32 Bit SP2 • Windows Vista 64 bit V10 Nov-2007 • Windows Vista 32-bit • Windows XP Pro SP2 • Windows 2000 SP4 V9 Sept-2005 • Windows 2000 SP4 • Windows XP Pro SP2 V8 Feb-2004 • Windows 2000 SP4 • Windows XP SP1 • NO support for Windows 9x/ME/NT 4.0 and earlier versions. • This software does not work under Windows 3.x. V7 Nov-2002 • Windows 98 (Second Edition) • Windows NT 4.0 (Service Pack 6) • Windows 2000 (Service Pack 2) • Windows XP • Windows ME is not supported by this version. V6 (6.00.07) Aug-2002 • Windows 98 SE • Windows NT 4.SP6 • Windows 2000 SP2 • Windows XP V6 (6.00.03) Nov-2001 • Windows SE • Windows NT 4.SP6 • Windows 2000 SP2 • Windows ME and Windows XP are NOT supported V5.63 Oct-2000 • Windows 95 • Windows 98 • Windows ME • Windows NT • Windows 2000 V5.5 Apr-2000 • Windows 95 • Windows 98 • Windows NT V5.03.30 Dec-1999 • Windows 95 • Windows 98 • Windows NT V5.02.20 Nov-1999 • Windows 95 • Windows NT V5.0 Nov-1998 • Windows 95 • Windows NT V4.0 - 32 bit V3.5 - 16 bit Dec-1996 • Windows 95 • Windows 3.1 V3.0 Nov-1995 • Windows 95 • Windows 3.1 V2.0 Nov-1994 • Windows 3.1 V1.5 (German and English) Dec-1993 • Windows 3.1 V1.0 (German only) Apr-1993 • Windows 3.1

Hello @jucimar. The digital input channels can be added to the Strip display alongside the analog input channels. Regards, Fausto

Hello @QiwenSheng. The MCC USB-1608GX-2AO uses analog multiplexing to gate each channel, one by one, to the A/D converter. Internally, the input multiplexer has a capacitance between each channel. When it switches, the voltage difference from one channel to the next appears as an AC signal and passes through to the next channel. However, as long as the input signal has a low impedance, the charge dissipates, allowing the input signal to charge the input to the correct value before the following A/D conversion. Recommend not scanning any open channels, which is not the issue here, and also recommend signal sources with an impedance of 100 Ohm or less. What are the specifications of your input signal? If not using all analog input channels, skip a channel between the connected signals. Add a short wire between the channel high screw terminal (CH#H) and AGND, but do not add the skipped channel to the acquisition's channel list. You may also want to check two other channels in case channels 0 and 1 are bad. Regards, Fausto

Hello @Srisharan. If using the USB-2416 with a Windows 10/11 OS, then download, install, and run the MCC DAQ Software CD. Afterward, run the MCC InstaCal software utility to detect the USB-2416. If using a Linux OS, then you will need to download and install MCC's Universal Library for Linux. Resource links: MCC USB-2416 User's Guide https://digilent.com/reference/daq-and-datalogging/documents/choosing-software Regards, Fausto

Hello @jucimar. DAQami does support multiple devices, but the data will not be synchronized. Which MCC devices will you be using? Regards, Fausto

Hello @nbv. So that I understand what transpired with your hardware configuration and testing, please confirm whether or not the following information is correct. You began with a RPi 4 module (Buster OS installed) that had no daq hat board mounted. You then installed a MCC 152 (with no jumper on W2; address 0) followed by a second MCC 152 (with jumper at A0 on W2; address 1). Afterward, you installed a MCC 118 (with jumper at A1 on W2; address 2). With both SPI and I2C options enabled and the MCC DAQ HAT library v1.4.0.8 installed, this hardware configuration worked with all three MCC daq hat boards and the MCC DAQ HAT Manager application. Next, you removed all three MCC daq hats from the RPi 4 module and then mounted only one of those boards. You ran the software and the board would not respond as expected. Was the MCC daq hat board over-flexed when it was removed from the RPi module? Can you think of anything else that may have happened when you removed the three MCC daq hat boards from the original RPi 4 configuration? For the next configuration, you mounted one of those MCC 152 boards on a new RPi 4 module (running Bookworm OS version) and the MCC DAQ HAT library v1.4.0.8 (or the v1.5.0.0 beta?). With the address jumper configured for address 0, the MCC 152 continued to not respond as expected. Regards, Fausto

Hello @CNDTEC. Please provide information regarding your sensors (i.e. include datasheets). DASYLab does not have a zero'ing option. The sensor's manufacturer may have their software utility to configure the sensor. Please provide additional information regarding your application. Regards, Fausto

Hello @Alibumaye. Installing Data Translation's MEASURpoint software copies the examples to the "C:\Program Files (x86)\IVI Foundation\IVI\Drivers\DtxMeasurement" folder. Regards, Fausto

Hello @Jaume. Please reference the following post. Regards, Fausto

Hello @da9da9. When you load an ULx example in LabVIEW, ignore the initial warnings. Those warnings will be cleared when you save the vi, for the next time you open the vi. Next, please update the InstaCal utility and ULx for NI LabVIEW to the current versions using the following download: https://files.digilent.com/downloads/MCCDaqCD/mccdaq.exe Verify the USB-231 is detected and capturing good data in the InstaCal utility before closing the utility and using LabVIEW. Note: both applications should not be open at the same time to avoid communication issues with the device. Please reply with screen captures if you continue to see this issue. Regards, Fausto

Hello @Alibumaye. The MCC DT9874 Series is not supported by MCC's mcculw library. This device uses Data Translation's MEASURpoint software, which appears to have been installed based on your screen capture of Data Translation's QuickDAQ application. The MEASURpoint software includes examples for C#, C++, VB.NET, LabVIEW, and MATLAB. There is no Python support for the MCC DT9874 Series devices. Regards, Fausto

Hello @TadSend. Which software are you using for your main application? The MCC USB-3103 supports two analog output voltage ranges (±10 V and 0-10 V), while the MCC USB-1608G supports four analog input voltage ranges (±10 V, ±5 V, ±2 V, or ±1 V). For testing purposes, configure the analog output voltage range to be 0-10 V and the analog input voltage range to be ±10 V. The simplest scenario would be to wire an analog output voltage channel from the MCC USB-3103 directly to an analog input voltage channel on the MCC USB-1608G module. Add scaling in your code to represent open/close position of the proportional valve based on the analog output voltage level and scaling to represent feedback level of a hydraulic cylinder based on measured analog input voltage levels. Regards, Fausto

Hello @Display Name. If your two MCC 152 boards do not work and the other two MCC 152 boards work with the encoder, then most likely the two nonfunctioning boards are damaged. I will send you a private message for replacements (if within the 1-year warranty period). I am not aware of a new hardware version of the MCC 152 to be released. Regards, Fausto

Hello @GGu2024. We do not recommend connecting the thermocouple tips directly to a sensor or metal surface without isolation (i.e. thin film, epoxy). A direct connection makes the thermocouple susceptible to noise which will affect measurements. Additionally, electrical surges or static from the target surface can damage the MCC 134 board. MCC 134 Electrical Specifications https://digilent.com/reference/daq-and-datalogging/documents/measuring-thermocouples-with-raspberry-pi Regards, Fausto

Hello @nbv. Are you using the same RPi 3 module with these new MCC 152 boards or a different RPi module? Please confirm that both SPI and I2C options are enabled via the OS main menu - Preferences - Raspberry Pi Configuration - Interfaces tab. Disconnect any wiring to the MCC 152 boards, restart the OS, and repeat your troubleshooting steps. If the issue continues, then you will need to unmount the boards and test the MCC 152 boards individually. Regards, Fausto

Hello @Roger Lo. There is no mean time between failure (MTBF) data for any Measurement Computing (MCC) device. Regards, Fausto

Attached are two Visual C examples. DTSerialNum.zipShowBoardInfo_x64.zip

Hello @gup_08. QuickDAQ was developed with Data Translation's Open Layers.NET. The DTx-EZ ActiveX library for Visual Basic 6 does not have a wrapper function to return a Data Translation device's serial number. However, the DTx-EZ document (found in 'C:\Program Files (x86)\Data Translation\Win32\DTx-EZ\Documentation') instructs a user to add the OLMEMDEFS.BAS and OLDADEFS.BAS modules to the project. In the OLDADEFS.BAS module, resides the DA SDK function olDaGetHardwareInfo(). The DA SDK Help describes the function. Regards, Fausto

Hello @StefanF. To use MCC's DT9829 module with MATLAB, a user must have a license for MATLAB and MATLAB's Data Acquisition Toolbox. Once in the MATLAB environment, use the Add-On Manager to install the Data Acquisition Toolbox Support Package for Data Translation Hardware. Reference the Data Translation DAQ Adaptor for MATLAB guide for supported capabilities. Note that temperature measurements are not supported by the Data Translation DAQ Adaptor for MATLAB. Regards, Fausto

Hello @jnieves. The following forum post was written for a MCC USB-TEMP-AI with DAQami, but can be applied to a MCC USB-TEMP module as well. The following table shows the maximum number of supported channels based on configurations. Regards, Fausto

Hello @Jose Medina. The MCC USB-502-LCD device is a legacy MCC product. The MCC USB-500/600 Series Help does not mention a calibration process for the USB-502-LCD device. Here is a link for the MCC USB-500/600 Series software. Regards, Fausto