Labview.ini

Hello,
How can I do to have each user its own labview.ini file ? And of course bee able to edit it.
I first copy a file labview.ini into a "home" directory and use a shortcut which is supposed to start Labview from
the same "home" directory, But still Labview does not use it. I probably need to change something else maybe in the regedit.
Thank

From the online Help:
LabVIEW stores options in a labview.ini file in the LabVIEW directory. The file format is similar to other .ini files. It begins with a LabVIEW section marker followed by the option name and the values, such as offscreenUpdates=True.
If you want to use a different options file, specify
the file in the shortcut you use to start LabVIEW. For example, to use
an options file on your computer named lvrc instead of labview.ini, right-click the LabVIEW icon on the desktop and select Properties. Click the Shortcut tab and type labview -pref lvrc in the Target text box.

Similar Messages

Labview ini file syntax

Hi
I have a ini file built into an application as a support file. When I did some changes on ini file, some change was reflected in executable file but some not. I suspect the syntax in ini file are not right so aren't recognized.
Besides, how ini file works? when I change the ini file, do I have to re-execute the application in order to getting the reflection in application? Or if the configuration is changed via the menu Tools->option in application, will they rewrite the ini file automatically? Do I have to stop the application in order to reading a changed ini file?
Where can I find a documentation about labview ini file as well as its syntax?
Thanks.

An .ini file is a standard file and is not something that is special to LabVIEW. LabVIEW itself uses an .ini file to store some application settings that you change via the Tools->Options menu. It is not wise to change this file yourself manually. You can create your own .ini files for your application. You can use the VIs in the Configration File VIs palette to read/write .ini files. This palette is a sub-palette from the File I/O palette.
As for its format, it's made up of sections and keys like this:
[Section1]
keyname=value
keyname=value
[Section2]
keyname=value
;this is a comment
If the value you're trying to save is a string you should use quotes.
What you store in the .ini file is up to you and how you use it is also up to you. You can access the keys on an as-needed basis, or you can read the keys in at the beginning of your program, store them someplace like a global variable and access them as needed. It's kind of dependent on the size and architecture of your application.

We want your LabVIEW INI files!

Hello:
As some of you might know, the Tools>>Options dialog box allows you to control options that are stored in the LabVIEW.INI file. With each release of LabVIEW, we have steadily increased the number of available options to customize LabVIEW environment. For example, the LabVIEW R&D team has added over 15 block diagram options since LabVIEW 5.x and only removed a small handful.
As the LabVIEW team introduces new features, we provide more and more configurable options to satisfy different development styles or interests. However, the proliferation of options can prove confusing. It becomes difficult to distinguish between widely-used options and ones that are applicable only to a small set of customers.
To gain a better sense of how customers use the settings in the Tools>>Options dialog box, I would like to collect as many customer INI files as possible. This will allow me to analyze option usage and improve the usability of the Tools>>Options dialog box.
Please help by sending your INI file(s) to the following email address along with answers to a few simple questions. The more INI files, the better. Therefore, encourage your colleagues to send their INI files, too! If you are a MacOS or Linux user, attach your LabVIEW Preferences or .labviewrc file. I'm interested in receiving INI files from users of all experience levels -- novice, intermediate, advanced!
Send to: [email protected]
What is the first version of LabVIEW that you used?
When upgrading to a new version of LabVIEW, do you copy the LabVIEW.INI file from the older version of LabVIEW to the newer version of LabVIEW?
When launching a new version of LabVIEW, do you immediately change any particular settings in the Tools>>Options dialog box? If so, which ones?
When upgrading to a new version of LabVIEW, do you review the New and Changed page in the Tools>>Options dialog box?
Which options are you the most passionate about? Please provide a brief reason for each.
Do you have any suggestions to improve the usability of the Tools>>Options dialog box?
Please do not forget to attach your LabVIEW.INI file.
Note: On Windows the LabVIEW.INI file resides next to the LabVIEW.exe. On Mac OS, your options are stored in the LabVIEW Preferences text file in the System: Preferences folder. On Linux, the .labviewrc file is in your home directory.
Thank you,
Noel Adorno
LabVIEW R&D

Hai noel,
Its great and delighting to hear that LabVIEW R&D team is in an constant effort in collecting the information about user experience and appropriate changes are done. Each enhancment or feature inclusion that is done to LabVIEW makes the users more comfortable with the environment and kindles the user for new version LabVIEW experience...
Hats off to LabVIEW R&D team.
With regards,
JK
(Certified LabVIEW Developer)
Give Kudos for Good Answers, and Mark it a solution if your problem is solved.

Labview.ini and graph rescaling

Hi everyone,
I'm using Labview 71. and 8.0 on Mac OSX.
It used to be (under Laview 6) that to disable graph rescaling a one line labview.ini file would do the job. The one line would be
EnableAutoScales=False
See for example
http://zone.ni.com/devzone/cda/tut/p/id/3815
This would work if you put the labview.ini file in the same directory as the Labview application.
Now, with Labviews 7 and 8, its not working anymore, well at least not for me.
Has the name of the file changed? (Does its capitalization matter?) Has it been superceeded by some other mechanism?
Exactly where should the file be? (Mine is in bootdrive:Applications:National Instruments:Labview 7.1
Has the syntax of labview.ini changed? (Is that single line sufficient?)
I noticed that the valuable web page discussing INI files, labview.brianrenken.com/ini, is not working right now.
Thanks in advance,
Peter H.

PGH wrote:
It used to be (under Laview 6) that to disable graph rescaling a one line labview.ini file would do the job. The one line would be
EnableAutoScales=False
Now, with Labviews 7 and 8, its not working anymore, well at least not for me.
I think that the the global .ini entry EnableAutoScales=False disappeared from use as of LV6.1 when it was replaced with the ability to right-click (or do the Mac equivalent) on individual graphs and toggle Advanced>Auto Adjust Scales.
=====================================================
Fading out. " ... J. Arthur Rank on gong."

Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

Hi all. Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop). This really slows things down! Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini. Has anyone seen similar, and/or any hints towards a solution?

Jeff-P wrote:
As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.
I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini" might indicate that the labview.ini file cannot even be created... strange...
LabVIEW Champion . Do more with less code and in less time .

[LAVA Cross Post] CTRL+SHIFT+Alpha Shortcuts don't work in LabVIEW

Cross-post from LAVA: http://lavag.org/topic/15619-ctrlshift-shortcuts-sometimes-not-working-in-labview/
Bug Synopsis: CTRL+SHIFT+Alpha shortcuts do not work in LabVIEW. Most notably, CTRL+SHIFT+Z, CTRL+SHIFT+E, and CTRL+SHIFT+S
Test setup: LV2012 32bit with f1 patch running in Win7 64bit inside a Parallels 8 VM in OS X 10.8.1
To summarize the testing I have tried:
Many different LabVIEW, Guest OS, and Host OS combinations all fail, including:
LV2012f1 32 and 64 bit, and LV2009 32 bit
Win7 32 and 64bit, and also WinXP x64
Parallels 7 and Parallels 8
OS X 10.7 and 10.8
Capturing the keyboard by the VM
Twiddling every keyboard setting possible on Parallels, Guest, and Host
Reinstalling keyboard drivers
Plugging in a known-good keyboard that works on a native Windows machine
Deleting LabVIEW.ini and letting it regenerate
Remapping the shortcuts from, e.g., CTRL+SHIFT+E to CTRL+E - in this case, "Show in Project" works, so this might indicate it's a problem registering the shortcut press, not invoking the action itself.
Sending the keystrokes via on-screen keyboards from both Guest and Host
Sending the keystrokes via SendInput from user32.dll WinAPI
Testing every imaginable combo of FN, CONTROL, ALT/OPTION, COMMAND/CMD, SHIFT
Reinstalling VMs from scratch and reinstalling LV
Here's a kicker: CTRL+SHIFT+Alpha shortcuts work fine on other Windows programs (I've tried 4 different programs, including Chrome, Notepad++, Paint.NET), yet it does NOT work for VIPM with CTRL+SHIFT+C. This means that the only two programs where the CTRL+SHIFT+Alpha bugs exist are both LabVIEW-related.
Here's another kicker: It's only CTRL+SHIFT+Alpha shortcuts with the prob - CTRL+SHIFT+3 properly toggles grid alignment, and the "Tools >> Options >> Menu shortcuts" will register any CTRL+SHIFT+Non-alpha shortcut; it just does not respond to the CTRL+SHIFT+Alpha shortcuts.
Any new troubleshooting ideas are highly appreciated; please feel free to jump in here or on LAVA.
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}
Solved!
Go to Solution.

X. wrote:
Still well and alive in Parallels 9 and LabVIEW 2013 SP1. Of course I could upgrade to the latest versions to check whether things have gotten any better.
Any news on that?
@mellroth figured out the solution :-)
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Is there any way to specify the default version of LabVIEW?

I have a sinking feeling that the answer to this question is "no." With more than one version installed, is there any way to set the default LabVIEW version for opening a VI? I have both 7.1 and 8 installed, and usually only use 8 to open an example or look at something posted here. When I do that, it resets all the OS hooks so that the default action for opening a VI is to open it in version 8. I've even gone so far as to create actions to open files in 7.1 and 8, but it always resets my default action.
I found this KB article for when version 7 came out, but it's suggestions don't seem to work with 7 and 8.
Ugh. I hate it when software thinks it knows what I want better than I do.

eaolson wrote:
I have a sinking
feeling that the answer to this question is "no." With more than
one version installed, is there any way to set the default LabVIEW
version for opening a VI? I have both 7.1 and 8 installed, and usually
only use 8 to open an example or look at something posted here.
When I do that, it resets all the OS hooks so that the default action
for opening a VI is to open it in version 8. I've even gone so
far as to create actions to open files in 7.1 and 8, but it always
resets my default action.
I found this KB article for when version 7 came out, but it's suggestions don't seem to work with 7 and 8.
Ugh. I hate it when software thinks it knows what I want better than I do.
Add
in the LabVIEW.ini file of those versions you do not want to rewrite
the registry on startup to point to themselves for VI files, the
following:
RegisterExtensions=False
Of course the VersionChooser utility mentioned earlier is even more convinient.
Rolf Kalbermatter
Message Edited by rolfk on 06-28-2006 08:21 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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

I still have no way how to deal with the LabView Data folder automatically created in the My Documents folder whenever I run the application

I tried numerous ways that some people suggested in this forum but did not succeed in having the LabView Data folder created somewhere else than in My Documents when running a built LabView application. Changing the target destination folder did not help at all. A member suggested to put some line like " defaultdestination = ..." or so into the build file, but I did not know where exactly to put such a line. That folder created is particularly anoying for people who don't normally use LabView but are only using the application. Please let me know when you LabView Experts out there have found a way to eliminate or relocate the creation of that folder at application startup.
Thanks a lot.
Tim, Van

Tim,
use the path constant located in the Functions pallette under 'File I/O->File Constants->Default Data Directory'. It refers either to the default directory (which is (osdatadir)\Labview Data on my WinXP system) OR TO A NON DEFAULT PATH if you have defined one. To define a non-default path, got to the menu 'Tools->Options...' and change the entry under 'Paths->Default Data Directory'. This change will create an entry in the labview.ini file (located where the labview.exe is), e.g. the entry 'DefaultDataFileLocation=d:\temp' is created when I change the default data dir to 'D:\temp'.
Now for a compiled .exe with the name (say) myapp.exe you will find a file myapp.ini in the same location where myapp.exe is. It is usually an emtpy file directly after the application build process. Put the line 'DefaultDataFileLocation=(your path)' in this file.
Users of your compiled app can either
- edit this .ini file to change the default,
- or you can make the menu entry 'Tools->Options...' accessible in the built VI
- or you can provide a self written dialog in your app and modify the myapp.ini programmatically
(This last way is probably not a good one since the user might have to relaunch myapp.exe in order to affect a change of the 'Default Data Directory' path constant)
-Franz
Tc@labView wrote:
I tried numerous ways that some people suggested in this forum but did not succeed in having the LabView Data folder created somewhere else than in My Documents when running a built LabView application. Changing the target destination folder did not help at all. A member suggested to put some line like " defaultdestination = ..." or so into the build file, but I did not know where exactly to put such a line. That folder created is particularly anoying for people who don't normally use LabView but are only using the application. Please let me know when you LabView Experts out there have found a way to eliminate or relocate the creation of that folder at application startup.
Thanks a lot.
Tim, Van

How can I write to the parallel port using LabVIEW 6.0.2

I have tried updating the labview.ini file and also using the parallel.llb available on the site. When I execute the program it gives me error 37 saying,"device not found". I am running this code on windows 98. I tried to use VISA write,serial port write (using port 10) but nothing seems to work. I also tried to develop a sample code using inPort and outPort, but no success, it is not able to read the data back from the parallel port, even if it seems (????i don't know any way to cross-check it though????) to write.
Does anybody know the problem here?
THanks.
Pari.

Thanks Brian.
Well here is the next problem. I got a VI (attatched) off ni.com and it works fine on a windows98 platform. But quits working on NT.
I can write perfectly (which i checked by hooking an LED display unit at the other end of the parallel port cable). I observed that the LEDs respond to the toggling of individual bits (data bits). But the error occures at the "out port.vi", when I try to run it on a NT machine (where I actually wanna use it). Are you aware of any changes to be made in order to run a VI on NT that works on 98?
Thanks again.
Pari.
Attachments:
parallelPortSwitcher.vi ‏124 KB

Is it possible to disable the optimized compiler in LabVIEW 2010

Hello,
I have a project that take 3 minutes in LabVIEW 8.6 to build and now with LabVIEW 2010 it take 10.5 minutes. 3x more longer.
In fact my project as 61 .lvproj for a total of 4300 vi's that take 1 hour to build. If I interpolate, the entire build process will take 3 hours in LabVIEW 2010. This is not acceptable
I know that the new compiler optimize the code for better performance, but if I don't need better performance.
Is it possible to disable the optimized compiler in LabVIEW 2010 with an INI key in LabVIEW.ini.
Dany Allard
Dany Allard
Solved!
Go to Solution.

Jarrod S. wrote:
One Application Builder setting you might try out to make builds go much more quickly is the Remove Unused Members of Project Libraries checkbox and the Modify Project Library File after Removi....
This can drastically cut down the build times. Note, however, that this option does not work well if your application will load external plug-in VIs when it runs, because the libraries of those plug-in VIs may conflict with the modified libraries in the executable file. If you don't have a plug-in architecture, this will not affect you.
The "Remove unused members of project libraries" was already selected but not the "Modify project library file after removing unused members" and selecting this cut the build time from 10.5 min to 4 min.
Thank you Jarrod for this tips
Dany
Dany Allard

Why does my LabVIEW occasionally display in Chinese?

Windows Vista and LabVIEW 9.01.
Occassionally when working in LabVIEW, different parts will suddenly begin displaying in ( presumed ) Chinese characters - see attached screen shot. I do not speak Chinese and have never had any of my OS regional settings configured for Chinese. Usually, if I just close LabVIEW and reopen, everything goes back to normal; although there was one instance where it happened in a VI which I accidentally saved in that form and could not get the characters to go back. Its more an annoyance than anything else, but it has happened multiple times is a single day and is becoming very aggrevating. Has anybody else ever seen this, or am I just lucky like that?
-A. Marks
Attachments:
LabVIEW Chinese.jpg ‏147 KB

I'm going to take an educated stab at your problem: your LabVIEW.ini file at some point had the key UseUnicode=True, or you are actively developing using UTF-16 Unicode on your front panels. From my experience, this is OS independent (I've been Unicoded on WinXP, Vista, and 7) and LabVIEW version independent (at least, between versions 8.2.1 and 2009)... it's linked simply to an unreproduceable, intermittent bug in the IDE's handling of 1-byte versus 2-byte string.
All of the "Chinese" characters you are describing are 1-byte ASCII strings that are being interpreted and displayed by the IDE as fixed 2-byte MBCS, or UTF-16. Take a look at all of the characters... there will be exactly half as many (or half minus one) characters of the "Chinese" string compared to the English ASCII string.
Take a look here where I have described the same issue.
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Labview doesn not care about "vi search path "?

We've had some problems with labview taking sub vi's from other library files than wanted. To clean up the mess once and for all I wanted to include the path to the active library files, and remove the <foundvi> from vi search path.
The added path is something like "\\acanova5\common\...", also tried the version "\\192.168.0.50\common\..."
So far so good, but when I open a vi that need sub vis (before located in now deleted lib files) LV don't find them. When then manually point to the lib file and point to the vi it is ok, but why doesn't it work as I expect?
I looked in labview.ini, and my path is the first in "vi search path" list.
Ola

We've had some problems with labview taking sub vi's from other library files than wanted. To clean up the mess once and for all I wanted to include the path to the active library files, and remove the <foundvi> from vi search path.
The added path is something like "\\acanova5\common\...", also tried the version "\\192.168.0.50\common\..."
So far so good, but when I open a vi that need sub vis (before located in now deleted lib files) LV don't find them. When then manually point to the lib file and point to the vi it is ok, but why doesn't it work as I expect?
I looked in labview.ini, and my path is the first in "vi search path" list.
Ola

Setting Search Directory with LabVIEW RTE

Hi,
I've LabVIEW 8.0.1 run time engine installed on target computer and would like to run LabVIEW executable on target computer. I also have required low level support VIs for developed VIs.
Question is: how do I set the search directory for low level VIs with LabVIEW run time engine installed on the system.
Suggestions/comments are appreciated. Thank you.

If your hierarchy is the same as was in the IDE, then there won't be a need to search for the VIs. If the VIs are not found where they are expected to be, then LV (including the RTE) starts to search for them first in the folder where the VI\application is and then in the folders in its list. To change the list, you need to place the viSearchPath key in your application's INI file. You can copy this key from the labview.ini file and then modify the paths listed in it.
Try to take over the world!

.ini not found error

When attempting to run my application, I continually get a ".ini" not found error. I have built the application with both the LabVIEW ini file and with a custom ini file. An issue that may be related is that the VIs were created using LabVIEW 5.1. We have been unsuccessful in building the files since transitioning to LabVIEW 8.0. Am I building the application incorrectly? Where does the executable look for the .ini file?

muks wrote:
see whether this will help
muks, honestly, what the HECK does that article have to do with this issue???? You often post links to articles which have NO bearing on the question! This case is especially bad since the article relates to LabWindows! Please try to be a little more selective in your article selection so people are not sent on wild goose chases.
To poster: An executable keeps its .ini file in the same folder as where it is located. The .ini file will have the same based name as the application.I don't understand what you mean by "not building the application correctly". If you can tell us what you are doing then we can tell you whether it's correct. Have you checked through the LabVIEW Help?
Message Edited by smercurio_fc on 02-05-2010 09:08 AM

Labview.ini

Similar Messages

Maybe you are looking for