Labview Error 1502
I would be nice if NI could do the build in a temp directory (as close to the root as possible) to avoid this, then copy it back to the dist The only thing the error says is to make sure the VI isn't broken and that it runs. Was the user's destination path for his built very long? Upon attempting to compile the executable, I was hit with the 1502 error with a particular VI. http://distributedsimulation.com/labview-error/labview-error-10.html
Open the VI in LabVIEW and fix the errors. I built an executable in another project that uses similar DAQ calls. The only thing the error says is to make sure the VI isn't broken and that it runs. If this is the cause, a few ways to avoid this error include removing the case structure, changing the constant to a control, or placing a diagram disable structure around the
This error is commonly caused by building an application from a VI that has code which will never execute; for example, having a constant wired to the selector terminal of a Hier war immer ein Problem in der Vorschau. Riconquistiamola 2008-02-21 14:40:11 UTC PermalinkRaw Message Jeff,Thank you for your post.
Have you been able to build an exe from this source code earlier or is it the first time you try to build? 1 person likes this Share this post Link KameralinaAsk NI (ni.com/ask)Search The KnowledgeBaseNI Developer ZoneMeasure It. Oops, I never realized that native English speaker never got that "pb" abbreviation. Register a new account Sign in Already have an account?
What is the make up of your top-level VI? Experimentation showed that the issue was not related to file or folder permissions, nor file or folder path length. George Share this post Link to post Share on other sites Antoine Chalons 60 The 500 club Members 60 640 posts Location:Geneva Area Version:LabVIEW 2016 Since:1999 Posted February 24, 2010 https://lavag.org/topic/18763-error-code-1502-when-building-application/ I've recently been building and resolving these errors (I always get it with the package manager). Orphaned VIs or those in a conditional disable are usually the culprits.
It would *supposedly* build OK (no errors were generated, at least) when the "enable debug" setting was checked under the Advanced tab in the build options, but after uploading to the Register a new account Sign in Already have an account? Sign In Now Sign in to follow this Followers 0 Go To Topic Listing Application Builder, Installers and code distribution All Activity Home Software & Hardware Discussions LabVIEW (By Category) Application If the VI is not listed in the Project Files section, then select Dependencies.
Clearing the compile cache and rebooting the PC didn't help either. navigate to these guys I don't think that this is the case (but I will check to be sure). I've waved the dead chicken and NI R&D has been looking at what's going on. I would LOVE to be able to isolate this issue so I could submit it to get it fixed.
I have complained before about Error 6 but am still of the opinion that it is better than having files outside of the build. his comment is here Well... "Development Environment is required to fix error" and "Dynamically launched VI cannot run because it is broken" (or whatever) are cases where LabVIEW is not descriptive enough in my book. Angehängte Datei(en) Date.vi (Größe: 8,65 KB / Downloads: 76) 23.09.2013, 07:42 Beitrag #6 Y-P ☻ᴥᴥᴥ☻ᴥᴥᴥ☻ Beiträge: 12.654 Registriert seit: Feb 2006 Developer Suite Core -> LabVIEW 2015 Prof. 2006 EN 71083 I trimmed my code back to a splash screen before the issue went away.
Is the code simple enough to be sent to support for evaluation? No to the JKI RCF and I don't really understand the second part of the question. Or sign in with one of these services Sign in with Facebook Sign in with Twitter Sign in with LinkedIn Sign Up All Content All Content This Topic This Forum Advanced this contact form It's easy!
Share this post Link to post Share on other sites Neil Pate 149 Extremely Active Members 149 414 posts Version:LabVIEW 2013 Since:2004 Posted January 24, 2015 Sometimes this error message One project I fixed by performing copy/paste into a new project that is (at least to me) identical in every way (file names and all). NI tech support is still der AB bleibt eine mein wöchentlicher (eigenwilliger) Beitrag zur Innovation http://innovation1.wordpress.com/ 23.09.2013, 07:35 Beitrag #5 sccompu LVF-Gelegenheitsschreiber Beiträge: 104 Registriert seit: Feb 2005 2014 2000 DE 89293 Deutschland RE: Error 1502
Please Contact NI for all product and support inquiries.
When these VIs execute they are in specific LabVIEW instance(or context), not the same instance were your project's VIs are. George Share this post Link to post Share on other sites Antoine Chalons 60 The 500 club Members 60 640 posts Location:Geneva Area Version:LabVIEW 2016 Since:1999 Posted February 24, 2010 One of the work around that has worked for me in the past (when dealing with this issue ), was to isolate the lvclass with problems in a separate virtual folder Das war als Neuerung ja gar nicht vom Marketing angekündigt – das ist ja wie Weihnachten …..
Unfortunately, I've tried all of the settings referenced without success. Like others had reported, enabling debugging or disabling "Remove unused members of project libaries" in the build specification allowed the file to compile correctly. I figured this was some problem I appreciate the links. http://distributedsimulation.com/labview-error/labview-error.html The project is quite big (700 VIs not counting vi.lib and OpenG), so finding the error was a pain since building Exe takes 10 mn.
Gruß, Marko 22.08.2013, 12:59 Beitrag #3 GerdW ______________ Beiträge: 13.988 Registriert seit: May 2009 09SP1, 11SP1, 14SP1, (16) 1995 DE_EN 10××× Deutschland RE: Error 1502 in LV 2013 Hallo Gottfried, Zitat:Mit Das soll die Arbeit von 40x12 Mannmonaten sein? My customer tried to isolated it but he was not very successful. In LV2012 wurde y oder Y akzeptiert. -------------------------------------------------------------------------- Bitte stellt mir keine Fragen über PM, dafür ist das Forum da - andere haben vielleicht auch Interesse an der Antwort !! --------------------------------------------------------------------------
Ich starte das Build und ziehe mich in die Stille zurück.
© Copyright 2017 distributedsimulation.com. All rights reserved.