Rename outside of labview

I am using 7.1. I need to rename a lot of vi(s) (I inherited this system). It would be a real pain to rename them from within LabView. I renamed them outside of LabView with a batch script; loaded the main vi, it doesn't find the renamed vi(s), but it won't let me pick the newly renamed vi.
Is there any way to do this?

Not with LabVIEW 7.1. With later versions NI added the ability to point LabVIEW to a different VI when it asked you to find a VI. So, you will need to let the VI load with the missing VIs and then manually replace the missing VIs with the new ones.
There may be a way to do with scripting. Scripting back in the days of LabVIEW 7.1 was not officially supported, but you could enable it with special keys in the LabVIEW.ini file. Since it was not officially supported, though, the functionality to do this may not even be there.

Similar Messages

Search function of tags not working when folders renamed outside of PSE

hi guys
have PSE 9 on MAC.
when saving foto files at another place and doing so outside of the program PSE, we all know already that PSE displays them in the organizer with a "?". This fact is not at all comfortable but, thanks to the link PSE makes, it still displays them.
however, when I want PSE to display all fotos tagged with a certain tag, let's say "house", PSE does not display ANYTHING!
so how can I make PSE to show the result when searching for all tagges fotos with "house" - for those fotos that are saved now at another place?
honestly, "the other place" is a bare renamed folder, so still at the same place somehwat.
I definitely don't want to tag all my fotos again. But I want PSE to show the fotos marked with example "house"
I've tried to copy - paste, from old to new folder. No success.
I've imported the fotos from the new folder. It works, but they are without tag! and sometimes it says an error message even, saying, the content inside is already in this catalogue.
anyone has a good hint?
many thanks!
PS: had the same trouble on PSE 7 for Windows...

File->Reconnect is the solution to your problem.
In the future, you might want to consider using a workflow that does NOT involve renaming/moving folders or photos outside of PSE. In fact, I think such a workflow would be mandatory to avoid problems and extra work.
If you absolutely MUST rename or move photos or folders, do so from within PSE, in the Folder Location View...but I would still recommend not having a workflow involving renaming and moving stuff from here to there; I would recommend organizing by keywords and captions; and putting photos into default named folders (capture date) and leaving them there un-moved and un-renamed.

Get version of EXE built outside of LabVIEW

Hi,
I was looking for a way to read the "Versions" File property of an EXE that was built in C++ (or any other EXE). I would like my application to read it programmatically instead of having the information in some other file that my application reads.
Thanks,
Gary
Solved!
Go to Solution.

Hello glstill,
There is a pretty good discussion of that problem as well as a few possible solutions using .NET or the WinAPI offered in this thread from 2006:
LabVIEW thread: File version info
http://forums.ni.com/t5/LabVIEW/File-version-info/m-p/361945?jump=true
Some of the .NET information may be out of date, but the discussion is relevant and a few people have provided code to do more or less what I think you're looking for.
Another pretty clean looking and more recent example is available here on the NI Developer Community:
Example: Get File Version Information for EXE’s and DLL’s
https://decibel.ni.com/content/docs/DOC-13866
Best Regards,
Tom L.

Viewing vi files outside of LabVIEW

I have LabVIEW 4, but want to see some LV5 vi files to give me some ideas. Is there any software on this site to let you view a .vi file?

You might also want to check out the LabVIEW player. You can find more information on it at the following page: http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/87392d1cb3c49dde86256ae30049ce55?OpenDocument
There are some restrictrions to it including that the VIs you are trying to read must be signed and the person who signed them will need LabVIEW 6 Professional Development System or higher.
For your case, obtaining an evaluation copy of LabVIEW would probably be the best route.

Making VI front panels modal outside of Labview

Hi,
I am calling VIs as Sequence Steps from a custom TestStand GUI (in visual basic). How can I make VIs modal => pop up in front of the GUI and remain frontmost until they are closed?
Using the "VI Properties >> Window Appearance >> Window is Modal" option makes the VI stay frontmost within Labview but in this instance it is still possible to switch focus back to the GUI.
Hopefully someone has a suggestion.
Thanks.

Answering my own question, as after this post I discovered what I was looking for.
Labview "Functions >> TestStand >> TestStand - Start Modal Dialog" included in a VI diagram called from TestStand causes the VI to be modal to the TestStand GUI.
Dan

Convert labview VI to C code

Hi,
I've to translate LabvIEW code to C code (CVI). Does any exist?
Thank you in advance.
Bim

bimbim wrote:
Thanks for your answer,
The purpose is to adapt drivers, tested via LabVIEW, into C in order
to load it in our device (real time). So we're close of the
hardware and we must have a "light" code.
Concerning the use of a dll or of an exe, don't we need to install
the LV runtime engine (heavy) and all associates runtimes to get it
running? If true, the installation and use of the program should take
more place and time than using a simple C executable?
I still have a few misunderstanding concerning the portability of LabVIEW code, even in exe or dll...
As
Dennis already has pointed out: The only sort of LabVIEW to C converter
is part of the LabVIEW embedded system. It's C code however is only
supporting a subset of LabVIEW (no IO libraries and some of the more
advanced internal nodes) and not really meant to be used as a C code
for further use outside of LabVIEW embedded. It's readibility as normal
C code is quite hairy eventhough it is syntactically C.
In fact it won't even compile on other systems easily as LabVIEW
embedded comes with quite some specific runtime support to connect to
the compiled code on the target system and do quite a lot of other
things too, which all get built into the executable as well and which
all will be used directly or indirectly by the created C code.
CVI has a runtime too, and I'm not sure what you mean with all its associated other runtimes.
LabVIEW code in source code is generally portable across all LabVIEW
platforms of the same version and also into newer versions. LabVIEW
executables are only portable inside the family of system they were
created for. This family is both a combination of OS and CPU. So
LabVIEW created for Windows will run on all supported Windows platforms
(the newest version only supports 2000/XP/2003 anymore) but not on
Linux, MacOSX or an RT system.
An executable for MacOSX will only run on MacOSX but I think on most of
their versions although there have been specific issues with certain OS
versions. If you happen to have an Intel Mac it would only run on a
dual boot system with XP on it too, or in the emulation environment
called Rosetta if they didn't rename that in the meantime.
Basically if the OS type changes or the CPU, you can't use an
executable anymore other than in certain emulation environments that
provide the old environment.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Preventing LabVIEW from automatically choosing replacement subVIs

I open my VI; then LabVIEW tries to load the subVIs which are called in the VI. But it cannot find them for whatever reason; perhaps I moved them or changed their names, for example. So, it automatically goes hunting through my hard-drive, trying to find them. If it finds something close, it automatically chooses and loads it, even though that subVI might be complete garbage--it just happened to have a close name.
There is no easy way for me either to stop it from automatically loading or to correct the damage once it is done. To correct the damage, I have to open each subVI and subsubVI and subsubsubVI (you get the picture) to replace it with the proper file. This is tedious, stupid, and annoying.
Please advise as to how to easily correct this problem. Please also force future LabVIEW editions to ask the user if the suggested replacement is correct before automatically loading it. The user should also be able to browse and choose the correct subVI file. Thank you.

Agreed, this is an annoying feature of LabVIEW and can cause headaches until you learn how to handle it.
The first thing you need to realize is that LabVIEW has only a single memory space. This means that no two VI’s can be loaded at the same time if they have the same name. It’s similar to the directory structure on any OS, you can’t have duplicate filenames in a directory.
Next is how does LabVIEW load sub VIs. The first place it looks is in its memory space. If it sees a VI with the name of the one it’s trying load, it must use that. Again, because it can’t have duplicate names in memory. If it’s not in memory, it looks for the sub VI at the path where it was when the top level VI was last saved. If it’s not there, it starts searching through a specified set of directories (that you can modify. Go to Tools>Options>Path>VI Search Path) for the VI. If you’re quick enough, you can hit the Browse button on the search dialog and find it yourself. If it doesn’t find it in the specified search paths, you then get a browse dialog to allow you to try and find it yourself.
To avoid problems like this, there are a couple things you need to keep in mind.
Don’t have duplicates of a VI on your hard drive. This will ensure that a top level always loads the correct one. If you have a sub VI that you use often, put it in the user.lib directory that’s located in the LabVIEWx.x directory.
Don’t have two VIs with different code use the same name. Even if they are used in different applications, you still have the possibility of getting the VIs cross linked.
Don’t rename a sub VI from outside of LabVIEW. If you want to rename, open it from the block diagram and do a “Save As”. This will relink everything correctly. If you change the name outside of LabVIEW, it has no way of knowing what you did and can’t track it.
Also realize that LabVIEW will only load a sub VI with an exact name match (not counting letter case). It won’t load something just because it’s close.
I’ve always thought they should have the search dialog ask you if you want to browse for the missing subVI or have LabVIEW search for. At least that way you would always have a chance to browse yourself.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

How can I install (download) a Labview FPGA code onto Altera FPGA chip using Labview FPGA module?

Hi there
Guys i'm a very new labview user (PhD student), my project is about ( design and implementation of a high speed-yet sophisticated system using Labview environment then install this project's code (using Labview FPGA module) onto Altera-made FPGA chip).
so kindly, can any body help me in this?...is there any way to connect labview with Altera FPGA?...please anything would be said 'd be of great benifits
thanks a lot in advance.

as previously mentioned, labview fpga only supports national instruments targets utilizing xilinx fpgas. the hdl generated by labview fpga is encrypted and cannot be used to synthesize a design outside the labview fpga design flow.
however, if you must use labview for your project, it might be possible for you to design the system in labview and use one of the labview embedded modules ( http://www.ni.com/embedded )to generate c code which you can then port to systemc and compile for the altera fpga. i'm not saying it will be easy, but it should be possible.

Problems in using Labview DLL with TestStand!

Hi,
I tried to put the VI's to create a TCP/IP Connection, read/write Data to it and close it inside a LabVIEW DLL and use these functions with TestStand.
The problem is to get access to the ConnectionID generated as TCP Network Refnum in LabVIEW.
I don't know how to specify the prototype entry for this Refnum in LabVIEW and how to read it with TestStand.
Another try to pass an ActiveXReference of SequenceContext and use the SetValIDispatch method to set a local variable (Type: ActiveXReference) to the returned ConnectionID of the TCPOpen.VI wasn't successful too.
It seems to me that the connectionID isn't a normal ActiveXReference.
Regards,
Sunny

Hi Sunny -
You should treat this parameter as a pointer to an int when calling the DLL from TestStand (or any language like C or C++). Note that you can't do anything with the value outside of LabVIEW since it only has meaning inside of LabVIEW. You can only pass it around for use in other VIs you call from TestStand.
Hope this helps....
Kyle G.
National Instruments
Kyle Gupton
LabVIEW R&D
National Instruments

Memory Management in LabView / DLL

Hi all,
I have a problem concerning the memory management of LabView. If my data is bigger than 1 GB, LabView crashes with an error message "Out of Memory" (As LabView passes Data only by value and not by reference, 1 GB can be easily achieved). My idee is to divide the data structure into smaller structures and stream them from Hard Disk as they are needed. To do so, i have to get access to a DLL which reads this data from disk. As a hard disk is very slow in comparison to RAM, the LabView program gets very slow.
Another approach was to allocate memory in the DLL and pass the pointer back to LabView...like creating a Ramdisk and reading the data from this disk. But memory is allocated in the context of Labview...so LabView crashes because the memory was corrupted by C++. Allocating memory with LabView-h-Files included doesnt help because memory is still allocated in the LabView context. So does anybody know if it's possible to allocate memory in a C++-DLL outside the LabView context, so that i can read my Data with a DLL by passing the pointer to this DLL by LabView? It should work the following way:
-Start LabView program--> allocate an amount of memory for the data, get pointer back to labview
-Work with the program and the data. If some data is needed, a DLL reads from the memory space the pointer is pointing at
-Stop LabView program-->Memory is freed
Remember: The data structure should be used like a global variable in a DLL or like a ramdisk!
Hope you can understand my problem
Thanks in advance
Christian
THINK G!! ;-)
Using LabView 2010 and 2011 on Mac and Win
Programming in Microsoft Visual C++ (Win), XCode (Mac)

If you have multiple subvis grabbing 200MB each you might try using the "Request Deallocation" function so that once a vi is done processing it releases the memory.
LabVIEW Help: "When a top-level VI calls a subVI, LabVIEW allocates a data space
of memory in which that subVI runs. When the subVI finishes running, LabVIEW
usually does not deallocate the data space until the top-level VI finishes
running or until the entire application stops, which can result in out-of-memory
conditions and degradation of performance. Use this function to deallocate the
data space immediately after the VI completes execution."
Programming >> Application Control >> Memory Control >> Request Deallocation
I think it first appeared in LabVIEW 7.1.
Message Edited by Troy K on 07-14-2008 09:36 AM
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

Labview executable installer cannot find windows favorites

When attempting to install an LabVIEW executable, using the Installer created with LabVIEW, before copying any files or making any changes to the local PC, the setup.exe queries for the location ‘My Favorites’ from the registry (HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\Favorites). If this has been moved to a mapped network drive, the setup will error saying that it is unable to access this location. Using Sysinternals Process Monitor, the setup.exe process does not try accessing this location.
Thanks in advance for any help
Inigo Rotzer

mikeporter wrote:
But why have favorites mapped like that in the first place?
Possible reasons:
1) Internal IT procedures
2) floating user account setups across the entire network
It's not uncommon to do these things but I have found to many problems with this also outside of LabVIEW to find it a practical solution.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Where can I find an example of a vi which reads a xml file using the Labview schema (LVXMLSchema.xsd)?

Where can I find an example of a vi which reads a xml file using the Labview schema (LVXMLSchema.xsd)?
�Unflatten From XML� is of little use in parsing because it requires the data type. So it seems that the user has to parse each data value, and then �Unflatten From XML� can help a little.
I would like to see NI provide a VI for parsing it�s own schema.

LabVIEW's XML functions are another way of saving data from controls and indicators that is in a more standardized format. If you look at the Unflatten From XML shipping example, it shows taking the data that you would normally send to a Digital Wveform Graph and converting it to XML instead. This data is then unflattend from XML and wired to the graph. Since you know what you wrote to the file, this is an easy thing to do. If what you are looking for is a way to look at any data in any LabVIEW XML file, then you are right, there is not a VI for that. However, I do not believe that that was the intention of the XML functions in the first place.
By wiriting data in XML, this allows other applications outside of LabVIEW to parse and recognize the dat
a. In LabVIEW, you would already know the types and can place a generic item of that type. The issue of knowing the type is that you need to know the type of the wire that comes out of the Unflatten function so that the VI will compile correctly. You could always choose a variant value to unflatten and then do some parsing to take the variant a part. Maybe this will help you out.
See this example for using the Microsoft parser for XML. (http://venus.ni.com/stage/we/niepd_web_display.DISPLAY_EPD4?p_guid=B123AE0CB9FE111EE034080020E74861&p_node=DZ52050&p_submitted=N&p_rank=&p_answer=)
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

LR5 Batch rename all photos to CAPTURE DATE+CAPTURE TIME+ORIGINAL FILENAME

Hello there,
Does anyone know of a way to get LR5 to batch rename all it’s photos to CAPTURE DATE+CAPTURE TIME+ORIGINAL FILENAME?
I know the data is in there somewhere but my DATE+ORIGINAL FILENAME import rename preset has named all our photos with the date photos were imported not created (eeek!)
Thanks in advance for any input,
Alex

alanterra wrote:
If you are using Macintosh, you could also try purchasing A Better Finder Rename 9—I love it, and you can create droplets for all your file-renaming chores.
Beware: such app is best used *before* importing.
If you rename (outside Lightroom) after importing, your files will go missing and you'll have to re-link (or god forbid: re-import). Maybe that will be OK with you, and maybe it won't..
Also, such app has no idea what the original filename was, so in this case it would not do what the OP wants.
Rob

Mercury's QTP and Labview

Hi,
I am trying to use Mercury's QTP to automatically test my application.
I am using an application over Labview 8.0, Using Windows XP pro.
The problem is, QTP does not recognizes any object in a window, besides the window itself.
I tried using SPY++ - result is the same. the SPY only recognizes the window.
Is there an API, maybe in a DLL form which I can hook up to and use it to connect to my objects from outside of Labview?

LabVIEW controls/indicators are not 'windows' objects as you have found out. The only way I know of to set/read LabVIEW objects is to use VI Server. If your test tool supports making ActiveX calls, then you can open a reference to the VI and use the Set Control Value/Get Control Value methods.

LabVIEW Connection to Ethernet IP I/O

Does anyone have information on how to connect LabView to an Ethernet IP I/O?

Unfortunately National Instruments does not have any hardware that natively communicates using the EtherNet IP protocol. You can easily implement applications in LabVIEW that use simple TCP/IP or UPD communication, but I do not know enough about the EtherNet IP protocol specification to know if these standard protocols will work. As you mentioned, LabVIEW can interface with an OPC server. If you have any hardware which uses this protocol that can access the OPC server tags, then this would be your best option.
How is this generally done even outside of LabVIEW? Namely, if I have just a PC without a PLC attached, how can I communicate using this protocol from another software interface? If there are PCI or USB devices available that can use this protocol, then you may be able to utilize them from LabVIEW. I hope this information is useful for you. Please post back if we can provide any additional assistance. Thanks,
Mike D.
National Instruments
Applications Engineer

Rename outside of labview

Similar Messages

Maybe you are looking for