Running labview application on windowsCE or WindowsXPe

does anyone have experience of running labview application on windowsCE or windows xp embedded system? I would like to build an lv application which plays videos on a CE or XPe system. Any comments are welcome.
thanks,
joe

I use the PDA Module for LabVIEW to run programs on Windows CE and Windows Mobile. You have to use a PC for the development and building of the application, then either use ActiveSync or copy the .exe over to the CE device. There are some limitations in the code and the user interface, but most things work fine.
I haven't actually tried video yet on CE, perhaps that is something I can play with soon.
Good luck!
B-)

Similar Messages

  • Running LabVIEW applications on Windows Terminal Server

    I have built a client application in LabVIEW that one of our users want to run on a Windows 2000 Terminal Server...the question is; how does Windows Terminal Server handle the different sessions; does is launch multiple copies of the application and if so how about support files? In my case the client application has a configuration and a temp file in it's directory...if multiple users use the application on the terminal server; does it or can it be set up to make one copy of the app directory for each session? If not - is there a way / what is the best way to get separate configurations and temp files for each session?
    MTO

    You have a better chance to get a helpful reply if you ask in the Acrobat forum, or even at http://forums.adobe.com/community/licensing

  • How to totally close a running LabVIEW Applicatio​n

    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 run Labview apps in tablet with android os

    How to run Labview application in tablet with android operating system?
    Can we use Labview mobile module or we must use google play data dashboard for labVIEW? how to install it in PC?
    Solved!
    Go to Solution.

    If you had looked at data dashboard and some of the other links on Android, you would see that you cannot run a LabVIEW app on Android. Nor can you use a serial port. With Data Dashboard, you have a pc running LabVIEW and it publishes to network shared variables. Data Dashboard on the Android allows you to view those variables.

  • Can i run labview on Windows CE or embedded XP?

    If it is possible, what are the minimum specifications for the PC? And can anyone recommend a manufacturer?

    Basically, anything that will run on XP should run on XP Embedded. I am
    presently running LabVIEW applications on XP Embedded. Windows CE is a
    totally different operating system and will not presently run LabVIEW (NI
    should verify this but I'm fairly sure this is true). You'll have to ask NI
    when this will change but I think there will be CE support in the future.
    XP Embedded should run on any PC that XP will run on but if you stick with
    better known brands and components you'll have an easier time building your
    XP application. Your speed should be similar to regular XP but your hard
    drive space is usually a lot less because you strip out as much of the
    operating system as you want. I am running on bootable CDs without any hard
    drive.
    "stew j" l> wrote in message
    news:[email protected]..
    > If it is possible, what are the minimum specifications for the PC? And
    > can anyone recommend a manufacturer?

  • Can labview produce a .exe that will run on PocketPC or WindowsCE?

    Can labview applications be built into an executable program which will run on PocketPC or WindowsCE operating systems? If not, can source code be generated which can be compiled for these operating systems?

    You should be aware that the PDA module does not support many features which are available in the desktop version of LV. Try reading the documentation available on this site. If you want this, I suggest you wait for version 8, which appears to be much better in some areas.
    Try to take over the world!

  • How can I run two independant LabView applications from the same computer, without taking a performance hit?

    I have two identical, but independant test stations, both feeding data back to a Data Acquisition Computer running LabView 6.1. Everything is duplicated at the computer as well, with two E-series multifunction I/O cards (one for each test station) and two instances of the same LabView program for acquiring and analysing the data. The DAQ computer has a Celeron processor w/ 850Mhz clock and 512MB memory, and is running on Windows NT.
    I have noticed that when I run both the applications simultaneously, I take a substantial performance hit in terms of processing speed (as opposed to running just one program). Why does this happen and how can I prevent it? (In t
    his particular case, it may be possible to combine both the tests into one program since they are identical, but independant, simultaneous control of two different LabView programs is a concept I need to prove out).
    Thanks in advance for any tips, hints and spoon feedings (!)....

    Depending on your application, you may or may not be able to improve things.
    Firstly, each task requires CPU time, so a certain performance difference is guaranteed. Making sure you have a "wait until ms" in every while loop helps in all but the most CPU intensive programs.
    Secondly, if you are
    1) streaming data to disk
    2) Acquiring lots of data over the PCI bus
    3) Sending lots of data o ver the network
    you can have bottlenecks elsewhere than in your program (limited Disk, PCI or Network bandwidth).
    Avoid also displaying data which doesn`t need to be displayed. An array indicator which only shows one element still needs a lot of processing time if the array itself is large.... Best is to set the indicator invisible if this is the case.
    I think
    it would be best if you could give some more information about the amount of data being acquired, processed and sent. Then maybe it will be more obvious where you can optimise things. If you are running W2000, try activating the task manager while the program(s) are sunning to see where the bottleneck is.
    Shane
    Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)

  • 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

  • LabVIEW application run on Windows XP Embedded

    I'm doing a Embedded system based on Windows XP Embedded operating system.I want to make a LabVIEW applications which can run on it.I see a lot of paper that show the LabVIEW does not support Windows XP Embedded.I want to know whether the official has already solved this problem?Or someone has done the same thing successful?

    Who is the official? NI?  If it isn't supported, NI is unlikely to be trying to solve the issue as we are a bit beyond XP.  You'd need to find unsupported methods to hack it a bit.  I'm not sure you'll enjoy this process

  • How can we launch the labview screen beyond other screens while running two applications on a same time

    Hi all,
     I need to run two applications in my system at same time. one of the application is labview. it is running in backside. the dialog boxes which i created in labveiew need to display in fron of all applications.... what should i do to do that.....any suggestions...
    thanks in advance
    Regards,
    Ragu 

    The easiest thing to do (but can be bad) is to make the LabVIEW window modal.  This will make it the front most window at all times, until the program stops executing.  As you can imagine if you don't have a way to close the window then you will be forced to kill LabVIEW through the taskmanager.
    To make window modal go to VI Properties (by right clicking the VI's icon) go to Window Appearance, click Customize, then under Window Behavior select Modal.
    The other more complicated solution is to use Dll calls to bring the window to the front.
    Message Edited by Hooovahh on 07-02-2009 08:44 AM
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • Labview application very runs poorly on better PC hardware

    What could cause a Labview application to run extremely poorly when deployed to a new higher performance PC verus the 4 year old one at my desk?  I'm using an Intel Core Due 2 on my desktop (2 cores), whereas my application is being deployed to an Intel Xeon (4 cores).  I've tried running both the old LV8.6 version of the software and the newer LV2011 version, and both are crawling to the point the application cannot be used.  The GUI isn't updating at the 4x per second, the mouse pointer is extremely jumpy when moved around the screen, and tabs/menus take several seconds to a couple minutes to be responded by the application.  On my desktop PC, the application runs smooth using the same executable file.  Both have the same OS (32-bit XP SP3) and both are running the same anti-virus software.

    ExarK,
    - Can you supply additional information on what your application is doing?  
    - Do you have the source code available with the LabVIEW Development Environment?  It sounds like LabVIEW is either hogging your resources (insert Wait functions into any loops you are running to periodically free up your processor) or that there is a memory leak (make sure you are closing your references correctly).
    - Try building one of our shipping examples to run with your DAQ device (a simple analog input will do).  See if this runs slowly on the target PC as well.
    Andrew T.
    National Instruments

  • Running LabVIEW 2012 Application builder get message about missing LabVIEW 2013 media

    I am trying to make an installer using LV 2012 (Latest version for which I have a license-- Installed from Developer Suite 2013, latest disks I have.)\
    I am asking the installer to include Run Time Engine 2012 SP1 f5-- Only choice presented to me for a 2012 RTE
    When I Try to build an installer, I get a message asking for a LV 2013 media path, which I don't have...
    Any ideas on why this is happening or how to get around it?
    Solved!
    Go to Solution.

    Hi Peter:
    Sorry for the long delay getting back to you, I've been off on other projects for the past few.
    I have NImax 5.4.0f0 on my computer.  Other than that, I don't see any stand-alone DAQmx-- mostly I configure the DAS equipment programatically from within LabVIEW. 
    Attached is a screen shot of the NILM display.  You'll note that there's a LV2013 in addition to the LV2012 SP1.  Not sure why the 2013 shows up in the LM-- don't recall ever loading it, not even a demo version, and what I'm using is the 2012 SP1. 
    Since my last post, a few other peculiarities with the app builder-- last week I had a period where it would only run the application builder once to make an installer.  After that I'd get an error message of some sort (I neglected to make a note of the exact message-- If I see it again I'll make a note of it.)  In order to run the app builder a second time, I had to shut down the computer & reboot.-- it then let me run the app builder one more time, then reboot needed to run it a third time.
    I also had a peculiarity where when I ran the installer on the target machine, it would give a "no software will be installed" message.  I am pretty sure that this was unrelated to the other problems-- A simple user error, that I wasn't updating the revision number of the exe application, so when the installer went to install on the target it thought the version on the target was the same as the version that I wanted to install?  But I mention it in case it has some bearing on the problem.
    Client testing the application reports that it is ready to go, so I'll be attempting to build on final (for this release) clean installer version later today-- I'll let you know how that goes.
    Thanks for your attention, and again, appologies for the delay in responding to your questions.
    Best regards, Louis
    Attachments:
    NILM Screen Shot.png ‏90 KB

  • Stand alone labview application (.exe file) does not run properly

    Hi all,
    I am trying to make a stand alone labview application to run on another computer ( I have never done this before).
    I went through the tools->build application prompts and was able to build an exe file.
    the program is supposed to control a power meter and make power measurements then save them to a text file.
    When I run the exe file, on the same computer I compiled the exe file on, the program generates a text file to save data to but it can not communicate with the power meter.
    There are some sub-VIs and a dll file that are used to communicate with the power meter. Could it be that I am not telling labview to correctly
    include these files when I create an executable?
    What are some common problems that occur when generating stand alone applications that could be causing my issues?
    And does anyone know of any good tutorials on generating stand alone applications in labview other than the NI help files?
    Thanks for your help,
    Solved!
    Go to Solution.

    edCubed wrote:
    Hi Bill, thanks for your suggestions.
    I haven't tried to run this app on another computer yet. I'm just trying to run it on the computer it was developed on.
    The computer I developed it on has all the drivers/resources I need to control the power meter.
    Also, I don't know how to include the VISA runtime with my installer. could you explain how this is done?
    This is the first time IV tried to turn any labview programs into stand alone exe files so I don't anything about how to do it other than what I've seen in youtube videos and help files.
    If you know of any good tutorials that will help me figure this out I would appreciate it.
    Thanks,
    My fault - I didn't read that this was the same computer.  I know the very end of Core 3 studies shows how to build an executable and installer, but even that is very general.  I'm not sure if there exists a tutorial on how to do it.
    As for including the runtimes, when you build an installer, you have to include the runtimes that your executable will need.  It's fairly straightforward.
    Since it won't run on the machine that built it, I'll have to think about it a little bit...
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

  • Is it possible to take a labview application and compile it to run on an embedded processor?

    Hi
    I was wondering if anybody out there knows if it is possible to take a labVIEW application and compile it to run on an embedded processor (e.g. ARM7)?
    If so does anybody know what the required capability of the target processor is (i.e. RAM, ROM etc.) and what tools I need.
    Many thanks
    Ash

    Ash,
    There is also another option for processors like the ARM7.  You can load a PDA OS on it and use the LabVIEW PDA toolkit.  The LabVIEW PDA toolkit is MUCH easier to use and is quite a bit less expensive.  You will have the problem of getting the OS correctly configured, but in the long run, it may still be cheaper and easier.  I use it quite a bit with my Dell Axim X51v which has this processor and Windows Mobile 5.  There are still problems to work out, but not nearly what there are with LabVIEW Embedded.
    If you want to go the LabVIEW Embedded route and you need some help, let us know on this forum.  There are several of us that have experience and can help to guide you.
    Hope that this helps,
    Bob Young
    Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
    DISTek Integration, Inc. - NI Alliance Member
    mailto:[email protected]

  • Minimizing LabVIEW application to system tray or running it as a Windows process

    Hi guys,
    Is there a way I can minimize a LabVIEW application to the system tray on the right bottom corner of the screen ? My application will run all the time and all I want is a pop-up when errors or information/reports have to be displayed. I have searched exhaustively and now am posting this question. Please let me know if this can be done.
    also, Can a LabVIEW application run as a Windows process? Like it starts up automatically on booting the system?
    Thanks!
    V
    I may not be perfect, but I'm all I got!

    If you search for System Tray you'll find lots of people trying to do the same thing and a few places with example code to get it working.  But the best method I've seen is actually on the Lava forums.
    http://lavag.org/topic/14060-put-your-labview-in-the-tray-once-and-for-all/page__p__86042__hl__+syst...
    As for starting a application on startup.  Again I expect searching you'll find alot of people saying the easiest way is to create a shortcut to your application, then place the shortcut in the Startup folder in your start menu.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Maybe you are looking for