NI DAQ Hardware Protection

Hi all,
I have been working with NI hardware for about 2 years now. I have found that some of the I/O channels of USB as well as PCI based DAQs tend to blow off after a period of time. I have also blown 2 PXIs till now. I'm sure this is not a problem with NI hardware as it may turn into a quality issue then. I want to know what kind of protection can I do in my control panel to avoid this. I would be greatful if I get some checkpoints from all you experienced people out there which I can ensure while building an electrical panel for my system. Please also share your experiences with such situations and how you solved it.
Regards,
Giridhar Rajan

I almost always use OPTO22 isolation modules for digital I/O. If you think that you have problems on the analog side, isolation modules are available, but be careful of the update rates they are capable of.

Similar Messages

Looking for DAQ Hardware

Hello,
I have been using LabView 5.0 for a few years to program, control
& retrieve information from the GPIB bus. I want to get into DAQ
programming. Where I work, we do not have much in the way of DAQ
hardware, so I am going to attempt to purchase what I need to play at
home in my spare time.
Looking for:
** DAQ card, preferably PCI for Windows 98: (PCI-MIO-16E-4 or 10)
** Signal conditioning hardware that will work with the PCI-MIO series
card I am looking for.
Please reply to: [email protected]

Chip,
If you are planning on using a breadboard for experimenting with you'e DAQ
board take a look at http://www.vicsys.com/pcbprods/bbdaqcvt.htm. It is an
inexpensive way to easily connect you're DAQ board to you're breadboard. I
also have some older used DAQ boards for sale at
http://www.vicsys.com/usedbrds/usedbrds.htm if you want to save a few bucks
on you're DAQ board.
Best Regards,
Neal Pederson, President, VI Control Systems
1923 Mendius Lane, Los Alamos, NM 87544
TEL: (505) 662-1461, FAX: (603) 388-4969
[email protected], www.vicsys.com
Chip Henkel wrote in message
news:[email protected]..
> Hello,
> I have been using LabView 5.0 for a few years to program, control
> & retrieve information from the GPIB bus. I want to get int
o DAQ
> programming. Where I work, we do not have much in the way of DAQ
> hardware, so I am going to attempt to purchase what I need to play at
> home in my spare time.
>
> Looking for:
> ** DAQ card, preferably PCI for Windows 98: (PCI-MIO-16E-4 or 10)
>
> ** Signal conditioning hardware that will work with the PCI-MIO series
>
> card I am looking for.
>
> Please reply to: [email protected]
>

Utilizing NI DAQ hardware on a remote system.

I noticed that the new version of Measurement & Automation Explorer for LabVIEW 8 now has a "Remote Systems" tab. Would this enable me to have say Computer A setup with some DAQ hardware and then utilize that hardware at Computer B over a 100 or 1000mbps ethernet network within LabVIEW?
If not, what would I need to be able to do that? I've played around with the web publishing tool, and would rather have the actual LabVIEW program running on Computer B rather then on Computer A.
Thank you for your input!
-nickerbocker

Thank you for your reply GDE [DE]!
That’s too bad. I assumed too much and thought we
were able to do something fancy.
I work at a test facility where the tests that we run are hazardous.
We have a lot of concrete walls between us and the tests that are run. We
have a test console setup where we have our entire test monitoring tools in a
central location. The problem is, whenever we make a new test chamber all
the transducer lines have to be drawn to our test console. These lines
consist of analog outputs from Omega DP units that power and read pressure
transducers and K-type thermocouple channels.
This makes it difficult, if not impossible when time is
constraining, to setup for a new test. Some of our newer test chambers
and rooms that we have added to our facility are further and further away from
our test console. Long analog lines are not good for noise reasons.
Long thermocouple channels are even worse since the signal is so small and varying
temperature gradients across the line can affect measurement readings.
The solution that seems apparent to me is: why don't we
read our transducer values closest to the test cells and network that
information back to the test console through a high speed gigabit network?
I was hoping that a remote data acquisition computer would
just consist of an operating system, the hardware and hardware drivers for DAQ,
and then MAX. The computers at the test console would be in charge of
actually administrating the test procedures (Digital I/O) and DAQ through the
network.
I have looked at the web features available in our license
of LabVIEW 8 Professional Developer and I'm pretty impressed with its
capabilities. The problem is I don't want to have to obtain a LabVIEW 8
license for each remote computer. It is just too expensive. I can
build executables with my developer’s license of LabVIEW 8, but I don't think
that the web server features can be built into an executable LabVIEW program
(or can they?).
Can I use this shared variables solution that you speak of
in a LabVIEW built executable?
I hope that I have provided enough information about my
problem to help stimulate some possible solutions and more discussion. I
really appreciate the help that these forums provide and hope that I am able to
give back to this community.
-Nic

Is there a way to use a DAQ VI without DAQ hardware?

Hello,
Is there a way to use a DAQ VI without having DAQ hardware?
Thanks,
Steve

Steve,
Yes, you can use the DAQ VIs without the hardware. With the DAQmx 7.5 and 7.4 version of the driver, you can simulate DAQmx devices. This will save you some time, as you can program and test your application without the actual HW present. However, you will not have the full functionality with simulated devices.
Regards,
Somendra

Why do i get a daq hardware configuration required window when trying to run the daq solution wizard?

i have recently installed the ni 4552 for pci dynamic signal analyser, and am attempting to configure my system and teach myself labview. when attempting to run the daq solution wizard i am presented with the daq hardware configuration required window.
Attachments:
DAQ_Hardware_Configuration_Required.ppt ‏38 KB

hi brian, thanks for your help. i have recently received version 6.1, and done a complete re-install. i have also downloaded the latest ni daq (6.9.2) and ni dsa (6.11) versions and installed them, but still i get the same error message when trying to open the solutions wizard (please see attached powerpoint presentation).
upon selecting the "go to ni daq config utility" option MAX opens. everything appears to be in order (device passes test, test panels run ok and virtual channels are configured correctly). i am unable to go any further.
i would appreciate any guidance that you are able to give me in this matter. many thanks in advance of your help.
best regards,
ben halkon

Sync CAN and AI DAQ hardware

Helo Experts,
I have a requirement to sync CAN based encoder data and other analog input channels into 1 program and write data to a file @ 1000Hz.
I am not sure how the timestamps on the CAN based NI devices (like NI USB-8473s) and NI USB 6343 would be synchronized? Has anyone has any experience in handling these 2 DAQ hardware at the same time and write data to a file?
I have seen some articles:
http://www.ni.com/product-documentation/4294/en/
http://www.ni.com/tutorial/4204/en/#toc2
However, I am little skeptical if my system would work, just becuase my AI DAQ hardware is not RTSI as mentioned in the examples.
Secondly, is NI CAN the best approach in this scenario to couple CAN based data & AI channels going into our system?

There is a good example that I think will get you most of the way there. It is under a lot of folders in the example finder so I figured I would just post a picture of where I found it.
This example shows how to sync your CAN device with 1 DAQ device, but you should be able to use channel expansion to sync your CAN hardware to 2 DAQ devices. If you are still having trouble, can you post the code you tried and tell us exactly what DAQ hardware you are using?

Do I need Daq s/w while running a Labview exe which contains the DAQ hardware cards on a pc which does not have Labview s/w

I am having a Labview 6i program which takes hardware status from the NI hardware cards...now I make its exe with Labview Run Time Engine & then I am unistalling complete Labview with "Remove all" option....then I am installing this exe......Do I need DAQ or MAX now ?

Hello,
If you have an executable with DAQ functions in it, then you are required to have NI-DAQ installed on the machine.
Also, please post your LabVIEW/DAQ questions in the appropriate category...this category is for questions pertaining to the NI product "Measure for Windows", which you do not appear to be using.
Have a nice day,
Darren N.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

I cannot access my multi-function DAQ hardware from VB/Meas Studio after upgrading to latest Meas Studio Version and NI-DAQmx

I have a farily complex project that was initially written in VB6.0 with Meas Studio 3.0 and using traditional NiDAQ. For seveal reasons, I wanted to upgrade to the latest NI software. So, I purchased the latest version of Meas. Studio. I installed this, along with NI-DAQmx. Now, I cannot access any of the hardware from the VB IDE / Meas. Studio DAQ objects. Nor can I get the installed examples to run. The test panels run ok from MAX.
The whole process of trying to do this upgrade process has been extremely confusing and frustrating. I have a support request in, but have yet to hear from anyone. Trying to get useful information on this problem from the NI web site has also been difficult since almost all of the support doucments of any detail reference Labview.
Any help will be appreciated.

I'd like to better explain the decision not to provide ActiveX controls for DAQmx. My intention is not to de-legitimize your concern or downplay the pain/inconvenience this caused you.
The decision not to provide ActiveX controls would be more accurately summarized as a cost/benefit decision.
DAQmx is an entirely different API. The choice not to support mx with ActiveX controls was not a matter of dropping support from an implementation perspective (I understand that from a product-offering perspective, it is dropping support). Rather, the choice not to support mx with ActiveX controls was a matter of not designing and implementing an entire new set of controls.
Given our resources, we have to make choices about what languages (C#, VB.NET, C++, VB6), frameworks and versions (.NET 1.1, .NET 2.0, ASP.NET, MFC 7.1, MFC 8.0, VB6), and development environments (VB6, VC6, VS2003, VS2005) that we support. When NI decided that mx was necessary (that is, we could not move forward with new hardware under the old Traditional DAQ API), the Measurement Studio team had to decide which of these languages/platforms/ADEs to support.
We view the ActiveX controls as native support for Visual Basic 6.0. In March of 2008, Microsoft is going to stop supporting Visual Basic 6.0 (http://msdn2.microsoft.com/en-us/vbrun/ms788707.aspx). It was largely because of this that we did not feel that our customers, as a whole, would gain enough benefit from us developing ActiveX controls to justify the cost. Instead, we developed native .NET and C++/MFC libraries for DAQmx.
We developed the type library for mx because we did understand that some customers would want or need to use mx boards in existing VB6 systems. While this is not an ideal solution, we hoped that it would be good enough. I am sorry that it doesn't meet your needs.
Looking back, we see that our customer base has not moved away from VB6 and to VB.NET or C# as quickly as we thought they would. This is why the Measurement Studio product continues to include VB6 support (the UI and Analysis ActiveX controls that you mention) and why we continue to fix bugs in these components. However, we are not putting much effort into developing new features in these ActiveX controls. Almost all of our new feature development efforts are in the .NET libraries.

Labview NI DAQ application with no daq hardware

1)LabVIEW 6i & NI DAQ with PCI 6023 E cardupport required for Application installation with no hardware and NI DAQ software drivers on target system.
Hello
I have prepared an installation application with
LabVIEW 6i and NI DAQ built-in functions with PCI
6023 E card.
I install this application on a system, which does
not have NI-DAQ driver software and PCI 6023 E
card hardware,and then I try to excute Application,
it starts up, but with the Error Messages stating
that it requires/ does not find DAQ functional vis
and drivers.
I wish to install my application and excute it
without getting the Error messages and must be able
to do the other tasks with the applic
ation created
for. And I dont want to install NI-DAQ software and
Hardware.
Guide me on this, with any possible ways.
Thanking in advance.
SN.

LVDEV wrote:
>
> 1)LabVIEW 6i & NI DAQ with PCI 6023 E cardupport required for
> Application installation with no hardware and NI DAQ software drivers
> on target system.
>
> Hello
> I have prepared an installation application with
> LabVIEW 6i and NI DAQ built-in functions with PCI
> 6023 E card.
> I install this application on a system, which does
> not have NI-DAQ driver software and PCI 6023 E
> card hardware,and then I try to excute Application,
> it starts up, but with the Error Messages stating
> that it requires/ does not find DAQ functional vis
> and drivers.
>
> I wish to install my application and excute it
> without getting the Error messages and must be able
> to do the other tasks with the application cre
ated
> for. And I dont want to install NI-DAQ software and
> Hardware.
Here is one approach: save a copy of each VI that calls a DAQ function.
Save the copy with the same name in a different folder called Dummy.
ENSURE you check the box "save without updating callers".
In that Dummy folder, edit the VIs to remove DAQ calls & return fake
values: zero, 5 VM, random values, whatever is appropriate.
Now preload all the dummy VIs, load up your main applicaiton, and you
will have an application that runs without DAQ.
Make an executable & install it.
This is a useful trick that predates dynamic loading, & you need not
rewrite your VIs to use dynamic loading.
You'll get up & running quicker.
(In the long run, you would need to write these dummy VIs anyway for
dynamic loading.)
Mark

Multiplexing channels after the analog inputs of a DAQ Hardware

Hi,
I need to sample a 5KHz analog signal with 48 channels.
It's needed all these channels simultaneos.
I know there is not a DAQ hardwere at NI beyond 4 simultaneos channels.
How could I or NI solve this problem? Have NI an hardware that could be applied?

Greetings,
You are correct in that there are no simultaneous sampling boards that have more than 4 channels. Performing truely simultaneous sampling will ensure that there is virtually no interchannel delay and that the phase relationship between each signal is retained. If you use a regular Multifunction Input/Output DAQ board and some sort of signal conditioning, like SCXI, to increase your channel count, you will be performing a multiplexed operation. However, in most cases the interchannel delay is on the order of microseconds. If this is still too much for your application then I'm affraid the only answer is to get multiple Simultaneous Sample boards. You would want to trigger each board's acquisition to start at the exact same time. In order to
do this you could either use a PXI system or use PCI and leverage RTSI.
However, even with this suggestion you should keep in mind that most PCs only have 5 PCI slots, which will limit you to 5 * 4 = 20 channels. If you went with a PXI system and used the PXI-1006 chassis, which has 18 slots, then you could fill it with 12 PXI simultaneous sample cards.
PXI
http://sine.ni.com/apps/we/nioc.vp?cid=1525〈=US
NI PXI-1006
http://sine.ni.com/apps/we/nioc.vp?cid=4889〈=US
S Series Multifunction DAQ
http://sine.ni.com/apps/we/nioc.vp?cid=10834〈=US
Regards,
Justin Britten
Applications Engineer
National Instruments

Can any NI/Labview DAQ hardware be used to input video? BNC, S-Video, RCA, etc?

Hello,
I am trying to manipulate digital video captured from security-type cameras and other devices. I am just beginning on this adventure and would like to know if the National Instruments Suite has some possible solution.
Thanks!
M. Logan

Sure! NI has a series of image acquisition products just for this. Check out this link and I think the best one is the NI-1411.
http://www.ni.com/vision/hardware.htm
Hope that this helps,
Bob Young
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]

Does MAX need to be installed for a built exe to utilize DAQ hardware?

Hello-
I'm currently working on a program that gets built into an exe and put on a target computer running XPembedded. Initially I installed MAX support and all the software I thought was necessary. It seems to slow the computer down a good bit during boot up.
Once the computer boots up, its almost as if XPe hangs for a good few minutes before you can even get the start menu up. I'm wondering if there is anyway I can uninstall MAX and use the "generate code" feature on all of the DAQ task names.
When I go to uninstall MAX the uninstaller tells me it will also remove all of the programs that have MAX as a dependancy (including my program).
Does anyone have any insight on this issue?
Thanks for any info!
-pat

just as an update- as it turns out, I did not include the MAX config support installer this last time and my software and hardware currently seem to be working great. I am now in the process of trying to slim down the services and startup activity to speed up boot time.
Right now my issue is as follows:
After putting my exe alias into the startup folder on the xpe target, it takes almost 5 minutes for the exe to load (including bootup)- AND my hardware does not work. If I close the exe and re-run it, it seems to run fine.
So now perhaps theres an issue with the order of services/programs executed on startup.
If anyone has any insight or suggestions on how to go about this- I'd appreciate it.
I did manage to get msconfig running on the target as well, but it seems most of the NI services are dependent on one another and if you disable more than one or two, you kill communication between them and stuff like that.
thanks for any ideas
-pat

DAQ input protection (overvoltage & overcurrent) question

Hello Everyone
I´m designing a DAQ board as my thesis work.
I have several questions about input protection, I have searched and searched and I have found only 2 circuits, a crowbar and another one using 2 zenner and a PTC resetable fuse or a ordinary fuse.
My question is, if there is any other circuits that can protect inputs.
The measurement limits are +-20V with a maximum frequency of 100 kHz. At the input there will be a INA163 IA, and then the rest of the circuit. I have to protect these inputs to 230 Vac.
If someone knows any other method of doing this, please reply. I'm pending to the PTC+diodes.
Thank you

That seems a good approach, to keep it simple. About the resistors I don´t know yet if I´m going to use SMD type or the normal type, I have to see if there is enough space on the PCB. Probably if I choose the SMD type I will have to connect several in series as you said (230 V SMD resistors with those values are a bit hard to find, Ive checked farnell), but I will test it.
About the zenner, when choosing it, It should whitstands also 230V of direct applied voltage right?
I´ve attached a file with the circuit, as I pretend to measure diferential signals with the INA163, I think that this circuit is correct using your sugestion.
Now about the PTC, for the overcurrent protection, if I´m not wrong there are 3 parameters that must be taken into account:
- Holding current (I think this is the normal working current)
- Tripping current (At this value the PTC cuts the current going into the circuit)
- Operating voltage (I think I must choose the 230V version)
The holding current I´ve pointed it to 50mA with a tripping current of 100mA (I have no ideia if this is ok), the maximum current input of the INA163 is 10mA, the resistive divider will limit also the input current, but I would like to have some more protection.
Shoud I put one PTC in each signal branch (Vin+ and Vin -)?
Attachments:
circuit.png ‏17 KB

DAQ Hardware Recommendation (air velocity measurements)

Hello
My application is relatively simple (I think). Basicaly I need to measure
and record the air velocity at a number of different locations.
I am quite new to the whole DAQ "thing", and I don’t really know how to
go about selecting a proper hardware (partially due to a huge selection available from NI).
The transducer I need to use is TSI Model 8465
(For the detailed specs go to http://www.geneq.com/catalog/en/velocicalc_8455.html)
I have a few requirements:
Relatively low cost (which should not be a big problem due to transducers low response time)
Hardware needs to be accessible through PC (I guess USB or PCI)
Hardware needs to be accessible by Microsoft .Net Languages (VS2005/VS2008)
I would also appreciate if you could point me toward more info on DAQ.
(Sort of like "Basics of DAQ" or "Introduction to DAQ" type tutorial/information)
Thank You
V

Hi Vuli,
Welcome to the NI forums! Although posting to the correct
forums is encouraged, don’t fret about this one.
There are a number of things I will address here:
Accuracy, timing , links for getting started & finding the right device for
your application.
Beginning note: Most DAQ cards (USB, PCI, and PXI) use
the DAQmx driver, which can be downloaded for free here .
When installing this driver, it will detect and install example with support
for VS. You can find out if a specific device uses the DAQmx driver by viewing
the ‘Data Sheet’ from the device webpage, which should say which driver
software is provided / used.
Accuracy:
Although your transducer may have the accuracy you are looking for, you also
need to consider the accuracy and resolution of our cards (12 bit, 14 bit, 16
bit, etc) as this will determine the accuracy which the computer reads back.
Timing: Timing
determines when the value of the ADC is latched. There are two types of timing –
software and hardware. Software timing will rely on your computer to call the
DAQmx Read function, which then calls the driver and sends a signal to the
card, which will then latch the ADC value, and return this to you. This amount
of time it takes, and the period of occurrence is purely system and program
dependant. Hardware timed, uses the clock on-board the DAQ card,
therefore acquiring samples (latching the ADC) at a specific and deterministic
rate. (Not all boards are hardware timed, but the ‘sample timing’ will tell you
the case, and how fast. Like you mention in your post, ‘ 10KS/s’ means that the
card will acquire at a rate of 10,000 samples per second). Again, your samples are returned when you call the DAQmx
read function. The key difference is that although the DAQmx read will still be
called non-deterministically, there is a FIFO which holds the samples until
this happens, therefore the samples still have values taken from the
deterministic on-board clock.
To find the best device for your application, you can
look at this webpage (http://www.ni.com/dataacquisition/)
or call us at 1-800-433-3488. We are more than happy to talk with you, and make
sure you get the right device for your application. Personally, I would
encourage this, so we can discuss the ‘big picture’ of your application, and
make sure we provide a solution which will work now AND in the future.
A few good links to help you get started are:
Learn 10 Functions in NI-DAQmx and Handle 80 Percent of Your Data Acquisition Applications
Getting Started with NI-DAQmx: Main PageI hope all of this helps!
Best Regards,
David L.
Systems Engineering
National Instruments

How necessary is an official NI Calibration or any DAQ hardware calibration?

How much can a USB DAQ like a 6218 or a 6210 really drift in terms of it's analog voltage read over time? Is this even a thing? As long as I feed it 5V and read 5V with little drift over time, can I assume it is "calibrated"? What will NI do differently?

labview12110 wrote:
I'm confused abou that, i mean it just reads voltage, do daqs fall out of calibration ever? They aren't exactly a sensor in the traditional sense...What component would degrade in performance over time in a daq?
If you do a measurement, it's for naugth unless you don't know the uncertaincy. Almost all DAQ devices use an internal voltage reference in conjuction with a ADC and signal conditioning. If any of these blocks change due to temp, overvoltage, shock, time, dirt on the PCB, radiation, chemical&physical processes, .... you can't trust the number you read.
The manufactor of the metering device (hopefully) has the experience how to choose, select, place and handle the components and after some testing he declares the specifications and the intervall and procedure how to check it. However statistics can beat and bite you, so the only way to be shure is regular calibration.
After some time and multiple calibrations you can start to trust your device.
Since I do my own calibrations (the standards I can access have less uncertaincy than most other cal labs ) I can tell you that I found NI devices out of cal spec that needed justification to meet their spec for the next periode.
In modern DAQs there are usually only two 'screws' you can access and 'adjust' : The internal reference timebase and the value of the internal reference.
While the crystal of the timebase can be trimmed (varicap and DAC) or not (in cheap devices) , the internal voltage reference value is internally measured,calculated and stored by applying a known voltage. Details are found in the calibration documentation.
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 ǝɥʇ'

NI DAQ Hardware Protection

Similar Messages

Maybe you are looking for