Unable to run vi with labview run time engine

Hi All,
I have a VI that controls and reads from an NI PXI Spectrum Analyser (5600). The VI works perfectly as expected, I can make a project of it and create a runtime application and installation with no problems, using Labview 8.6.
When I make a call to it from Test Stand 4.1 it works lovely.
When I change the VI adaptor in Test Stand 4.1 from development to use the LV Run Time engine 8.6 it fails to work, Test Stand gives the following dialogue (see attached).
I have uninstalled all older versions of Labview as I've had similair issues before, I've mass compiled everything I think is associated with this VI.
I don't really understand! And am tearing my hair out.
The only idea I have is that perhaps there is something in one of the 5 DLLs that is causing a problem or the NI_AALBase.lvlib, NIAALPro.lvlib or NI_PtbyPt.lvlib librarys that are password locked and I presume don't get mass compiled.
I have attached the problemVI.lvproj.
Thanks for any advice or help.
Matt
Attachments:
problem VI.lvproj ‏41 KB
teststand.JPG ‏43 KB

Matt,
it sounds like you are having older versions of toolkit/driver VIs in your application. In developement environment, this works since the dev-system is capable to recompile older VIs just during loading and therefor not having issues with older versions.
Running the VIs using the Runtime Engine, recompilation is not possible. Because every VI knows "its version", the VI will not be executable unless the RTE version matches the VI's. If the VI is older (or newer, doesn't matter), the observed error occurs.
Please make sure that you have current versions of drivers and toolkits installed in your LV environment instead of simply copy them from older versions of LV (this would be the common source for such issues).
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Similar Messages

Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

Hi,
My TestStand sequence calls a VI which includes a call to "system exec.vi". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.
Is there any way to use "system exec.vi" in a VI which is called in TestStand with LabVIEW run-time ?
Thanks,
Alex
Solved!
Go to Solution.

Hi Alex,
In you case, you are getting a -18002 error.
The reason is explained in the following link:
-18002 Errors in TestStand
http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument
Please have a look at the 2nd reason. This is your case.
Hope it helps,
Regrads
Julien De Freitas / Applications Engineer / Certified LabVIEW Developer (CLD)
National Instruments Switzerland

UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71

UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71 REQUIRES A VERSION 7.1 (OR COMPATIBLE) LABVIEW RUN-TIME ENGINE。PLEASE CONTACT THE VENDOR OF LVBROKERAUX71 TO CORRECT THIS PROBLEM
Uninstalled DAQ and reinstalled. MAX still throws an error.
Any Isead besides uninstalling 3/4 of my software?
Merry Christmas!
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

To clean up your system, you will need to uninstall the LabVIEW 7.1 run-time engine, and the "LVBroker," and the "LVBrokerAux71" components using the MSI Blast utility. To obtain this utility, please create a service request for phone or e-mail support, and contact one of our Applications Engineers about this issue. Thank you!

How come you can not use more than 126GB of a 1.5TB diskdrive with LabVIEW Real Time?

How come you can not use more than 126GB of a 1.5TB diskdrive with LabVIEW Real Time?
This is only 8.3% of the available disk drive space!
http://digital.ni.com/public.nsf/allkb/E7E2F5657B6026358625750B007201A6?OpenDocument
National Instrument's solution is either reformat you drive to less than 126GB or replace the drive with one less than that size.
Please NI, tell me you are going to fix your LabVIEW Real Time soon, and that we won't have to wait for LabVIEW RT 9.2.1 in 2011 for this one to be fixed.
http://upload.wikimedia.org/wikipedia/commons/9/90/Hard_drive_capacity_over_time.svg
Drives as large as 126GB or more have been around since about mid 2002. That's about 7 Years now and LabVIEW Real Time STILL can't use drives larger that 126GB! Please NI. Do something.
We deserve fixes to the old versions of LabVIEW RT. How about updates to LabVIEW RT. Such as 7.0.2, 7.1.2, 7.6.2, 8.0.2, 8.2.2, 8.6.2.
We don't need new features or versions of LabVIEW RT such as 9.0 until we have some of bugs fixed in the existing versions.
Kevin.
Message Edited by kmcdevitt on 05-29-2009 03:39 PM
Solved!
Go to Solution.

Coq rouge wrote:
NI is not making the Real Time OS in house. I do not remember which firm that is making it. Anyway you are allowed to use a hard drive that has been partitioned. And 126GB is some space is it not? I remember Bill Gates declared one time that 640Kb ram should be more than enough for any PC application also in the future
Coq Rouge (formerly t06afre),
The RealTime OS is an NI Product that is purchased from NI.
NI may or may not outsource design, developement, or manufacturing of the products that it sells under its own Company name.
For this reason I would be concerned if I were a PXI Embedded Controller designer/developer in the United States.
Yes, 126GB is some space. I see that there are now 2TB drives available. 126GB would be 6.3% of a new 2TB drive. Should we all be happy with being able to use 6.3% of the available drive space. Moore's Law seams to be alive and well. Drives larger than 126GB have been readily available for 5 or 6 Years. This should not be a surprise to NI. Why don't they do something about it.
Thanks for the trivia on Bill Gates. I must have missed that one since I don't try to keep up with Microsoft. I believe that he is a wonderful person and he and his family are doing wonders for the world in their "retirement". The world needs more like him.
What I do remember is Steve Jobs telling us that we would never need more that 128MB and that we would never to need to do anymore software development because everything was already in the "ToolBox".
McKevin.

Can I use third party DAQ boards with Labview real time?

I have an Adlink DAQ 2010 card that I curently use with labview. Will this card also work with Labview real time? What requironments are there for 3rd party cards to work with Labview real time?
Thanks!

Hello George,
Here is a great link for you to take a look at: Can I Use a Third-Party Device with LabVIEW RT?
Have a great day,
NathanT

System error 988 whlie loading the LabView eun-time engine (C:\Program file\....\\lvrt.dll)

I am trying to use NI devices with Lazarus (there is no pascal section, so I post here).
When I try to run my application:
DAQmxBaseCreateTask('TaskHandle', TaskHandle);
DAQmxBaseCreateAIVoltageChan(taskHandle,'Dev1/ai0','',DAQmx_Val_Cfg_Default,-10.0,10.0,DAQmx_Val_Volts,'');
I get the following error message:
„System error 988 while loading the LabView eun-time engine (C:\Program file\....\\lvrt.dll)
nidaqmxbaselv requires a version 2010 (or compatible) LabView run-time engine. Please contact the vendor of nidaqmxbaselv to correct this problem.“
I installed LabView run-time engine 2012, but I still get the same error.
Then I tried to install LabView run-time engine 2010- the same result.
I removed LabView run-time engine 2012- same result.
I tried to install LabView run-time engine 2010 again (since I did not see it in the add/remove list)- then I noticed, that the installer shows „A newer version is already installed".
What shall I do?

Hi,
   Can I ask the same question too?
   I am using
   Windows 7 sp1 x64
   Visual Studio 2010 pro
   NI USB-6009
   ni-daqmx base 3.4.5
I created a empty win-32 console project and putted the ANSI C Example program: acquireNScans.c with the include file and lib file of nidaqmxbase in the same folder. I added this line on the top of the source code #pragma comment(lib,"nidaqmxbase.lib"), built without any error. When I tried to run it, I got this same message.
  I tried changing to shared dll mfc and delaying linking lvrt.dll, but did not work.
  Looking forward to your reply.
all the best.

How do I talk to 1-Wire devices with LabVIEW Real-Time?

Hello, I'm trying to use LabVIEW Real-Time to talk to some older 1-Wire devices that my company has previously communicated with using C code. We are currently developing on a cRIO and are trying to use a Dallas Semiconductor 2480 serial port device to talk to some iButtons and a secure SHA 1-Wire device. I have run into a few problems where the 1-Wire device stops communicating and just repeats the data sent to it. I was wondering if anyone has successfully created any VI's to talk with 1-Wire devices via the serial port that do NOT use any kind of Java or .NET or Windows based device drivers supplied by Dallas Semi. A last resort would be that we keep the C code and place it in a block in LabVIEW and run it as is but I would prefer to have some LabVIEW-native code. Any help would be greatly appreciated. Thanks.

Brian_T,
Thanks for that link about compiling a shared library for use on a VxWorks cRIO. The only thing they mention that I don't understand is this bit:
"GNU toolchain distributed with Wind River VxWorks"
I have been unable to locate a compiler for VxWorks so I am assuming that is located in this GNU toolchain thing? Does that come with the cRIO? I think I noticed a VxWorks C compiler somewhere else online but we're talking a totally different product I would have to purchase, assuming it would even work. I guess once the stub and the shared library are all good to go, I just call the C functions in the shared library and when it comes time to talk to the serial port, just slap a VISA Read/Write VI on the block diagram. I've been using a cRIO and COM1 access for some time now so I do understand at least that much. Let me know how to get ahold of this "toolchain" thing. Thanks.

Is Ardence RTX required when I use PCI-7831R with labview real-time module for RTX target

I am new in the labview real-time field. I want to use labview real-time module for RTX target on only one desktop. My card is PCI-78331R. Is Ardence RTX necessary? Why I cannot find my card in the MAX after I configured the RTX?
Thank you very much.

Hi Ziaozhongda,
You must have the RTX runtime engine installed before the LabVIEW Real-Time RTX module will install. Additionally, you should follow the instructions in the "Using the NI PCI-7831R with the LabVIEW Real-Time Module for RTX" section of Getting Started with the NI 7831R (page 8).
Please see Configuring Hardware for Use with RTX.
Also useful is "How Can I Validate That My PC Will Run RTX?

RMAN backups running slow with Catalog , Running fine using control file.

I am facing a weird scenario
RMAN backups are running fine with Control file but are failing using Catalog
There are other databases configured on the same catalog and they are running fine leaves us to suspect this is issue with Database.
Can you please suggest what need to be checked in such scenario
DB: 11.2.0.2
OS: Aix 6.1
Catalog : 11.2.0.2

Hi,
Basically its not only with backups, simple list incarnation also taking a lot of timeDo sql tracing on your catalog session and target db session while running the 'list incarnation' command for your problem dbs and a normal dbs.
Regards,
Tycho

How can i access remote front panel in RT with LabVIEW run time engine in client PC

Hi to all,
I have developed the RT application with cRIO 9075 integrated chassis. And i have access its remote front panel in client PC. Now i want to access the remote panel in the client PC without having LabVIEW runtime engine. If i connect the remote panel with that client, it shows only the vi border. i doesn't downloads the front panel.
How Can i access its remote front panel without LabVIEW runtime engine in the client PC?

You cannot view a remote front panel without the LabVIEW runtime - the LabVIEW runtime is what makes the remote front panel possible. What you will want to do instead is likely create a Web Service that you can access from a remote PC without requiring the LabVIEW runtime. However, this will require you to develop a web-based HTML or similar UI to interact with the VIs running on your system - NI hasn't yet created a way to export a LabVIEW front panel as an HTML'ish page.
-Danny

Running Multisim with Labview

Hey,
I am trying to convert a series of student labs for a dynamic systems course to run on a newer, better setup. Previously, the lab I am working on took input from a sensor, fed that input through an analog circuit, and fed the output from that circuit into a Labview VI. My question is, can that be done using a Multisim simulation instead of a physical circuit? I have found volumes regarding running Labview VIs in Multisim, but nothing regarding a VI taking input from a Multisim circuit. If this can be done, what configuration would you suggest?

bjw5,
It is likely due to the fact that some of the vi.lib or DAQ driver libraries that you need to link into the VI are missing in the build of your Multisim LabVIEW .llb.   If Multisim cannot locate missing subVIs (from vi.lib or elsewhere) Multisim will not load the LabVIEW VIs that you have built.   Sometimes you need to include these vi.lib subVIs (usually contained in a LabVIEW library - lvlib) in the project build (by default all vi.lib functions are excluded).   When Multisim loads, it loads in the appropriate base level LabVIEW functionality only - this includes most LabVIEW functions, basic math, etc - however any advanced measurments or additional toolkits or drivers need to be included in the .llb build or the support folder directly.
How do you know? In your LabVIEW project, if you click on the 'Dependencies' +/- twisty you will see any subVIs or .lvlibs which contain subVIs that may be used in your Multisim VI application ...
Here is a sampling of a recent project that I used that included some advanced measurement VIs in LabVIEW.   I believe the only ones included by default in Multisim are the 'Base' lvlibs (which does include most of the LV functionality, but for my application advanced measurements were needed).
If you DO have any that say 'Pro' in the name or any hardware driver level functions or subVIs, you'll need to do one of two things:
1. Easiest method - Include all vi.libs in the Source Distribution under 'Additional Preferences'
Basically change this ....
to this...
Note that it will take some additional time to build (since when LabVIEW builds your llb it will search all of the lvlibs for VIs that it thinks are in your application and then remove the ones that are not)... but your VI should then run in Multisim...
2.   Advanced method -> explicitly add the subVIs or lvlibs to the top level project and make them 'always included' in the Source Distribution 'Source Files' options.
Here you can explicitely call the lvlibs to be included in your build and then take out functions you don't need (but you may not know what subVIs are used if they are embedded in lvlibs that you're not aware you are using (such as the case with Express VIs) ).   You also have to be careful since I have found out the hard way that menus within the lvlibs cannot be included in .llbs, so you have to exclude any menus folders within the lvlibs (you can include/exclude pieces of lvlibs by the way)...   Sometimes this can reduce the build time, but it can be a little trickier since you need to know which things to include/exclude.   If you are just beginning, use method #1 at first.
Ok thats they way it is with most Multisim VIs that I am familiar with but there may be some things that I am missing because you are using myDAQ...   I've requested that someone familiar with the myDAQ products on the academic team also reply to this thread.
Hope this helps and good luck!
Regards,
Pat Noonan

Set up Express just to run iPhones with Extreme running Computers?

For some reason I see no search feature so I appologize if this is common knowledge.
I want to run my Extreme on "n" but our iPhones won't work with that of course. I'd like to take my older Express and set it up just to run the iPhones. I hope I don't have to hard-wire it to the Extreme because I fear it might not reach to where I need it - but I'd like to try.
Would anyone know where I can find instruct on this? I can't find anything so far. Thank you.

Are you using one of the "n only" radio modes on your 802.11n AirPort Extreme Base Station's (AEBSn) wireless network? If not and using the default "802.11n (802.11b/g compatible)" your iPhone should have no trouble connecting to it.
On the other hand if you are trying to maintain an all "n" network with your AEBSn, then you basically have two choices with the 802.11b/g AirPort Express Base Station (AX):
1) As you eluded to, you would connect it directly to the AEBSn via Ethernet, and then, reconfigure the network as a "dual-band" network. In this configuration, the AX would be placed in bridge mode to allow the AEBSn to continue to provide both NAT & DHCP services for both networks. In addition, you would have two separate wireless networks, one for each type of wireless client, but since the AX is bridged, wireless clients on either network would be able to "see" each other.
2) Configure both the AEBSn & AX into a Wireless Distribution System. The advantage of this would be that you would connect the AX to the AEBSn wirelessly. The greatest disadvantage of this would be two-fold: 1) You would not be able to run a "n" network as a WDS only works in "g." 2) The overall bandwidth performance will be cut in half.

How can I create a Report with LabView Real-Time?

With conventional LabView, I can create Reports in HTML, for example to document Errors.
I need this feature in LabView Realtime. Is it possible?

It is possible, but you got to put a name to the file with an extension of three letters. i.e. errors.htm
Three letters on the extension is what the RT Operating system allows to use.
Then you will need to do an ftp to your RT machine and get the file and maybe change the extensions.
Not all the vis for Report generation can be used in the RT engine. The ones that use ACTIVE X will not work. i.e printting
Another way to generate reports and the most recommended is to use the host machine to generate the reports.
Regards,
Blasioz Valenzuela
National Instruments

Unable to empty trash with data from Time Machine Drive

Hi there,
Cause of the current issue:
I am hoping the experts can help me with this one. I have an external hard drive which is used for my Time Machine Backups. Recently there has been an error on the backup to this drive on occasion. This error only occurs when the system does the back up, and appears only periodically, never when I do the back up manually. One of the threads I read to solve this issue is to delete some older backup files from your time machine drive, and all is good. This worked for awhile.... but now a new problem:
New Problem:
I have been able to empty all of the trash save one particular set of folders. So the trash always appears with content.
The structure of the trash content appears as such...
Macintosh HD
+-Users
+--<username>
+---Library
+----FK6T0KGc9y4KBB <-- This changes each time I try to empty the trash.
The library folder always has the time/date of the last time I tried to empty the trash.
What I have tried:
1. I have tried to empty the trash Securely. No good.
2. I have tried the terminal command : sudo rm -rf ~/.Trash with no success
3. I have tried this terminal command : sudo rm -rf ~/.Trash/* with no success
4. I have tried just plain old Empty Trash. But I get the message "This operation cannot be completed because the item 'FK6T0KGc9y4KBB' is in use.
Any thoughts, recommendations?

Hey thanks for the help anyway VK.
I tried that command and no go either.
Last login: Fri Jul 25 08:13:39 on console
iMac:~ tmlohnes$ sudo rm -rf /Volumes/Time\ Machine\ Backups/.Trashes/501/*
Password:
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD/Users/tmlohnes/Library/8xMlmPGUHzilET: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD/Users/tmlohnes/Library: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD/Users/tmlohnes: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD/Users: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634: Directory not empty
iMac:~ tmlohnes$
I am wondering, would it make sense to try this same command if I were to do a safe boot?
What about formatting the external hard drive and starting fresh?

Can you use event case with labview real time?

I have a real time application I am putting together and until recentally have concentrated on getting the data acquisition working as expected.
I am using a PXI-8183 in a 1031 chassis.
I am now trying to add the functionality for setting up the system in the form of a GUI remote front panel that I connect to with a host laptop. I am connecting with the host as expected and it seems to be working well in that respect.
My problem is with event cases, operating in a while loop on the target. They just dont seem to want to trigger when i click on a button I have set an event for.
I have looked through the documentation and cant see any reference to issues with event cases on rt, but I feel I am missing something fundamental. Can anyone help?
Regards,
Barry

look here maybe:
http://digital.ni.com/public.nsf/allkb/42B70D2D0C4B568586256E2F0051441D
Harold Timmis
[email protected]
Orlando,Fl
*Kudos always welcome

Unable to run vi with labview run time engine

Similar Messages

Maybe you are looking for