Labview 6.0 run-time engine will not control BKPrecision power supply.

I created a test program in Labview 6.0 to control a BKPrecision power supply and Measurement computing DAQ in our test system. I am able to control both intsruments from my PC which has Labview loaded on it. I created an executable from the application builder tool for distribution. When i install the run-time engine and executable on a new PC (Labview not installed), i am unable to control the BKPrecision power supply. The BK power supply is connected to the serial COM port of the PC.
Do i need to install drivers that are not included in the executable build?
Do i need to install VXIpnp (VISA interactive control)?
thanks,
Tim
Solved!
Go to Solution.

tmann-
The API Drivers are often times for more specific Operating Systems than the others (Linux, Pharlap, etc.) and they are more easily accessible for programmers that want to (and have enough time to put up with the headaches ) of building speciality drivers off of ours. 99% of the time you just want the drivers that come up first when you type in your driver name (NI-VISA). As to versions, issues can crop up later from not using the exact same driver version but all the drivers are built off of each other (they hardly ever scrap an entire driver and start over) so the problems should be minor. Its up to you about switching. Unfortunately to downgrade version you have to completely uninstall the driver from Add/Remove Programs>>National Instruments Software>>Your driver and then reinstall the correct one. If you have time, I think it is well worth it to do it right the first time. Hope this is helpful!!
Grant H.
National Instruments
LabVIEW Product Marketing Manager

Similar Messages

LabVIEW VI with Report Generation Toolkit elements in a TestStand sequence does not run with a LabVIEW 8.5 Run-Time Engine

Hi all,
I am using LabVIEW 8.5.1 and TestStand 4.1. I have done a TestStand sequence with a VI in it, which uses Report Generation Toolkit elements. On my machine I am using LabVIEW and TestStand with a Development System license. On the other machine I am using TestStand with a Base Deployment license and I have chosen the LabVIEW 8.5 Run-Time Engine in the Adapter Configuration. Everything is running well except of this VI with Report Generation Toolkit elements. The error message is showing that the VI is not executable. It works well only after I have installed LabVIEW with an Evaluation license and chosen LabVIEW 8.5 Development System in the Adapter Configuration.
I have found other posts and a document in the KnowledgeBase with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument But I am not using EXE files in my sequence, so I don't know how to solve mine. Anybody has an idea?
Solved!
Go to Solution.

Hello guys,
thank you very much for your answers!
@Ruediger:
I tried to follow the instruction for Method 2 in the mentioned document: http://digital.ni.com/public.nsf/allkb/F3DC40A6E3F3B25B862570AD005D1D3D?OpenDocument, but the steps on my machine are different starting from step 4. After I click "Continue..." in step 3, I dont get a window, the system just makes a new folder with the same VI.
To be honest, I am new to LabVIEW and have some difficulties at this time. What I understood from your reply is, that I need to make a LLB-File, where the files from Report Generation Toolkit are in!?
@GovBob:
I was following the instruction in the document: http://digital.ni.com/public.nsf/allkb/9E00E7EFE0635E678625734600779EFE, but it wasnt working. Can you please tell me how I can check if the VI Server is installed and running on the machine?
I am using LabVIEW 8.5.1 and TestStand 4.1 on my machine, on the deploy machine there is TestStand 4.1.1. The version of my Report Generation Toolkit is 1.1.2.
Kind regards, Roman

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

LabVIEW 8.0 Run Time Engine

Hi,
I've a question about LabVIEW 8.0 run time engine.
I installed "LabVIEW_8.0_Runtime_Engine" from the NI website, but NI software in Add/Remove Programs does not list LabVIEW 8.0 Runtime Engine. However, LV 7.0 and 7.1.1 run time engines are listed in there.
Did anyone notice this?
I also have installed TestStand 3.5 on the same computer.
When I run an executable created in LabVIEW 8.0, I get the error message:
"VI version is too early to convert to the current LabVIEW version"
Comments/suggestions are appreciated.
Thanks.

CarlaU wrote:
The first thing that I would check is to go into Measurement and Automation Explorer (MAX) and click on the Software Tab. I would then check to see which version of the LabVIEW RTE shows up (if any). In theory, if the RTE shows up in MAX, then it should show up in Add or Remove Programs under National Instruments Software (highlight this and click Change....this should pull up a list of all NI products on your computer).
It's in MAX, but not Add/Remove Programs>NI
CarlaU wrote:
If it doesn't show up there, then there are two other things that can be done. The first one involves modifying the Windows Registry. There are a great KnowledgeBase article that discusses how to do this in order to remove the driver.
Nope - there's nothing to do with the RTE there either.
CarlaU wrote:
The second idea is to use a utility we have that I cannot post on the forum. If you create a service request via email or phone then we would be able to help you get the older versions fully uninstalled. You can create a service request at www.ni.com/ask. I hope this helps!
Thanks Carla - I'll try that avenue.
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

LabVIEW 8.0 Run-Time engine & shared variables

Has LabVIEW 8.0 Run-Time Engine the shared variable's support, I wonder?
The thing is that .exe with globals/locals runs alright, but beeing replaced with shared variables it refuses to run.
What's wrong? May be need in library(s) absend?
Thanks.

You can use the Shared Variable in the Run-Time Engine (you do not need DSC).
Can you be more specific about what happens when it refuses to run? Are you seeing an error message?
If you are using Network-Published shared variables, they need to be deployed before you run the application. You can either deploy them manually with the project, or your application can programmatically deploy them. You can find some more information about this in the LabVIEW Help under "Shared Variables and Stand-Alone Applications or Shared Libraries" (follow this link and scroll down to the bottom):
http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/project_variables/
-Chris

Why is VI not executable using Labview 7.1 Run-Time Engine?

Hi,
In our Teststand sequence, we have a Labview Action step which is returning an error: "The VI is not executable", along with the error code: -18002.
This error occurs on a Production PC using the L.V. 7.1 Run-Time Engine.
I'm aware of Mass Compiling to ensure all the VI's are the correct version, but this has not resolved the problem.
The software was installed on the production PC using a Teststand created installer, with the Labview Adapter set
correctly to the Run-Time Engine, i.e. not trying to open the Labview Developer Server to execute the step at run time.
Because it's the 1st Labview module to be executed, I added another similar step to run beforehand, i.e. the new simple
Labview code ran first. This executed correctly, but then the next step caused the error above.
The small number of associated sub-vi's are on the target PC, and have been mass compiled.
I've had -18002 errors before, but this is one I cannot cure.
All suggestions gratefully received.
Gary.

Hi Guys,
Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
Best wishes,
Mark
Applications Engineer
National Instruments

Can LabVIEW Run-Time Engine 7.0 control LabVIEW 6.1 VIs?

I'm attempting to remotely control a LabVIEW 6.1 example VI through the browser plugin on another system. On that other system, can I use LabVIEW Run-Time Engine 7.0? Or do I need 6.1?

Never mind, I should have read the RTE 7.0 information first. I need LabVIEW Run-Time Engine 6.1 to run LabVIEW 6.1 VIs.

Uninstall LabVIEW but leave run-time engine and DAQmx

Hoping there is an easier way to do this, basicall we are developing software on a customers computer that we buy and will eventually ship to them. However we can't ship them LabVIEW so we make an executable and just keep the run time, DAQmx and MAX. Is there anyway to do this easier than uninstalling LabVIEW and reinstalling everything else?
Windows 7
LV2013

Under Windows, try going to Control Panel | Programs and Features and find National Instruments Software. You might be able to select all except the run-time, DAQmx and MAX, then select uninstall. If not, then perhaps consider just making a full installer for your LabVIEW executable solution, this will clearly install only the necessary components for your code to work (if it's LabVIEW 2013).
Thoric (CLA, CLED, CTD and LabVIEW Champion)

G5 iMac Will Not Turn On - Power Supply Diagnosis?

My A1145 20" iSight PPC G5 iMac will not turn on - it doesn't respond to the power button. It had been shut down for a few days, I turned on the power and it booted up as normal, the desktop appeared and I was about to open the web browser when it suddenly went dead; the screen immediately turned off with no warning or noise. There is no fan or disk noise coming from it when the power lead is plugged in, just a very, very faint electronic hum from inside.
From reading various webpages, it seems possible that the power supply could have failed. Is there a simple way that I can diagnose this before deciding whether to attempt to replace it myself or not? I understand that there should be some diagnostic LEDs which could help identify a problem - I've removed the surround from the iMac and peeled back the black EMI film below the display but I'm not sure for what or where I should be looking (they seem to be easier to find on the 17" models).
Whilst I know a repair might not be cost-effective on such an old machine, I have 220GB of photographs, documents and music on it - none of which is backed-up - so I am very keen to get it working and backed-up as soon as possible.
Could anyone suggest how to diagnose the problem?

Hi there:
My experience with Macintosh computers has not included the G5 iMac even though I almost got one to replace a failed-under-AppleCare iMac G4 17" 1.25GHz after three/four major failures and no local support.
...So, I think you may be able to pull the hard disk drive out of that computer and see if an external enclosure could allow you access those files IF the drive spins up at all. Sometimes odd things happen, and the G5 iMac had some history of capacitor and other failures that could be a problem. I see there are a few free information guides here that may be helpful: http://www.ifixit.com/Device/iMac_G5
If the battery on the logic board was dead, but the computer kept in running condition by leaving it plugged in, once the computer was left unplugged for a time then the device may fail to start. There is a way to reset the power management chip (different names for same idea as technology moved forward) and that could help in the process of troubleshooting most power related issues in the PPC Macs of later G3/G4/G5 design.
There are troubleshooting items of interest in here http://www.apple.com/support/imac/g5/ ie: what to do when your computer won't turn on...
Sorry to not be of direct help in this matter.
Good luck & happy computing!

Run time engine compatibility

I want to install a executable developped with LabVIEW 2009 and its run-time engine on a PC with LabVIEW 7.1. The executable is used to control an instrument by GPIB. The project in LabVIEW 7.1 use a digital IO board (PCI-DIO-32HS) and also use the GPIB board.
I just want to make sure that installing the executable and LV2009 run-time engine will not cause any malfunction in the LabVIEW 7.1 VIs.
Thanks
Ben64

Should be no problem. LV 7.1 and 7.1.1 had some engine conflicts between them but I think you're safe with any 2009 executable. If 2009 corupts 7.1 I'm sure someone would have seen it by now.
Using LabVIEW: 7.1.1, 8.5.1 & 2013

Executable not working - Looking for LabVIEW Run-Time Engine

This has been one of those days.
I'm trying to create my .exe file to place onto another computer. I've done this before with success. But that was then and this is now.
I believe I have all the files I need in my LLB, and I believe I did my application distribution correctly and I believe I built the DLL correctly. But when I took the resulting .exe file and placed it on another computer and attempted to run it, it gave me the error message: "Unable to locate LabVIEW Run-Time Engine. Program requires a version 7.1 (or compatible) LabVIEW Run-Time engine. You should have already realized this, you moron."
Anyone have any idea where I went wrong or what step I might have missed? This has been a crazy, non-stop, massive brain fart of a day and I can't seem to remember what I'm missing here.
Amateur programmer for over 10 years!

Hi.
Whenever you want to use executables or .dll's created with LabVIEW you must make sure that the LabVIEW runtime engine of the SAME version as the LabVIEW version used to create the files, is installed in the target computer.
There are basically 2 ways to get the run-time engine installed on a computer:
1. (the one I prefer): Download the correct version of the LabVIEW run-time engine installer from www.ni.com/downloads, or more specifically from
http://digital.ni.com/softlib.nsf/websearch/369618104E25B08E86256F54006A4E2F?opendocument&node=132050_US
for the latest one. Once you have the installer for the run-time engine, just install it in the target computer. I prefer this option because the run-time engine is installed independently, so if you then uninstall your program, the run-time engine remains.
2. Create an installer for your program that includes the run-time engine. To include the run-time engine, when you are creating your application, go to the "installer settings" tab, click on "Advanced" and make sure there is a checkmark on "include LabVIEW run-time engine". This way when you install your program in the target computer, the run-time engine will also be installed.
Just as a note, any computer with LabVIEW on it, will also have the run-time engine.
Good luck.
Alejandro

Will hardware drivers work with the run-time engine or only a full version of Labview?

Hello.
I'm trying to get a quatech I/O card to work. The instructions with the drivers we were given state "you must have labview installed before installing these drivers".
A program I wrote on my machine works fine with those drivers and does toggle outputs on the card, but when I build it into an executable on our test unit (doesn't have a full version of Labview, just the Run-Time engine) the card doesn't work.
We installed the run-time engine on the unit, then the drivers.
I guess my question is: Do most drivers work with both the full version of Labview and the run-time engine? Or do I need to somehow 'convert' these drivers to work with the run-time engine?
Th
anks for your help!
Dave Neumann
[email protected]

Dave:
I can't determine which dll is required but if there are more than one that
shipped with the quatech I/O card try to placing one dll at a time in the
same directory as the exe so that you can determine which one is the
required one. If that doesn't do it then it may need more than jsut one of
the dlls so placing all that came with the quatech I/O card s/w driver
package in the same directory as the exe should do the trick.
Best of luck.
-Tom
"Neumannium" wrote in message
news:[email protected]..
> Tom,
>
> Thanks for your reply. One of the problems I'm having is figuring out
> which .dll I would need to include (I'm not a software guy).
>
> Would the .dll your speaking of be different th
an the one which is
> installed with the drivers? I'm looking at a .dll that is installed
> when you install the labview drivers for this card, but the run-time
> engine still doesn't want to get the card to work. (The file installed
> when I install the drivers is called 'daqlv32.dll' and I don't know
> how to find any other .dll's I might need)
>
> Actually, it appears the card 'is' being seen by the run-time engine,
> but I'm getting impulses rather than distinct changes of state.
>
> Anyway, thanks for the help.
>
> Dave Neumann
> [email protected]

Install labview 6.1 (or compatible) run-time engine with labview 2011

I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
Solved!
Go to Solution.

Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
So I guess my question is..is there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

Labview 2010 run-time engine silent install

I am having trouble with installing the run-time engine for LabVIEW 2010 with the silent option.
I am using the minimum version of the run-time engine.
Before I used the LV7 run-time engine. Then I could install it silently using LVRunTimeEng.exe /qb!
In LabVIEW 2010 the run-time engine is no longer a single file but a directory that contains the installation files. There are two files that can be used to launch the installer Setup.exe and LV2010runtime.msi.
Setup.exe does not seem to accept any command-line arguments. LV2010runtime.msi however accepts the command-line arguments and can be installed silently.
Now my problem is that I am building a windows installer using a third party application and it is only possible to launch exe files after the installation completes. Before I could launch the LVRunTimeEng.exe /qb! to install the labview 7 run-time engine but now when I have upgraded to labview 2010 I cannot do the same for Setup.exe.
My question is if it is possible to use the Setup.exe file to install the Labview 2010 run-time engine (minumum) silently?

Setup.exe runs a number of other .exe files during its execution. This article looks like it will allow you to run setup.exe silently by supressing all messages and windows:
http://digital.ni.com/public.nsf/allkb/878FC4C374013ADF8625733D00688F67

Is Labview Run-Time engine 2009 SP1 compatible with Windows 8

I potentially need to install a Labview executable and Run-time engine 2009 on a Windows 8 OS. From looking at the run-time engine support, it only looks like it only shows windows 7 down to XP. Does anyone have any experience using Runtime 2009 on Windows 8?

Hi Awhite144,
The first version of LabVIEW to officially support Windows 8 is LabVIEW 2012 SP1. That being said, I would expect LabVIEW 2009 to work fine on Windows 8, and if you run into any trouble, feel free to post it here. LabVIEW 2012 SP1 installs a number of older LabVIEW run-time engines (including LabVIEW 2009), so it will install on Windows 8.
I have not personally used LabVIEW 2009 on Windows 8, maybe if someone else has experience with it they can weigh in, but I expect it to work.
As an important consideration, I assume you are talking about the full version of Windows 8, not Windows 8 RT.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

Labview 6.0 run-time engine will not control BKPrecision power supply.

Similar Messages

Maybe you are looking for