Todd

Nevermind. I wasn't paying close enough attention to red and black wires in correlation to the drawing in the user manual. Essentially it should have been red wire on pin 1, black on pin 2, then black on pin 3 and red on pin 4, and then that works.

Hi, I am using the DT9829 to connect two different types of RTDs. I successfully connected Omega PR-26SL-3-100-A-0900-M12-1, but when I connect Omega HSRTD-3-100-A-10M with the same configuration and wiring, it shows up as -770 F when the sensor is connected. I tried swapping RTDs on the same channel and the same issue followed the HSRTD. I measure ~1.0 ohm between the two red wires as well as between the two black wires. I also measure ~110 ohm between the red and black leads, which is reasonable for an ambient temperature of 72F. Any recommendations on what might be causing this issue? Thanks, Todd

I think it might be within the 1 year timeline. It is serial number 20EEC80. I had a second unit and at first it had an issue where the sensor reading did not match the pressure. I think there was a weird bug for Analog input channel 2 where it would not accept the mV/EU input value. I tried changing it several times. I was able to resovle it by deleting all the configuration files from the ...AppData\Local\Data Translation and then it would accept the input mV/EU values. I am using version 3.7.0.49 of QuickDAQ. Have you seen this issue before?

The sensor is Noshok 100 series (100-30-1-1-25), which is a 2-wire sensor. I temporarily added a current meter and I am getting the expected 4 mA when the sensor is at 0 psi and 20 mA when the sensor is at 30 psi, however ithe DT9829 shows a -21mA when the sensor is connected at 0 psi. I am supplying 12VDC to the sensor and the return of the sensor is connected to CHn+ and CHn- is connected to the 12VDC supply return. I found this issue only occurs on Channel 0. The rest of the channels appear to be functioning normally so an offset of -7.5psi results in 0 psi when no pressure is supplied. Channel 0 appears to have a large offset nominally and I am not sure why. Todd

Fausto, I tried that this morning and got the following. I configured the channel to display Amps and set the mV/EU value to 1 and offset to 0 psi and then compared it to a current meter. At 0 psi: DT9829 Displays -0.021A (-21 mA) Current meter displays -4.1 mA At 30 psi: DT9829 displays -0.005A (-5mA) Current meter displays 20.1 mA I think the large initial offset required for the DT9829 is because the DT9829 is reading -21 mA at 0 psi. I would have expected the DT9829 reading to be close to the meter reading or about 4 mA. Todd

Fausto, Using the .000533 mV/EU makes sense however for current measurements it should be interpreted as mA/EU. The offset of 7.5 psi makes sense however I had to use +40.4 and then I would get 0 psi when no pressure is applied and ~29.8 psi when 30 psi was applied. When I change the input to mV/EU and 0 offset to use the DT9829 as a current sensor input, I get -0.021 A at 0 psi and -.004 A at 30 psi. I am not sure why this is occurring. Todd

I was DT9829 focused on the voltage and didn't double check the Noshock 100 datasheet. I checked it and it specified a minimum voltage of 10 VDC and when I supply 12VDC, the .000533 value correlates within .2 psi at full scale if I use a large offset. I still haven't been able to figure out how the mV/EU conversion works for mA sensors. If I measure straight current using the DT9829, it appears to be a nominal -20mA and then increase to -4mA. I thought maybe I had the wires reversed on the sensor and I tried swapping them but then it just rails at -25mA. I would have expected to measure ~4mA with no pressure and ~20mA at full scale for the 30 psi sensor. Let me know if you have any suggestions. Thanks, Todd

John, I just traveled out to the test site today. When I tried 1875 instead of .001875, I didn't get any response when I supplied pressure to the pressure transducer, however 1/1875 (0.000533) is a lot closer but appears off by about a factor of 2. For the configuration value, I create a custom value of psi. The mV/EU value is the slope however the measured value should be 4-20 mA. For current measurement is the value mA or does the DAS internally run the voltage across a resistor and measure the voltage drop in mV? Trying to understand what units the current measurement is. The voltage input sensors are much more straight forward. Thanks, Todd

John, Thanks for the feedback. Based on your example, my sensitivity should be 1875 instead of .001875. I will give that a try. Thanks, Todd

I have a 30 psi sensor that I have connected to the DT9829 with an external source voltage supplied. I configured the sensor in QuickDAQ as a current sensor and then used custom units as psi. For sensitivity I am using 0.001875 but it appears to be too low. The sensor is 4-20 mA, so 4 mA = 0psi, and 20 mA = 30 psi, or 1.875 psi/mA. I think the DAS measures current as A instead of mA, so I divided 1.875 by 1000 to get 0.001875. I am waiting to get a pressure gauge to compare the output to but at the moment the displayed "psi" appears to be much lower than expected. Let me know if you have any guidance for setting up a 4-20mA sensor using the Current input option on the DT9829 with QuickDAQ hardware. Thanks, Todd

Thanks, that worked. Initially I didn't have the mV/EU value correct as it was a different conversion than I initially expected. Once corrected the 4-20mA pressure displayed the expected pressure range. Todd

Hi, I have a DT9829-8 and I am trying to connect a two wire 4-20 mA sensor. I connected the two wires to the DT9829-8 per page Figure 10 on page 41. I initially assumed the DAS would source voltage for the sensor but this morning I see the current source is external to the DT9829-8 in Figure 10. I need to supply a source to my 4-20 mA Noshok series 100 sensor. What voltage source can I use? Table 31 on page 152 specifies 5V maximum @ 20mA and an input voltage maximum of ± 12 VDC and overvoltage projection at ± 15VDC. What source voltage can I use, anything between ± 5 VDC and ± 12 VDC? Thanks, Todd

Thanks for confirming there is no need to complete the calibration procedure per chapter 7, if the hardware is being used within the facotry calibration period.

The Omega LSHD-15K load cell is ratiometric with a nominal gain of 3 mV/V excitation, so for an excitation voltage of 10VDC, the output will be 30mV at full scale of the load cell. The QuickDAQ software has an input for the 3 mV/V value for the load cell setup. The excitation voltage is 3VDC for the DT9829 module which would reduce the full scale output from 30mV to 9mV. I think there is an issue with the QuickDAQ software when the Shunt Calibration is selected. Sometimes the value gets applied and sometimes it doesn't. A different data Aquisition system I used recently completed the shunt calibration automatically vs installing a shunt resistor, so I assumed it was a similar feature for the DT9829, which was an incorrect assumption. When I completed the shunt calibration several times without the resistor, I noticed the correction value would change drastically each time. It would also be ideal if the correction factor had a limited range vs any calculated value. When I tried not including the shunt calibration, I had the same issue. I found that re-setting the channel type and starting over appeared to fix the issue. Now the load cell reading is displaying 15-20 lbf when I push on it. Regarding completing the calibration procedure in chapter 7, I just received a new DT9829 from the factory with a calibration sheet. Does it still need to be calibrated, or should the factory calibration be good for 6 months to 1 year? Thanks, Todd

I am having trouble configuring a load cell with the DT9829. I have setup load cells on other data acquisition hardware without issues before. I am having issue with the load cell either displaying 0 lbf or almost 10x the applied force. I have also found the calibration function results in a different correction factor every time I run it. I am using an Omega LDSH-15K, which has a transducer Rated Output of 3.002 mV/Vnominal. I put 15,000 lbf in the box for transducer capacity. The load cell is sitting on a bench, not mechanically attached to anything. If I push on the load cell, it shows -8,000 lbf if I don't include offset nulling and shunt calibration. When I include offset nulling and shut calibration, I get a different "gain" just about every time. One time it worked and the output was reasonable. I am not sure why the output of the 15,000 lbf load cell is so variable. Any suggestions? Thanks, Todd

On another note, I am currently unable to turn on the Memory Integrity feature. Windows tells me this is because incompatible drivers have been installed and to contact the manufacture for the latest drivers. Is the DT9829 driver version 7.0.0.3 from 1/16/2014 the latest driver? Does MCC plan on updating the driver in the future to be compatible?

The issue appeared to be a Windows issue, so I did a search for Windows 10 blocking drivers and found which setting need to be changed. I did the steps listed in the article below to turn off Memory Integrity feature and now the driver works as expected. https://www.windowslatest.com/2020/03/07/windows-10-security-app-blocks-driver-updates/ The bug applies to all versions of Windows 10 and it can be resolved if you turn off the setting in Windows Security app. To fix the driver blocking bug, follow these steps: 1.) Open Start and navigate to Settings. 2.) Click Update & Security and then open Windows Security. 3.) In Windows Security, navigate to Device Security. 4.) Under Core isolation, turn off Memory Integrity feature. A system reboot is required for the changes to take effect. Microsoft also recommends users to look for other drivers from Windows Update or manufacturer’s website.

I was able to install the installation package successfully on a Windows 7 computer. I checked Dell Latitude 9420 Windows 10 Pro laptop (version 21H2) and it doesn't have Windows Defender Security Center. It only has Windows Security. I checked the Bios and Secure Boot was not selected. I suspect it is something security related but I am not sure what might be blocking the driver.

HI, Is the new MCC technical support? I just installed the DT-OMNI software (DataAcqOMNI_V7.8.9.zip) per the instructions in the box onto a Windows 10 laptop. The installation worked without issues however when I connect the USB cable to the DT9829-8 it can't connect. When I check device manager I get the following error message. Any recommendation or is it possible to download just the DT9829 driver? Thanks, Todd