Lm_sensors: sensors output

Hi,
When I type "sensors", I get:
acpitz-virtual-0
Adapter: Virtual device
temp1: +51.0°C (crit = +105.0°C)
and nothing else. I can't seem to get the chipset info.
"sensors-detect" detected:
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
* ISA bus, address 0x290
Chip `ITE IT8705F Super IO Sensors' (confidence: 9)
Do you want to generate /etc/conf.d/lm_sensors? (YES/no):
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
Unloading cpuid... OK
Why doesn't "sensors" print it87-related info?
I don't know if it is related, but sometimes the temperature gets very high (I notice it with my fingers) and I have to reboot; then the fan runs at full speed for about 2 min to cool the CPU.
Any help?
Last edited by jmss (2011-08-12 10:33:24)

I made sure i2c_dev, i801, and core were all loaded.
when i run sensors-detect, this is the output
[timms@arch ~]$ sudo sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: Alienware M11x (laptop)
# Board: Alienware 0VWGCV
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
Next adapter: SMBus I801 adapter at 18c0 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x1d
Probing for `Texas Instruments TMP421'... No
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... No
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-1)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-2)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter 2 at 1:00.0 (i2c-3)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-4)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-5)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter 7 at 1:00.0 (i2c-6)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter 8 at 1:00.0 (i2c-7)
Do you want to scan it? (YES/no/selectively): y
Next adapter: NVIDIA i2c adapter 9 at 1:00.0 (i2c-8)
Do you want to scan it? (YES/no/selectively): y
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): y
You should now start the lm_sensors service to load the required
kernel modules.
and here's my conf.d/lm_sensors
# Generated by sensors-detect on Fri Aug 12 16:23:45 2011
# This file is sourced by /etc/rc.d/sensors and defines the modules to
# be loaded/unloaded.
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).
HWMON_MODULES="coretemp"
# For compatibility reasons, modules are also listed individually as variables
# MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.
MODULE_0=coretemp
Anything else that would help?

Similar Messages

VFD noise on other sensor output such as : Thermocouples, Accelerometer, Torque meter

Hi,
I'm using a PCIe-6351 Daq board (and SCB-68) for my test rig. I'm collecting different kinds of sensor outputs through this DAQ board such as temperatures, acceleration, and torque meter output.
beside that, I have connected a VFD (Baldor H2 inventor) using a USB cable to the PC case. I use this VFD to control motor speed. (http://www.baldor.com/products/accontrols/vs_inverter.asp)
Here is my problem:
when I turn on the VFD I get a lot of noise on every signal. This noise is like a peak which repeats every 5-6 seconds.
So it's not 50-60 HZ noise of outlets.
You can see related uploaded video clips on :
http://www.megaupload.com/?d=4NHDIVV7
http://www.megaupload.com/?d=2461Z7KN
I have uploaded some pictures too.
Is there any way that I can filter this noise in Labview? ( I have tried Filtration VI in labview, but couldn't find a correct setting)
How can I get rid of this noise?
I really appriciate your help on this matter.
Thanks.
-Jeff
Attachments:
Pics.zip ‏585 KB

I can very much identify with this issue. I have a test bench with two motors and corresponding Baldor H2 VFD's on it. I have a variety of sensors such as accelerometers, hall effect sensors, and a torque meter. The bench was put together "professionally" but still get this kind of noise.
The *only* sensor that I have this trouble with is the torquemeter. I get an impulsive EMI blast every 12 seconds on this signal with just one drive turned on. With the other drive turned on, the noise is excessive. I have spent weeks troubleshooting assumed ground-loop faults with the torque meter company's tech rep - to no avail.
I have confirmed that this EMI is from the drive. I hooked up a wire to the signal lead of an oscilloscope's VFD (acting as an antenna) and the noise I get on this oscilloscope is very similar to what I get on my torquemeter. (The noise is present only when the drive is powered up)
The noise from the VFD will not be cured by using a low pass filter. Impulsive type events have very broad band noise.
My new approach is to try and use adaptive noise cancellation to get rid of the the VFDs' EMI on the torquemeter. I gather the noise signal on my DAQ card (PCI-7851-R) by plugging just one wire into the positive port of an AI port and tying a 1 mega Ohm resistor from that port's ground to the AI port; this provides a means of collecting the EMI from the drive with an "antenna." The wire dangles by the side of the VFD with the other end taped up. See the following for a description of adaptive noise cancellation with labview (also possible on an NI FPGA device):
http://zone.ni.com/reference/en-XX/help/372357A-01/lvaftconcepts/aft_noise_cancel/
I believe this to be the only sound signal processing means of addressing this issue. I am still struggling to get it to work myself. I'll advice as I progress.
Cheers
Jordan McBain, PhD
LabVIEW Controls Engineer
Revolutionary Engineering

Is it possible to multiplexe 8 analog sensors output into one PXI4472 channel?? can PXI4472 recognize those signals??

I have around 64 analog sensors to connect to PXI4472. Instead of buying 8 PXI4472, is it possible to multiplexe 8 analog sensors output into one PXI4472 channel?? can PXI4472 recognize those signals??

Such a set up is not recommended. Some of the drawbacks are:
Depending on how you plan to multiplex the signals together (SCXI/PXI switch, 3rd party mux), you could very easily be introducing noise to your system.
Multiplexing the signals together into one line limits your sampling rate to the switching speed of you multiplexer device.
You will probably need to spend more time developing handshaking schemes in order for switching and acquisition to occur in such a way that you don't miss signals that you want to acquire.
These are only some of the drawbacks to this setup. All in all, the only functionality of the 4472 board that you would be left with is it's ability to sample all eight channels at the same time. So, you could multi
plex all the signals together, but doing so is not recommended.
However, I have a couple of questions. Do you want to sample all 64 sensors at the same time? Assuming that you are not, how are you planning on multiplexing the signals together? What kind of a chassis are you working with? Please let me know.
Logan S.

Nxt infrared sensor output

Hello,
I am working on a project that involves the lego nxt mindstorm. In my labview block diagram, I have the nxt infrared sensor connected to a waveform output. That is, a waveform is displayed according to the movement of the robot and the infrared sensor.
I am writing to find out if it is possible to make the output numbers instead of a waveform. Basically, I don't want it to draw a graph, I want to read the output as numbers. Better yet, it could also draw the graph but I also want to be able to get the numbers.
What function do i use?
Any suggestion is definitely appreciated.
Thank you.

Hi olams,
You should be able to right-click on the output terminal and select Create»Indicator. It sounds like this waveform graph is not the standard output for that VI, so creating an indicator should make a numeric output. Thanks.
Stephen Meserve
National Instruments

NI 4351 giving wrong sensor output

Hey guys, thanks in advance for any help recieved.
I have 6 sensors (3 RTD's and 3 thermistors) connected to a NI 4351 and the sensors were giving the right outputs a few months ago, but now all the sensors are giving out very low values. Any help will be greatly appreciated.
Regards,
Alim
Solved!
Go to Solution.

Glad things worked out.
-CC
"If anyone needs me, I'll be in the Angry Dome!"

Sensor output as input to java program

hi , pls tell me how to use output from infrared senors as input to java program..................???????
mail me the code at [email protected]

Hi,
Check the following syntax:
SUBMIT <rep> TO SAP-SPOOL
[<params>|SPOOL PARAMETERS <pripar>]
[ARCHIVE PARAMETERS <arcpar>]
[WITHOUT SPOOL DYNPRO].
Ex:
The following executable program is connected to the logical database F1S:
REPORT SAPMZTS1.
TABLES SPFLI.
GET SPFLI.
NEW-LINE.
WRITE: SPFLI-MANDT, SPFLI-CARRID, SPFLI-CONNID,
SPFLI-CITYFROM, SPFLI-AIRPFROM, SPFLI-CITYTO,
SPFLI-AIRPTO, SPFLI-FLTIME, SPFLI-DEPTIME, SPFLI-ARRTIME,
SPFLI-DISTANCE, SPFLI-DISTID, SPFLI-FLTYPE.
The following program calls SAPMZTS1 and sends the output to the spool system:
REPORT SAPMZTST NO STANDARD PAGE HEADING.
DATA: VAL,
PRIPAR LIKE PRI_PARAMS,
ARCPAR LIKE ARC_PARAMS.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
LAYOUT = 'X_65_132'
LINE_COUNT = 65
LINE_SIZE = 132
IMPORTING
OUT_PARAMETERS = PRIPAR
OUT_ARCHIVE_PARAMETERS = ARCPAR
VALID = VAL
EXCEPTIONS
ARCHIVE_INFO_NOT_FOUND = 1
INVALID_PRINT_PARAMS = 2
INVALID_ARCHIVE_PARAMS = 3
OTHERS = 4.
IF VAL <> SPACE AND SY-SUBRC = 0.
SUBMIT SAPMZTS1 TO SAP-SPOOL
SPOOL PARAMETERS PRIPAR
ARCHIVE PARAMETERS ARCPAR
WITHOUT SPOOL DYNPRO.
ENDIF.
Regards,
Bhaskar
Edited by: Bhaskar Chikine on Sep 9, 2008 4:33 PM

0-30mv Sensor Output

Hi. I'm new to labview and data acquisition so please excuse the newbie question:
What is the best way to read a 0-30mv output from a load cell or strain gauge? Does NI make DAQs for this voltage range? Can the same DAQ be used as would be for reading a 0-5V signal (is the accruacy of the DAQs enough to get good readings from a 0-30mV device).
Thank you for any help.

Without getting too deep into the electronics, basically, you need a load cell amplifier, or strain gauge amplifer. Google it. With an amplpifer, you can "convert" the 0..30mV to 0..5V or similar.
What DAQ are you using?
Richard

Lm_sensors and wrong output

I installed lm_sensors and did the detection also and while detecting the result was :
sudo sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: Dell Inc. Inspiron 1545 (laptop)
# Board: Dell Inc. 0G848F
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... Yes
Found unknown chip with ID 0xfc11
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): yes
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
Module i2c-dev loaded successfully.
Next adapter: i915 gmbus disabled (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 gmbus ssc (i2c-1)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 GPIOB (i2c-2)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 gmbus vga (i2c-3)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 GPIOA (i2c-4)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 gmbus panel (i2c-5)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: i915 GPIOC (i2c-6)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: i915 gmbus dpc (i2c-7)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 GPIOD (i2c-8)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 gmbus dpb (i2c-9)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 GPIOE (i2c-10)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 gmbus reserved (i2c-11)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 gmbus dpd (i2c-12)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: i915 GPIOF (i2c-13)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: DPDDC-D (i2c-14)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: SMBus I801 adapter at 1100 (i2c-15)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): yes
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
Unloading cpuid... OK
BUT doing sensors i get
sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +44.5°C (crit = +93.0°C)
i did everything but the result is still the same. at lest I have MORE than one CORE.
more information:
CI ID Works? Vendor Device Driver Kernel
80862a40 Yes Intel Corporation Mobile 4 Series Chipset Memory Controller Hub intel-agp
80862a42 Yes Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller i915 v2.6.32-
80862a43 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
80862937 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4
80862938 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5
80862939 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6
8086293c Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2
8086293e Yes Intel Corporation 82801I (ICH9 Family) HD Audio Controller snd-hda-intel
80862940 Intel Corporation 82801I (ICH9 Family) PCI Express Port 1
80862942 Intel Corporation 82801I (ICH9 Family) PCI Express Port 2
80862944 Intel Corporation 82801I (ICH9 Family) PCI Express Port 3
80862948 Intel Corporation 82801I (ICH9 Family) PCI Express Port 5
80862934 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1
80862935 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2
80862936 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3
8086293a Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1
80862448 Yes Intel Corporation 82801 Mobile PCI Bridge i810_rng
80862919 Yes Intel Corporation ICH9M LPC Interface Controller iTCO_wdt v2.6.28-
80862929 Yes Intel Corporation ICH9M/M-E SATA AHCI Controller ahci v2.6.25-
80862930 Yes Intel Corporation 82801I (ICH9 Family) SMBus Controller i2c-i801 v2.6.25-
11ab4354 Yes Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller sky2 v2.6.25-
14e44315 Yes Broadcom Corporation BCM4312 802.11b/g LP-PHY ssb v2.6.30-
Module Size Used by
nls_utf8 1320 1
udf 79241 1
crc_itu_t 1297 1 udf
ppp_async 7090 0
crc_ccitt 1331 1 ppp_async
fuse 67290 7
pppoe 10402 2
pppox 2066 1 pppoe
ipv6 290791 12
ppp_generic 23397 7 ppp_async,pppoe,pppox
slhc 5193 1 ppp_generic
rfcomm 34909 4
bnep 9245 2
ses 6238 0
enclosure 6171 1 ses
btusb 11577 2
bluetooth 139297 23 rfcomm,bnep,btusb
sg 25557 0
joydev 9895 0
uvcvideo 64963 0
snd_hda_codec_idt 55175 1
usbhid 35256 0
processor 24256 2
snd_hda_intel 22122 3
videodev 78006 1 uvcvideo
snd_hda_codec 77927 2 snd_hda_codec_idt,snd_hda_intel
uas 8088 0
ums_cypress 2990 0
hid 81635 1 usbhid
ums_realtek 4458 0
usb_storage 44263 4 ums_cypress,ums_realtek
serio_raw 4294 0
lib80211_crypt_tkip 8538 0
psmouse 55192 0
evdev 9530 13
media 10437 2 uvcvideo,videodev
v4l2_compat_ioctl32 8292 1 videodev
wl 2527176 0
dell_wmi 1517 0
thermal 7863 0
sparse_keymap 3088 1 dell_wmi
pcspkr 1819 0
snd_hwdep 6325 1 snd_hda_codec
snd_pcm 73888 3 snd_hda_intel,snd_hda_codec
snd_timer 19416 2 snd_pcm
snd 57818 10 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6146 1 snd
snd_page_alloc 7121 2 snd_hda_intel,snd_pcm
i2c_i801 8187 0
wmi 8347 1 dell_wmi
dell_laptop 7947 0
ac 3265 0
battery 10905 0
rfkill 15402 3 bluetooth,dell_laptop
iTCO_wdt 12717 0
iTCO_vendor_support 1929 1 iTCO_wdt
dcdbas 5488 1 dell_laptop
sky2 46875 0
lib80211 4158 2 lib80211_crypt_tkip,wl
ext4 370398 2
mbcache 5817 1 ext4
jbd2 71074 1 ext4
crc16 1297 2 bluetooth,ext4
sd_mod 28307 6
sr_mod 14951 1
cdrom 36329 1 sr_mod
uhci_hcd 23084 0
ahci 20865 3
libahci 18885 1 ahci
libata 173297 2 ahci,libahci
ehci_hcd 39511 0
scsi_mod 131546 8 ses,sg,uas,ums_cypress,usb_storage,sd_mod,sr_mod,libata
usbcore 142576 10 btusb,uvcvideo,usbhid,uas,ums_cypress,ums_realtek,usb_storage,uhci_hcd,ehci_hcd
i915 707339 2
drm_kms_helper 25409 1 i915
drm 183380 3 i915,drm_kms_helper
intel_agp 10904 1 i915
i2c_algo_bit 5199 1 i915
button 4470 1 i915
intel_gtt 14423 3 i915,intel_agp
i2c_core 20133 6 videodev,i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
video 11228 1 i915
Last edited by krax (2011-09-14 16:44:51)

I'd love to see this thread solved as my Dell XPS L1502 has the same situation. A sensors-detect brings the same module as you but the sensors outputs temperatures for just 2 cores for an i5 should be listed, which are about 50°C (normal?).
acpitz-virtual-0
Adapter: Virtual device
temp1: +54.0°C (crit = +100.0°C)
temp2: +54.0°C (crit = +100.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +55.0°C (high = +86.0°C, crit = +100.0°C)
Core 0: +54.0°C (high = +86.0°C, crit = +100.0°C)
Core 1: +49.0°C (high = +86.0°C, crit = +100.0°C)
The pwmconfig returns an error "no pwm-capable sensor modules installed".
Thanks for everyone contributing to this thread.
Last edited by nunobaba (2011-10-14 16:08:32)

Unable to detect a thermal sensor: lm_sensors and ACPI

HP Pavilion ze5600 laptop, latest Arch kernel, ran sensors-detect and this is the result:
Sorry, no sensors were detected.
This is relatively common on laptops, where thermal management is
handled by ACPI rather than the OS.
I tried "sudo modprobe thermal" and although successful there is no thermal entry in /proc/acpi . I also tried adding "acpi_enforce_resources=lax" to kernel boot line without success. I also attempted to insert the i2c-dev module before running sensors-detect, without success.
As I have not tried any other OS on this laptop I am unsure whether it does actually have a sensor but googling around others seem to have been successful. Any suggestions on how to proceed would be most welcome.

I'd love to see this thread solved as my Dell XPS L1502 has the same situation. A sensors-detect brings the same module as you but the sensors outputs temperatures for just 2 cores for an i5 should be listed, which are about 50°C (normal?).
acpitz-virtual-0
Adapter: Virtual device
temp1: +54.0°C (crit = +100.0°C)
temp2: +54.0°C (crit = +100.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +55.0°C (high = +86.0°C, crit = +100.0°C)
Core 0: +54.0°C (high = +86.0°C, crit = +100.0°C)
Core 1: +49.0°C (high = +86.0°C, crit = +100.0°C)
The pwmconfig returns an error "no pwm-capable sensor modules installed".
Thanks for everyone contributing to this thread.
Last edited by nunobaba (2011-10-14 16:08:32)

What is the difference between LV general and LV RT if we consider I want to read the output of a temperature sensor online??

Hi everybody,
I am very new in LV and I need to read my temperature sensore outputs online in order to make needed changes to the system each time that the temperature changes. If I use LV genral or LV RT??
Thanks
Solved!
Go to Solution.

Hi elahetal. The LV vs. LV RT decision really depends on what your timing requirements are.
RT isn't necessarily about being as fast as possible, but rather as consistent as possible.
If you have a measurement that must be taken every 100mS +/- 2mS then you pretty much have to use RT. A general purpose OS like Windows will randomly go off and do other things (read a cd, feed the printer, index the disk, etc.), causing your measurement to be late.
An RT environment will allow you to determine precisely when the system should do what. The trade-off is that the RT environment is somewhat restricted, in that you don't have all the bells and whistles of a gp OS.
If your measurement must be taken every 15S +/- 10S then you may very well get away with standard LV on a PC.
In some instances, a combination works well. For example, RT on FieldPoint or CRIO to handle the time sensitive issues and LV on a PC to handle the user interface and data analysis.
Hope that helps, please elaborate on your requirements if you wish.
Matt

Lm-sensors: match up reported temps to physical stuff on the board

I've got lmsensors up and running on my DFI LP LT P35-T2R motherboard. I think I can figure out what most of the data are but there are some that I don't really understand.
I am currently using Handbrake to encode some video files so the temps should be up:
$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +36.0°C (crit = +64.0°C)
it8718-isa-0290
Adapter: ISA adapter
in0: +1.17 V (min = +0.00 V, max = +4.08 V)
in1: +1.31 V (min = +1.28 V, max = +1.68 V)
in2: +3.28 V (min = +2.78 V, max = +3.78 V)
in3: +2.88 V (min = +2.67 V, max = +3.26 V)
in4: +2.98 V (min = +2.50 V, max = +3.49 V)
in5: +1.34 V (min = +0.58 V, max = +1.34 V)
in6: +2.02 V (min = +1.04 V, max = +1.36 V)
in7: +2.85 V (min = +2.67 V, max = +3.26 V)
in8: +3.26 V
fan1: 1523 RPM (min = 3245 RPM)
fan2: 0 RPM (min = 3245 RPM)
fan3: 0 RPM (min = 3245 RPM)
temp1: +36.0°C (low = +127.0°C, high = +64.0°C) sensor = thermal diode
temp2: +39.0°C (low = +127.0°C, high = +64.0°C) sensor = thermistor
temp3: +43.0°C (low = +127.0°C, high = +64.0°C) sensor = thermistor
cpu0_vid: +2.050 V
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +45.0°C (high = +76.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +44.0°C (high = +76.0°C, crit = +100.0°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2: +45.0°C (high = +76.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3: +50.0°C (high = +76.0°C, crit = +100.0°C)
Obviously the coretemp-iso-000x data are the temps for cores0-3.
My questions are what physical component of the system are the following measuring:
1) "Adapter: Virtual device temp1: +36.0°C (crit = +64.0°C)"
2) "temp1: +36.0°C (low = +127.0°C, high = +64.0°C) sensor = thermal diode"
3) "temp2: +39.0°C (low = +127.0°C, high = +64.0°C) sensor = thermistor"
4) "temp3: +43.0°C (low = +127.0°C, high = +64.0°C) sensor = thermistor"
One of those should be the northbridge temp, and one of those should be the CPU temp as it's reported in the BIOS (not temp of the cores). What are the other two and how can I know for sure which is which?

Sorry to bump an old post but I'm having the same problem. The examples I see here on this board save for the one above me all have CPU Temp or Sys Temp next to the values. I just have temp1, temp2, temp3. I assume I have 8 coretemps because my i7 is quad-core but with hyperthreading. But I don't know for sure. Also where is my gpu temp? All I see is the cpu0_vid voltage and I'm pretty sure it shouldn't be 0. Plus I have lots of ALARMs and I'm not sure why. The fan alarms I understand because my case fans have manual switches on the case and aren't hooked to the mobo. The setup is a asus p6t mobo, intel i7 cpu, nvidia gtx-260 vcard.
My sensors output is:
$ sensors
w83627ehf-isa-0290
Adapter: ISA adapter
Vcore: +1.03 V (min = +0.00 V, max = +1.74 V)
in1: +1.73 V (min = +0.32 V, max = +0.19 V) ALARM
AVCC: +3.33 V (min = +2.98 V, max = +3.63 V)
VCC: +3.30 V (min = +2.98 V, max = +3.63 V)
in4: +1.70 V (min = +1.81 V, max = +0.02 V) ALARM
in5: +2.04 V (min = +0.54 V, max = +0.64 V) ALARM
in6: +1.60 V (min = +0.66 V, max = +1.29 V) ALARM
3VSB: +3.41 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.33 V (min = +2.70 V, max = +3.30 V) ALARM
in9: +0.00 V (min = +0.58 V, max = +1.84 V) ALARM
fan1: 0 RPM (min = 753 RPM, div = 128) ALARM
fan2: 2057 RPM (min = 423 RPM, div = 16)
fan3: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan4: 0 RPM (min = 1054 RPM, div = 128) ALARM
fan5: 0 RPM (min = 2636 RPM, div = 128) ALARM
temp1: +48.0°C (high = +20.0°C, hyst = +116.0°C) ALARM sensor = thermis
tor
temp2: +40.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
temp3: +2.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
cpu0_vid: +0.000 V
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +45.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +40.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2: +45.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3: +42.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0004
Adapter: ISA adapter
Core 4: +45.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0005
Adapter: ISA adapter
Core 5: +40.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0006
Adapter: ISA adapter
Core 6: +45.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0007
Adapter: ISA adapter
Core 7: +42.0°C (high = +80.0°C, crit = +100.0°C)
my sensors-detect is:
Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Winbond W83667HG Super IO Sensors' (confidence: 9)
Driver `adt7473':
* Bus `NVIDIA i2c adapter '
Busdriver `nvidia', I2C address 0x2e
Chip `Analog Devices ADT7473' (confidence: 5)
Driver `coretemp':
* Chip `Intel Core family thermal sensor' (confidence: 9)
Driver `max6650':
* Bus `NVIDIA i2c adapter '
Busdriver `nvidia', I2C address 0x4b
Chip `Maxim MAX6650/MAX6651' (confidence: 3)
* Bus `NVIDIA i2c adapter '
Busdriver `nvidia', I2C address 0x4b
Chip `Maxim MAX6650/MAX6651' (confidence: 3)
I have modprobed the modules successfully, added the modules to rc, and added "sensors" to my daemons.
This is my lm_sensors:
# Generated by sensors-detect on Sun May 10 02:31:05 2009
# This file is sourced by /etc/rc.d/lm_sensors and defines the modules to
# be loaded/unloaded.
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).
HWMON_MODULES="adt7473 coretemp max6650 w83627ehf"
# For compatibility reasons, modules are also listed individually as variables
# MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.
MODULE_0=adt7473
MODULE_1=coretemp
MODULE_2=max6650
MODULE_3=w83627ehf

Setup lm_sensors : im stuck

I have tried setup lm_sensors for reading cpu temp, but i do fail.
I use udev, i believe it can have something with that to do
[root@archbox dio]# sensors-detect
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
[root@archbox dio]#
i downloaded the sources with abs and run the above script and after that i can run sensors-detect but after rebooting the system all is back to failure.
When i DO run the sensors-detect it tells me to load the w83627hf but when i try to do that i get following result:
FATAL: Error inserting w83627hf (/lib/modules/2.6.10-ARCH/kernel/drivers/i2c/chips/w83627hf.ko): No such device
sensors-detect output:
[root@archbox lm_sensors]# sensors-detect
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no):
Module loaded succesfully.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Next adapter: SMBus I801 adapter at 0c00
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x69
Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan the ISA bus? (YES/no):
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... Success!
(confidence 8, driver `it87')
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Do you want to scan for secondary Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627THF Super IO Sensors'
Success... found at address 0x0290
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x82)
Probing for `Winbond W83L517D Super IO'
Failed! (0x82)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus I801 adapter at 0c00' (Algorithm unavailable)
Busdriver `i2c-i801', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
Driver `it87' (may not be inserted):
Misdetects:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `ITE IT8705F / IT8712F / SiS 950' (confidence: 8)
Driver `w83627hf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627THF Super IO Sensors' (confidence: 9)
I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)?
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-i801
modprobe i2c-isa
# I2C chip drivers
modprobe eeprom
modprobe w83627hf
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): no

Does your BIOS detect the CPU fan speed? If not, there's your problem: the fan has to be connected to a special fan header on your mainboard to enable RPM-readouts. In some cases, you may not want to connect the fan directly to your mainboard tho. If you have a powerful fan like a 50 dB Delta that can take your fingers off if you try to stop it, connecting it to the fan headers is a bad idea: the fan is very powerful so it drains a lot of power and mainboards simply can't deliver it (they'll die a lot faster). It's better to connect the fan to a molex (white powerplug on your PSU) and just do without the RPM reading. You could, however, connect it to a molex but disconnect the "RPM-reading cable" (one of the 3 cables in the fan) and attach a plug to it so you can connect it the fanheader. This way you won't kill your mainboard and still have the RPM readout. It takes a little craftsmanship and balls tho.
If you do get a readout in the BIOS, you'll have to fiddle around with lm_sensors' configfile: it might print the info on with the wrong title.
The same goes for your RAM-voltage: right down the figures and compare them to the readouts in the BIOS. This way you'll know which number means what.

How to create a type of 'alarm event' based on acquired sensor data and system time?

Hello all,
I'm fairly new to LabVIEW and have successfully created a VI that reads voltage data from sensors. Each sensor outputs 2 voltage values and I treat these values as 2 different DBL values. I'd like to be able to record each voltage value as a base and then compare the subsequent data readings with that base. Once the base is determined, I'd like a sort of 'variable' set as "TIME" to be recorded at the moment the base voltage is recorded.
The alarm should occur (or anything Boolean set to TRUE I guess) once the continuously read voltage remains within certain limits for about 2 hours. I know I can compare the system time w/ the "TIME" that the voltage base value was recorded. If the voltage readings escape those limits, I'd like the voltage base value reset and the TIME set to the corresponding system time again.
I apologize in advance if this I haven't' described my problem well, but if anyone could help me figure out the best way to create this code, I would appreciate it much!
Thanks!
Solved!
Go to Solution.

ill try to illustrate a couple scenarios:
keep in mind that i dont necessarily want the voltages in these specific ranges, but just a range of +/- 20 mV ... in an above post i refer to a "base" voltage reading, in this case that would be 200 mV for V1 and 400 mV for V2, just because the voltage has shifted to those values for an extended amount of time each (> 2 seconds)
Scenario 1
1:00 pm
Sensor readings
Voltage 1: 200 mV
Voltage 2: 400 mV
between 1:00 and 3:00 pm:
Voltage 1 does not deviate from 180-220 mV range
Voltage 2 does not deviate from 380-420 mV range
at 3:00pm I want an alert/alarm/Boolean to change to 'true'
Scenario 2
1:00 pm
Sensor readings
Voltage 1: 200 mV
Voltage 2: 400 mV
at 1:45 pm:
Voltage 1: 2 mV
Voltage 2: 600 mV
Since the voltage has shifted out of the range, i want the new base voltage to equal whatever it changed to out of the range, and also the time spent within the new range (2 +/- 20 mV and 600 +/- 20 mV, respectively for V1 and V2) would be reset, so a new 2-hour counter would begin

How do I use elvis to record data from a pasco rotary motion sensor

I want to use a pasco rotary motion sensor (a rotary encoder) with ELVIS to record angular velocity. I have a LabPro system which I could also interface. But I was hoping to keep the hardware less complicated by wiring the sensor directly to ELVIS. Does anyone have a sample .vi which would record sensor output?

Hi PCM,
Measuring the time between pulses can be a little complicated. You can have a look at this knowledge base to get an idea of how it can be accomplished. However, since the sensor's output is a stream of digital pulses you can use the counters in this card to get some information from the digital signal. You can use one of the counter’s inputs in the NI-ELVIS and get the frequency or period of the digital signal. One good point to get started is by looking at the counters examples built in LabVIEW, you can find them going to Help > Find Examples > Hardware Input and Output > DAQmx > Counter Measurements. I hope this is helpful.
Ana P
National Instruments
Applications Engineer

How to improve output accuracy

Hi all
I have to buy an analog output card to simulate pressure sensors output signal to a UUT in the range of 0V - 50 mV. The customer requirement says that the simulating card must provide differential isolated output with 0.1mV accuracy and better resolution. So far after all comparisons I have landed in NI PXIe-4322 card. But this would partly match my requirement because the accuracy level is not matching my requirement.I tried to calculate the minimum accuracy that can be obtained using the example mentioned in datasheet and resulted in 1.12mV. So I need to get atlest 0.5mV accuracy. can this be solved using potential divider network in line and will it improve the accuracy. Have any one used this card or similar card and performed the experiment to imrove the accuracy.If yes what all parameters I have to take into consideration. Please anyone help me in resolving this.have any one used this card or similar card and
d

Hi all
I have to buy an analog output card to simulate pressure sensors output signal to a UUT in the range of 0V - 50 mV. The customer requirement says that the simulating card must provide differential isolated output with 0.1mV accuracy and better resolution. So far after all comparisons I have landed in NI PXIe-4322 card. But this would partly match my requirement because the accuracy level is not matching my requirement.I tried to calculate the minimum accuracy that can be obtained using the example mentioned in datasheet and resulted in 1.12mV. So I need to get atlest 0.5mV accuracy. can this be solved using potential divider network in line and will it improve the accuracy. Have any one used this card or similar card and performed the experiment to imrove the accuracy.If yes what all parameters I have to take into consideration. Please anyone help me in resolving this.have any one used this card or similar card and
d

Lm_sensors: sensors output

Similar Messages

Maybe you are looking for