Control where a LabVIEW executable write it's Settings Configuration file

Is there any way to control which directory a LabVIEW executable writes it's configuration settings file to? I am using version 7.1.

I believe the INI file must be in the same directory as the executable. You can use the keys found in the LabVIEW.ini file and they will apply to your executable without any special programming on your part. That being said, you can always create a custom settings file or files anywhere you like to store configuration information specific to your application.
If we could specify some other path for the executable settings file, it would probably hurt more than help in the long run. The same directory as the executable is the only one whose existance you can be sure of..... or of whose existance you can be sure.
Dan Press
PrimeTest Corp.
www.primetest.com

Similar Messages

Read / Write a MAX .daq configuration file?

How can I read or write a .daq configuration file programmatically ?(channel names, range, units, etc.)
And/Or:
Does anyone know the internal structure of a .daq file? Is it documented?
Thanks.
MichelC.

Michel,
The .daq file, where all the MAX information gets stored, is in binary format. You will have a hard time decoding it LabVIEW.
However, you can use some DAQ VIs to get this information.
Under Data Acquisition>>Calibration and Configuration>>DAQ Channel Utilities palette, use the following VIs:
Get DAQ Channel Name
Get Channel Information
Get Scale Information
Zvezdana S.
National Instruments

Where is the best target location to put configuration files (.csv), report templates (,dotm) and instructions (.pdf) when building a LabVIEW program and installer?

I am unsure of the best location to the above type of support files. I would like the files to be available to all users accounts. If I place them into something like c:\LabVIEW support files this can create an issue if manual changes are made to any of these files by a user without administrative rights. I can also place them into public documents. Any recomendations?
Related. I have added a PDF "help" file to the project. and given a path in the VI properties documentation field. I have then added a custom runtime menu with "Help for This VI". Running the application on my development machine, it works just fine. Making this in an application installed on a test machine, results in the application crashing. The PDF file is in the correct location on the target machine. Any ideas?

It seems you want to put the files where just any user can't get to them to edit them. Unfortunately, if the user account can't get to them, I don't think LV will be able to get to them. I could be wrong. To test this out, use a target location somewhere under your user account folder and then have another user try to run the app. if LV finds them then that gives you more options. If not, then you are going to have to have a common location that users are not likely to go to.
I generally create a dedicated folder structure for LV apps on a target system as shown below. I also make this the My Documents folder so that the LabView Data folder is created under this structure. Yea, it means that users can get to the files but that's where training needs to be executed. If you are in a network environment, you can place the templates, config (ini) files, etc on a network location and users are a bit less likely to inadvertently navigate to them.
I use both for some apps, Local folders for system specific files and Common folders on the network for files that all systems will share.
Not sure if this will address your location issues but thought I would share it nonetheless.
Doug
"My only wish is that I am capable of learning each and every day until my last breath."

Labview executable error - system cannot find the file specified

Hi
I am trying to create a stand-alone application and I'm getting the error message below:
"System cannot find the file specified"
This error message occurs when I run the setup.exe. Does any one know why this is happening? I've also attached the error message screenshot.
Thanks
Attachments:
Specified file error.png ‏34 KB

What type of hardware are you using? What do you mean by stand alone? Are you using any RIO device? (Just trying to understand)
The best solution is the one you find it by yourself

Read text from a string control in a compiled LabView executable from C#

I have a third party complied LabVIEW executable and no source code. I need to read values from the front panel in C#. I know that LabVIEW controls and indicators are not actual windows. Is there a way to programmatically access this information(i.e. without using screenshots and OCR)? I couldn't find this exact question answered in this forum. I've read a few things about VI Server doing this from LabVIEW, but I don't think you can access VI Server from C#. Any help would be appreciated.
Thanks in advance.

You should certainly be able to access VI Server from C#. LabVIEW has an ActiveX server built in that allows other applications to access a sizeable subset of VI Server functionality. I would guess you could access ActiveX servers directly from C#, but the worst-case scenario would be to wrap the ActiveX calls into a .NET assembly. I've seen this done before. This blog entry is slightly off topic, but might help you.
Actually, I do need to revise this answer... If you are working with a LabVIEW DLL, the DLL would have to be compiled with the ActiveX Server option enabled. Otherwise, LabVIEW won't include the code that allows the DLL to be hooked into using this method. So if you don't have the source and you can't recompile it, you might be out of luck. Does the DLL really not have a function that exports this string value?
Message Edited by Jarrod S. on 10-26-2006 01:39 PM
Jarrod S.
National Instruments

Open VI Reference to a LabVIEW executable.

Hello,
I haven't done this for a while and it's not working like expected. I'm trying to "Open VI Reference" from executable A.exe to B.exe. I'm trying to get a control value from B.exe in A.exe. Can someone send me an example?
Right now I'm at this stage: I have A.exe running as a LabVIEW executable. I'm trying to "Open VI Reference" to A.exe from LabVIEW development without success. Not sure what I'm doing wrong.
Don't hesitate to ask more info if you need some.
LabVIEW 2012, Windows 8.1.
Thanks,
Michel
Solved!
Go to Solution.

Bob_Schor wrote:
Once you have an Executable, does it matter that the underlying Development system is LabVIEW, rather than (say) Visual Studio, or Matlab? I suppose you could write an application that "knows" to, for example, listen to a TCP/IP port and interpret/execute commands, but that doesn't sound like the question being asked.
BS
LabVIEW-built executables still run as VI's in the RTE, though. Their identities have not been abstracted away into one single object or anything, and they still have name-based VI server access.
You can configure a build specification to include almost nothing, and require the VI files to be present in expected locations (i.e build specification's data or support directories). By default, all items in an executable application build specification are set to be put in the same location as their caller, which results in most things going into the .exe file, internally referenced in a directory-esque form like crossrulz mentioned, "MyExecutable.exe\MySubVI.vi".

Queue data sharing between multiple LabVIEW Executables

I have 2 LabVIEW Executables(Exe) where one Exe produces data and other one consumes the same. Is there anyway I can use a single queue reference for the same ? First Exe obtains the queue reference number and stores the reference number in V.I.G where as the second Exe read this reference number from this V.I.G. The error from the second VI dequeue was invalid queue reference.
Is there anyway I can share the same data between different exes with the functionality of a queue ?.
Solved!
Go to Solution.

Ben wrote:
Each exe is mapped into its own memory space so refs to resource in one context will not work in another but...
If you exposed an Action Engine in one instance to be used via VI server Invoke Node from the other, the AE (Note: it will be running in the server context) could queue the data in behalf of the client.
Plese note:
If the server porcess goes idle all of its resource will be invalidated (including the queue) but a ref to the AE will still be valid. In this case the enqueue op will fail so you have to code to account for this situation. (been there done that )
This smae approach will work in any network architecture where VI serve can be used. I used this approach about 10 years ago (minus the queue) to allow control of a factory floor from a laptop with a internet connection.
Ben
Do you think the same must work with following scenario:
1. LabVIEW Exe calling a data acquisitio thread dynamically(VI Server) and enqueue the data into a Queue with reference in VIG.
2. Same Exe calling a TestStand Engine and one sequence inside that calling the same queue to dequeue the data.
3. Remember that the LabVIEW adapter I use with TestStand is LabVIEW Run-Time Engine(Not development system)

How can I call a LabVIEW executable from within another LabVIEW executable?

I have a customer requirement for two LabVIEW executables. Based on their current setup, they need to run executable "A" or "B", both of which are under independent revision control. I have created a third "selection" executable that allows the operator to choose between one of the two, but I am receiving errors when I attempt to call a LabVIEW executable from within a LabVIEW executable using either the "System exec" VI or the "Run Application" VI. If I call a non-LabVIEW executable (such as Windows Explorer) everything works fine.

> I have a customer requirement for two LabVIEW executables. Based on
> their current setup, they need to run executable "A" or "B", both of
> which are under independent revision control. I have created a third
> "selection" executable that allows the operator to choose between one
> of the two, but I am receiving errors when I attempt to call a LabVIEW
> executable from within a LabVIEW executable using either the "System
> exec" VI or the "Run Application" VI. If I call a non-LabVIEW
> executable (such as Windows Explorer) everything works fine.
As with the other poster, I suspect a path problem. You might try the
path out in a shell window, and if it works, copy the complete absolute
path to LV to see if that works. LV is basically passing the comma
nd to
the OS and doesn't even know what is in it, so you should be able to get
it to work.
The other poster commented on subpanels, which is a good suggestion, but
without going to LV7, an EXE can have open more than one VI. You can
use the VI Server and the Run method to fire up another top-level VI.
The decision is whether you want both to be in unique processes.
Greg McKaskle

Where are configure files for Grid Control components?

I installed Grid Control 11g on Redhat 5.2, the repository database is Oracle 11.2.0.2 on the same box. It worked after installation, but after some weeks, I restart oms and got error [oracle@cchbi bin]$ ./emctl start oms
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Starting WebTier...
WebTier Successfully Started
Starting Oracle Management Server...
Oracle Management Server is not functioning because of the following reason:
Connection to the repository failed. Verify that the repository connection information provided is correct.Tried to google and search the forum, the message is not very selective and got few relevant resut.
Hope your exterts can point me to the configure file where I can verify the connetion to repository. Alos some one would share with me the knowledge on the following topics
1) What are the processes/components of Grid Control ? I am aware of oms, opmn, and a process run as /u01/app/midware/oms11g/ccr/bin/nmz -cron –silent. ANy others? What are their functions?
2) Location of configure files, log files and binary executables of this processes/components.
Many thnaks.

Hi,
to check if the OMS is running properly execute the command "emctl status oms" ($OMS_HOME/bin).
The result should be "Oracle Management Server is up".
To check which components are currently running execute the command "opmnctl status" ($OMS_HOME/opmn/bin).
The result should be something like:
Processes in Instance: EnterpriseManager0.<host
-----------------------------------------------------------+---------
ias-component | process-type | pid | status
-----------------------------------------------------------+---------
DSA | DSA | N/A | Down
LogLoader | logloaderd | N/A | Down
HTTP_Server | HTTP_Server | 26470 | Alive
dcm-daemon | dcm-daemon | 26301 | Alive
OC4J | home | 1953 | Alive
OC4J | OC4J_EMPROV | 1954 | Alive
OC4J | OC4J_EM | 26523 | Alive
WebCache | WebCache | 27085 | Alive
WebCache | WebCacheAdmin | 27086 | Alive
Executing this command will answer your question whioch components need/should be up when using OEM/GC.
You will find some logfiles of the OMS under $OMS_HOME/sysman/log (e.g. emoms.trc, emoms.log). Please check logfile OC4J~OC4J_EM~default_island~1 under $OMS_HOME/opmn/logs as well...
To start the OMS you might try the command "opmnctl startall"...
HTH

Best way to create a Windows service from a LabVIEW executable?

What would be the best way to run a LabVIEW executable as a service? I needed this recently and I think I have set up such a service using srvany.exe from the Windows 2003 Resource Kit, but that seems like a bit of a hack. The Kit is not offically supported in Server 2008, but seems to work. I don't know about Server 2012 or beyond.
So what would be the "proper" way of going about creating a Windows service from a headless LabVIEW application?

The proper way is to interface to the according Windows service control API. That is however not a trivial task to do. We used to sell a LabVIEW toolkit which supported a full interface to this, but it's not currently actively marketed.
srvany.exe is sort of a hack but works reasonably well for most use cases, as long as you do not need any further interaction with the service manager interface in Windows than to start and stop your service.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How to view waveforms in DIAdem that were saved in Labview using "write waveforms to file" VI

I'm new to DIAdem but would appreciate any help to my question.
I seem to be having a little trouble but how do I view waveforms
in DIAdem that were saved in Labview using "write waveforms to file" VI??
tks, Terry

Hello,
There are several ways to write waveform data from LabVIEW so it can be accessed from DIAdem. Two of the easiest ways are to use either .lvm files or .tdm files. You can write .lvm files using the Write LabVIEW Measurement File.vi which is located in the File I/O palette. You can write .tdm files by using the storage VIs which are located in the File I/O >> Storage palette. So, I would recommend using either of these file formats if you are developing a new application since these can be loaded into DIAdem directly.
If you are interested in loading files that where already created from the Write Waveforms to File.vi, I am wondering what file type you are using. For example are you saving your files as .dat or .txt with your Write Waveforms to File.vi? Feel free to reply to this thread with this information and I would be glad to help you out.
Regards,
Kevin L.
Applications Engineer
National Instruments

Run labview executable without installing

Hi
We need t run a LabVIEW executable without the need to install the runtime engine first.
In fact we use a LabVIEW program to distribute LabVIEW within our company.
We add our own library and a special license request form and make it possible to install a LabVIEW development environment
with only the push of one button.
In LV8.2 however this no longer works. First the runtime environment has to be installed before we can run our LabVIEW application.
Previous LabVIEW versions worked OK.
Are we missing an option in the installer somewhere or can somebody show the way to make this work again otherwise we have to keep 8.01 until infinity....
greetings from the Netherlands

Hi Albert,
Long time no see... Perhaps at the user group meting okt. 5?
We (Andre) did some experiments with this just last week. He copied everything from the normal installation directory (program files) runtime directory to a new directory on a clean PC. In the same directory he put an executable, and it did run properly (although I think he also copied the models directory to get proper control images).
Only thing is that at the startup of the exe, we get a dialog "Installing...". Still working on that. This might even work from a CD...
He made a big effort to remove all previous LabVIEW stuff, but to be honest, we didn't try it on a completelly "clean" system.
Regards,
Wiebe.
"Albert Geven" <[email protected]> wrote in message news:[email protected]..
Hi We need t run a LabVIEW executable without the need to install the runtime engine first.In fact we use a LabVIEW program to distribute LabVIEW within our company.We add our own library and a special license request form and make it possible to install a LabVIEW development environmentwith only the push of one button.In LV8.2 however this no longer works. First the runtime environment has to be installed before we can run our LabVIEW application.Previous LabVIEW versions worked OK.Are we missing an option in the installer somewhere or can somebody show the way to make this work again otherwise we have to keep 8.01 until infinity....

Labview executable monthly password distribution via internet

We control some equipment with a Labview executable that operates a USB DAQ board (Analogue Inputs and Digital Outputs). Does anyone know of software that would automatically email operating parameters and data files and would manage Password Access. The proper password would be available weekly or monthly on our server when the account is in good standing. If the payment for the equipment has not been made the software should show information pertaining to making a payment and how to obtain the appropriate Password.
It appears that the Internet Toolkit only partially solves the internet access problem the secure password distribution, if it exists, is most likely a third party software. Does anyone know how secure this solution in the face of some person who prefers to crack than pay?
I am open to suggestions. I would like to use the solution nationally and internationally.
Raymond

I'm pretty sure you won't find a ready made solution for this to download. Your requirements are quite specifc and involve quite a bit of different componenets. And any one having written something like this has spent A LOT of hours into it, so he will not post it for free.
So lets look at your description:
1) Having a password to download from your server. Why??
You simply want to connect to your server with a license key that the user got when purchasing the software and see if the application has still support in your database. But you do not immediately want to disallow operation when the internet connection is flaky so you need to add some grace period, with a warning to that fact but still allow to run for some time. A legitimate user that can not run your software because something messed up that he does not understand, will in the best case call you up and tell you what he thinks about your #$%^ company.
2) Password access is not for you to check that the application is used properly (you do that through the license key) but for your users to allow protecting the software to be run by anyone he doesn't want.
But for your online license check you do need also a VERY reliable database backend on your server. And an internet access component that can query your database through some interface like CGI or Web Services. And of course you do not want to have this connection through unencrypted connections, so there needs an underlaying SSL connection.
So let me ask some question? How much would you be willing to pay for such a LabVIEW component and how much time and money would you be willing to spend yourself to build and test the database backend?
Message Edited by rolfk on 11-06-2009 09:25 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

3 axis motion control- where do I start?

I have to develop a hearing aid hybrid test system which will test an array
of hybrids. I already have the individual hybrid test code but need some
guidance with the motion control. Does anybody have any good references
for me on what aspects should be considered. All I really want to do is
step
and test but don't know much about motor types stepper/servo etc, limits,
calibration etc. Any tips would be greatly appreciated.
Regards,
Dow Airen
Design Engineer
Crystalaid Microelectronics P/L

We use http://www.jrkerr.com/index.html motor control system. This uses
low cost Pics and a serial network. The drivers are a DLL and can be
called from LabVIEW. I have built multi axis devices and it has worked
real reliable. (No problems).
A company called Compu-Motion has experience building low cost hardware and
software for mult-axis devices. Compu-Motion web site is
www.compu-motion.com. Compu-Motion could help you build the hardware or
software.
John Harmon
330-848-0460
----- Original Message -----
From: Dow Airen
Newsgroups: comp.lang.labview
Sent: Wednesday, November 24, 1999 12:33 AM
Subject: 3 axis motion control- where do I start?
>
> I have to develop a hearing aid hybrid test system which will test an
array
>
> o
f hybrids. I already have the individual hybrid test code but need some
>
> guidance with the motion control. Does anybody have any good references
>
> for me on what aspects should be considered. All I really want to do is
> step
> and test but don't know much about motor types stepper/servo etc, limits,
> calibration etc. Any tips would be greatly appreciated.
>
> Regards,
>
> Dow Airen
> Design Engineer
> Crystalaid Microelectronics P/L

LabView Executable files

I had a question about LabView executables files- (one of the main differences between LabView Full and LabView Professional). If I am able to create LabView executables (LabView Pro), then I would be able to run LabView programs (executable files) on PCs that do not have LabView installed? If I use LabView Full (no executables created), then I can only run LabView files from PCs that have LabView installed?
Thanks,
Alex

Charles_CLD wrote:
As a long time user of LabVIEW and someone who is not in any financial way affiliated with National Instruments, I would highly recommend the Developer Suite over the Pro version. I believe the cost to benefit ratio to be VERY high.
Charles
I agree completely. Besides, once you add one or two of the essential toolkits to the pro version you are at about the same price as the developer suite.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Control where a LabVIEW executable write it's Settings Configuration file

Similar Messages

Maybe you are looking for