When choose DAQ and when choose GPIB?

Whats the difference between DAQ and GPIB?

Zurdo..
A very open ended question but I will give it my best shot. I would suggest searching on our website for additional info. GPIB is simply a communications protocol much like serial. Many instrument vendors provide a GPIB "port" on their instruments in order to control and automate the configuration, display, and acquisition. When you use GPIB you install a GPIB board on the host computer and then connect that via a cable to the instrument. There are then instrument drivers available for communicating with the instrument via its given set of commands/instructions. Most of the instrument drivers are written in LV.
DAQ is different in the fact that there is no instrument involved. You install a data acquisition card in your system and then wire that directly up to the phenomenon you want to measure (i.e pressure transducer, voltage source, current, etc). National Instruments then provides a driver and LV interface to configure the board for acquisition.
So...which one you choose is up to what you have available. If you have a standalone instrument from a vendor such as Keithley, Agilent, etc that does all of the measurements then you probably will use GPIB. If you are wanting to take measurements from some external sensor then you probably will want to choose DAQ.
StuartG

Similar Messages

Problems when the GPIB-ENET/100 is powered off.

Is there a way, other than Ping, to prevent the long timeout periods when a GPIB-ENET/100 is in or enters a bad state such as powered off?
Attachments:
GPIB_Power_Problem.doc ‏23 KB

Hi,
I did some tests and searched through the documentation, but I couldn't find any NI-488.2 function that would explicitly verify if the IP address is valid.
An EDVR means that an operating system error occured. Some function within the driver failed and the error code returned by the function is store in ibcnt.
You could use this error to as a signal that the ENET is not there or it is off. Any EDVR means some fatal error occur, so you can assume you need to restablish communication. It doesn't matter if the ENET is off or the network is failing, in any case the EDVR will indicate a fatal condition.
You can then call a function that handles this situation by calling ibonl(ud,0) to close the handle (which i think will also return an EDVR error)
and then try to restablish communication using the ibdev function.
The reason the timeout value doesn't affect the time it takes for the function to return is that the timeout is used to abort GPIB operations, not function calls. The timeout value is used by the ENET firmware to determine when to abort an I/O operation on the GPIB bus. The driver doesn't use this value to timeout the network communication.
Finally, you could use the windows socket API in your code to determine if the IP address is valid. You could probably find some simple ping code that you could include in your application.
Hope this helps.
Diego

DAQ and Labview on different partitions

Hello,
I installed DAQmx (8.9) on a C partition and Labview (8.6) on a D partiton but LV does not see DAQmx ?
Is it the reason ?
I tried to edit the path the palette (I would have like to just replace the D by a C), in fact LV looks for in C:\Na......\menu.mnu.
I also tried to add a palette, but then a lot of VI are missing.
I also wanted to modify the labview.ini, but I was not able to recognize the path to the palette tool.
To I tried to reinstall LV from the DVD and when it asks my for the driver, I tried my own installation, but the installer asks me
insert media for the driver. I do not have the media for 8.9 (the one on the media is 8.7.9 if I am correct), so I tried to
give it the path of the dowloaded file(NIDAQ890f1) as well as the path to the directory where I unzipped the dowloaded files,
but any of thoses paths are accepatble for the LV Installer.
Is it not possible to have a separated installation of DAQ and LV ?
Thank

Hi pdupre,
i never tried to install it on different pations, but in which order did you install it? You first have to install LabVIEW and then the Driver.
Hope it helps.
Mike

Acquire with DAQ and write DATA on can bus

I acquire data with a 6040E card and I would to send some of these data on CAN bus (card CAN DS) at 100ms but my industrial PC crash (1.2GHz 512Mo win2000 LV6.1).
The frequency of the acquisition is 1KHz and i aquire 4 data, my while loop run at 4ms, all seem to be normal.
In the same loop i try to send data on CAN bus all the 100ms but after sending 3 or 4 data my computer crash.
In two differents loops it's the same problem.
When I communicate with RS232 instruments during this acquisition i have no problem.
Can I do it? what is the problem? ...
Thank you for your response.
XAVIER

I'm using NI CAN 2.0, NI DAQ 6.9.2, and NI VISA 2.6.1.
In fact I would like to acquire data with a 6040E and 6602 counter at the same frequency (250Hz). I have a continuous acquisition of 16 DAQ channels with a sampling rate of 1KHz. I read 4 data in my buffer (1000) but only the first element of the buffer interresting me. The time of my while loop is 250Hz and all this 250Hz I read the value of my counter (simple read). A buffered read with the counter is not good because of the low frequency of my input signal. That increases the time of my acquisition loop.
I use the RTSI bus to synhronise the starting of the counter with the ai scan start of my DAQ card.
All the 100ms (in the same while loop) I write 1 CAN frame (1 2 3 4 5 6 7 8 at this time) w
ith ncwritenet.vi of the frame API.
But after few second (5 to 60) the image of my computer freezes, my mouse doesn't move, I can only shutdown my computer to restart it.
I have find only this solution to synchronize my DAQ and counter acquisition but it takes many CPU time and it would be the reason of the crash.
Thank you for your futur response.
XAVIER

How do I run a J-type thermocouple to the usb-6363 DAQ and program labview to measure temperature?

I have a usb-6363 DAQ and a J-type non-contact thermocouple that I am looking to connect and measure temperature through. However, the DAQ does not have any T/C inputs, which is needed to measure in the thermocouple temperature. I am connecting the thermouple to an analog input (+/-) and I am not looking to buy an amplifier, converter or any other hardware. I believe there is a way to program labview to read in the voltages of the thermocouple and convert it into accurate temperature readings. Any help/ideas?

Hello George,
This tutorial should step you through the basic process of configuring the device and connecting the thermocouple:
Tutorial: Connect Thermocouples to a Data Acquisition (DAQ) Device
http://www.ni.com/gettingstarted/setuphardware/dataacquisition/thermocouples.htm#Connecting a Thermocouple to Your Device
From there, there are a number of things you can do- I'd recommend taking a look at the LabVIEW shipping examples (Help>>Find Examples...) as well as the DAQmx getting started tutorials:
Getting Started with NI-DAQmx: Main Page
http://www.ni.com/white-paper/5434/en
At first glance, the 6363 you're using should have enough resolution to acquire usable data from a thermocouple- if you attempt reading raw voltages be sure that the acquisition range is configured for +/- 0.1V, though.
Regards,
Tom L.

Daq and sensors question

Hi, I am working on a semester long project:
build a data acquisition system, with the following sensors:
RPM
Torque
Strain of material
Temperature
Noise
Vibration
I am starting from scratch. I have experience in digital design, some embedded system stuff, and the usual - C/C++.
I don't have much experience in DAQs and have no idea whats out there
and how to start on it. I have a limited budget of lets say 250$. The
system needs to be portable as well, as it will be put on a moving
object. I do have access to Labview through school.
What I am looking for is some pointers and help on getting started,
info about sensors, about DAQs, and all that. So any info is much
appreciated. I'm not even sure if I'm posting in the right forum.
thank you
-Mike T,

Can you tell us what the unit under test is? The RPM sensor may be a once per revolution pulse.
PCB, www.pcb.com, has some nice vibration sensors
Thermocouples are inexpensive, and strain sensors may be a bit more expensive.
For portable, you may be interested in USB DAQ devices. We have several that will work with LabVIEW
Which University are you at? There are some advance signal processing libraries that might be available to you for analyzing and displaying the data.
Is there a traditional instrument that has been used in the past?
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

DAQ and timed loop

Hi,
I have a question about DAQ and timed loop. I used timed loop while acquiring data. I need timed loop since I have tvo more loops in my application and ı need give some priority to them.
Data acquisition should have a high priority. But the example codes about DAQ always use wlile loop. Is this wrong to use timed loop in DAQ application, or there is a unexpected result about
this usage.

You could use timed loops in Data acquisition operations as well
But, one thing you will have to watch is the 'number of samples per channel' terminal of DAQmx Read function.
Suppose you have rate as 1000 samples /sec, in your DAQmx timing vi
In continuous acquisition, if you specify number of samples per channel as 500, instead of performing 2 iterations / sec to get your 1000 samples as your nor mal while loop would, your Timed loop will run for 1 sec and you will get an error that all samples could not be acquired

When using GPIB hardware, do I need the exact driver[HP-3478a] or can I use simple raw GPIB-read or 488.2-read commands to take measurements?

If so, which would I use in order to take a reading from a lab instrument?
GPIB-read or 488.2-read commands to take measurements?

GPIB and 488.2 are the same thing, so the question if kind of moot. If you have a driver for the instrument then that's the best place to start, as it's quite likely to have been debugged and worked out. You can, however, code up your own communication. You would want to use VISA rather than the lower-level 488.2 commands, as this is the preferred API for programming. VISA is just a layer that sits on top of GPIB and allows you to write code so that you can communicate with a device via a serial or GPIB interface.
You should take a look at the examples that ship with LabVIEW as there's a couple that do basic communication using VISA functions.

Constant BSOD with nidgpibk.sys when receiving GPIB commands

Greetings,
I have a mainframe with a PXI GPIB card installed. I'm controlling the mainframe with my PC using GPIB and very frequently, the mainframe crashes (BSOD) listed nidgpibk.sys as the culprit. Them mainframe manufacturer says they can only use NI-Device 1.1 since it's the only version compatible with their system.
Is nigpibk.sys part of the NI-Device install? Is there any way to debug or fix this problem?
Thanks,
Jason

Hi,
Was there ever a solution found for this? I'm getting the same BSOD using the
nidmgpib.sys driver (v1.5).
The company we're working with says upgrading is not a quick fix, as they have
a lot invested in this driver.
Attached is the dump file.
Thanks,
Jeff
Attachments:
DumpAnalyzed.TXT ‏10 KB

NI-DAQ and LabVIEW

I am having a hard time convincing myself that there is any value in the generic
DAQ functions available in LabVIEW when it is desired to have software reusability/compatibility
with possibly non-NI hardware. It seems to me that I would be much better
off writing code to talk to ActiveX drivers. Am I missing something?

> I am having a hard time convincing myself that there is any value in the generic
> DAQ functions available in LabVIEW when it is desired to have software reusability/compatibility
> with possibly non-NI hardware. It seems to me that I would be much better
> off writing code to talk to ActiveX drivers. Am I missing something?
For interchangable HW, or the ability to shift between HW, then
what you want is a common interface -- sets of VIs that have common
connectors and common functionality. Below this set of VIs, they
can call a DLL, a CIN, they can call peek and poke, or they can
call an ActiveX server, OPC server, TCP to an ethernet device, or
whatever you like. ActiveX doesn't magically make components
interchangeable unless they have a common interface. LV is pretty
much the same. With the VIs, it isn't too difficult to shift
between them.
The most common interface for doing DAQ with LV are the NI-DAQ
icons. They have shipped for a long time and support a wide
range of boards including different busses, remote DAQ, etc.
There is at least one other company that makes a driver that
uses this interface. They have VIs that look and act the same.
That means changing your program between these two vendors is
pretty easy. Other vendors share some common functions, but
are not complete. Then you have the vendors that only have DLL
or an ActiveX server for their driver. This may be great for
you, but I suspect it will be considerably harder to use from
LV. You will end up writing the layer of VIs to go between the
DLL and C types or the ActiveX server and OLE types to LV types.
You will be the one to write it instead of the vendor.
As I said, it is possible to call DLLs, ActiveX servers, talk
to serial, GPIB, ethernet, and register based devices without
any vendor supplied VIs, but the easiest way to have functionality
in LV is to wrap them in VIs. Give them help, good icons, good
parameters, and place them logically in a palette.
So, in my opinion, the best interface to choose is the highest
level one that can accomplish your task. The one that is widely
used and has a good history. I'd recommend that you go with NI-
DAQ.
Of course you need to remember that I work for NI; so you
can do whatever you like with my advice.
Greg McKaskle

Help required with DAQ and waveform generation

Hi,
I'm using DAQ 6024E card for waveform acquisition using LabVIEW 8.2 version. I've also attached my vi for your reference.
My next step is , I want to add another waveform to the acquired waveform, i.e. I mean to say if the acquired waveform is a sine wave with 60 Hz frequency and amplitude of 8V peak-to-peak, I want to finally display a wave which is 8V peak-to-peak with sinusoidally changing freuency.
To be more clear...I want a sine wave with frequency = 60 Hz + 1*sin( 2*pie**t).
As cane bveen seen in my vi, I can extract the phase and magnitude of the original acquired signal.
Can anyone help me out with this...as I'm not able to figureout how should I proceed next.
Looking forward to hear soon,
Regards,
Rohit
Attachments:
test_analog.vi ‏162 KB

You'd probably want to use the DAQmx VI's instead of the Express VIs, when doing something more exotic. You can start by converting the existing Express VIs to code by opening their front panels and saving them as a VI.
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

DAQ and motor control in the same VI

Hello,
I am a beginner in labview and I am trying to control a maxon motor and run a NIDAQ at the same time. Basically, I need to measure the pressures and the angles at the same time and record these.
The problem that I am facing is that when I execute the VI, the motor runs first and this is followed by the measurement. I have twiddled around with it a lot getting a lot of help from this community but I can't figure it out. No matter what I do the motor starts running first and after the motor has completed its movement then the DAQ takes the measurements.
Is there any way to run the motor and the sensors together? I can run the motor seperately and I can run the sensors separately in their own VIs but can't seem to run them sequentially.
Any help would be appreciated.
Aman
Attachments:
VI.jpg ‏64 KB

In LabVIEW, your wires between VIs (and structures like While Loops) determine the order in which things happen.
There are several approaches that you can take to de-couple the motor and DAQ processes. The most obvious would be to put the motor control in one while loop, and the DAQ in another. Yes, you can do this in LabVIEW. Just don't get too carried away. Each loop usually will go to a separate core to run.
If there is data that has to be shared between the loops, you can use local variables, or the Value property nodes of the controls and indicators of your VI.
Machine Vision, Robotics, Embedded Systems, Surveillance
www.movimed.com - Custom Imaging Solutions

How can I read the active (plugged in) DAQs and then send that to the device name input on DAQ assist?

I have a system property node for daqmx but it does not let me change it to read when i right click on it. I am trying to have my program detect the name of the daq that is plugged in to the PC and then send that to daq assistant so that it will run properly wiithout me manually having to change the device name every time i switch hardware.
Solved!
Go to Solution.

labview12110 wrote:
Im just frustrated that the only function I have is to get a list of things that I can't do anything with. MAX knows which is active can I call it up somehow?
You have do do programming. That is what LabVIEW is. MAX gives you all the tools to do everything you want and much more just program it to do what you want.
Attached is a VI that I think does what you want. I looks at all of your devices and returns the first non simulated one. Apparently this list already excludes devices not connected to the system.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
Attachments:
Find Non Simulated Device.vi ‏6 KB

How Do I Install and Uninstall the GPIB Driver on

When I use GPIB as interface, I meet the problem "GPIB-32.DLL is either missing or damaged." In order to solve the problem, I need to uninstall all GPIB software, including NI-488.2 and reinstall NI-488.2. How can I do that. Thanks

One more suggestion. Can you find your gpib-32.dll file, if it still exists. It should be located under the system directory "C:\Windows\system32" (for 32-bit systems). From there, right-click on the file and select properties. In the properties you can go to version»company or digital signature and it should display a company name. I would be curious to see who made the dll. If another dll with the same name got copied over this one it may give you the same error that you are receiving.
Regards,
Steven Zittrower
Applications Engineer
National Instruments
http://www.ni.com/support

NI-DAQ and tcl/tk?

Has anyone had any luck using tcl/tk as the GUI of an
application that uses the NI-DAQ libraries? I'd like to
know what you did to bring the two together (the basics).
Thanks
Patrick Cevasco

Patrick Cevasco wrote:
>
>Has anyone had any luck using tcl/tk as the GUI of an
>application that uses the NI-DAQ libraries? I'd like to
>know what you did to bring the two together (the basics).
Hi Patrick,
Not in Tcl/Tk, in Java. The idea will probably be the same,
however:
The C part:
Once you have Ni-Daq installed (verify this by using the NiDaq
test panel)), there is a header file, \include\nidaq.h,
which gives access to all NiDaq functions. Include this file.
When compiling, also use the library \lib\nidaq32.lib
Now you only need to access C from Tcl. As far as I know,
that's quite easy. In Java, I had to make an intermediate DLL,
which can be accessed by the java-native interface, and which
passes all
calls to the NiDaq functions.
To make the required DLL, I used the following line: (MSVC,
compiled from the command line)
"cl -Ic:\ni-daq\include -Ic:\java\jdk\include -Ic:\java\jdk\include\win32
c:\ni-daq\lib\nidaq32.lib -LD ptt_util_NiDaqLib.c -FeNiDaqLib.dll"
Hope it helps,
Walter van Iterson

When choose DAQ and when choose GPIB?

Similar Messages

Maybe you are looking for