Pressure sensor calibration in labview

Hi all,
I have a problem in calibration of pressure sensor.In attachment i am sending the data-sheet of the sensor and the block diagram i made.I used linear fit to calibrate.y axis range:0-100 bar x axis range:0-10VDC
Are there more accurate solutions existing?
Regards,
Attachments:
H72300.pdf ‏380 KB
pressure read 2.vi ‏33 KB

That linear fit being in there makes the VI more complicated than it needs to be. Since 0-10V equals 0-100 psi, it is simple enough to just multiple the DAQ read by 10 and your done.
Back to your other thread, now that you've told us that the sensor outputs 0-10V, that means you have the right DAQ card, but using Pressure(Bridge) in the DAQ assistant was just wrong. You would have used analog input. You can set a custom scale in there to convert 0-10V to 0-100 psi.
At the end of the day, your current VI is better because you are using the real DAQmx VI's rather than the DAQ assistant.

Similar Messages

Creating bridge scale in labview -No calibration certificate with pressure sensor

Hello everyone,
I watched a Laview video online on how to measure pressure transducer and applied the steps to my laboratory work ( https://www.youtube.com/watch?v=spTHTfjVlo8 ) but I couldn't go further when I got to the section of creating a bridge scale for the pressure sensor model I bought from Measurement Specialties (EPX-N02-1B-/Z2/L1M/25M) because the calibration certificate did not come with the device.
I proceeded to run the test but the pressure value I got was way beyond the capacity of the device (1 bar).
My question is; is there a way to sensibly adjust the values of the physical and electrical units without having the calibration certificate of the device?
Thanks in advance for your response.

Hi Wapz,
My name is Mitchell Goon, from National Instruments Technical Support.
You will be able to download a detailed calibration certificate for your device from the NI website. You can refer to the link below for more information on how to obtain the Calibration Certificate:
http://digital.ni.com/public.nsf/allkb/7695C93D283BC1A086256B1800631DCF?OpenDocument
With regards to your query, you will need to have external signal conditioning before acquiring any data from the pressure transducer. These may include:
Bridge completion
Excitation
Remote sensing
Amplification
Filtering
Offset
Shunt Calibration
Connecting the pressure transducer directly to the DAQ device may yield unexpected results. You may wish to refer to the following links if you need more information of acquiring pressure with a DAQ device:
http://www.ni.com/white-paper/3816/en/
http://www.ni.com/white-paper/3639/en/#toc4
Additionally you may wish to refer to this tutorial on how to setup your DAQ device for pressure measurements:
http://www.ni.com/tutorial/7138/en/
I hope that this information will be useful for you. If you require any further assistance, please do not hesitate to contact us and we would be more than happy to assist you.
Kind Regards,
Mitchell Goon
National Instruments
Applications Engineering
www.ni.com/support

Running a system which conclude "Stepper motor + Pressure sensors"

Hello
I need some help as a beginner. Would u please guide me?
Actually my project is about running a system with LabVIEW which is contain a stepper motor (with different speeds in clockwise and unit clockwise) a pressure sensor, a switch for calibration the sensor and finally reporting the output as a graph with shows the distance that motor moves a barrier and changes of pressure during the movements of barrier.
Right now, I have stuck in ordering the hardware parts for connecting the PC to the system. I don't know exactly what do I need to handle the hole system. Would you please help me? I don't know from were and how should I start?
Thanks a lot

As GerdW mentioned in the other post you might want to speak with a NI applications engineer. If this is a school project of some type and/or you just want to spec everything yourself then you certainly can. Your first step is to define all the physical parameters of your devices. So you need to know what kind of stepper motors you need based on the required angular resolution, torque, etc. What kind of pressure gauge will you use? What type of output will it provide you (simple voltage, pulse train, full USB interface)??? What kind of switch will you use. Can it be controlled by low-current TTL or will you need a driver or relay?
Make a list of everything you will need for your application: motors, sensors, switches, etc. Then determine how to interface to them. THEN you can start looking through your hardware options and pick the best choices based on your needs.
Using LabVIEW: 7.1.1, 8.5.1 & 2013

I2C interface (Sensor Data Acquisition) LabVIEW

Hi all!
Hope you are doing great!
Well I have a question which is more about asking all you for an idea!
The Situation:
I have a circuit board which has an On-Off Valve, Digital pressure sensors (manufacturer AMD) and Humidity/Temperature Sensors (make- IST Hygrosens). On the board all the sensors communicate as I2C slave devices and all the data from the sensors is read into an I2C --> USB adapter chip which further connects to the PC via normal USB cable.
Additional to this board, There is a Relay circuit with a simple 1-pole relay which controls an on-off valve on the above Circuit board. This valve is controlled totally separate via a coaxial cable from the relay directly to the Valve. But the relay board has a I2C interface and it also acts as a slave device. The relay board has the same I2C --> USB adapter chip.
Both the Relay board and Sensor board connect via USB to the PC which I suppose is the Master device.
The software code written for this arrangement and Sensor data acquisition is too old and there are a lot of problems coming. I have almost given up troubleshooting..
I now want to translate this automation system onto LabVIEW. I searched the NI website where there is a DAC card called - USB8451 which supports I2C interface... I am a beginner in LabVIEW and cant really make sense out of how should I go about implementing this system on LabVIEW..
If you guys can please help me out to atleast start (like what all hardware I would need etc..), to have a clear picture, it would be great help!!
Looking forward to your inputs and Thank you so much in advance!
Cheers!
Pramit

NI provides a LabVIEW API for the USB8451. If you use the USB8451, you would use the provided API to write a program that controls the USB8451 and you would do all of the I2C communication in your program. This would mean using functions / SubVI's to connect to the USB8451 and then perform I2C operations through it.
If you use USB already on your device, then you would probably use NI-VISA as the driver and have to get / write your own API to talk to the specific device. The manufacturer may have a LabVIEW (or other) API available for talking to the device that you could get. If not, then you would have to understand the details of how to communicate with the device and then write an API using NI-VISA serial functions. This would mean making NI-VISA be the assigned driver for the device and then using VISA Serial functions / SubVI's to send the messages and receive the responses.

How can I configure NI PCI 6221 and DAQ SCB-68 for pressure sensors?

Hello
everybody,
I am using the measuring board (NI PCI 6221) and DAQ
SCB-68 for the data acquisition.
With the DAQ-Assistant I created AI for the voltage of
pressure sensors. In a big indicator panel from this DAQ-Assistant I see the
voltage for both sensors in the correct size. But if I set sensors in the
blockdiagramm to control the signals for sensor one I get a wrong voltage size
and for sensor 2 nothing.
How can I configure this data acquisition equipment to
get the correct signals?
Thanks a lot for your help.

I do not know the type of sensor you are using. But pressure transducers may have a very low output voltage(in the mVolt range). They also need an excitation voltage. Here is an introduction. http://focus.ti.com.cn/cn/lit/an/sloa034/sloa034.pdfThen working with pressure sensors I always use 3 stages in the circuit.
1 Instrumentation Amplifier as a preamp
2 filterstage
3 Final amp and output buffer
(you may combine stage 2 and 3)
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Pressure sensor interface

Hi,
I am trying to building an application to test pressure leak on my instrument. I am using (30) MPXH6400A pressure sensors interfaced to NI USB-6218 DAQ card. I looked at the signal level compatability for the outputs from pressure sensor and input to DAQ and everything looks ok. I am a newbie in using Labview and I am trying to build a .exe for manufacturing to test my instrument on the line for any pressure leak. I figured there will be some starting point which I could use to build my application. The way that I envisioned the program would work: Interface each output from the sensor to a seperate A2D channel in DAQ and have a threshold in the software. If it passes the threshold light an LED with green showing the instrument has passed pressure leak test or if not light the led "RED". I would really appreciate if I could get some pointers to where I could start.
Thanks

Help\Find Examples...\Hardware Input and Output\DAQmx\Analog Measurements\Voltage : will lead you to lots of examples
Pick this one: "Cont Acq&Graph Voltage-Int Clk.vi" as a start
On your computer, you should find it here C:\Program Files\National Instruments\LabVIEW 8.5\examples\DAQmx\Analog In\Measure Voltage.llb\Cont Acq&Graph Voltage-Int Clk.vi
Like Dennis said enter "Dev1/ai0:29" for 30 consecutive channels on a Device named "Dev1".
If you named your USB DAQ something else, use this instead of "Dev1" of course.
Process the "Data" output from the "DAQmxRead" vi as requested to turn your 30 led's red or green.
Attachment SNAG-002.jpg is just a very rough idea on what you could do.
Average 1 second data and compare it with some threshold levels.
Message Edited by Alain S on 01-03-2010 03:13 PM
Attachments:
SNAG-001.jpg ‏292 KB
SNAG-002.jpg ‏45 KB

How to save the dynamic data from a pressure sensor

Hello Everyone,
We have a FPGA board NI cRIO-9073, a temperature module NI 9217 and a pressure module NI 9203. Right now we have problem with saving the data from pressure sensor. I succeed in getting and saving the data from the temperature sensor. Then I just simply modify the FPGA VI and host VI of the temperature function block which are shown in the attachment files.But I get an error saying I cannot connect two different data types.
Could anyone here give me a help on this?
BTW: we are using a 2 wired pressure sensor with 4~20mA. The brown one is +Vcc and the white one is GND.I connect the white one with the COM of NI 9203 and the brown one is connected to AI7. DidI make a right connection?
Thx for any help from anyone!
Attachments:
pre_tem.JPG ‏36 KB
pre.jpg ‏35 KB

Hi, I get this error message:
Write to textfile: function contains an unrelated or improper connection.You have combined two different types of connections among each other.
At least one entrance of the function required for their operation, is open or not properly connected, the connection scheme is illustrated in the context help.
They have combined two different types of connections with each other. This connection is not possible because the data types (such as "numeric", "String", "Arrary" or "clusters do not match"). Open to see the contextual help at what must have a data type for the connection. The type of data source (fixed) costs. The type of data is dynamic data.

Interfacing temperature sensor LM35 with Labview

I would like to know the best possible way by which I can interface a temperature sensor LM35 with Labview for monitoring the temperature of patients that can be incorporated into a patient monitoring device that includes monitoring of ecg, hrv, spo2 and cuffless bp (calculated using PPT, pulse transit time).

Sorry no Danny, thanks to Dennis_Knutson,
By some how you have cleared my confusion a little bit, now i will apply it practically and will ask queries if having any problem.
I appreciate to you quick response Dennis_Knutson

Which Xperia phone models have pressure sensor?

I've downloaded many specs (e.g. Z, Z1 compact, ...) but haven't found information about whether one of the newer phones have a pressure sensor (barometer, typically used to calculate altitude).
Is there a feature matrix showing devices and features like "pressure sensor"?

Thanks. If Xperia active is the only phone with pressure sensor (barometer), then this is really sad, because Sony doesn't sell it any more.
Calculating altitude based on GPS is a desaster, especially if you want to know current and total incline when doing outdoor activities. In the following graph you can see the altitude (GPS-based) of a Xperia active resting on the same location for about 3 hours. Height varies by almost 100 meters and it's steadily going up and down:
I'm afraid I have to change to Samsung Galaxy S4. This makes me sick - Sony has about 26 models (A..Z), they already had a compact outdoor phone (active: waterproof, ANT+, barometer, compact) and now they produce indistiguishable, longish phones which lack important features for outdoor freaks.
@Sony: Is it true that you haven't spent a barometer for Z1 Compact? Are there any plans for Z2 compact to have barometer (pressure sensor)? I have some time left, Xperia neo and active are still working...

SCXI 1520 for potentiometer type pressure sensor

I am usig 1520 for bridge type pressure sensor data acquisition.
I have a requirement for potentiometer type pressure sensors. The sensor is a potentiometer that needs 5V exciation.
+---------------- Exc+
|
|
+--+
| |
| |
| |<-------------- O/p+
| |
| |
+-+
|
|
+---------------- Exc-
I was wondering if I could use 1520 for interfacing with such sensors?
I am hoping I can short P- and S- lines and connect to Exc-. P+ would be Exc+ and S+ would be O/p+.
The resistance between Exc+ & Exc- is of the order of 1-5 kOhm. So the current drawn from the excitation supply is of no concern for the 1520, I believe.
Can I do this with the 1520?

Dear Cas,
Thanks for your enquiry. You have obviously done a great deal of research into this matter already. I am afraid that it is unlikely that you will be able to use a single SCXI module to carry out all the functions you have listed. As accelerometers require such specialised conditioning, it will require a dedicated module - as you already mentioned, something like the 1530 (4 channel accelerometer input module) would be ideal.
However, you have a number of different options for the pressure, voltage and temperature measurements.
For example, you could purchase a 1520 mudule for your pressure measurements, and then use a general purpose 1102B for the voltage and temperature (you would require the 1303 isothermal terminal block to condition the thermocouple readings... and bypass the CJC technology for the voltage readings).
Or, perhaps you could use the 1102 thermocouple module for your temperature readings, and then use a 1102B to take the voltage and pressure readings. Obviously this would involve making your own bridge configuration for the pressure sensor, but that should be fairly easy.
Before you make any final decisions, I would recommend that you call your local branch of NI and speak with a sales representative. Perhaps, a member of the field sales staff could actually come to see you to discuss the matter face to face.
lastly, it sounds like you have a relatively high channel count for some of your readings, which is why you have decided to use the SCXI platform. I was just wondering if you had considered compact DAQ (cDAQ), which combines DAQ hardware with signal conditioning. Higher spec, ease of use, lower channel count. Swings and roundabouts I guess.
I hope this has been of some use to you.
Best wishes,
Rich R
Applications Engineer
National Instruments UK & Ireland

Vi to Control Baratron Pressure Sensor not working

Hello,
I have a VI which has been written to control an MKS baratron pressure sensor. The set-up I have is as follows:
MKS Baratron Type 628B Pressure Transducer ---> MKS Baratron Type 274 Multiplexer -> MKS Type 670B Signal Conditioner
I have connected the 670 unit to laptop via NI card and 15 pin D type connector (serial).
The VI I am running does not work unfortunately and I am seeking advice as to what could be wrong with it.
I should be able to change channels on the 670B to read either 1 of 3 selectable channels but this I cannot do. I should see a light change on fron of the unit indicating that a different channel has been selected. Also, It does read some sort of value from the unit but not the correct value. I select the correct port as COM3 with the input stage of the VI.
I have attached the VI I am using.
Nevica
Attachments:
Baratron2.6.vi ‏524 KB

IF you are running the Microsoft Windoze Operating System (ie: XP), it should be located from the Start Menu:
All Programs > Accessories > Communications > HyperTerminal
Start HyperTerminal
It will ask you to setup a new connection. Give it a name such as MyCom1 and select any of the icon (the red phone is fine so just click OK).
Select the COMM port in the connect using (example COM1). Click OK
Then configure your COM port based on the settings that are recommenced by the manufacturer of the pressure sensor.
It is often but not always 9600, 8, None, 1, None... but not always... Check what they recommend and use the serial cable that should have been provided with the sensor.
Click OK.
Then try sending some commands or at least a carriage return (ENTER) so see if there are any responses from the sensor.
R

Writing in sensor calibration data to my virtual channels in MAX using Labview.

System consists of a few pxi6713 cards, a 6527 digital input card and some scxi cards (1520, 1104c, 1125).
Every 3months or so we run a calibration on the testing stand which uses these cards, and the sensor ranges and physical ranges listed in MAX has to be manually entered each time.
I am looking for a way to do this automatically. This may be a problem, but we are using NI-DAQ legacy (perhaps if absolutely necessary we could goto daqmx).
I have figured out howto read virtual channel information from max correctly, but I have no understanding of trying to write calibration information to the virtual channels.
Any help is greatly appreciated!
Thank you!
jacob

Hi mak90,
There are no ways to change the sensor range and physical ranges
programmatically in Traditional DAQ. Under DAQmx, you have Scaling VIs,
Calibration VIs, Task VIs that allow you to change various settings in
MAX programmatically.
Please let us know if you have any further questions.
Best regards,
Nathan Yang
Applications Engineer
National Instruments

USB interface pressure sensors

Hello all!
I've recently acquired a DigiTacts pressure array sensor like those depicted in the following link:
http://www.pressureprofile.com/products-digitacts
Has anyone already worked with these sensors using LabView?
The interface is USB. Will it be possible through LabView to communicate and acquire information from these sensors?
They come with an API...
Thanks in advance!
Best regards!

I forgot to say but the API was built with C++ and comes with a DLL file.
An example code could be as follows:
#include "d500_include.h"
#include <windows.h>
#include <vector>
#include <iostream>
#include <fstream>
namespace
byte const averageLength = 0x03;
byte const scanCount = 0x30;
int const nFramesToRead = 50;
char const * outputFileName = "data.txt";
int main(int argc, char* argv[])
std::cout << "Configuring sensor...\n";
configureD500 ( averageLength, 0x01, scanCount);
Sleep( 2000 ); // wait for configuration to complete
setDAQEnabled( true );
// The following section automatically finds the attached sensors and
// allocates memory accordingly. This can be done manually if preferred.
Sleep( 500 ); // wait for sensor data to start arriving.
std::vector<int> config(17);
int numDevices;
getConfig( &config[0], numDevices );
//Calculate the packet length
int packetLength = 0;
for( int x = 0; x < 16 ; ++x)
packetLength += config[x];
int nSensors = packetLength;
++packetLength; //Add an element for the time stamp.
std::cout << nSensors << " sensors are connected.\n";
// End of optional automatic setup routine.
std::vector<float> dataArray(packetLength, 0);
std::vector< std::vector<float> > buffer;
int framesReceived(0);
//Main loop
std::cout << "Reading " << nFramesToRead << " frames of data:\n";
for (int ii = 0; ii < nFramesToRead; ++ii)
getData( &dataArray[0], framesReceived, 1); //Request 1 frame
if( 0 != framesReceived) // We have new data
std::cout << (ii < (nFramesToRead - 1) ? "." : ".\n");
buffer.push_back(dataArray);
Sleep(50); // Pause so we can see the loop run
// Write data to file
std::cout << "Writing data to " << outputFileName << "\n";
std:fstream out(outputFileName);
out << "Time\tSensor Data\n";
for (int i = 0, n = buffer.size(); i < n; ++i)
for (int j = 0, m = buffer[i].size(); j < m; ++j)
out << buffer[i][j] << ((j == m-1) ? '\n' : '\t');
stopScanning( SEN_I2C_BROADCAST ); //Stop the sensors
return 0;
How could I do something similar using LabView?
How could I use the DLL file in order to do this?
Any help would be greatly appreciated.
Thanks in advance.
Best regards.

Calibration avec Labview IMAQ Vision

Bonjour,
Nous sommes étudiants en première année à Polytech' Clermont-Ferrand, université Blaise Pascal.
Nous utilisons le module de traitement d'image du logiciel Labview depuis plusieurs mois avec M.Lafon afin de repérer les coordonnées en centimètres des centres de gravité de particules.
Pour cela nous utilisons une grille de calibrage constituée de 4 points disposés en carré, espacés entre eux de 13cm. Or lorsqu'on lance le programme de calibrage (bloc « Learn Calibration Template »), l'origine du repère choisit par Labview change régulièrement. A savoir que certaines fois Labview choisit le point en haut à gauche en tant qu'origine et d'autres fois il s'agit du point en haut à droite, par contre nous avons remarqué que l'orientation des axes ne change pas.
Nous avons effectué plusieurs tests afin de comprendre le processus utilisé dans le choix de l'origine, cela sans résultats, nous ne comprenons toujours pas comment le logiciel la choisit.
Pouvez-vous nous aider à répondre à cette question, ou nous dire comment l'obliger à toujours choisir le point en haut à gauche en tant qu'origine ?
Merci d'avance.
Cordialement.

Bonjour,
Merci d'avoir posté sur le forum NI. Vous avez déjà posté votre question ici des personnes ont déjà commencées à vous répondre. Je vous invite donc par la suite à poster uniquement une fois votre problématique
Cordialement
Mathieu B
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Forum Aéronautique, Spatial et Défense. Avec la participation exceptionnelle de Bernard DUPRIEU, Res...

While performing travel sensor calibration get error code 1802. What is this means in plain language.

We are using NI configurator 3.1. On our DVC5010f fisher controllers we have replaced potentiometer. While performing calibration thru NI we are getting error code 1802. Can some one explain in plain language what is this means and what can be done to fix this.

We have replaced potentiometer (Travel sensor ) on our Digital Valve Controller DVC5010F (Fisher). After Replacing this travel sensor, we were doing calibration using NI configurator software. During the calibration the software did not recognized the set range (variable) of travel sensor and gave us error code # 1802. These codes are accesible through www.ni.com web site. To get to listing of error codes. go to main page and in search block type in Fieldbus error code and select option 2 from several choices. these gives you listing of error codes. Code # 1802 derived from combination of error codes 0x0002, 0x0800 and 0x1000. These is where I am getting confused ...what is this? can some one explain this in simple term.
Attachments:
FieldBus Error Code 1802.JPG ‏47 KB
FieldBus Error Code tavel count.JPG ‏53 KB

Pressure sensor calibration in labview

Similar Messages

Maybe you are looking for