JRys

Hello, The WebDAQ devices can be used only with mail services that allow signing in with a username and password. It does have the ability to negotiate security with the mail server. Perhaps you could find a third party mail service that still allows username/password login. I tried both gmail and yahoo but could not get them to work with my WebDAQ. I suspect most mail servers have security that exceed our WebDAQ email abilities. I will file a defect report and hopefully when new firmware is posted, it will fix the email issue. Best regards, John

Hello, Windows 11 requires InstaCal 6.73, which you can install from our latest CD download: https://www.mccdaq.com/downloads/MCCDaqCD/mccdaq.exe Best regards, John

Hello, Contact IFM regarding their wiring diagram and how to connect it to an analog input. The USB-1608G maximum input range is 10 volts with protection to 20 volts. Use a 10 volt power supply to avoid exceeding our 10 volt input range. best regards, John

Hi Rob, I don't see anything obvious but then again I can't simulate your system. If this is a critical application, I can recommend a consultant to help figure it out. best regards, John

Hello, Use the following link to download our DAQ Software CD. https://www.mccdaq.com/downloads/MCCDaqCD/mccdaq.exe best regards, John

Hello, I'm sorry, but MCC no longer provides phone support. We switch to this forum so that questions and answers are searchable to everyone. The MCC 128 installation instructions can be found on this page: https://github.com/mccdaq/daqhats After installation, examples for all the MCC daqhats will be in `/daqhats/examples/ Best regards, John

Hello, My suggest is to start a new worksheet and put down only a Data Translation Analog Input module. Set the module to the DT9816 board and press Start. If you don't get an error then DASYLab can control it. If you cannot set the module to the device, remove it and restart the computer. Plug it back in after the restart and try the above test again. If it works, attach your worksheet to your reply. Best regards, John

Hello, Error 6623 is undocumented and does not happen often. However, the few past incidents point to the device itself. If you are on a Windows 11 Computer, make sure the InstaCal utility is version 6.73. Otherwise, if it is possible try a different E-1608. Best regards, John

Hi Brad, Assuming you have channels enabled, it could be that the program itself needs more permission. Using File Explorer, find C:\Program Files (x86)\Personal DaqView\Applications\pdaqview.exe. Get the properies and on the Compatibility page, set Run this program as administrator. Also, the top title bar of the program should show something like PDAQxxxxxx, where xxxxxx is the serial number. This indicates it's talking to the device. John

Hello, Measurement Computing return policy is 30-days. The MCC 128 on PO 25522241 shipped on August 8 and allowing for one week delivery, you are still 10 days past. If it is still in the sealed static bag, I can make an exception. Best regards, John

Hello, A typical steady state temperature can move around due to noise on the input and on the thermocouple. However, 0.05 Degrees C is well within the accuracy of the device. My suggestion is to display data to one decimal place, which is more inline with it ability. Best regards, John

Hello, if the non-admin users get the screen with the "Remaining Time" on the evaluation period - see below, have them enter the license key. Daqami keys are now free and to obtain one go to: https://www.mccdaq.com/support/daqamikey.aspx If the evaluation period has expired, then as an admin uninstall Daqami followed by reinstalling. Your license key will be remember and it will run as it did before, but the non-admin users evaluation period should get be reset. Upon starting the program they should see the following: Press Enter Key and enter your key. After the they should have the ability to save data. Best regards, John

Hello, Your device was manufactured in 2007 and should work. However, I cannot explain why the software fails to find it. Usually this problem is caused when the device plugged in while Personal DaqView is running. That's why I asked to restart the program. Look in C:\Windows\System32\ There should be two DLL: pday.dll and pdaqx.dll. Both should have Date Modified of 2011. Look in C:\Windows\System32\Drivers\ There should be pdaq.sys file with a Date Modified of 2011 The other thing to check is if your system uses virtualization for security. Our product don't play well with virtualization. Best regards, John

Hello, Check the power LED indicator next to USB plug - it should be on. if it is, restart Personal DaqView and check View Active Devices again. Your device will have a six digit Serial Number. If it is not listed, send me the serial number and I'll try to determine it age. If it turns out to be from the early 2000's, its firmware won't support the newer driver and OS. If the LED is off, the computer's USB support should be update. Check with the manufacturer or try a different computer. Best regards, John

Hello, If you've installed a 15 year old copy of Personal DaqView it's not going to work unless you have Windows XP or a 32-bit version of Windows 7. Ten years ago we updated the software to include 64-bit driver support. The version you need is 2.2.1 and can be downloaded with the following: https://www.mccdaq.com/downloads/iotech_software/PersonalDaq50_Series/pdaqviewsetup_x86_x64.exe It was never officialy supported on Windows 10, but there are many customers that have made it work. If the laptop was purchased as a Windows 10 Laptop it should work, but if it is older and was upgraded to Windows 10 it most likely won't. I recommend uninstalling the existing version and unplugging the device before installation. After the installation has completed, plug it in and try it. Make sure to start the program with the Run as administrator option to enable the Meters. if you need help using the software, the following is the user manual: https://www.mccdaq.com/pdfs/manuals/personal_daq50_series.pdf Best regards, John

Hello, The following command will read the EEPROMs of all the attached boards and update the available board list: sudo daqhats_read_eeproms Best regards, John

Hello, Inside the USB-TC is a known millivolt reference. During calibration the channels are first connected to ground to measure offset. Then they are connected to the millivolt reference and with the two values, gain and offset coefficients are calculate and stored. This allows it to measure the thermcouple voltage accuractely. During operation, it measures the thermcouple voltage, the CJC sensor and from these to values it determines temperature for the particular thermcouple type. As for the calibration date, 11/26/15 is the last factory calibration date, which happens to be the manufactured data. I check, and this particular USB-TC has never been sent in for a factory calibration. One thing to keep in mind, the millivolt reference used in the self calibration does eventually drift. The factory calibration reset the reference so that future self calibration are accurate. The current price for a calibration is $62.75 plus shipping. Email your contact info and model/serial number to info@mccdaq.com to receive a quote. Best regards, John

Hello, The MCC 128 takes over the SPI bus as well as some of the GPIOs. The MCC 152 uses the I2C bus as well as some GPIOs. For the full list of what we use, check the Interface Specifcation section in the following electrical specifications. https://mccdaq.github.io/daqhats/_static/esmcc128.pdf https://mccdaq.github.io/daqhats/_static/esmcc152.pdf For the Pi Camera to work, it cannot use any of the resoures that we use. Best regards, John

Hello Brian, For both the USB-1608GX-2AO and the USB-2637, use the AOutScan function. It will stream the data buffer out using the "rate" variable as the update rate. Create an array where every other value is 0 (-10v) and 65536 (+10v). Use the function WinArrayToBuf to transfer it into a driver buffer, which you pass into the AOutScan function. Set the scan options to CONTINUOUS + BACKGROUND. If all goes well it will write out the buffer over-n-over until you call StopBackground. The output (+/-10v square wave) frequency will be one half the update rate. If this is not working for you, could you include a short snippet of code showing how the function is called and any errors that are encountered? Best regard, John

Hello, Using 1 for the logic state works if you're use cbDBitOut and VB6, which is essentially VBA. However, your VEE code appears to use our Dot Net DLL and it functions are strongly typed. Instead of using 1 for the logic state, try the enumeration DigitalLogiceState.High. This is also true if you're using VB.NET (or C#). John

Hello, The eight pins you wish to control (21-28) are designated FirstPortA. There are 2 or 3 functions that can be used. First, you must declare the direction as input or output. To do this, use cbDConfigPort. For example, returnValue = cbDConfigPort(boardNumber, FIRSTPORTA, DIGITALOUT). To write the port use cbDOut or DBitOut. For example, returnValue = cbDBitOut(boardNumber, FIRSTPORTA, 3, 1) sets pin 24 high. If you wish to write all eight bits use returnValue = cbDOut(boardNumber, FIRSTPORTA, 85) sets every other line high. We do not support VBA, but I believe you can call UL functions as long as you import the cbw.bas file into the VBA project. This is the file that declares the FIRSTPORTA and DIGITALOUT enumerations as well as the functions themselves. It is located in C:\Users\Public\Documents\Measurement Computing\DAQ\VBWIN. If you don't have this folder, reinstall InstaCal from the DAQ Software CD download:https://www.mccdaq.com/downloads/MCCDaqCD/mccdaq.exe good luck! John

Hello, The following URL will download the DASYLab 2016 installation program. You can use it to install DASYLab 2016 on a different computer. Because you use the USB-1608GX-2AO you also need InstaCal, which can be installed with the second URL. https://www.mccdaq.com/downloads/archive/DASYLab/DASYLab_2016.0.1.exe https://www.mccdaq.com/downloads/InstaCal/icalsetup.exe Here's a video that brings it all together Best regards, John

Hello, The MCC 118 absolute accuracy is 20.8 mV at full scale. This equates to a 0.2% accuracy. Therefore, the minimum detectable value is 0.4 Bar x 0.002 or 0.008 Bar. As for maximum detectable frequency, are you performing an FFT to get the frequency spectrum? Best regards, John

Hey Sam, There is no canned solution that we offer. The digital outputs are 3.3 volt compatible and can only source about 1mA. They work well when interfaced to 3.3 volt logic. You could try using the output as a switch to ground. Connect the SSR (+) control line to (+) Power (external power supply) and the (-) to the USB-1616HS-4 output. Connect (-) Power to the USB-1616HS-4 ground. When the output is set high, the SSR will be off but when it is set low current will flow from (+) Power down through the output to ground, which is (-) Power and this turns on the SSR. Test the output with a load on the SSR output because they need some current to flow to stay on. Best regards, John

Hello, The "can't open device" error is typically one of the following issues: 1. Trying to access a board with an incorrect address 2. Either or both SPI and I2C got disabled 3. The board has a hardware problem and should be replaced. Could you provide the following: Raspberry PI model and operating system; if it is a headless system and what you're using for C programming. I didn't understand what you meant by Temporary solution for this problem is to make remote GPIO (in raspberry menu) "on" or "off" and try firmware update again. The MCC 172 uses the following resources: If you have other non MCC HAT boards attached, make sure they don't use these. The daqhats installation installs a program called MCC DAQ HAT Manager. With it you can update the board list with Read EEPROMS and List the devices or boards found. It makes it easier to test each board. My suggest is to execute: sudo apt full-upgrade sudo reboot then run the following which assumes the two boards are using address 0 & 1 mcc172_firmware_update 0 ~/daqhats/tools/MCC_172.fw mcc172_firmware_update 1 ~/daqhats/tools/MCC_172.fw Best regards, John