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

Similar Messages

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

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]
>

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?

Installing labview before DAQ card?

Hi,
We've just bought LabView 8.2 and a new DAQ card, PCI 6281 M series...
What I was wondering was whether there is any order in which these need to be installed. At the moment there is no pre-existing version of LabView or DAQ Software on the computer.
I have just read that the drivers that came with the DAQ card need to be installed before the card is inserted into the PC, but am not sure if LabView is supposed to be installed before or after the card or if it even makes any difference.
Thanks,
Harry

Thanks!!

Problems installing FP v4.1 with LabVIEW v6.1 application

We have a LabVIEW v6.1 application that interfaces to a FieldPoint FP-1000 Network Module for its I/O. We have been distributing it to customers for about 18 months with the FieldPoint v4.0.1 driver - no problems other than some difficulty getting the Watchdog Timer setup properly via MAX.
The latest purchase of FieldPoint hardware came with FieldPoint v4.1 driver. There are three issues that have arisen with the advent of FP v4.1.
1.) There occurs several (identical) warning messages during the FP v4.1 installation on Windows XP SP2 (the exact number depends on the selection of features to install). The message is "Error 1931" and it says that Windows stopped the installer from updating the stdole2.tlb file. It suggests that we update the OS, which has been done, but the messages continue.
Question: is it critical that the stdole2.tlb in the FP v4.1 distribution be installed, or is this an error with no consequences?
2.) When installing FP v4.1, we select LabVIEW v6.1 support, but disable the Real-Time v6.1 Support and the Examples. We also disable the LabVIEW v7.0 and v7.1 Support and the LabWindows/CVI Support. We keep the Documentation and MAX features. We have gone through the install/uninstall cycle several times and each time when uninstalling the list of features includes LabVIEW v7.0 Support - not v6.1.
Question: does this indicate that the installer is erroneously installing v7.0 support and omitting the selected v6.1 Support? Or is this just an error in what is displayed by the uninstaller?
3.) After FP v4.1 is installed (with LabVIEW v6.1 Support selected) our LabVIEW v6.1 application runs but fails to communicate with the FP-1000 Network Module. Upon quiting the application, there is an error message stating that the FP.Open.vi failed to run because the FieldPoint Server .dll was not found (no filename for the server- just ".dll").
Question: Is this an issue of the installer not putting the proper FP Server .dll file on the computer (see question 2) or is this a matter of compatibility (do I need to install FP v4.1 on the development computer and remake my application)? Something is wrong here, FP v4.1 doesn't support a LabVIEW v6.1 application that runs fine under FP v4.0.1. Do I need to install the LabVIEW v7.x Support in addition to the v6.1 Support?

Hi lkj,
There has been few reported problem with installing FP4.1 in LabView 6.1, but none of them are similar to what you are experiencing. According to the 4.1 driver documentation certain vis from this driver version cannot be installed and used in LabView 6.1. What I would suggest is to uninstall the current driver and revert back to the ver. 4.0.1 since we know for sure it works in the LabView 6.1 environment. If you you'd like to use the 4.1 driver, then if would suggest upgrading to LabView 7.0 or 7.1.
Regards,
Natasa

Would like to monitor and control a labview application with a hand held device.

Would like to monitor and control a labview application with a hand held device.
Would like to use a palm or ipac on a local area network or communicate directly with the PC running windows.

LabVIEW doesn't run on a hand held device. But, check out these documents:
Is it Possible to Use Remote Front Panels to Control a LabVIEW VI Remotely Using my PDA?
"What OS is recommended for LabVIEW to run on a PDA?"

Cannot build application with labview 7.0

I had built application previously using labview 6.X while some of the V.I. are without block diagrams, but I couldn't do that any more with labview 7.0 as a error will be prompted, why is this happening & are there difference in application builder between labview 7.0 and previous version? Must I load those V.I. without block diagrams dynamically now ?

Unfortunately it is impossible to build application with newer version with VIs without block diagrams, which saved in oldest version.
from ni web site:
"National Instruments does not recommend saving VIs without block diagrams because LabVIEW needs the block diagram to recompile the VI after an upgrade. When you upgrade LabVIEW, you must find a version of the VI that includes its block diagram to recompile it. Such a version did exist before the block diagram was removed because it is impossible to create a new VI without a block diagram."
"Based on that information, it should be clear that once a VI is saved without diagrams:
You cannot open or run the VI on any other version of LabVIEW, older or newer."
More information:
http://digit
al.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/00a6bacda1c01a0786256b60006163e7?OpenDocument
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/28c4cb0cf83e1a1d862566e2007a2a9c?OpenDocument
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/fee732f4b1541b9586256bf0006a78ca?OpenDocument
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/0649a3350de20aa186256d91007b3d61?OpenDocument

LabVIEW application with cameras

Hello,
I have build an application with LabVIEW and I am using two GigE cameras. In NI MAX, I set the names cam0 and cam1 respectively.
Everything is working properly in the computer where I have build the application, when I execute it but when I execute the application in a different computer (that doesnt have LabVIEW installed, just VAS, Vision RTE and RTE), the application executes but the cameras dont show images.
It seems that the application doenst recognize the name and doesnt open the cameras...(I have set the same name as in the other computer: cam0 and cam1)
Any help?
Thank you.

If you can see the images in MAX but not your app, that points to an app error.
What happens when you run the EXE on the development computer? Do you get images?
Surely one of the aquisition VIs or something is throwing an error. Are you correctly passing errors around? Maybe there's an error opening a config file you forgot to put on your RTE computer.
Also, when you say you can't see the images, are they black or gray or what?

GPIB Labview NI-DAQ, Micro 1401 and Windows 7

Does anyone know if:
a) GPIB, Labview/NI-DAQ is essential for running a Micro1401 unit?
b) If it is, will it work in Windows 7 please?
Thanks loads!!!!!
Jo

If you mean this then I cannot see any easy way of making it run in LabVIEW... unless you have an older version of the Micro1401 that has a GPIB interface?
Mark B
===If this fixes your problem, mark as solution!===

Want to learn LabVIEW, or DAQ?

Want to learn LabVIEW, or data acquisition with LabVIEW?
I�ve finished the first draft of my book for Prentice Hall, �LabVIEW
For Data Acquisition�, and I need a few people who are new to LabVIEW
to proofread it. If interested, this would be a good way for you to
learn
(1) LabVIEW in general (the first third of the book),
(2) data acquisition with LabVIEW (the rest of the book), or
(3) both (the whole book).
The book is currently about 340 pages in Microsoft Word, which would be
about 500 pages as a book. It has plenty of pictures.
If you feel you have time to proofread my book, or either part of it,
before the end of July, please email me at:
[email protected]
I will want feedback concerning errors or hard-to-u
nderstand parts.
You�ll need to get LabVIEW 6.0, still in beta, but I should be able to
arrange that. For the data acquisition part of the book (the last 2/3),
you�ll also want any NI data acquisition device capable of analog input
and digital I/O, and preferably analog out.
Bruce Mihura
Sent via Deja.com http://www.deja.com/
Before you buy.

This has tutorials http://www.apple.com/findouthow/mac/

Problems building a stand alone application with LV 8.6.1.

I'm having problems building a stand alone application with LV8.6.1. I'm using a USB- 6008 DAQ and USB-6501 Digital device in the application. I already have an simple executable on the machine so the Run time Engine is already installed. For the USB DAQ device, I assume I need to include the DAQmx8.8 as one of the installers. When I attempt to build the application, I'm prompted for several disk, one being a distribuition disk 1. I have the installation disk for the developer package. I did not see a distribuiton disk as one of the installation disks. When I insert disk 1 I get an error that another application is trying to run. Could someone tell me which installers I need to include and where do I find the "distributor" disk.
Thank you,

are you building installer for the first time on this PC?...It usually asks for the drivers CDs and some toolkits if required.
you just need to use drivers CDs (comes with LabVIEW) from which you installed on this PC. If you have ever upgraded drivers, then you have to use the latest CDs only.......
another issue may be ...when u insert the driver disk, it has autorun, it will launch drivers installation wizard....close that and then try to build distribution.........
Message Edited by Anil Reddy on 09-25-2009 01:22 PM
Anil Punnam
CLD
LV 2012, TestStand 4.2..........

Advantages of using labview in embedded application when compared to c ?

Hello all,
I am looking to develop embedded application with help of labview programming
Started with Lm3s8962 evaluation board.
So i would like to know
1 Advantages of using labview in embedded application when compared to c ?
2 Can we deploy the code in any kind of controller by writting drivers for it ?

hello, the LM3S8962 microcontroller is a good sispositivos for developing applications of medium complexity, according to your questions:
1. if you work applications with embedded systems will save labview time in prototyping, we know that if you work with a company specific microcontroller, you must learn the language with which you are working Asm, Basic, C, then if you change hardware again start adapting your code in the libraries of the new compiler. Labview does not happen.
2. Labview only works with some microcontroller manufacturers and specific models.
Atom
Certified LabVIEW Associate Developer

Labview NI DAQ application with no daq hardware

Similar Messages

Maybe you are looking for