Multi-languages labview application

Hi,
Is it possible with labview to do a multi-languages application?
I want the user to be able to select language in the execution menu, then,
it will translate all label with languages information from a configuration
file.
I know haw to use configuration file, but i don't know how to change all
label easily.
Can anyone help me?
Regards,
Jean-Michel.

Hi,
"jm" wrote in message
news:3e2e75cc$0$226$[email protected]..
> Hi,
>
> Is it possible with labview to do a multi-languages application?
> I want the user to be able to select language in the execution menu, then,
> it will translate all label with languages information from a
configuration
> file.
>
> I know haw to use configuration file, but i don't know how to change all
> label easily.
The easiest way is to make a recursive vi. This vi would read a
configuration key, e.g. viname.tabname.clustername.controlname= "some text".
The recursive vi must look for the viname. Then it should get all objects,
and find a refernce to the tabname. Then it should find all names (on the
tab) again, and find the clustername. Then it should find all name
s (in the
cluster) and find the control name.
In pseudo code:
for all keys in the section of the selected language:
ref= vi ref of the first name
while there are names in the key
get all controls that are in ref
find the ref with the proper name
endwhile
set the name of the reference to the name in the key
endfor
Regards,
Wiebe.
> Can anyone help me?
>
> Regards,
> Jean-Michel.
>
>

Similar Messages

Peoplesoft Multi Lang Installation

Hi All,
I have installed PSFT 9.1 HCM with 8.53 PSFT tools in windows 2008 R2 server. Database version is 11gR2 (11.2.0.3). I have created database in AL32UTF8. Installed peopletools,application and peoplesoft database in Non-Unicode platform. Now the requirement is need to install Multi Lang. Can I install ML media pack on existing application? or Do i need to convert the peoplesoft system to Uncode and then install?. Please let me know.
Thanks,
Mani

Have a look at this doc
Document 618765.1 E-UPG/INST: PT8.4x, PT8.5x: Adding Translations (ML) to Existing English-only PeopleSoft Database
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=618765.1

How can i use multi threading in labview?

i want to run a Digital storage oscilloscope and an energ ratio meter simultaneously using labview. i am using GPIB interfacing and windows XP. how can i do this using multi threading. Bot the instruments shd run and give data at the same time.

You can't do this - at least not with a single GPIB board. It has nothing to do with threading or LabVIEW. There can only be one talker at a time over the bus. Depending on the instruments, you could probably set them up to take measurements simultaneously but you have to sequentially poll them to get the data.

"System error KERNEL.446571: 1528: Internal error detected by SMP multi-tasker" in LabVIEW RT 8.5

When I try to run my startup executable on LabVIEW RT 8.5 I get the message "System error KERNEL.446571: 1528: Internal error detected by SMP multi-tasker". What does this mean? How do I get around it? Has anyone else seen something simliar?
Robert C. Mortensen
Certified LabVIEW Architect
Certified LabVIEW Embedded Systems Developer
Endigit

Just crashed again with the same error. This time it was accompanied by a support.cpp error line 1112. The data in the error log file (rtlog.txt attached) doesn't seem to correlate with the crashes I'm seeing. I think a lot of the crashes aren't getting logged at all. The latest development is crashes after it's been running a while (1528 & 1510 happen on startup). The RT desktop simply reboots without showing or logging an error. Any way to track that down? Does this file mean anything more to you than me? I don't feel like I have enough material or info to create an SR.
Thanks,
Robert C. Mortensen
Certified LabVIEW Architect
Certified LabVIEW Embedded Systems Developer
Endigit
Attachments:
rtlog.txt ‏548 KB

How to distribute the serial core only with my exe and DLL application using the Labview application builder 8.21. I'm not interested having MAX and other components installed on the customer PC and in the program menu

Since Labview ver 8.0 and later, I am not very happy with the new way the project installer is managing the additional drivers such as Serial.
With LV 7.11 the serial components was included in the cab file and was installed on the target computer in a specific directory. The size of the distribution was pretty small and well suited for compact distribution.
My LV application use only the serial object and with LV 8.21, if I include the serial 3.2 component, I get an enormus file including max, visa ... and a lot of fucky component I do not need.
To distribute my application, I just need, the runtime engine and the serial driver as it was with the version 7.XX
Looking for clever advises from you gentlemen!

Thanks Dennis for you input
My problem is in fact very simple. 3 years ago, I developped a software suite for X ray generator; My company is selling such generator all over the world and our control panel software and DLL (for OEM integrator) is based on Labview professionnal development plateform.
To drive our generator, we just need to transfer ascii data using the strandard RS232 port still present on most of equipments used in the industrial area.
Until LV version 7.11, there was no problem to include serial component in my distribution with a very reasonable size and transparency for the end user.
with LV 8.xx (preparing a new release), I'm very disapointed to see, my distribution is increased of about for 10 Mo to 180 Mo just because I increase the serial component.
May I mix a previous version of the serial component with LV 8.21?
Should I change my source to Visa instruction only and merge visa runtime only to my distribution?
is there any simple serial example based on visa and distributed with th application builder?
I will appreciate your help in order to optimize my distribution
Pascal

LabVIEW Application throws Error in Run VI Invoke node

Hi All,
We are facing an issue with an application developed from LabVIEW 2010SP1.
Application Description:
In our application, there is a top level VI which tries to run VIs dynamically[using Run VI invoke node] from a particular folder. This folder is like a plugin - not part of Exe. This implies when the top level VI is launched, the plugin VIs under particular folder will not be in memory. When we try to run a VI dynamically from the top level VI, the VI execution works perfectly in LabVIEW development mode.
Problem Faced:
When we created an EXE, it worked well in my PC [LabVIEW is installed]. We created an installer and tested in few other PCs.
[Non LabVIEW PCs – Win XP and 7]. In few PCs it throws the following error, when the plugin VI is run dynamically.
Error 1003 occurred at Invoke Node
Possible reason(s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.
Method Name: Run VI
We tried the following possible ways to find the reason for the issue:
1. Installed LabVIEW - Issue got fixed.
2. Installed .net 2.0 without installing LabVIEW - Issue got fixed.
3. But in one of the Windows 7 [Non - LabVIEW PC] in which .net was already installed, we faced the same error.
Only after installing LabVIEW the error got fixed.
4. When .net 2.0 is uninstalled the EXE itself is broken.
We are not sure what is the Exact reason fo the issue. Anyone faced these kind of issues? Please share the solution. Thanks in advance.
Note:
1. The VIs which are dynamically called is a plugin and not a part of EXE.
2. These plugin VIs have no dependencies from vi library and is completely isolated.
3. We are not using any .net related objects in any of the VIs.
4. The plugin VIs use Call library function node in which a C DLL developed from Microsoft Visual Studio 2010 is used.
Thanks,
Meena
Solved!
Go to Solution.

Error 1003: This clearly indicates that the 'Dynamic VI' is broken and now you should check for the various reasons, why the 'Dynamic VI' is broken.
Also path of 'Dynamic VI' is not a problem.
One thing that you may try is:
-> First open just the 'Dynamic VI' in a new LabVIEW project and check for the 'Dependencies'.
-> Now if any of the item in 'Dependencies', other than what is listed in vi.lib (lets call it 'Dependency.VI'), is also a part of your 'Main Exe', then its a problem. Because when you will execute the 'Main Exe', say in a new computer other than your development computer, it will load all its dependencies including 'Dependency.VI' (and the path will be within the 'Main Exe', but when it will try to (dynamically) load the 'Dynamic VI', this VI will also try to load the same 'Dependency.VI' but from different path and that will cause a conflict. I had experienced this.
-> If thats the issue, you may want to rename (add suffix/prefix) to all dependencies of your 'Dynamic VI' which is common to the 'Main Exe'.
Hope this solves your issue.
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

How to totally close a running LabVIEW Application

Hello NG,
I have a little problem closing a running LabVIEW Application. For
example I run 2 Applications in parallel. I would like to totally close
one of them. If I use the "Exit LabVIEW" VI both Applications will be
shut down. If I only stop the Application, the not running Front Panel
is still available. How could I close an Application like a normal
Windows program?
Thanks a lot for your help.
Best regards,
Michael

If you build both applications into seperate executables, I believe Exit LabVIEW should only affect the one where it was run.
If these are 2 VIs running inside LV, you can wire F into FP.Open property of the top level VI. Once the FP of the top level VI closes, the entire hierarchy will be closed as well. This also works with the RTE.
To do this, you need to create a property node (Application Control palette), right click it and select the VI class and select the property.
The other option (basically the same thing) is to use the invoke node with the Close FP method.
Try to take over the world!

How to make a LabVIEW application into a screensaver?

How can I turn my Labview application into a screensaver. I read an old email from Jean-Pierre Drolet from 2001, where he writes that you only need to make a application of your .VI and then change the extension from .exe to .scr, rightclick and 'install'.
When I did that I got some error msg. in the 'display properties' 'screensaver' ... %1 requires %2 ... (cant see all). Does anyone know the answer how to make it correct?
(if you want a more difficult task.....)
To make it a complete screensaver the program should should act differently according to commandline switches:
/s : enter screen saver mode
/c : enter config mode
/p : enter preview mode
How to make it?
I would be happy if someone could ans
wer my first question(that easy part).By the way im running Laview 6.1 on a win 2000 comp.

Just made a simple VI with no menu or title bar, set the window size to always fill the screen and built it as application.scr. Installed it...everything OK. However if the RTE is located in the same directory as the application launching it returned an error saying the application could not find the neccesary resources...that might be what you see as well...(?).
On a machine with LV installed the RTE is already available so that is not a problem...Making it respond to commandline switches can be done either using the new commandline functionality of LV7 or using the commandline dll you can find here on the zone...it allows the application to capture and act on the commandlines when the application is launched.
Now you may want to add code in your application t
hat reacts to mouse actions so that the application terminates when the user moves the mouse /clicks a key etc...like other screensavers do. Use an event structure to capture such events...
Here's a general description on how to create screensavers that also applies in this case (nothing new there..but just to show that the procedure you already have is as MS says...):
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b146907
MTO

Failure to build LabVIEW application on Linux using "Shared library"

In order to create a LabVIEW application on linux without an X display, I complied the LabVIEW VI using the Linux Shared Library. I did this by right clicking on Build Specification and selecting New >> Shared Library, and in the Advanced section, checking the box labeled Use embedded version of run-time engine. At the end of the build process, a message came up informing that the build was unsuccessful, with the following message:
"Error 127 occurred at System Exec: sh: gcc: command not found
The error code is undefined. No one has provided a description for this code, or you might have wired a number that is not an error code to the error code input."
I had no compling the LabVIEW VI in the normal fashion, so am confused about what the problem is.
Solved!
Go to Solution.

Hi Julian,
gcc is a C and C++ compiler on Linux. An easy way to check if it is installed is to open a terminal and type "gcc", if the command is recognized then the package is already installed and the problem must lie elsewhere. If this distrobution of Linux has a package manager included then it should be displayed in there as well. If not then it could point to it being not installed or some dependency is missing making it not accessible from the command line. Here is a link that should hopefully step you through installing gcc with Redhat: http://www.cyberciti.biz/faq/centos-linux-install-gcc-c-c-compiler/ .
Justin D
Applications Engineer
National Instruments
http://www.ni.com/support/

Stop labview application from MS VC got internal error: image.cpp line 11450

Hi:
I need to control a labview application (It's been compiled as exe file)from my MS VC program. I tried using PostMessage(hWnd, WM_CLOSE) from whithin my program as MSDN suggested method to stop an application
cleanly. However, when i put my program in debugging mode and run it step by step, the LV program generate an internal error "image.cpp linexxxx" after it reached that PostMessage() call. in run mode , the Labview app simply ignore the WM_CLOSE message sent from my program.
So is there any other ways to stop labview application from VC program?
Thank you!
ls

> So is there any other ways to stop labview application from VC
> program?
You can use ActiveX. Turn the server on for your built app, open a
connection from VC, and use the app or VI properties to get LV to exit.
Greg McKaskle

How can a LabVIEW application be run from the guest account in Windows 7?

I want to make some of my labVIEW applications (no DAQ or external hardware involved) available to temporary visitors in the lab. A natural choice would be the guest account of Windows 7, but if I try to run LabVIEW or any of my built LabVIEW applications, I get the following error dialog.
I am sure this can probably be fixed with a few permission settings. What is the easiest way to allow running these applications from the guest account?
LabVIEW Champion . Do more with less code and in less time .
Solved!
Go to Solution.
Attachments:
LabVIEWGuest.png ‏36 KB

Ah, I missed that article somehow. Thanks!
I actually already made a "labguest" account yesterday with normal user permissions and that works fine.
LabVIEW Champion . Do more with less code and in less time .

LabView application hangs up when scrolling the block diagram

Hi all.
I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
Regards,
Francisc
Hi all.
I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
Regards,
Francisco
Attachments:
Main (v3.1).vi ‏257 KB

It didn't hang up on my computer, but it did make me nauseous, luckily I keep a bucket by my desk.
You might have video card issues. Try this: open the VI, and hit Auto Cleanup, then save. Close LabVIEW, reopen. If that does not work, try to get to the far right side by going to the Front Panel, and double clicking something that will take you there. If you get there successfully, use the disable structure to disable ~ 1/8 or more of the diagram on that side. Save, reopen.
Richard

LabVIEW application fails to run properly at Windows startup

I have experienced problems with my Labview application after putting it in the Windows XP startup folder. The application runs perfectly if I start it manually but whenever I get Windows XP to start it after boot-up, I see various error messages. My application uses calls to the NIMotion library and it's these calls that are generating the error messages. I don't always get the same errors and the problem has occurred with two different programs on two different computers. I think it is something to do with NI services for the motion controller that load at startup and haven't yet been started before my application runs. I have configured Windows to login automatically and I have noticed thay my program executes quite early, sometimes even before the desktop icons appear.
I have seen that a number of other users have experienced similar problems. There was a recent post titled "Waiting for Windows Idle" in the LabWindoesCVI forum that is related. The only solution that I have come across is to wait at the very start of the program until the rest of the dependent services have loaded. I have added a 30 second wait to my programs and this appears to have largely solved the problem. This is no the best solution because it is not always guaranteed to work. I have had a situation recently where Windows was installing an automatic update and the bootup process was slower than normal. This caused my program to fall over again. I don't wan't to extend this time too much or the user will be waiting every time the machine is turned on.
Another solution would be to check for those specific errors that are generated and keep trying the function calls until they are successful. I have not tried to do this yet. It would probably be quite time consuming process to write the code to process the errors because I need to build an executable and reboot everytime I want to test. And again this method is not guaranteed to catch all errors. Surely there must be a better way. I have done some initial investigation into the Windows Service Manager but haven't got too far. I've discovered I'm not a Windows programmer and I don't know what all those NI services listed under "Administrative Tools" actually do. Surely there must be some better way or some tool out there that can check that Windows has finished loading?
David Reeves

Sorry dreeves, I don't have an answer for you. I would like to know the solution myself. I had similar problems recovering from a standby state.
DAQmx takes a while to get going for USB devices and the queue functions didn't recover properly at all. I just sat in a loop checking the status of my attached devices until they initialised properly then moved on from there.
It would be great if there was some way to check the status if the various LabVIEW modules that load on startup. Then, when all the ones you need are ready, continue with the rest of your application.
I would think checking LabVIEW for its status would be more reliable then asking Windows if it has finished starting up.
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

Invoke Labview application from Command line

hi,
I have a labview program which does some analysis on my Test data.
My application is that,i have a Test sequencer program(Different application) which collects data and stores it in .dat file.
After this i invoke exe of Labview Analysis program from Test sequencer & i enter the Test data filename as a command line argument.
My first step in analysis program is read command line argument(thru App.Args property) & get filename(the command line gives array output , index 0 will be Labview,index 1 will show filename)
This works absolutely fine.
I made a copy of this analysis prog to include some more functionalities and renamed it as different Labview program(prog structure is same) & trying to do the same abovesaid process.
But somehow im not able to get Command line arg(basically here filename) passed to labview.
The error im getting is that it's showing the path of my application (say if my application is in C)."C:\xxxx.dat is not a LABVIEW data file".
My question is:
Is there any settings changes to be done for Command line args property node when we make a copy from one prog to other prog.? Im not having clue why this should occur?
-Murali

Just to confirm I understand what you are asking... you copied the App.Args property from one vi to another, compiled the new vi to an exe, new exe doesn't receive the command line parameters.
Did you make sure the "Pass all command line arguments to application" check box (in the 'Advanced' category of the application builder) was checked for the new application?
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

Multi-Threading in Labview (not teststand)

I have heard that it is possible to write a Labview application using
more than one execution thread, but I don't understand what the help
files are saying.
Do I have to have a HyperThreading CPU to do this?
This was easy in CVI.
Can more than one thread make changes to the front panel controls or even display it's own panel?
Maybe someone has some pointers or simple examples of how to create a second thread.
(Please - no TestStand examples. Just 100% Labview)

You don't need hyperthreading. Parallelism is built into LV in several levels. First of all, you can simply have parallel code by having 2 pieces of unconnected code which will run "in parallel" (the scheduler will make sure they both get executed).
You can assign priorities and threads to VIs by going to File>>VI Properties>>Execution, but there is usually no need to deal with this because is LV will be fast enough without this (plus, you have to know what you're doing).
Like I said earlier, if you just want different pieces of code to execute in parallel, just make sure they are not connected. You can open as many VIs as you like like this and let them execute in parallel. You can have seperate loops updating controls on the same front panel. Basically, whatever you like. It's really very simple. If you want an example, simply create 2 while loops which do something, and you can see they do it the same time.
To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here and here are a couple you can start with. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf).
Try to take over the world!

Multi-lang​uages labview applicatio​n

Similar Messages

Maybe you are looking for

Multi-languages labview application