Will Labview 8.2 EXE (developed in windowsXP) run in WinCE?

Hi,
I have developed a labview8.2 EXE and installer in windows Xp. My client want to run this EXE in WinCE.
Is it possible? If so what all toolkit should i get to make it run.
Basically my application uses NI Imaq and Visa for communication.
Thanks,
Vignesh

http://www.ni.com/white-paper/4577/en
Maybe this'll help.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Similar Messages

Will LabVIEW 5.1 play ok with WindowsXP?

I have LabVIEW 5.1 running on a Windows98 Second Edition laptop. Things work ok. If I upgrade the laptop from Win98se to Windows XP Professional, will LabVIEW 5.1 still work on the WinXP operating system?

It's worked fine on all of our XP boxes and win 2k as well. The older NI-DAQs, however, do not, so you can't use the old ISA legacy boards (not an issue if you're using a laptop). You'll likely have a harder time getting laptop specific drivers than any labview problems. Also, there can be complications regarding file privaledges and labview, such as a limited user trying to run an admin created file, which you can search for solutions for on the discussion forum or ni.com.
2006 Ultimate LabVIEW G-eek.

Will Labview VIs developed on a MacIntosh run on a Windows PC? How about visa versa?

Will Labview VIs developed on a MacIntosh run on a Windows PC? How about visa versa?
Thanks,
Dennis U

As long as you don't use platform specific tools (such as IMAQ vision, ActiveX...), or advanced DAQmx functions, LabVIEW portability between platforms is excellent.
On MacIntosh, LabVIEW works fine with virtual PC, but is very slow (5-10 times...). Try it and see if it suits you needs.
Message Edité par chilly charly le 01-09-2006 09:19 AM
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...

My project will only build an EXE in 8.5 but not 8.6, 2009, 2010, or 2011

Hi there.
I have come across bug in the LabVIEW programming enviroment.
I have a project that consists of about 600 VI's... ie very large.
The project compiles and runs perfectly fine and I can create an EXE in Windows 7 or Windows XP using LabVIEW 8.5 that works perfectly fine.
I can then take take this project and import it into 8.6, 2009 , 2010, or 2011 (after a very long time manually opening most of the vis and saving them - as the automatic method causes it to crash) - but once imported and updated the project runs fine in each of these newer versions of labVIEW.
The problem arises when I try to compile the project into an EXE...(using any labVIEW 8.6 or higher)
the first error (or feature? who knows) is that instead of creating an EXE with the project name it instead creates a FOLDER witht the project name and proceeds to copy all the vis into this folder,... - i assume it must be part of the newer compile features and that after 5-10 mins it might delete those when it finally creates a EXE... but instead at the end it gives me a compile errror message saying it cannot save a Vi with a bad or missing block diagram.. (but the vi in question is fine when I open it, and it runs fine...no missing diagram etc)..
Normally in 8.5 I get the *.EXE and an *.alias file, and a *.ini and a folder called data with some dlls in it...
but in any later labview version the EXE fails to compile and I get random errors...
The 1502 error is the the most common..
but I get others too, haven't saved them all -
but error 6 has occured a few times...
Errors Codes
===============
Possible Reasons
================
An error occurred while saving the following file:
C:\[Calibre Backup]\02-OPC\2012-03-21- 8.6 US-58-OPC-F\Ecoustic Grader sub-vis\Ecoustic Grader grade board.vi
Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>
Details
=======
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1502 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Cannot save a bad VI without its block diagram.
============================================
Attachments:
details.png ‏22 KB

Hi everyone, thanks for the help, but its getting rediculous for me....
I've done EVERYTHING that NI engineers on the phone and others have said..
in every permutation and combination as well...
I'm pretty sure the problem lies with labview not my code...
I've recoded the "problem" vi code from scratch... it runs fine in development mode..there are no broken arrows anywhere, and no missing block diagrams.
So as far as labview is concerned there shouldn't be a problem....
There must be a fundamental change from LabVIEW 8.5 to the other versions on the way the project gets built because this code works perfect in 8.5, but results in an error in later versions ONLY when Building - NOT WHEN RUNNING in DEVELOPMENT MODE....
Also there cannot possibly be a "conversion" error as some have suggested from earlier LabVIEW versions because I hand coded the "problem" vi from scratch in labview 2010 sp1 in case there was some sort of corruption with the vi the error code mentions.
There are no unused parts of the block diagram or code that does nothing as people have suggested..
(BTW the exact same issue happens in 8.6.1, 2009, and 2011 regardless. I just perfer to work in 2010 because its the last version of Labview that the same version of DAQmx will also work with 8.5)
When I go to make an exe of the project it again complains of the same error.
except this time it says the "grade board v2.vi" is the problem - the one that I rebuilt in LabVIEW 2010sp1
(BTW I do get this same error code 19 times out of 20)
Is there someone that knows exactly what this error refers to?
is there some way that the build process has changed from 8.5?
When I enable debug mode, this doesn't help as the final exe has a broken arrow
Attachments:
grade board v2 error.gif ‏16 KB

Will LabVIEW 5.1.1 run on Windows XP?

Will LabVIEW version 5.1.1 run on the Windows XP operating system?

We have recently installed it on WinXP, don't have a real feel for any possible issues, but the only noticeable issues was a little error message box "Wrong OS", which goes away when clicked. Good luck.
Putnam Monroe
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Loading new labview exe files from a running vi

Hi! Me again
I've been thinking about another way to reset my running application (some data doesn't get reset due to it being in a case structure...(see http://forums.ni.com/ni/board/message?board.id=170&message.id=145525&requireLogin=False for details ).
What I would like to do is to be able to open a simple menu labview exe file, while closing the main file. This would enable the user to quit labview at the click of a button, or reload the main exe, freshened up , and then the menu closes. I can get vi's to open and close but an exe file would be supurb, as it can be used from the start, without needing a run button.
I've been fiddling with invoke method : open fp and loading a vi rather than an exe file. I'm sure it can be done. Bear in mind I'm a chemist, not a programmer, so some terminology may be lost on me, but examples are not

Hi Fios,
Why don't you just use the system exec.vi, found at All Functions >> communications >> system exec.vi
then you just put the full path to the executable in "command line" and set "Wait until completion?" to False
This will open your LV exe and then you can use VI server as you described in your post.
Regards
JamesC
NIUK

Using sound VIs in labview 7.0 professional development suite

hello all
i hav a built a VI that aquires a thermocouple signal through my daq card....i intend to use sound VIs whenever my temp.exceeds set point..in short sound should b generated whenever temp.exceeds certain limit...... i hav used a "Beep" VI in my code....but no beep occured even if my temp.crossed set point.....is there any other platform required for using sound VIs??....i work on labview 7.0 professional development suite.
best regards
Solved!
Go to Solution.

hello
after i posted this msg i heard a beep sound on my pc speakers by placing only beep vi on block dig...and also with my code running properly.( that when my set point exceeded beep started ringing)......but after that i tried experimenting on many sound VIs.....n now when i place beep vi seperately on a block diagram it is not giving audio signal....same is happening with my code also....i cant here sound.....after successfully hearing beep sound on my pc speakers now wat suddenly happened with it??......would it b due to opening and closing many sound vis at a time??....like it happens in case of DAQ devices..that wen v use traditional daq devices n try using DAQmx devices after that they don't run unless v reset our traditional daq drivers.....so is it possible in case of sound vis also?...atleast a separate beep vi should run giving sound on speakers if i assume my code is wrong...
best regards

Interacting with labview with my own developed scritpting language.

Hi all,
I am Divya.
My aim :
I need to develop a programing language to interact with Labview such that the script should call labview front panel, execute the given task and front panel shold give back the result to the script.
I want to achieve this by using my own developed programing language (Valid reasons are there why not to use already exixting scripts which I dont want to discuss here as it is not relevant).
My idea :
As developing a new scripting language is a big task I am planning to start with Python scripting. I am trying to interact with labview using python script for now.
My problem :
As I am fresher to this field I dont know the possible ways to interact with Labview using python scripting. (Except using Labpython). If there is any way to achieve this please guide me on this.
Thanks in advance

Hi Dennis_Knutson
I am doing the same as the original question I have asked. As I have mentioned in my question I am starting off with a small addition (or any basic mathematical operation) function using Python script.
And yes the basic idea is to call Labview from script not the vice versa. To achieve this I need to pass the parameters from the python script to Labview and output from Labview to Python. For this purpose I am developing a small VI which vil take Python commands and carry on furthur operations.
I can explain with an example.
I have a command in python as sum=x+y. I want to take this command and send 'x' to a numeric control, 'y' to another numeric control and 'sum' to a numeric indicator and at the same time back to script. In between numeric controls 'x' and 'y' I need to carry out '+' operation. Say if the command is sum=x-y I need to carry out '-' operation(Where identifying '+' or '-' or any other operation is the job of labview).
I have developed a VI which can take the command from python and give it to Labview as a string. I need to know how to bifurcate that string to numeric controls, operands etc.

When will LabVIEW Drop Support for the NXT?

We currently use LabVIEW to program LEGO NXT kits in our engineering courses. However, LEGO is phasing out the NXT within the next year or two. Does anyone know the LabVIEW/NXT life cycle plan, i.e., when will LabVIEW no longer support the NXT platform?

Hi Joel777,
NI doesn't currently have a definitive roadmap for future NXT support in LabVIEW, but I recommend you check out the community page for updated modules. I would also recommend adding any feedback you have regarding future releases to this page in the comments section and periodically checking this page for support updates.
Rick C.

Will LabVIEW run in Windows Azure ?

Will LabVIEW run in Windows Azure? If not, why not?

Hi, I'm on the NI cloud team, and thought I'd chime in here even though the thread's old. We've been doing work with both the Amazon and Azure clouds.
We have LabVIEW working on Amazon just fine, in fact the LabVIEW FPGA Compile Cloud that's in beta right now is hosted on Amazon EC2.
We've been working with Microsoft Azure as well. I haven't yet tried to deploy LabVIEW on it, it should be possible to try as of the Azure 1.3 release by using a startup task although those may have an eventual timeout (LV installs take a while). Azure role instances are not meant to be long running and the disk on them is completely ephemeral. Probably using a VM role would be better. This isn't guaranteed to work because various low level drive stuff may run afoul of the limitations (Azure isn't *quite* stock Win2008R2, it does have limitations). The wrinkle will probably be licensing.We had to bypass our own usual licensing scheme to work on the dynamic cloud for Amazon.
This is a good candidate for the idea exchange, perhaps I'll add on there too.

Which frame works will support for blackberry application developement.

Hi
Which frame works will support for blackberry application developement?
Thanks
Achyut

hello,
I think you'll have much more answers if you post in one of the three discussion boards "Blackberry Development" :
http://supportforums.blackberry.com/rim?category.id=BlackBerryDevelopment
Anyways, RIM has a website for people who want to start developing, it's here :
http://na.blackberry.com/eng/developers/started/
The search box on top-right of this page is your true friend, and the public Knowledge Base too:

Will LabVIEW 8.0 work with Windows 7?

Will LabVIEW 8.0 work with Windows 7?
Thanks in advance.

According to this kb, LV2009 is the first version to be supported in Windows 7. We have had problems getting LabVIEW 8.6 to just install in Windows 7 machines. You might be able to get it to work, but I would recommend upgrading your version of LabVIEW if you really need to use Windows 7.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Memory Footprint for LabVIEW 7.1 Full Development System

Hello,
I would like to know the memory footprint for LabVIEW 7.1 Full Development System.Both during the installtion and for developing applications later.
Can someone help.Thank you.
Solved!
Go to Solution.

There isn't a single answer for that, as this varies considerably.
As far as disk space goes, if memory serves, the basic 7.x takes up a few hundred MB, but that could inflate considerably depending on which modules and drivers you add to it.
For RAM, I believe 7.0 used to take up ~20-50 MB immediately after being loaded, but that number would then also change a lot over time depending on what you do. Loading, editing and running code all regularly change the amount of RAM used.
Why are you asking? Also, are you aware that 7.1 is relatively old by now (came out 7 years ago)?
Try to take over the world!

Real Time Module, upgrading Labview 6.02 Base Development System?

Hi,
I have Labview 6.02 Base Development System but I need the Real Time module.
Would it be possible to get it upgrading the Labview 6.02? Is the full development systemm needed?
Which could be the cheapest way to get Real Time module?
Thanks.

You can upgrade to the latest version of LabVIEW Real-Time version 7.1 by upgrading both LabVIEW and LabVIEW Real-Time. You can all about the new features of LabVIEW Real-Time at the following link. For more information, please contact us at .
Regards,
Kristi H
National Instruments
>

My catalog pictures render fine in the Library module but will not render in the Develop module. I get a blue box with a white X across it in the window where the picture should render. Any ideas on how to resolve this?

My catalog pictures render fine in the Library module but will not render in the Develop module. I get a blue box with a white X across it in the window where the picture should render. Any ideas on how to resolve this?

Developer Module only shows blue square with a white cross, images are displayed in the library ok but not im developer Module

Will Labview 8.2 EXE (developed in windowsXP) run in WinCE?

Similar Messages

Maybe you are looking for