Data acquisition question

Iam using a pci6040e card to acquire data from lvdt load cells and pressure cells and also to control an Airbox interface box...I have managed to control the Airbox interface box but when I acquire data from the channels mapped to the particular lvdt or load cell or pressure cell, the readings tend to keep counting and does not come to a set value.,,even when nothing is connected it still tends to count when it is suppose to read zero..does anyone have any clues on how to go by getting these readings to be steady???

peni wrote:
the readings tend to keep counting and does not come to a set value.,,even when nothing is connected it still tends to count when it is suppose to read zero..does anyone have any clues on how to go by getting these readings to be steady???
The key word might be BIAS CURRENT
If nothing is connected you can read every possible value. You should get values close to zero if you short wire your inputs to ground.
Read in the manual about bias currents and how to handle it.
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

Similar Messages

BI 7.0 Question on RDA (Real Time Data Acquisition)

Those who have all implemented RDA (real Time Data Acquisition) in BI 7.0, could you please tell me if this is limited to only a few of the extractors or available to all the business content extractors. Reason I ask this question is I read that if you have PI_BASIS 2005.1 then RDA is possible, but when I go into ROOSOURCE table in R/3 I do not see the Real time flag checked for any of the transactional Businees content extractors!!
Also does this mean that we need to set this flag manually and if so is this supported by SAP? please throw in expert your responses...
Ram

Dinesh, thank you...after going throught the posts I am still more confsued and not sure if SAP supports any Business content data sources as RDA Capable yet...also if someone has successfully implemented RDA for any of the following applications please do reply back, thank you...
1. Plant maintenance
2. GL
3. EC-PCA
thank you

High Accuracy Analog Input,Data Acquisition Modules questions

At present,i produced a Data Acquisition Modules,but work not well,pls give me some suggestions.i produce according to a product from USA,but i only produce one channel.pls check the link.
http://www.sun-yuan.com/english/readnews.asp?id=71
Thanks for your help.pls send to my email:[email protected]

I haven't done this with NI-DAQmx, but I assume Read.vi works the same way as it does with traditional NI-DAQ. The way I do it is to give Read.vi the number of samples that it will read in 1 second. For example:
4 channels, 1000 Hz, read 4000 samples in Read.vi
All you have to do to accomplish this is multiply your scan rate and number of channels and pass the answer in as the number of samples to read. It will always read a second of data, even if it gets behind on one iteration of the loop it can catch up on the next. I also use a Wait Until Next ms Multiple and wire like 400 to it as not to bog down the CPU. Then you can just keep track of the elapsed time and stop the loop after 24 hours. Just be sure to clear the acquisition after the loop now that you're using a continuous acq, otherwise the buffer will overflow.
As I said, this is how AI Read.vi works for traditional NI-DAQ, I'm not positive that DAQmx Read.vi works the same way, but I don't see why it wouldn't.
Message Edited by Marc A on 01-16-2006 05:07 PM
Message Edited by Marc A on 01-16-2006 05:09 PM

Z600 workstation missing pci data acquisition and signal processing controller driver

I just installed Win7 Pro x86 on my Z600 workstation. It was an upgrade from WinXP Pro. In Device Manager I am missing the driver for the PCI Data Acquisition and Signal Processing Controller and Hardlock USB 1.02. Can someone assist me in finding these drivers. I looked on the Support/Drivers page for this model but couldn't find anything.
This question was solved.
View Solution.

Hi,
You might get better assistance on the HP Enterprise Business Forum since you have a professional worktsation.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

PCI Data Acquisition and Signal Processing Controller driver

I've installed win 8.1x64 on my HP Probook 450 G2 but I am missing the PCI Data Acquisition and Signal Processing Controller driver.
Can you please help?
Thanks,
Leontina
This question was solved.
View Solution.

Hi:
Please see if installing the Intel Chipset driver installs that device.
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775&lang=eng&ProdId=816

Data acquisition in a state machine

I've recently learned how to implement state machines, but I have a question that I haven't been able to find an aswer to.
Question:
How do I record uninterupted data (presently i'm using the DAQ assistant to record a single channel at 10kS/s at 1kS intervals) without interfering with my state machine?
Background:
I have a time sensitive test setup (measuring pressure in a rocket chamber), and I'm using labview to both record a single pressure transducer as well as operate the valves (O2, N2, igniter, etc). I'm using a state machine Labview architecture (just learned how). Presently, the DAQ assistant sits in the "Idle" state, and timers (valves need to be turned on at specific times) and manual buttons control when the other states are activated. I have a 10ms timer controlling how often each state is run, and this is the root of my concern.
Main concerns:
I'm worried that:
1) I'm forced to change my data recording to 10ms intervals to match the 10ms timer, and
2) The 10ms timer will interrupt my data recording when it's in another state.
It's very important that the pressure data is recorded without interruption but that I have high time resolution in controlling my valves as well.
Thoughts:
1) Maybe I put the 10ms timer in the "Idle" state only, and this way the other states won't interrupt the data acqusition
2) Maybe there is a way to completely isolate the state machine for controlling the valves and the data acqusition. I'm not sure how to do this.
3) People on the forums have been talking about Queuing their data acqusition, but I'm not sure how this would benefit my situation.
Thanks to everyone for their feedback!

The data acquisition and state machine timer do not have to be equal, you should however have the same data write rate as you have data read rate, otherwise over the course of long running programs you can build up a large buffer of data to be written using a lot of memory, or lose data.
Your data acquisition should be continuous, the most common way of doing this is every time you receive data write it to a queue, then when you are in other states except your data write stage you simply build up data in the queue that is to be written when you enter the write state again.
Think of it as traffic reaching a set of lights:
The traffic represents the data acquisition, there is a constant flow of it always coming through, the state of your state machine is the lights, green is the data write state clearing the queue, red is when in any other state, letting the traffic build up behind the lights.
It is just important that the light is green long enough to let the traffic not build up too much, otherwise you have a jam.
EDIT: For the basics of how queues work, look at the Queue basics example from the example finder.

Data acquisition from switching 500lbs load cell to 100lbs load cell

I am using 500lbs load cell, and acquiring data by inputing 2volts from 2345 signal conditioning board, and sensor output is connected to SCC-AI03 pin 3 and 4 , and configure this load cell to a channel using NI MAX, data neighborhood, traditional NI-DAQ virtual channel, the physical quantity is voltage set at range -10 to 10, and sensor also set at voltage with no scaling, but, I couldn't get any signal when 100lbs load cell is use, the difference of this 100 lbs load cell is the rated output is at 2.958mV/V, while the 500lbs rated at 1.8295mV/V , how should I do this?
Thanks.

Hi,
At this point, it is difficult to determine exactly what is happening to your acquisition. Could you please provide some additional information by answering the following questions:
What voltage are you reading with the 500 lb load cell?
Would it be possible to connect your load cells to a DMM and see what voltage reading you receive? If so, what do you see?
What is specifically happening when you connect the 100 lb load cell?
I also noticed that you are using the Traditional NI-DAQ (Legacy) driver. I recommend upgrading to the NI-DAQmx driver. Here are a couple of links with more information about DAQmx:
Advantages of NI-DAQmx:
Transition from Traditional NI-DAQ to NI-DAQmx:
Learn 10 Functions in NI-DAQmx and Solve 80% of Data Acquisition Applications:
Regards,
Hal L.

Data acquisition driven by encoder

Hi everyone,
I need to sample a capacitive sensor that measures the radial run-out (radial small displacement) of a rotating spindle. LabView v. 7.1 is employed to acquire the data by means of PCI-6036E card commercialized by National Instruments (NI). The spindle rotates at 100 rpm and a rotary incremental encoder is fixed at rear of spindle. The encoder gives two types of digital pulses as follows: a) A-quad-B pulses (it will be used only “A” pulses in this experiment); b) index pulse (one pulse per revolution). This encoder provides 1024 pulses type “A” per revolution. The measurements made by the sensor are driven by “A” pulses which are used as “external clock”. Therefore, every “A“ pulse, the card acquires one sample from sensor. Thus, 1024 data/rev are acquired. I want to sample 5 consecutive revolutions of the spindle. To start the data acquisition, the index pulse of the encoder is used as “start digital trigger”. Also, the index pulse should be used to count the number of revolutions of the spindle. In this way, when the number of revolutions is equal to 5, the data acquisition finishes. By contrast, the programmer also can set the number of samples equal to 5x1024 in the VI. The data acquisition is finished when the number of samples reaches this value. Similarly, the sampling process is started by the index pulse which is the “start trigger”. Note: 1) the sampled data should be put in a buffer. After the sampling process is finished, this data should be saved in a file of LabView; 2) In fact, the data acquired by the sensor are voltage analog input. Questions:1) Could you make a VI for this problem, please? Note: You can use the DAQ ASSISTANT EXPRESS VI or DAQmx TASK NAME CONTROL method.2) How to program the LabView in order to sample data triggered by the rotary encoder (pulse “A”)?3) What should I do to stop the data acquisition at the end of 5 revolutions?4) Could you send examples (VIs) similar to my problem above?5) How can I know if the program (VI) looses an “A” pulse? Is there any kind of error in VI that indicates a miss pulse? In anticipation, thank you very much for any help. My e-mail: [email protected] Bruce

Hello Bruce,
I have a complete solution for this but I cannot give you the VIs because my customer has paied for it and all rights are transfered to him.
What you need are two tasks. One task is the analog in task. You must use the DAQmx Timing.vi and the DAQmx Trigger.vi to set it up as needed. Or you create a task in MAX with this setup. The other task is a counter task just counting the pulses from the z-Index.
Next you need a small state machine with the states:
init, start, wait and stop.
init will initialize and start the tasks
start will read out the z pulse counter and wait for a change from 0 to 1
wait will read out the z pulse counter or the available samples property, when the desired number of z pulses or samples are available read the buffer with DAQmx Read.vi
stop will stop both tasks and clear them.
You will need two additonal counters which you don't have to check for lost A pulses and a external flip-flop electronic. The flip-flop will change it's state with each z pulse and the output will be used for gated counting. With each change of the z pulse counter you need to read out one of the additional counters to check if he had seen the correct number of pulses.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Data acquisition on the basis of time

Hi everyone,
I want to acquire the radial run-out (radial small displacement) of a rotating spindle using a capacitive sensor. To do so I will use the LabView v. 7.1. The PCI-6036E card from National Instruments (NI) will be utilized for data acquisition. The spindle turns at 100 rpm and a rotational incremental encoder is fixed at rear of spindle. This encoder provides an index digital pulse per revolution. This pulse should be used to start and finish the sampling process. I want to sample on the basis of time, by means of sampling rate of the card (Ksamples/s). So, let us suppose that I want to acquire 500 data/rev. The spindle takes 0.6 sec to complete one revolution. Thus, the required sampling rate is Fs = 500 samples/0.6 s = 833 samples/s. So, I should set the VI in LabView so that it samples only 833 data/s. Therefore, I will have to reduce the sampling rate of the analog-input channels in use. For example, let us suppose that the card provides 100 Ks/s when operating in multiple channels. Let us admit that there are 4 analog-input channels in use. So, the scan rate per channel is 25 Ks/s. This is too much for this application. I only need 833 samples/s. So, I should program the VI so that the card provides that required sample rate. As said earlier, I need to start and end the sampling process at the same point. Thus, to do that the index pulse of the encoder will be used. Also, I want to sample during 5 consecutive revolutions of the spindle. So, by means of a loop in VI, I should count the index pulse of encoder until the number of pulses be equal to 5 (= number of revolutions). At this instant, the sampling process should be stopped. Note: 1) the sampled data should be put in a buffer. After the sampling process is finished, this data should be saved in a file of LabView; 2) In fact, the data acquired by the sensor are voltage analog input. Questions:1) Could you make a VI for this problem, please? Note: you can use the DAQ ASSISTANT EXPRESS VI or DAQmx TASK NAME CONTROL method2) What should I do to stop the data acquisition at the end of 5 revolutions using the index pulse of encoder?3) Could you send examples (VIs) similar to my problem above? In anticipation, thank you very much for any help. My e-mail: [email protected]
Bruce

duplicate post
Continue in other thread
Message Edited by smercurio_fc on 11-14-2008 09:10 AM

Data acquisition from NI PXI 5152 using LabVIEW

Hi,
This might be really stupid question, I am new to LabVIEW and the Digitizer equipment. I was wondering if there are already any labVIEW based application available to read the data from PXI5152. I would be using both channels available and may be trigger. If there is no such application available, what would be port numbers I would be using for data acquisition. But, If I am to develop an acquisition software, I would be looking at every single specification of the equipment. I am assuming the output will be a digitized signal varying with the clock input, since It is used as oscilloscope. When working with labview how would I specify the port to read from and how would my PC recognize the port. I working on a pre-configured system and they won't let me unplug anything to check the configuration. Does NI provides a software to read into the signal fed into the channel and trigger inputs. I have tried looking into the different forum discussion but didn't find any that address my issue. May be it's too simple and stupid. But, it would be a great help if you could point out my misunderstanding.
Thanks in advance.
BP

There are numerous examples. Help>Find Examples> Modular Instruments>Ni-Scope. There is a test panel available in MAX. On the Measurement I/O>NI-Scope palette, are all of the driver functions includeing the NI-Scope Express.
I'm not quite sure I understand your references to 'port's. Once installed into the chassis, it should be listed in MAX. In the functions you will be using, there will be a dropdown menu that you will be able to select the scope resource name.

Data Acquisition - using local variables to write data to a file

Hello,
I am running a Data Acquisition vi (currently in LabVIEW 7.1 but soon to be updated to 8.2) that collects ~100 parameters of data from several sources contained in a while loop. The current configuration (which I did not write) uses very few subVIs and writes to ~100 local variables to store each parameter. It then reads all the local variables and builds an array of all the strings, converts then to a spreadsheet string, then uses the write characters to file function to append to a datafile. I am trying to clean things up and have came up with subVIs to collect the data from the following sources:
8 serial port sources collecting btwn 8 and 20 parameters each
~15 thermocouple readings
~10 analog inputs
~20 parameters read off an ARINC 429 bus.
I have come up with a subVI to read each of the sources and have placed the subVIs in the while loop. Each subVI outputs the data that it collects in array or cluster form. I was wondering how best to write each parameter to a CSV file at between 1 and 10 Hz. Should I write each subVI output to a LV and then read them off as was done before (the difference being that I have reduced the # of LVs to ~10 vs >100?
I should add that precise timing is not that important, so if all the subVIs are not collecting simultaneously (which I understand that they won't be), it does not really matter.
Thanks.

Hi jilla,
jilla wrote:
What I think that you are saying is to turn the outputs of the 4 subVIs into inputs of a 5th subVI that writes to the data file. Correct?
Yes. It may sound like a fine-point, but I beileve it's better to create a VI specifically for formatting data - in your example, 4 arrays IN, a single string OUT. Then write the string to file as a seperate operation. GUI-displayed data can go through a similar transformation, the four arrays wired to a subVI which builds output-structures specifically for display. It's a beginner's mistake to put lots of individual controls and indicators on the screen when groups of them are naturally related (in an object-oriented sense.) Use clusters to group related controls - this will keep the diagram much cleaner.
One more question: at what point (either # of data points or frequency of data collection) does it become necessary to use queues? Thanks.
Well, there's not really a clearly definable "point". I'd say if your update-rate climbs above 100Hz, or you witness poor program or system performance, then it's time. The scenario you've described is a fairly simple acquire/display&log loop - and simple is good. Then-again people can't see/react-to updates faster than about 10Hz - so it doesn't make sense to sacrifice performance - if performance becomes an issue.
Re: queues: Queues are sometimes used to buffer data that's "produced" in one place and "consumed" in another.
Here, if/when logging data, you're logging with every DAQ. I wouldn't recommend using a queue to transport data from a "DAQ loop" to a "Logging-loop" - those functions can be in the same loop. Should/could a queue be used to get data from a "DAQ loop" to update the GUI at a lower frequency? Sure, but a Notifier might be a better choice. Further, in the (simple?) program you've described, you might use a case structure (True/False) to only update FP indicators every "X" iterations - a simple solution that doesn't require Queues or Notifiers.
Cheers!
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

Data Acquisition Step Type

Hi, is there a step type to perform Data Acquisition and Basic comm control such as RS232 and GPIB within teststand ?
This question was raised when I was training one of our Technicians today, he asked/suggested that having a step type which performs Data Acquisition and comm control would reduce there development time down dramatically, They have just started to use Teststand on small cycle test rigs as part of an evaluation stage. They have no experience with LabVIEW or CVI, they basically want a quick and easy way to produce a test sequence with Data Acquisition and comm control.
if there is anything like this at the moment can you possibly reply. If there is not, is this a something which will be avaible in the future ?
Message Edited by ds1638 on 12-09-2008 02:44 PM

Data Acquisition usually refers to a DAQ board from NI so I think what you are looking for is a generic NI-VISA step type and a specific RS-232 step type. I have a NI-VISA step type that was originally written with LabVIEW 6.1 and for use with TestStand 2. I've atached that below. I don't have the .ini file handy and don't have time to recreate it but from the code, you should be able to see what needs to be added to the step properties. The basic step is a modified Pass/Fail Step.
It's not that difficult to create your own custom steps. I've done a lot and it only takes a little while longer than doing a code module in LabVIEW or CVI. The extra time is in creating the edit step.
I've got an RS-232 step type but part of it is product specific so it is proprietary and I can't post that. Look at the VISA example and the other examples of custom step types that are on the developer zone and see how far you get.
Attachments:
VISA IO.zip ‏188 KB

Data-acquisition with NI 6036E DAQ card & GPIB using an external trigger

Hi all,
I hope somebody could give me some help with the following and answer some questions:
Simple system description:
Labview 6.1
PCI-GPIB card
6036E DAQ card
In my system, I am using an external analog trigger signal (A) for continuous data-acquisition. Characteristics of the analog trigger signal (A) are: ~40 Hz, signal height +1.48V, triggered by rising edge (the analog trigger signal (A) could be changed to a TTL signal). Each data-acquisition is done within ~1.0 ms after the rising edge of the trigger pulse. The timing of the data-acquisition and analyzing procedure is controlled by execution in a sequence structure placed in a loop.
Now, I connected a power meter to the system, to measure the laser power during the data-acquisition. The power meter has two options to provide the laser power data:
a) via analog signal output (voltage corresponds to laser power in watts)
b) via GPIB (direct output reading of laser power in watts).
Problem:
During a certain point in my data-acquisition sequence structure (defined by a frame), I want to use the next occuring analog trigger signal (A) to acquire 1 value from the power meter.
How do I do this in Labview programming for the following two situations?
a) If I connect the analog output from the power meter to an analog input channel of the 6036E DAQ card. The analog trigger (A) would be connected to a second analog input channel (In case the analog trigger signal (A) is changed to a TTL signal it would be connected to the PFI0/Trig input pin on the DAQ card).
b) If I use the GPIB connection of the power meter. The analog trigger (A) would be connected to a second analog input channel (In case the analog trigger signal (A) is changed to a TTL signal it would be connected to the PFI0/Trig input pin on the DAQ card).
An other possibility would be to trigger the power meter directly, so it outputs constantly power meter values at ~40 Hz. How could I than acquire 1 power meter value (at a certain time im my sequence structure) via analog input at DAQ card or GPIB?
Additional questions:
How do I configure the PFI0/Trig pin on the 6036E DAQ board individually as an INPUT?
How do I use an analog trigger signal (A) as counting signal for a loop, or as an activation signal for a sequence structure which includes GPIB commands?
It would be very nice if somebody could give me some help.
Kind regards,
beam

Hi beam,
I just want to verify that I understand your situation correctly:
An external trigger signal (A) is wired to one of your input channels (e.g. CH0) to trigger data acquisition of a second channel (e.g. CH1). Your power meter is connected to an analog input channel, which you would like to trigger with a certain rising edge at some of your sequence structure.
Problem:
During a certain point in my data-acquisition sequence structure (defined by a frame), I want to use the next occuring analog trigger signal (A) to acquire 1 value from the power meter.
How do I do this in Labview programming for the following two situations?
a) If I connect the analog output from the power meter to an analog input channel of the 6036E DAQ card. The analog trigger (A) would be connected to a second analog input channel (In case the analog trigger signal (A) is changed to a TTL signal it would be connected to the PFI0/Trig input pin on the DAQ card).
If a task has been configured to acquire signal from one analog channel, it's not possible to run a second analog input task or to add a second channel on the fly. You had mentioned that it's possible to read from the instrument through GPIB. Is it possible to perform a software trigger such that at a certain frame of your structure, when the trigger signal A reaches voltage "x", a GPIB command is written to your power meter to query a measurement reading?
Additional questions:
How do I configure the PFI0/Trig pin on the 6036E DAQ board individually as an INPUT?
You do not need to explicitly configure the PFI0 line as an input. If you want to use it as an input such that it acts as an analog trigger, simply wire the trigger signal to this pin. When configuring the trigger in your software, specify PFI0 as the trigger source.
How do I use an analog trigger signal (A) as counting signal for a loop, or as an activation signal for a sequence structure which includes GPIB commands?
You can try using the Limit VI to find out when the trigger signal reaches a certain level, and count how many times this level is reached. Similarly, you can use this as the condition to execute GPIB commands.
Hope this helps,
Lesley

Data acquisition time not continuous, but starting over and over again

Hi,
My data acquisition time is not continuous but loops over and over
again. Could someone please take a look at my vi to see if you
have any thoughts on how to fix this. Also, I tried to set up my
vi so that I could take the mean of the signal at any time I
choose. However, at the same instance that the data acquistion
time "starts over" again, the mean is calculated (before I trigger it to take the mean)
I have attached my vi and my output file as a text file so that what
I'm trying to say will (hopefully) make a bit more sense.
Thanks for your help in advance!
Sherri
Attachments:
Datalog1 71805.vi ‏1252 KB

Hi,
Thanks for responding to my question. Attached is the vi with added
comments as to what I think I am doing. By DAQ time, I mean the
first column of data that is in the data file that I attached
previously. I am only simulating a signal (at the beginning) so
that I can program in my office. I do, however, have the same
problem as stated above when I change the simulate signal to DAQmx
using my instrument.
I hope this clearer. If not, I'll try again.
Thanks so much!
Sherri
Attachments:
Datalog1 71805 83.vi ‏1228 KB

Data acquisition from SPCM-AQRH-15 and Nano-ViewTM 200-2/M

I am trying to acquire data from APDs (PerkinElmer, SPCM-AQRH-15) and Nanopositioner (Mad City, Nano-ViewTM 200-2/M). The second equipment has USB 162 or 202 digital interface integrated but I am not sure abut the first one since I am still waiting my order. anyway, I want to control/communicate with both of them using your product, does anyone know what software and hardware I need? thanks.
Solved!
Go to Solution.

Hello Confuciusl,
I have been looking into the problem
statement that you gave us above and have some questions for you as well as
some answers. I am going to go with the basic understanding that we will be
using LabVIEW to not only communicate with your devices, but also for data
acquisition and analysis.
In reference to your APDs (PerkinElmer,
SPCM-AQRH-15), I have looked at the data sheet for the product located here,
and have determined that the best method of communication with your device
would be to use some type of Counter/Oscilloscope card in a PCI/PXI standard.
This will allow for proper recording of your signal from your Output Terminal.
For more information on cards please refer to this link.
As for the second instrument listed, the
Nano-ViewTM 200 from MadCity, it mentions here that The Nano- View/M™
system includes the Nano-Drive™ controller and is compatible with user written
LabVIEW software. Since we do not have the capability to obtain the product you
are specifically trying to communicate, the best option at the moment would be
to try and contact MadCity and see if they have any specific Instrument Drivers
pre-built for LabVIEW that will allow you to communicate with your device. If
they do not, the next option would be to develop your own by following the
guidelines at the following link.
Thanks again and have a great day!
Regards,
Nicholas K
National Instruments
Applications Engineer

Data acquisition question

Similar Messages

Maybe you are looking for