Bird Power sensor 5012

I need to integrate a Bird Power Sensor 5012 on a Virtual Instruments LabVIEW.
I have the windows library "BirdDCom.dll" , "BirdSensor.dll" and "HIDLibrary.dll".
Can sombody help me to put this sensor on a LabVIEW project?
Thanks

Duplicated post: http://forums.ni.com/t5/LabVIEW/power-sensor-5012/m-p/2501534

Similar Messages

"Te12/9 Receive Power Sensor on SW-NL-EDC_eupdswcore001 ".

I am recieving this frequent warning alerts "Te12/9 Receive Power Sensor on SW-NL-EDC_eupdswcore001 ".
switch is 6513
swcore001#sh inventory
NAME: "Transceiver Te12/9", DESCR: "X2 Transceiver 10Gbase-SR Te12/9"
Can you please what all issues related to above device mentioned.How to recitfy this alerts

eupdswcore001#sh int te12/9
TenGigabitEthernet12/9 is up, line protocol is up (connected)
Hardware is C6k 10000Mb 802.3, address is a493.4c0b.fa30 (bia a493.4c0b.fa30)
Description: Connected to EUPDENCD00
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10Gb/s
Transport mode LAN (10GBASE-R, 10.3125Gb/s), media type is 10Gbase-SR
input flow-control is on, output flow-control is off
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:08, output 00:00:21, output hang never
Last clearing of "show interface" counters 6w5d
Input queue: 0/2000/367238/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 36230000 bits/sec, 5702 packets/sec
5 minute output rate 30438000 bits/sec, 5706 packets/sec
     13367144638 packets input, 9126136368797 bytes, 0 no buffer
     Received 6645935 broadcasts (3920984 multicasts)
     0 runts, 367238 giants, 0 throttles
     367239 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     14612403292 packets output, 10106745813442 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out
eupdswcore001#sh int te 12/9 transceiver detail
Transceiver monitoring is disabled for all interfaces.
ITU Channel not available (Wavelength not available),
Transceiver is internally calibrated.
mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable.
++ : high alarm, + : high warning, - : low warning, -- : low alarm.
A2D readouts (if they differ), are reported in parentheses.
The threshold values are calibrated.
                            High Alarm High Warn Low Warn   Low Alarm
           Temperature         Threshold   Threshold Threshold Threshold
Port       (Celsius)          (Celsius)   (Celsius) (Celsius) (Celsius)
Te12/9       35.3                74.0        70.0         0.0       -4.0
                            High Alarm High Warn Low Warn   Low Alarm
            Voltage            Threshold   Threshold Threshold Threshold
Port        (Volts)            (Volts)     (Volts)    (Volts)    (Volts)
Te12/9       N/A                   N/A         N/A         N/A        N/A
                            High Alarm High Warn Low Warn   Low Alarm
            Current            Threshold   Threshold Threshold Threshold
Port        (milliamperes)     (mA)        (mA)       (mA)       (mA)
Te12/9        6.9         --     N/A        N/A        N/A       N/A
            Optical            High Alarm High Warn Low Warn   Low Alarm
            Transmit Power     Threshold   Threshold Threshold Threshold
Port        (dBm)              (dBm)       (dBm)      (dBm)      (dBm)
Te12/9       -2.8                 2.9        -1.0        -7.3      -11.3
            Optical            High Alarm High Warn Low Warn   Low Alarm
            Receive Power      Threshold   Threshold Threshold Threshold
Port        (dBm)              (dBm)       (dBm)      (dBm)      (dBm)
Te12/9      -13.0         -       2.9        -1.0        -9.9      -13.9

I am recieving this frequent warning alerts "Te12/9 Receive Power Sensor on SW-NL-EDC_eupdswcore001 ".

I am recieving this frequent warning alerts "Te12/9 Receive Power Sensor on SW-NL-EDC_eupdswcore001 ".
switch is 6513
swcore001#sh inventory
NAME: "Transceiver Te12/9", DESCR: "X2 Transceiver 10Gbase-SR Te12/9"
Can you please what all issues related to above device mentioned.How to recitfy this alerts

If the interface is in down state with being admin down, you will get this message. In that case it can be remedied by putting the interface administratively down.
If it is up, you may be having link loss issues (i.e . not enough light received to meet the design threshold of the optical transceiver). Investigate using "show interface te12/9 transceiver details" and check the receive optical power level.

Sensor Power

Hi,
Just a note. I'm using the sensor power output on the WSN 3202 node. I have found that when I deploy a VI to the programmable node, the power sensor out turns off unless I am reading an Analog Input. I've got it set to 'Always On' and initially I've only been reading digital input, but the sensor out kept turning off.
Thanks,
Jevon
Solved!
Go to Solution.

Hi JChec,
When you set an analog attribute, you actually to have to then explicitly read that channel for the attribute to be set. If you set the attribute, then never read that AI channel, then the property won't actually make it down to the hardware. I'm assuming you are setting the property in the start case? If you are, then set the property, then perform a read on that channel. After that read is performed, you should see the sensor output stay on.
Not intuitive, I know. We are looking at ways we could make this easier for the user.
Let me know if you need any clarification.
Kevin
Message Edited by Kevin_H on 02-19-2010 08:45 AM
Message Edited by Kevin_H on 02-19-2010 08:45 AM
National Instruments
WSN/Wireless DAQ Product Support Engineer

Problems with getting accurate power readings during sweep

Ok, so I have an Agilent N1912A power meter with N1921A power sensors on Ch A & B. I have RF power (from signal generator/ amplifier) going into input of a coupler, then Ch A connected to the coupling and Ch B connected to the coupler output. I am trying to measure the loss of the coupling (nominally 20 dB) by just taking the difference in power readings (Ch B- Ch A). I have a VI to read the power from both channels as a signal generator sweeps through different power levels. For the most part it works, except the problem is I am a getting strange "kink" in power reading whenever the power sensor reading is around -10 dBm...see first image attached. Because of this, i get over 0.5 dB change in the coupling loss i am trying to measure, which is unacceptable.
Now with extensive troubleshooting I have ruled out things like amplifier having unstable gain, or faulty sensors. One interesting thing I have noticed - it tends to improve significantly when i change sweepintervals to be much smaller (e.g. 0.1 dB intervals instead of 0.5 dB), which makes me think it is something I'm not setting properly in my VI when I am reading the power from each channel. If i use 0.1 dB intervals the kink is much smaller..resulting in a more stable measurement of coupling loss. See second image attached.
Anyway, wondering if there are any ideas what could be the source of the issue. As you can see from the images, this always happens at -10 dBm..dont' know what's so special about -10 dBm (where's the shrug emoticon?? ) Anyway, I know can greatly alleviate this problem by always using really small intervals of 0.05 dB or something, but that is just so not practical for my application...(would be too slow). I want to be able to use 0.5 dB intervals and have smooth power readings.
Attachments:
power sweep with kink.jpg ‏88 KB
coupling loss.jpg ‏39 KB

neets wrote:
Ok, so I have an Agilent N1912A power meter with N1921A power sensors on Ch A & B. I have RF power (from signal generator/ amplifier) going into input of a coupler, then Ch A connected to the coupling and Ch B connected to the coupler output. I am trying to measure the loss of the coupling (nominally 20 dB) by just taking the difference in power readings (Ch B- Ch A). I have a VI to read the power from both channels as a signal generator sweeps through different power levels. For the most part it works, except the problem is I am a getting strange "kink" in power reading whenever the power sensor reading is around -10 dBm...see first image attached. Because of this, i get over 0.5 dB change in the coupling loss i am trying to measure, which is unacceptable.
Now with extensive troubleshooting I have ruled out things like amplifier having unstable gain, or faulty sensors. One interesting thing I have noticed - it tends to improve significantly when i change sweepintervals to be much smaller (e.g. 0.1 dB intervals instead of 0.5 dB), which makes me think it is something I'm not setting properly in my VI when I am reading the power from each channel. If i use 0.1 dB intervals the kink is much smaller..resulting in a more stable measurement of coupling loss. See second image attached.
Anyway, wondering if there are any ideas what could be the source of the issue. As you can see from the images, this always happens at -10 dBm..dont' know what's so special about -10 dBm (where's the shrug emoticon?? ) Anyway, I know can greatly alleviate this problem by always using really small intervals of 0.05 dB or something, but that is just so not practical for my application...(would be too slow). I want to be able to use 0.5 dB intervals and have smooth power readings.
So what are you trying to accomplish here? I would be more interested in a coupler's response over frequency. Usually if you're talking about gain/loss over power, you are measuring the characteristics of an amplifier. (Which I understand you aren't doing, as the DUT is the coupler.)
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

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?

Power stats?

Hi,
I've recently heard that Xserve contains a wide range of power
sensors, and that some server management software can report
power dissipation stats. However, I haven't been able to find
exactly: (1) the list of sensors, (2) the name of the management
software that I can use to generate statistics.
I've skimmed the basic Xserve documentation, but couldn't find
what I'm looking for.
Ideally, I would like to access these sensors from my own
software and perform the readings when needed.
Thank you. Kind regards and happy holidays,
Domagoj

Thanks Camelot for replying so quickly.
Can Server Monitor also track power dissipated by memory/CPU/disk/motherboard?
If yes, two sub-questions:
1) Are those real measurements, or estimates computed from
temperature/fan_speed/voltage measurements?
2) Can I access the sensors from my own code? (I.e., are the detailed
motherboard specs and programming manuals available?)
Thanks. Kind regards,
Domagoj

10.6.8 freezes periodically on MBP 3,1

Dear all, I am hoping someone could shed some light on an issue that I've been having for the past two days...
To start, this is my system spec:
-MacBook Pro 3,1 - 2,2GHz C2D, 4GB RAM (upgraded 3 months ago), 64GB SSD (Crucial M4 - upgraded 1+ year ago), 6-month-old NewerTech replacement battery
-OS X 10.6.8, up-to-date software updates
The problem is the following:
Since about 2 days ago, I've been experiencing periodic freezes. They come in a variety of forms, but fit into two categories - (a) a complete freeze, where nothing is occurring (not even the beach ball is spinning), or (b) a "partial" freeze, where everything except for the Safari windows that I have open freezes - I can use those normally for a while more, even move between them, before even they become unresponsive after a few minutes. In both, the fans start to spool-up after about a minute.
I considered all the changes to the system that I had done in the past days, and all I could think of was the installation of the GarminCommunicator plug-in for Safari (where the installation did not work, or rather, it worked, but the element was not recognized), which I subsequently removed completely (from the Library/Internet Plug-ins folder), as per Garmin's instructions. The other idea was that it could be malware, but a deep scan of the system with ClamX antivirus showed nothing.
After the freeze happened the first time (after closing VLC with an mkv file still playing), I kept the Activity Monitor open, and watched it as a later crash happened, and there seemed to be no unusual behaviour - no task taking up a significant amount of CPU to warrant the spooling-up of the fan.
This all comes after the weeks before (at least 3) I've had some issues with the battery, where the charge would not show in the taskbar, there would only be an X in the battery, despite it being charged, and working as usual (plug-in, charge, battery life as expected, etc.). After contacting NewerTech I did a reset of the SMC, which did the trick. I mention this only because it was the only other issue that I had with the computer in the past 2 years since my HDD failed.
Thanks for your attention!

Hi Ogelthorpe
I see that some Apple Hardware test files include a list of codes, and since that isn't part of a confidential Apple service document, there seems no reason that the lists can't be shared .
Here's an example list, from an F42388C8 test. Look for an Fnumber.tdf file on any other machines.
{"ALSL","Photometer (ALSL) - Light Sensor"}, {"TA0P","Temp (TA0P) - Ambient air temperature sensor"}, {"TALP","Temp (TALP) - Ambient air temperature sensor"}, {"TB0T","Temp (TB0T) - Battery temperature"}, {"TCAH","Temp (TCAH) - CPU-A heatsink temperature"}, {"TCBH","Temp (TCBH) - CPU-B heatsink temperature"}, {"TC0C","Temp (TC0C) - CPU-A Die 1 Temp offset"}, {"TC1C","Temp (TC1C) - CPU-A Die 2 Temp offset"}, {"TC2C","Temp (TC2C) - CPU-B Die 1 Temp offset"}, {"TC3C","Temp (TC3C) - CPU-B Die 2 Temp offset"}, {"TC0D","Temp (TC0D) - CPU0 Die Temp"}, {"TC0H","Temp (TC0H) - CPU Heat-sync"}, {"TCOH","Temp (TCOH) - CPU Heat-sync"}, {"TC0P","Temp (TC0P) - CPU VR area"}, {"TC1P","Temp (TC1P) - CPU1 Temp Proximity or alt. CPU0 Temp Proximity"}, {"TC2C","Temp (TC2C) - CPU-B Die 1 Temp offset"}, {"TG0D","Temp (TG0D) - GPU0 Die Temp"}, {"TG0H","Temp (TG0H) - GPU0 Heatsync"}, {"TG0T","Temp (TG0T) - GPU0 Discrete Thermal Diode"}, {"Th0H","Temp (Th0H) - NB/CPU/GPU HeatPipe 0 Proximity"}, {"Th1H","Temp (Th1H) - NB/CPU/GPU HeatPipe 1 Proximity"}, {"TG0P","Temp (TG0P) - GPU0 Proximity"}, {"TH0P","Temp (TH0P) - Hard disk drive 1 body temperature"}, {"TH1P","Temp (TH1P) - Hard disk drive 2 body temperature"}, {"TH2P","Temp (TH2P) - Hard disk drive 3 body temperature"}, {"TH3P","Temp (TH3P) - Hard disk drive 4 body temperature"}, {"TM0P","Temp (TM0P) - FBDIMM Riser A incoming air temperature"}, {"TM1P","Temp (TM1P) - FBDIMM Riser A outgoing air temperature"}, {"TM2P","Temp (TM2P) - FBDIMM Riser A voltage regulator area temperature"}, {"TM8P","Temp (TM8P) - FBDIMM Riser B incoming air temperature"}, {"TM9P","Temp (TM9P) - FBDIMM Riser B outgoing air temperature"}, {"TMAP","Temp (TMAP) - FBDIMM Riser B voltage regulator area temperature"}, {"TM0S","Temp (TM0S) - Temperature of AMB IC on FBDIMM in Riser A Slot 1"}, {"TM1S","Temp (TM1S) - Temperature of AMB IC on FBDIMM in Riser A Slot 2"}, {"TM2S","Temp (TM2S) - Temperature of AMB IC on FBDIMM in Riser A Slot 3"}, {"TM3S","Temp (TM3S) - Temperature of AMB IC on FBDIMM in Riser A Slot 4"}, {"TM8S","Temp (TM8S) - Temperature of AMB IC on FBDIMM in Riser B Slot 1"}, {"TM9S","Temp (TM9S) - Temperature of AMB IC on FBDIMM in Riser B Slot 2"}, {"TMAS","Temp (TMAS) - Temperature of AMB IC on FBDIMM in Riser B Slot 3"}, {"TMBS","Temp (TMBS) - Temperature of AMB IC on FBDIMM in Riser B Slot 4"}, {"TN0H","Temp (TN0H) - Temperature of MCH heatsink"}, {"TN0C","Temp (TN0C) - Temperature of MCH die temp diode"}, {"TN0D","Temp (TN0D) - Temperature of MCH die temp offset"}, {"TN0P","Temp (TN0P) - NB Proximity"}, {"TN1P","Temp (TN1P) - NB Proximity"}, {"TO0P","Temp (TO0P) - ODD Temp"}, {"Tp0C","Temp (Tp0C) - PSMI supply AC/DC Supply Temperature 1"}, {"Tp1C","Temp (Tp1C) - PSMI supply AC/DC Supply Temperature 2"}, {"Tp0P","Temp (Tp0P) - PSMI supply AC/DC Supply Temperature"}, {"TS0C","Temp (TS0C) - Temperature of LM94, between CPU-A and CPU-A's VR"}, {"Ts0P","Temp (Ts0P) - Palm rest L"}, {"Ts1P","Temp (Ts1P) - Palm rest R"}, {"VCAC","Voltage (VCAC) - CPU-A core voltage"}, {"VCBC","Voltage (VCBC) - CPU-B core voltage"}, {"VC0C","Voltage (VC0C) - CPU0 V-Sense"}, {"VC0c","Voltage (VC0c) - CPU0 V-Sense"}, {"VC0R","Voltage (VC0R) - CPU0 High Side "}, {"VC0r","Voltage (VC0r) - CPU0 High Side "}, {"VD0R","Voltage (VD0R) - DC V-Sense"}, {"VD0r","Voltage (VD0r) - DC V-Sense"}, {"VeES","Voltage (VeES) - PCIe Slots +12V rail voltage"}, {"VG0C","Voltage (VG0C) - GPU0 V-Sense"}, {"VG0c","Voltage (VG0c) - GPU0 V-Sense"}, {"VMAS","Voltage (VMAS) - FBDIMM Riser A +12V rail at VRs"}, {"VMBS","Voltage (VMBS) - FBDIMM Riser B +12V rail at VRs"}, {"VN0C","Voltage (VN0C) - MCH core voltage 0"}, {"VN1C","Voltage (VN1C) - MCH core voltage 1"}, {"Vp0C","Voltage (Vp0C) - PSMI supply AC/DC output voltage, +12V rail"}, {"VP0R","Voltage (VP0R) - PBus V-Sense"}, {"VP0r","Voltage (VP0r) - PBus V-Sense"}, {"VP1R","Voltage (VP1R) - PBusA V-Sense"}, {"VP1r","Voltage (VP1r) - PBusA V-Sense"}, {"IB0r","Current (IB0r) - Battery I-Sense"}, {"ICAC","Current (ICAC) - CPU-A core current"}, {"ICBC","Current (ICBC) - CPU-B core current"}, {"IC0c","Current (IC0c) - CPU0 I-Sense"}, {"IC0C","Current (IC0C) - CPU0 I-Sense"}, {"IC0R","Current (IC0R) - CPU0 High Side "}, {"IC0r","Current (IC0r) - CPU0 High Side "}, {"ID0R","Current (ID0R) - DC I-Sense"}, {"ID0r","Current (ID0r) - DC I-Sense"}, {"ID1R","Current (ID1R) - PBusA I-Sense"}, {"ID1r","Current (ID1r) - PBusA I-Sense"}, {"Ie1S","Current (Ie1S) - PCIe Slot 1 +12V Current"}; {"Ie2S","Current (Ie2S) - PCIe Slot 2 +12V Current"}; {"Ie3S","Current (Ie3S) - PCIe Slot 3 +12V Current"}; {"Ie4S","Current (Ie4S) - PCIe Slot 4 +12V Current"}; {"IeAS","Current (IeAS) - PCIe Slot Boost 1 +12V Current"}, {"IeBS","Current (IeBS) - PCIe Slot Boost 2 +12V Current"}, {"IF0C","Current (IF0C) - FWire I-Sense"}, {"IF0c","Current (IF0c) - FWire I-Sense"}, {"IF0R","Current (IF0R) - FWire I-Sense"}, {"IG0C","Current (IG0C) - GPU0 I-Sense"}, {"IG0c","Current (IG0c) - GPU0 I-Sense"}, {"IMAS","Current (IMAS) - FBDIMM Riser A 12V supply current"}, {"IMBS","Current (IMBS) - FBDIMM Riser B 12V supply current"}, {"IM0R","Current (IM0R) - Memory I-Sense"}, {"IM0r","Current (IM0r) - Memory I-Sense"}, {"IN0C","Current (IN0C) - MCH core current 0 - Supply input"}, {"IN1C","Current (IN1C) - MCH core current 1"}, {"IN0c","Current (IN0c) - NorthBridge I-Sense"}, {"IN0R","Current (IN0R) - NorthBridge I-Sense 1"}, {"IN1R","Current (IN1R) - NorthBridge I-Sense 2"}, {"Ip0C","Current (Ip0C) - PSMI supply AC/DC total output current, +12V rail"}, {"IP0R","Current (IP0R) - PBus I-Sense"}, {"IP1R","Current (IP1R) - PBusA I-Sense"}, {"PC0C","Power (PC0C) - CPU Core Power"}, {"PD0R","Power (PD0R) - DC-In Rail Power"}, {"PF0R","Power (PF0R) - 1394 Rail Power"}, {"PG0C","Power (PG0C) - GPU Core Power"}, {"PM0R","Power (PM0R) - Memory Rail Power"}, {"PN0R","Power (PN0R) - NorthBridge Rail Power"}, {"PP0R","Power (PP0R) - P Buss Rail Power"}, {"PP1R","Power Sensor - P Buss A Rail Power"}, {"MSC0","CalibrationKeys (MSC0) - Calibration Key 0 - CPU"}, {"MSC1","CalibrationKeys (MSC1) - Calibration Key 1 - GPU "}, {"MSC2","CalibrationKeys (MSC2) - Calibration Key 2 - Memory "}, {"MSC3","CalibrationKeys (MSC3) - Calibration Key 3 - NB"}, {"MO_X","Accelerometer (MO_X) - Motion Sensor"},

Display Problem - Video noise with 15" Powerbook and 23" Studio Display

I just bought a used 23" Studio Display to act as a second monitor for my 1.0 GHz 15" Powerbook. In my set up, the display is rather noisy -- there are consistant flickering lines of white pixels throughout the display. The lines are worst in dark areas, though they may just be showing up under contrast. The Powerbook it is connected to still looks normal.
The first strange thing is that the display works perfectly with another 1.25 GHz 15" Powerbook I have to test it on. In both cases, I have connected the monitor to the Powerbooks with a new Apple brand powered DVI to ADV Adapter.
The second strange thing is that the display seemed to act fine until I reinstalled my Wacom tablet driver so that it would work with dual displays. I've uninstalled the driver, but it the problem is still there.
The third strange thing is that the display is fine while booting up. The blue boot up screen is very crisp looking and noiseless. It only starts showing noise when the login screen shows up.
Any thoughts about what may be causing the problem or how to fix it would be appreciated.
Thanks.
angus.
Powerbook 15" G5 dual 2.0 Mac OS X (10.4.7) 23" studio display

Well I called AppleCare yesterday and, believe it or not, we actually got the USB ports acting normally - well at least I can boot up with the keyboard plugged into the back of the monitor.
They had me reset the Open Firmware and that seemed to do the trick. Of course, the night before I updated to 10.4.10 so that may have had something to do with it, too. No idea.
As for the power sensor button thing, they wanted me to plug the monitor into a different system, either at a Genius Bar or a friend or whatnot to see if it would behave in the same manner - not wanting to activate. I took it to school with me and hooked it up to one of my teacher's G5 and it behaved the same way. It took like 15 times touching the sensor to bring the system up.
So I'll be calling them back and see where they want to go with this. Maybe I'll get lucky and get a new shiny monitor - or not...

How to display a waveform in XY format where X is the time in seconds?

I am aquiring voltage from a power sensor and I am displaying this voltage as a waveform in a waveform chart. Now, I would like to display this waveform such that on X axis I have a range from 0 to 30 seconds (X axis should be displayed in seconds of recording not actual time). On Y axis I would have the value of parameter I am aquiring of course.
Any suggestions/examples?

It is a data signal type that has timing info in it.
What I am actually trying to achieve is to display the data in a chart (that has seconds on X axis) only when I turn on a button. When I turn off the button the data should stop being displayed in the chart. Problem is that when I turn on the button again the new data displayed should flow from the point where old data stopped being displayed. In a chart having actual time on X axis this is not possible because the time will be different that the time when the data stopped being displayed so you will have a gap between the old and new trains of data. I want continuity and I was hoping to get this if I take the timing info out...
Do you see a better solution for this?
Thank you.

2003 HD cinema display pinkish Hue round top right edge

Hi
Just bought a HD Cinema display 23" from ebay for £100 and it has a very slight pinkish hue around top right edge I could live with it only if it does not mean the LCD is dying?
Any reasons? is the display dying or possible ideas on how long it has left?
thanks
John

Well I called AppleCare yesterday and, believe it or not, we actually got the USB ports acting normally - well at least I can boot up with the keyboard plugged into the back of the monitor.
They had me reset the Open Firmware and that seemed to do the trick. Of course, the night before I updated to 10.4.10 so that may have had something to do with it, too. No idea.
As for the power sensor button thing, they wanted me to plug the monitor into a different system, either at a Genius Bar or a friend or whatnot to see if it would behave in the same manner - not wanting to activate. I took it to school with me and hooked it up to one of my teacher's G5 and it behaved the same way. It took like 15 times touching the sensor to bring the system up.
So I'll be calling them back and see where they want to go with this. Maybe I'll get lucky and get a new shiny monitor - or not...

Mac Mini can't identify BlueTooth smart devices

I have a Kurt Kinetic InRide Watt meter and corresponding Heart Rate Monitor (Wahoo Fitness TICKR) that our Late 2014 Mac Mini (2.6 ghz i5 OS X 10.10.2) can't identify. The devices pair fine with my iPhone 5s and iPad Air 2 so I'm sure it doesn't have to do with the devices. But when I turn off the bluetooth for these other Apple Products and open Bluetooth preferences on the Mac Mini, the computer can't find the bluetooth smart devices.

Reading this
https://kurtkinetic.com/products/kinetic-inride-pod/
which includes
The system uses the new Bluetooth Smart™ communication protocol found in Apple devices including the: iPhone 4s and 5-series and 6 and the iPad 3, 4 and Mini and iPod Touch 5th generation to wirelessly pair a heart rate monitor and power sensor pod with the new Kinetic inRide iPhone App* to measure power with any Kinetic fluid trainer. Learn more about getting started with the app in our video library.
It appears to not be compatible with computers.

[SOLVED]Installing it87 driver for lm_sensors support

Hello,
I've done much research on how to properly install an update it87 driver that could make 0x8620 work.
I ran sensors-detect and ran into this:
# sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
# System: Gigabyte Technology Co., Ltd. Z97X-Gaming 7
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
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
AMD Family 16h 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'... Yes
Found unknown chip with ID 0x8620
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 systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): y
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... 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
Found unknown SMBus adapter 8086:8ca2 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.
Next adapter: i915 gmbus ssc (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus vga (i2c-1)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus panel (i2c-2)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpd (i2c-5)
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):
Created symlink from /etc/systemd/system/multi-user.target.wants/lm_sensors.service to /usr/lib/systemd/system/lm_sensors.service.
Unloading i2c-dev... OK
Unloading cpuid... OK
So I did some research and found that this was updated and available as a potential driver for my MOBO:
http://www.lm-sensors.org/wiki/Devices
You will see the IT8620E which covers the unknown chip lm_sensors found.
I downloaded the file, extracted it and tried to do a
sudo make
but I ran into an error because it was looking for
KERNEL_BUILD := /usr/src/linux-headers-$(TARGET)
which is NOT in that directory. I installed the linux-headers and saw that it adds files to
/lib/modules/3.19.3-3-ARCH
. I modified the Makefile and it got past that part but it ran into another error during
make install
After much frustration I looked and saw
usr/lib/modules/3.19.3-3-ARCH/kernel/drivers/hwmon/it87.ko.gz
so now I'm questioning if I even need to install this driver or if I need to update it. Is there a way to learn more about these drivers that come in the linux package?
I can't find anything concrete on how to make this work. I'm just trying to add my fan speeds and other junk to my conky!
Edit:
modinfo it87 gave me this result:
filename: /lib/modules/3.19.3-3-ARCH/kernel/drivers/hwmon/it87.ko.gz
license: GPL
description: IT8705F/IT871xF/IT872xF hardware monitoring driver
author: Chris Gauthron, Jean Delvare <[email protected]>
depends: hwmon-vid,hwmon
intree: Y
vermagic: 3.19.3-3-ARCH SMP preempt mod_unload modversions
parm: force_id:Override the detected device ID (ushort)
parm: update_vbat:Update vbat if set else return powerup value (bool)
parm: fix_pwm_polarity:Force PWM polarity to active high (DANGEROUS) (bool)
So, this tells me that this driver does not cover 8620.
Last edited by SirMyztiq (2015-04-10 06:23:31)

Update:
I believe after some researching and actually going for it that I managed to install the it87 test driver.
I modified the Makefile on this line:
KERNEL_BUILD := /lib/modules/$(TARGET)/build
And when it failed on this line:
SYSTEM_MAP := /boot/System.map-$(TARGET)
I did:
sudo cp /proc/kallsyms /boot/System.map-`uname -r`
Because Arch doesn't put this file there because it isn't needed to boot...I think.
Either way it finished and I was able to use the lm_sensors.

CSV to Oracle Table

Hi
In BLT I am FTPing a CSV file with approx 7000 lines, then loading it with "TextLoader" and parsing with "FlatFileParser" then stepping through with a repeater running an SQL insert.
It all works OK, but takes about half an hour, I was wondering if anyone had any better suggestions?
Thanks
Nick
PS Here is a sample of the CSV file
"Ident","Make","Model","Description","Serial","LastCal","NextCal","DueDate","StatusChanged","CalStatus","Live","Job"
"xxx1706","AGILENT","34401A","DIGITAL MULTIMETER","US3612","2003-09-12","2003-09-12","2003-09-14","N","ok","N","10410"
"yyy1724","AGILENT","8482H","POWER SENSOR","MY4109","2001-04-18","2002-03-18","2009-03-21","N","so-so","N","1048"
My repeater strips out the header row ([LineNumber > 1]), and my insert is just
INSERT into mytable VALUES ([Param.1])
The only other thing I have to do is a string replace on each line as follows
stringreplace( stringreplace( stringreplace( Repeater_0.Output{/Row/Line} , "'" , "" ) , "\"" , "'" ) , "'None'" , "''" )
to first of all strip out single quotes (found in the description field), then replace double quotes with single quotes, then replace empty date fields (in the csv file as 'None') with an empty string.

Nick:
I would use SQL*Loader also. Info at:
http://www.orafaq.com/faqloadr.htm
Any time you are doing "bulk inserts", there are special DB techniques that can avoid substantial overhead (e.g. don't commit each row, grab a connection once, etc.). This automatically happens with SQL*Loader.
Alternatively, you might be able to run some PL/SQL with the "LOAD DATA" syntax (and specifying your CSV file with INFILE). Google for examples. Also, there are many performance options that can make a HUGE difference in load speed.
You could theoretically write a custom BLS action to do this also.
Rick

NI VISA

Hi,
Hope you will be fine. I am doing my final year project on Labview 2011. I have to read RF power from Agilent U2002A USB power sensor and plot it in labview. Instrument driver for Agilent U2002A power sensor is not available. so i am using Visa open, visa read, visa write, Visa close etc. to prgram my instrument. I have made a program but its not working it gives an error of timed out. I want you to plz make a program for me which only sends *IDN? command to the usb power sensor and returns the status of the device in the read buffer. I shall be very thankful to you. Plz also inform me that the instrument driver for that perticular USB power sensor or any alternate is available or not.
Waiting for your sympathetic consideration.
Regards,
Husnain Taseer Student of BS(Electrical Engineering).

As long as you install the driver for the Agilent U2002A (linked above -- http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=17871), then you should be good to go for talking to your U2002A. That driver has been tested for that sensor.
You can possibly find that same driver using the "find instrument drivers" method, but you want to make sure that it's the same driver as the one I linked to above. You don't need to use the "VISA Driver Wizard" though - you can just use the VIs that come with the driver you installed in order to talk to your instrument. Just make sure you follow all the documentation in the driver and correctly configure the serial port inputs (that is, if you plug into COM1 on your computer, be sure to use COM1 in the example).
Colden

Bird Power sensor 5012

Similar Messages

Maybe you are looking for