Fausto

Hello @Jonaskb. We do not provide support for NI DIAdem software. On your Windows 11 system, do you have a C:\Program Files (x86)\Data Translation\DeviceDrivers\DT9800 directory with files? With the DT9803 device connected to your Windows 11 system, install Data Translation's QuickDAQ application and then launch it. Does the application detect the DT9803? If so, then add the device to the right-side column and continue with QuickDAQ. Once in the QuickDAQ environment, press the start acquisition or record button to capture data. If that all works, then the issue is not with the DT9803. Regards, Fausto

Hello @WFTXglass. Please provide more information regarding your issue, i.e. screen captures, worksheet, any processes running in the OS background, any virus scan apps running, are hibernation and sleep modes disabled. Have you attempted to create a simple worksheet to debug your issue? Regards, Fausto

Hello @WFTXglass. You may be using an older version of InstaCal, not supported under Windows 11. Please download and install the current version of InstaCal. Restart your Windows 11 system and then retest the MCC USB-1608X-2AO with InstaCal first. If the device is detected by InstaCal and no errors, then close the application and launch DASYLab 2016. Any errors using the device with your DASYLab worksheet? If so, create a new simple worksheet to test the MCC USB-1608X-2AO. Reply with your script and screen captures if errors continue to be an issue. Regards, Fausto

Hello @shebbar. Which OS and software application are you using with your MCC USB-1608G devices? Regards, Fausto

Hello @Joero. Thank you for the update and screen captures. Your serial number 1FC83C9 is out of warranty (shipped Sept. 2021) and the MCC USB-CTR08 is not cost-effective to repair. You mentioned that you already tested the device with other Windows systems and USB cables. Try testing a different PC and Windows OS if all previously tested systems were the same model and running the same OS version. Also, try using other cables, ports, and USB hubs. Regards, Fausto

Hello @Joero. Which version of Windows are you using? Download, install, and launch MCC's InstaCal utility to detect the MCC USB-CTR08 connected to the target system. File location: https://files.digilent.com/#downloads/InstaCal/ Is the device detected by InstaCal? What other software do you use with this device? What is the device's serial number on the backside label (or in InstaCal)? Regards, Fausto

Hello @gilgeonics. Please download and install Data Translation's OMNI software. Data Translation devices (i.e. DT9816) are not compatible with MCC's InstaCal software. Regards, Fausto

Hello @Ron Byron. A PDF version of the MCC Universal Library (UL) Help is not available. Please refer to the online UL Help for Windows. Regards, Fausto

Hello @nicktts. If you recently installed DAQami on a Windows 11 system (or upgraded to Windows 11), then you need to update the target system with the latest version of InstaCal. https://files.digilent.com/downloads/InstaCal/icalsetup.exe DAQami installs a version of InstaCal which is not compatible with Windows 11. Please confirm that the target system has the current version (6.74) of InstaCal installed. If the system does have the latest version of InstaCal installed, then it could be a corrupt daqami.mcfg configuration file. Browse to the C:\Users\{username}\Documents\Measurement Computing folder. Delete the daqami.mcfg and restart DAQami. DAQami will create a new configuration file. Regards, Fausto

Hello @daquser. The DT9837 Series (i.e. DT9837A and DT9837B) supports a ±10 V signal on the analog input channels. Have you tested the daq and sensor combination already, but noticed an issue? Please provide a datasheet of your sensor/probe. Regards, Fausto

@Mike R, Thank you for correcting the NI board model as a NI PCI-6035e. If you are only using the analog input channels, then the MCC USB-1608G does have nearly compatible specifications. The MCC USB-1608G does not have an input voltage range setting of +/-500 mV nor +/-50 mV. MCC USB-1608G NI PCI-6035e Regards, Fausto

Hello @lesthaeghet. Thank you for testing. Please test a few other channels with TB3, 18 (5V Analog) and in single-ended mode. If you continue to get similar readings, then please reply via private message with the serial number from the backside label on the DT9844; an image of the label is helpful. The serial number is used to determine if the module can be serviced. Regards, Fausto

Hello @Osiris. Please confirm the SPI and I2C options are selected under Preferences - Raspberry Pi Configuration. Also, since you changed your board stack, you must update the saved EEPROM images so that the library has the correct board information. You can use the DAQ HAT Manager or the Terminal command: sudo daqhats_read_eeproms If the MCC 152 continues to be undetected, remove both boards and install just the MCC 152 onto the Raspberry Pi. Be sure to remove the address jumper from the MCC 152. Restart the RPi and then use the DAQ HAT Manager or the Terminal command: sudo daqhats_read_eeproms Regards, Fausto

Hello @lesthaeghet. Please confirm the acquisition input mode was changed to SingleEnded in QuickDAQ. What is the set sampling frequency? From the DT9844 User Manual, figure 7 shows a simple single-ended connection to a DT9844-32-STP box. Please test the following scenario with QuickDAQ and in single-ended mode. Disconnect all your wiring to the terminal blocks. Afterward, connect TB3, 18 (5V Analog) to TB1, 1 (Analog In 0). Also, connect TB3, 17 (Digital Ground) to TB1, 3 (Analog Ground) and TB3, 13 (Amplifier Low). Reply with a screen capture of the acquisition. The reading should be around 5V. If it is, retest your signal source. Regards, Fausto

Hello @Dauple. Unfortunately, the DT9847-3-1 is no longer manufactured and an equivalent replacement is not available. Regards, Fausto

Hello @Mike R. I am unable to find a NI PCI-6053E, but did find a NI PCI-6052E. Please confirm the NI device model. The NI PCI-6052E supports two analog output channels, which the MCC USB-1608G does not support. Please consider the MCC USB-1608GX-2AO. Since you and/or your colleagues are familiar with how the NI device is used and your application's requirements, compare those NI specs with the MCC USB-1608GX-2AO to determine if the MCC device is a suitable replacement. Note that your software application will need to be updated to support the MCC device. Regards, Fausto

Hello @Ron Byron. Welcome to the Digilent Forum community. MCC related questions reside in the Measurement Computing (MCC) sub-forum. Use this link for the current version of MCC software for Windows, which includes InstaCal. The MCC software installation copies Universal Library examples to the C:\Users\Public\Documents\Measurement Computing\DAQ directory on the target system. Recommend using the UL Help as a reference for the supported functions of each device. An updated firmware version is available for the USB-1608GX via this link, along with instructions. Two versions are available depending on the hardware revision of the USB-1608GX. Select the firmware update compatible with your hardware revision. A label on the device identifies the revision. The letter just before the dash denotes the hardware revision. For example, part number 151440E-xxL indicates revision E. Regards, Fausto

Hello @JMG. I am unable to assist on-site, but can attempt to troubleshoot your issue via this forum given additional information from you. Which MCC device, software application (and version), and operating system (and version) are you using? If you are unsure of the device model, please connect the device to a Windows system, launch MCC's InstaCal utility, and capture a screen image of the device information. Alternatively, snap an image of the physical device (top and bottom) and include it with your reply. Can you describe in detail (and capture screen images) of the issue(s) you are experiencing? Regards, Fausto

Hello @Rob Clements. To be clear, you can drop a 'DT AIN00' module onto a worksheet, but the 'Select Board' field is empty. Is that correct? Open your Windows' Device Manager and search for a 'DT-Open Layers Data Acquisition Devices' branch. Does your DT9816 appear in that branch? If it does double click on the device to view the status on the General tab. What is the status? If you are using a virtual machine with Windows OS or Parallels Desktop on a MAC, then support is not available. If that's not the case, is the DT9816 plugged directly into a USB port on the system or is a USB hub (non-powered or externally powered) used? Externally powered USB hubs are preferred over non-powered USB hubs. Please reply with a screen capture of the expanded 'C:\Program Files (x86)\Data Translation' directory including the sub-folders. Next, with DASYLab not running, are you able to use the DT9816 device in Data Translation's QuickDAQ application? Lastly, please test the DT9816 on a different Windows system that does not have the same configuration or security settings as those machines experiencing an issue with the DT9816 device. Regards, Fausto

Hello @Rob Clements. What is the Data Translation package version in DASYLab 2016's Configurator? Please create a new DASYLab worksheet with a Data Translation Analog Input module and a Digital Meter display module. In DT AIN module, select the attached DT9816 and reply with a screen capture of the configuration. Close the module and connect the default channel between the two modules on the worksheet. Save the worksheet and run it. If it does not run, then reply with a screen capture of the entire worksheet and any errors. Be sure to capture all displays on the screen. If the worksheet runs, then close DASYLab. Launch DASYLab and load the worksheet. Are you able to run the worksheet without an error? Reply with full screen capture. How many DT9816 modules are connected to that target system? Is the target system managed by an IT Administrator? If so, does your Windows user login account have admin privileges? Does the target system have the following DT9816 folder and files? Regards, Fausto

Hello @komondor. Yes, the MCC 128 is compatible with the RPi 4. Use the 'rpi5' branch to install on the RPi 4 module. Regards, Fausto

Hello @Domme. Please confirm that your target system is using a previous version (v7.8.2) of DT Open Layers library for the DT9857E. Disconnect your microphones and loop the analog output directly to the five analog input channels. Please test and reply with screen capture(s) and comments. Regards, Fausto

Hello @Francky. The MCC 134 Electrical Specifications mentions a 15 minute warm-up time. Please verify the three CJC sensors are not damaged. You initially reported the following CJC temperatures. Have readings varied significantly? CJC 26.7397420913332 26.367750118973106 25.348451403433273 24.073498502352948 Please retest the MCC 134 boards without the mini thermocouple connectors; direct connection to the screw terminals. https://digilent.com/reference/daq-and-datalogging/documents/measuring-thermocouples-with-raspberry-pi Regards, Fausto

Hello @komondor. What changed from the time the MCC 128 boards did work? Using a Raspberry 5 model with one MCC 128 board installed, remove the address jumper and then uninstall the MCC DAQHATS library using the steps below via a terminal. Afterward install the MCC daqhats software branch (beta version 1.5.0.0) for RPi 5 modules. https://github.com/mccdaq/daqhats/tree/pi5 1. $ cd daqhats 2. $ sudo ./uninstall.sh 3. $ git pull 4. $ git checkout pi5 5. $ sudo ./install.sh 6. $ pip install daqhats (manually add Python support) You can switch back to the released library by uninstalling the library, running “git checkout master”, and then installing the library. Use the installed MCC DAQ HAT Manager utility application to verify communication with the MCC 128 or terminal commands. $ sudo daqhats_read_eeproms $ daqhats_list_boards Does the MCC 128 work? If the board is not detected, then power off the RPi and swap out the MCC 128 board. Is the second board detected by the MCC DAQ HAT Manager utility application or terminal commands? Reply with screen captures and images of your hardware if the issue is not resolved. Regards, Fausto