AI-110 incorrect readings

I'm getting incorrect readings in MAX from cFP-AI110 even when I wire 10Vdc directly to the input. Does someone know what causes this to occur?

rmorais,
What kind of readings are you getting? Do you have the module
configured for -10.4 to 10.4 Volts? Have you double checked your supply
voltage with a DMM or some other device capable of measuring voltages?
Finally, do you see this incorrect reading on only one channel, or all
the channels? Please let us know the details of the error and I'd be
more than happy to help.
Regards,
Ryan Verret
Product Marketing Engineer
Signal Generators
National Instruments

Similar Messages

VISA Read gets incorrect data from serial connection

I am having difficulty using the VISA functions in LabVIEW to read data from a virtual COM port. Data is being sent from a serial to USB chip via a USB connection using OpenSDA drivers. I have a python program written to read from this chip as well, and it never has an issue. However, when trying to achieve the same read in LabVIEW I am running into the problem of getting incorrect data in the read buffer using the VISA Read function.
I have a VISA Configure Serial Port function set up with a control to select the COM port that the device is plugged into. Baud rate is default at 9600. Termination char of my data is a newline, which is also default. Enable termination char is set to true. A VISA Open function follows this configuration, and then feeds the VISA Resource Name Out into a while loop where a VISA Read function displays the data in read buffer. Byte count for the VISA Read is set to 20 so I can read more of the erroneous datat, however actual data will only be 6-12 bytes. The while loop has a wait function, and no matter how much I slow down the readings I still get incorrect data (I have tried 20ms thru 1000ms).
The data I expect to receive in the read buffer from VISA Read is in the form of "0-255,0-255,0-255\n", like the following:
51,93,31\n
or
51,193,128\n
And occasionally I receive this data correctly, however I intermittently (sometimes every couple reads, sometimes a couple times in a row) get incorrect readings like this:
51,1\n
51,193739\n
\n
51,1933,191\n
51,,193,196\n
51,1933,252
51,203,116203,186\n
Where it seems like the read data is truncated, missing characters, or has additional characters. Looking at these values, however, it seems like the read was done incorrectly because the bytes seem partially correct (51 is the first number even in incorrect reads).
I have search but haven't found a similar issue and I am not sure what to try from here on. Any help is appreciated. Thanks!
Attachments:
Serial_Read_debugging.vi ‏13 KB

The first thing is that none of the error clusters are connected so you could be getting errors that you are not seeing. Are you sure about the comm parameters? Finally, I have never had a lot of luck looking for termination characters. You might want to just capture data and append each read into one long string just to see if you are still seeing this strangeness.
What sort of device is returning the data? How often does it spit out the data? How much distance is there between it and your computer? Can you configure it append something like a checksum or crc to the data?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

My thermocouples reading are incorrect

I am acquiring temperatures using type-J thermocouples with PCI-6033E and SCB-100. I have created a virtual channel for each thermocouple and I also have a channel for the CJC that I tested and it works ok. I am running the channels in differential mode which is the mode of the board. I have also 27K resistances between the negatives and the AIGND.
The thermocouples give incorrect readings. For example, if I move one thermcouple signal from one channel to another, it gives totally differnt readings.
Another example is that sometimes the readings are ok while other times the readings are wrong without modifying anything in the circuit. Am I doing something wrong or what?

I am using the board (PCI-6033E) to measure 24 signals, 8 of them are for thermocouples. All the remaining signals are working properly. So, I don't think there is something wrong with the board. I did also the on-line calibration test for the board and it turned out to be ok. It's only the thermocouples that cause me problems. Now, 7 of the thermocouples are giving me correct values while the 8th one is giving me unphysical values eventhough it was working ok some time ago. (same signal, same channel, same everything).
Regarding the interchannel delay, I'm sorry but I am new to LabView, How can I set the interchannel delay?

Smart collections not reading correct number of images inside

I have an issue with smart collections for the first time. I have just set up a new workflow with 4 stages and the number counter next to the collection is counting wrong despite the images being represented in the collection. For example if I click on the smart colection I can see 10 images inside but the counter reads 3. Does anybody have this experience?
I have optimised my cataloge, however I do have some 20,000 images inside... will this reduce the ability of LR to keep up to running speed with such smart collection operations, giving incorrect readings.
What are best practices for image numbers and the arguement for running multiple cats. I've just tried in a fresh catalogue and the results were perfect. Is this an inherent limitation of Lightroom? I was under the impression that I could manage my whole archive and current projects under one roof, as it were.
Thanks,
Graeme

I suppose it would be worth optimising the catalog, if you haven't already done so.
Another idea, may be to make a fresh catalog and "import from another catalog" your current one, into that. This transfers pictures and keywords, collections, smart collections etc. But if there is something "structural" or "infrastructural" wrong with your live catalog, I'd expect that to get left behind by this process - since everyting should AFAIK get re-indexed after being brought in.
Then you'd go forward with the new catalog, if successful. Doing this makes no change to your present catalog so can do no harm to try - the various pictures' source files are simply shared across both catalogs - single file referenced by both, IOW.
One thing in your post (which I did not fully understand) suggested to me that your workflow relies at some point, on external metadata being written. If your workflow and smart collections criteria rely on the LR tracking of the status of external metadata, such as "is up to date", I believe this specific aspect has been found quite buggy and unreliable by many people: the metadata status badges etc, being sometimes rather approximate in their correspondence to reality . So if some other criterion could be found on which to base your workflow, that would probably go more smoothly .
However, if you do have more than one catalog pointing to just one set of photo source files, that aspect of writing metadata out, will of course be a little problematic - since the latest catalog to have written to the file will "overwrite", and the other catalog(s) will regard that same image as having been externally modified meanwhile.
regards, RP

Errors -200329 and -200077

Hi guys,
I was wondering if anyone could shed any light on an odd problem I am having with an old vi. I've attached an image of the aquisition element of the program. The program aquires continuously from 32 thermocouples and two pressure gauges (analogue voltages). Basically it was working great until the time I had to add an extra channel for a new differential pressure gauge (analogue voltage output). It had a custom scale so I created a new virtual channel as I had done with the other channels. Now when the vi is run, it seems to work roughly 30% of the time, whilst the others show either nothing at all or incorrect readings from the channels. Highlight execution shows an error -200077 or -200329 from the 'start task'. The errors read this:
Error -200329 occurred at an unidentified location
Possible reason(s):
An error has occurred while attempting to configure the device for an analog input acquisition.
If an external master timebase is being used, make sure the source is connected and generating an appropriate clock. Otherwise, contact National Instruments Technical Support.
Error -200077 occurred at an unidentified location
Possible reason(s):
Requested value is not a supported value for this property.
I am using Labview 7.1 with a SCXI-1600. It has two slots: SCXI-1520 (where the problematic task is configured) and SCXI-1102 (for 32-thermocouples). I would really appreciate any advice that anyone could offer on this subject, I've sort of hit a dead end.
Many thanks
Luke
Attachments:
DAQ.JPG ‏64 KB

Hey Ipaza,
I'm basically just regurgitating the main points from the links that muks has kindly posted.
1) Try and update to the latest driver for DAQmx as this error can be thrown up when acquiring from more than 2 thermocouples. (error -200329)
2) Test your acquisition card using the following link to ensure that your clock is functioning properly. http://digital.ni.com/softlib.nsf/MainPage?ReadForm&node=132010_US (error -200077)
3) Ensure that your clock is connected properly. (error -200077)
Hope this helps.
Chris
National Instruments - Tech Support

Leaving MacBook Pro Plugged In

The majority of the time I use my MacBook Pro, it is near an outlet (about 50% time on my desk at work, and 50% on couch at home). I want to make my battery last as long as possible, but I do not know if that will be accomplished by leaving it plugged in whenever I can, or by letting it run off the battery whenever I can. I do run it all the way down at least once a month (more like once a week), per apple's advice. Does anyone know the best solution? Thank you.

There is nothing wrong with using the computer on AC power or on battery. If the battery is charged above 95 percent, the charging circuitry is shut off to prevent constant battery charging. If the charge level drops below 95 percent then the battery will recharge.
You do not need to run the battery down purposefully more than once every couple of months. This is only for the purpose of maintaining calibration of the battery circuitry that measures the amount of charge remaining. If the battery is not used much or is rarely run down then the measurement circuitry can be off leading to incorrect readings of remaining battery life.
If you frequently use the computer on battery such that the battery is being substantially depleted then there is no need for the periodic calibration ritual suggested in the Apple documentation.
Lithium-Polymer batteries have an average life of around 500 full discharge/recharge cycles. If you put your laptop in storage for an extended period of time you should discharge the battery to about a 30-40 percent charge level. That's the recommended storage level.

Ipod is not working on iphone

The sound is on when I check youtube or itunes. When I try to play a song on the ipod, there is nothing playing on the speaker or the headphones. I just did an update earlier this week at the store. I've checked the website and can't find any troubleshooting info for this on the iphone.

Does the iPod see the sensor? Can you calibrate the iPod but get incorrect readings?
Whick app are you using? The built-in app requires the seperate sensor.
The Nike+ app
Nike+ Running for iPhone 3GS, iPhone 4, iPhone 4S, iPhone 5, iPod touch (3rd generation), iPod touch (4th generation), iPod touch (5th generation) and iPad on the iTunes App Store
uses semsors built in the iPod

Frquency & Duty cycle Value changes- every time

Hello all
im using pcie 6320 to measure the frequency and the duty cycle of a signal.i have attached my vi & the data measured for reference.The values highlighted in red ,is my actual frequency and duty cycle but values changes for every 1 sec.Please correct me if i have any mistake.
Solved!
Go to Solution.
Attachments:
measure frquency-duty.vi ‏54 KB
HZ-DUTY.JPG ‏37 KB

You'll need to enable digital filtering--insert the following property node into your code (call the property node before starting the task):
Try a "Min Pulse Width" of a few us and increase it if you still are picking up incorrect readings.
The errant numbers are coming from false edges being picked up during transitions, enabling digital filtering will cause the DAQ device to ignore any transitions with a pulse width of less than the set value. Your 475 Hz 72% duty cycle signal should have a high time of about 1.52 ms and a low time of about .59 ms):
656 Hz = ~1/(high time)
1718 Hz = ~1/(low time)
MHz values = multiple edges picked up during a single transition.
Best Regards,
John Passiak

[Athlon64] Problem with MSI RS480M2-IL

Hi all,
I have problem with MSI RS480M2-IL. My problem is My temperature is very high... around 55-60c ... i am using AMD 3000+ Venice and no OC... and SpeedFan unable to detect my Voltage usage... Aida32 also same... 1 more thing is when i tried to run SiSoft Sandra 2005... it will take alot of time to load, sometime will just hang. i Test PCMark04 and found only got 3k for average mark... my friend getting 4k+ and we are using same spec... Below is my Spec:-
MSI RS480M2-IL
AMD 64 3000+ Venice E3
Bios Version 3.8
Geil PC3200 DDR400 2.5-3-3-6
Maxtor 60GB HDD 7200RPM 2mb
Verudium Power Vortex 420W
Hope some one can advised me what to do... my score too low and my board detect temperature and voltage is not accurate... Hope MSI Engineer will look thought and help me... Thank for Viewing !

the underlying "Who's fault is it?" question: AMD64 VENICE CORE (E3) PROCESSORS? or MSI RS480M2-IL MOBOS?
so far, ALL users with this proc/mobo combination HAVE the high (or incorrect) temperature issue. replacing the mobo obviously will not resolve the issue but replacing the proc with one that is NOT a Venice E3 core, does the trick. but of course, not everyone will have the privilege of exchanging their damned proce via the retailer specially if it's beyond the first 21 days of purchase.
in my case, my retailer refused to have the E3 proc replaced with the 'corrected' E6 version no matter how hard you explained the known issues with the E3. no chance of AMD recalling the E3 cores since problems with are only isolated to the particular MSI RS480M2 boards.
so for users that are and will be stuck with this combination, what is the solution then to the temperature issue? in my opinion, it's up to MSI to perhaps release a bios update that will correct this. another important thing to consider is the question: IS MY VENICE CORE INDEED OVERHEATING OR IS IT JUST THE MSI MOBO SHOWING INCORRECT READINGS? the proc overheating in actuality is obviously a lot different thatn just having an incorrect bios temp readings.
based on what i have observed, my Venice core displays the correct cpu temps (33-35*C) when being used on a MSI K8 Diamond mobo. placing the proc back to the R2480M2 board shows a very unusual 61-63*C bios cpu temp. furthermore, if i touch the stock heatsink/fan cooler that i have (for both motherboards), it really does NOT seem to be extremely hot to think that the cpu is actually overheating. in addition, my system using the RS480M2 performs well and has no spontaneous shutting down problems whatsoever. of course, my sense of touch is not as accurate as a thermometer but more or less, if you consider all the points i mentioned, most of us can say that the whole issue is just a matter of incorrect cpu reading.
perhaps the ATI chipset is the one to blame since i have notices as well that the Venice core processors do not seem to have this high temp problems with MSI's K8 mobos with the NVIDIA chipsets.
one last question: so do you guys think that this problem can be resolved by a simple bios revision? (as a dell tech guy, i do know for a fact that bios updates resolves overheating error messages in Inspiron/Latitude laptops)

[875 NEO] Temperature issues

Hello everyone
I recently upgraded my bios to version 2.4 and now my cpu temps are showing a considerable increase in temp readings.
before I upgraded I was showing cpu at 27C to 31C (watercooled) now temps are around 50C.
Anyone know if bios 2.4 has temp reporting issues? I am using speedfan configured from the instructions on this board.
BTW I have the earlier version of the 875 Neo.
Thanks
einsteins

Quote from: WolfgangV on 26-February-05, 04:24:32
AAAHAA, I'm not a SpeedFan user myself, but I have read a lot of post pretaining to incorrect settings therefore resulting in incorrect readings on SpeedFan. Their should me a lot of Moderators and Users that can help you, if your settings have accidently change or what type of core or chipset or something like that.
My opinion "Long Live CoreCenter".
I also use Motherboard Monitor...it is giving me the same temp readings .....both of those apps worked correctly prior to the temps starting read wrong.
It was my thought also abut the settings (since BIOS is reprting the correct temp in the PC HEALTH section) ...and I did set up speedfan according to Danny's post.
[quote When you ran LiveUpdate, you made a RescueDisk right?
*Rename the 2.3 BIOS file to AMIBOOT.ROM
*Copy it
*Paste it into youre rescue disc, say 'YES' to overwrite
*Leave the disk in youre HDD and restart
*Follow the onscreen promts
Quote
I did make a backup and tried to boot with it but when I inserted the backup disk and started the computer it got just past the ram drive part and gave me an error.
I remember reading something about holding CTRL-HOME at some point in the process...maybe thats why it failed?
I will copy the 2.3 BIOs file to the disk and try again....anyone have any comments on the disk error by chance?
I am at work atm so I cant give the exact error message right now, but is just after I saw AMIBOOT on the screen below the loading ram drive part.
Thank you again everyone for all your help....
einsteins

Lenovov G505s high temperature reading, bios related????

Hello! I recently bought the Lenovo G505s (AMD A8 5550M) and so far am very impressed with it. I couldn't stand windows 8 so I installed windows 7.
Recently I started playing Dead Island and I noticed the computer was getting hot - not too hot - but hot enough for me to check the temperature using HWmonitor. It displayed a cpu temp of 103*C! I was shocked. So I stopped playing immediately and let it cool down until the morning. I started up the computer and the temperature read 83*C, even though the computer was dead cold. After searching for this issue, I've noticed that some people have had this problem. I'm guessing there's a problem with the way the temperature is being reported by HWmonitor, because the computer isn't hot at all. I read that HWmonitor may give incorrect readings for AMD based systems, so I downloaded Core Temp. This program wouldn't give a cpu temperature, it simply said N/A. So something's up.
I tried to check the temperature in the BIOS (83CN33WW v2.03), but there is no option for checking the temperature. I thought that was weird. But maybe this is why Core Temp isn't reporting the temperature? Because the BIOS isn't even reporting it? Tried to find an updated version of BIOS for windows 7...Unfortunately none available (only for windows 8).
What do you guys think? Is there another BIOS I can install that would report the temperature? I don't want to keep gaming if it kills my computer, and I don't want to game until I have accurate cpu temperatures.
Solved!
Go to Solution.

Hi Lauberse,
I’m sorry to inform you that the BIOS update is not be available for Windows 7, This version of BIOS installed does not have the option to display the temperature, I suggest you to download the below software and check the CPU temp once again and please check the compatibility of the Game before playing in the computer.
Core Temp
As an alternative I suggest you to check the steps in the similar post provided by Solid_Cruver
Hope to hear back soon
Best Regards
Shiva Kumar
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Problem reading 70.0 Vdc using NI 4060 DMM.

I guess it's due to low input impedance for 250 V and 25,that I'm getting incorrect readings. What is your recommenation to correct that problem?

Hi Dean,
I have used the 4060 but it worked for me.
Please provide more details.
What works?
What does not?
Post an eaxample.
etc.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

P7N Diamond - Memory Problem ???

Hi all,
I have recently purchased a new computer and have been having trouble with it since day 1.
My current RAM (see specs bellow) is showing incorrect readings. My tech friend is thinking that I have gotten ripped off...
I downloaded Nvidia's nTune and
nTune seems to be reading the Memory Modules as:
2 part numbers as KTC1G-UDIMM
the other 2 Part numbers as KHX8500D2/1GN
In this order:
0 dimm - KTC1G-UDIMM
1 dimm - KHX8500D2/1GN
2 dimm - KTC1G-UDIMM
3 dimm - KHX8500D2/1GN
>>> [EDIT]: Also I'm only able to stably or somewhat stabley runn it at 800... and if I try 1066 it doesnt load my Win XP and tryed the CPU/FSB down at 1066.. while that is ok... when it comes to video or HD video is starts to play up giving me black screens and audio hiccups and a few click of a mouse and boom... time to hit reset.
Is this a Bios issue that can be updated or has the guy given me to older ram sticks??
I play Age of Conan... I know that the game has some issues... but My issue is that the computer just Restarts its self... Straight off and the continues to reboot.
There has not been reports about this regarding AoC.
My Specs:
Intel QX9650
MSI P7N Diamond
2 Kingston KHX8500D2k2/2G KIT's (4gigs)
Gigabyte 9800gx2
WD Raptor 72GB
Segate 1TB

Hi again,
Well this is deffinetly UnMatched RAM....
I ran CPUZ and got founf that the 2 different pairs of RAM have different Manufacturing Dates.. not sure if thats something to go by though i guess it would be since it is in WEEK not Days lol ...but the actual "Part Numbers" show what the deal is:
Memory SPD
DIMM #1
General
Memory type      DDR2
Module format      Regular UDIMM
Manufacturer (ID)   Kingston (7F98000000000000)
Size         1024 MBytes
Max bandwidth      PC2-6400 (400 MHz)
Part number      KTC1G-UDIMM
Serial number      A8249D51
Manufacturing date   Week 10/Year 08
Attributes
Number of banks      2
Data width      64 bits
Correction      None
Nominal Voltage      1.80 Volts
EPP         no
XMP         no
Timings table
Frequency (MHz)      200   266   400
CAS#         3.0   4.0   5.0
RAS# to CAS# delay   3   4   5
RAS# Precharge      3   4   5
TRAS         9   12   18
TRC         12   16   23
DIMM #2
General
Memory type      DDR2
Module format      Regular UDIMM
Manufacturer (ID)   Kingston (7F98000000000000)
Size         1024 MBytes
Max bandwidth      PC2-6400 (400 MHz)
Part number      KHX8500D2/1GN
Serial number      8C31F302
Manufacturing date   Week 11/Year 08
Attributes
Number of banks      2
Data width      64 bits
Correction      None
Nominal Voltage      1.80 Volts
EPP         yes (3 profiles)
XMP         no
Timings table
Frequency (MHz)      200   266   400
CAS#         3.0   4.0   5.0
RAS# to CAS# delay   3   4   5
RAS# Precharge      3   4   5
TRAS         9   12   18
TRC         12   16   23
EPP profile 1 (abbreviated)
Voltage level      2.200 Volts
Address Command Rate   2T
Cycle time      1.875 ns (533.3 MHz)
tCL         5.0 clocks
tRCD         6 clocks (9.50 ns)
tRP         6 clocks (9.50 ns)
tRAS         15 clocks (28.00 ns)
EPP profile 2 (abbreviated)
Voltage level      2.200 Volts
Address Command Rate   2T
Cycle time      2.500 ns (400.0 MHz)
tCL         4.0 clocks
tRCD         4 clocks (10.00 ns)
tRP         4 clocks (10.00 ns)
tRAS         13 clocks (32.00 ns)
EPP profile 3 (abbreviated)
Voltage level      2.200 Volts
Address Command Rate   2T
Cycle time      3.000 ns (333.3 MHz)
tCL         3.0 clocks
tRCD         3 clocks (9.00 ns)
tRP         3 clocks (9.00 ns)
tRAS         10 clocks (30.00 ns)
DIMM #3
General
Memory type      DDR2
Module format      Regular UDIMM
Manufacturer (ID)   Kingston (7F98000000000000)
Size         1024 MBytes
Max bandwidth      PC2-6400 (400 MHz)
Part number      KTC1G-UDIMM
Serial number      AA249C51
Manufacturing date   Week 10/Year 08
Attributes
Number of banks      2
Data width      64 bits
Correction      None
Nominal Voltage      1.80 Volts
EPP         no
XMP         no
Timings table
Frequency (MHz)      200   266   400
CAS#         3.0   4.0   5.0
RAS# to CAS# delay   3   4   5
RAS# Precharge      3   4   5
TRAS         9   12   18
TRC         12   16   23
DIMM #4
General
Memory type      DDR2
Module format      Regular UDIMM
Manufacturer (ID)   Kingston (7F98000000000000)
Size         1024 MBytes
Max bandwidth      PC2-6400 (400 MHz)
Part number      KHX8500D2/1GN
Serial number      8D31BC02
Manufacturing date   Week 11/Year 08
Attributes
Number of banks      2
Data width      64 bits
Correction      None
Nominal Voltage      1.80 Volts
EPP         yes (3 profiles)
XMP         no
Timings table
Frequency (MHz)      200   266   400
CAS#         3.0   4.0   5.0
RAS# to CAS# delay   3   4   5
RAS# Precharge      3   4   5
TRAS         9   12   18
TRC         12   16   23
EPP profile 1 (abbreviated)
Voltage level      2.200 Volts
Address Command Rate   2T
Cycle time      1.875 ns (533.3 MHz)
tCL         5.0 clocks
tRCD         6 clocks (9.50 ns)
tRP         6 clocks (9.50 ns)
tRAS         15 clocks (28.00 ns)
EPP profile 2 (abbreviated)
Voltage level      2.200 Volts
Address Command Rate   2T
Cycle time      2.500 ns (400.0 MHz)
tCL         4.0 clocks
tRCD         4 clocks (10.00 ns)
tRP         4 clocks (10.00 ns)
tRAS         13 clocks (32.00 ns)
EPP profile 3 (abbreviated)
Voltage level      2.200 Volts
Address Command Rate   2T
Cycle time      3.000 ns (333.3 MHz)
tCL         3.0 clocks
tRCD         3 clocks (9.00 ns)
tRP         3 clocks (9.00 ns)
tRAS         10 clocks (30.00 ns)

Meter readings on the incorrect equipment

Hello ISU experts,
In which table one can see Time slices of the Device.
Incicent description:
Meter readings on the incorrect equipment
When meter readings are received for the old meter after a rate change the meter readings are set to the incorrect equipment. This has consequences for reconciliation. Example EAN 871694840010613215.
There are errors since the meterchange. According the rate data equipment 11501576 is removed since 02.04.2005. But still meter readings are received AFTER this period. It looks like that the last record of equipment 15559930 is the previous meter reading of the old equipment.
Thanks in advance
Regards

Hi SHABNUM,
you can see technical device data in view V_EGER or ETDZ. The billing relevant information is stored in EASTS (association of device to installation). If you are using device info records --> table EGERR has to be chosen.
BUT I thin what your issue is: the meter reading order seems to be wrong --> table EABL and EABLG. You can still read a meter which is not installed!
Correction supposal: use EL37 to reverse the meter readings and use EL28 to create NEW meter reading orders for the correct device --> store the meter reading results.
I hope that helps
Uwe

Incorrect AMUX/PCI6025 readings using Labview/DAQ

I have an AMUX64/PCI6025. Using my DVM, I measure the voltage at the AMUX screw terminals on various channels with correct readings obtained. Performing measurements with Labview/DAQ are incorrect. What is causing this?

Hello;
The first thing to double check is if the input mode is set accordainly with the connections made.
The best bet is to revisit the AMUX Users Manual and double check the connections you made with the ones shown in the manual. Furthermore, go to MAX and check the input mode of the DAQ device.
Everything must match.
In case you got everything accordainly with the manual, and you still see the same behavior, the problem is probably hardware related.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

AI-110 incorrect readings

Similar Messages

Maybe you are looking for